Predictika · Software subscription quotes

An AI sales agent's Visma Severa subscription quote, checked before it goes out

An AI sales agent prepares a monthly subscription quote for Visma Severa, a professional services automation product: a plan, a number of users and the features the customer needs. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the published plans and prices and returns a verdict, every reason, a line-item quote and the figures it computed.

Scope: Severa subscription quotes in euros, with the published per-user price of each plan and the features that start at each plan. See everything this validator covers

This validator models Severa subscription quotes built on the plans and prices the Severa pricing page publishes, not just the scenarios shown below.

  • Plans and prices — Basic (€25), Business (€39), Platinum (€49) and Enterprise (€69) per user per month, excluding VAT, multiplied by the number of users into a line-item quote and compared with the total the agent states.
  • Features by plan — the REST API, resourcing and work planning, travel expenses and the proposal tool start with Business; custom fields, automated invoicing, revenue recognition and multi-currency start with Platinum; single sign-on, the audit trail and the testing sandbox are Enterprise only. A quote whose plan lacks a feature the customer needs is blocked.
  • Size and currency — at least one user, euros only, and organizations over 500 users go to a person because Severa recommends contacting its sales team.

Any Severa subscription quote that touches these rules is in scope — not only the scenarios pictured here. Not covered: other currencies, VAT, other Visma products, storage allowances, discounts and contract terms, and the other features listed on the plans. Assumptions: one plan applies to all users on a quote (the page does not say whether plans can be mixed), and the monthly total is a list-price estimate.

The AI sales agentBuilds the subscription quote from the conversation and says it is ready.
Predictika validatorChecks every rule at once and returns the verdict, each finding, and the computed figures.

7 scenarios in 3 groups · each group runs from the agent’s first attempt to the outcome · click one to switch

What the agent proposes

The AI sales agent says

Illustrative agent statement. The validator receives the structured request below.

Proposing agent: AI sales agent (scripted)

Before sending, the agent must call Recorded run

Predictika validator


      
Waiting for the call.

Where rules-based CPQ gets it wrong

Click to expand

Our assessment of what a typical rules-based CPQ (product rules, price rules and validation rules, as in Salesforce CPQ) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.

What the validator caughtTypical rules-based CPQPredictika
Stated monthly totals that must equal what the list prices giveOnly with care
A stated figure is a free-entry field; a rule can compare it with a computed total, but the total depends on the plan chosen and the number of users and has to be kept in step with the price page.
The stated total travels with the quote and is compared with the computed total on every call.
Features that start at different plansOnly with care
A product rule per feature and plan. It works, but each feature is another rule, and a plan change means revisiting them all.
The features the customer needs are counted for each tier and checked against the plan quoted.
Needs from several tiers in one quoteOnly with workarounds
A quote can need a Business feature, a Platinum feature and an Enterprise feature at once, and rules often stop at the first mismatch.
Every tier is checked on every call and each shortfall is reported together.
Large organizations that must go to salesOnly with workarounds
A threshold on users that has to route the quote to approval without hiding any other error on the same quote.
The user count is checked with everything else, so an approval and a block can appear together.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the quote is saved or a step is completed, so a rep often fixes one error and meets the next.
All findings come back together, whatever order the choices arrived in.

What this validator catches: findings from its test cases

Click to expand

Every rule is checked on every call, in any order the choices arrive; one problem never hides another. Blocking findings stop the quote; approval findings need a person to sign off; everything else is computed.

1The quote needs 1 feature(s) that start with the Business plan, but the Basic plan is quoted.
2The quote needs 1 feature(s) that start with the Platinum plan, but a lower plan is quoted.
3The quote needs 1 feature(s) that are only in the Enterprise plan, but a lower plan is quoted.
4The quote has 0 users; at least 1 is needed.
5The quote has 501 users; Severa recommends that organizations over 500 contact its sales team, so a person should confirm the price.
6The quote states a monthly total of €30,000.00; the list prices give €39,200.00.
7The quote is in a currency other than euros; only the published euro list prices are modeled.

Scenarios and results

Click to expand

The recorded result of the validator for each scenario on this page: the request the AI agent sent, the verdict, and every finding, in the order they appear above.

1. Plan and feature tiers: Basic plan quoted for a team that needs Business features

The agent's request. Please quote a Severa subscription for 60 users on the Basic plan, for a team that needs the REST API, resourcing and work planning, travel expenses and the proposal tool. The quote states a monthly total of €1,500.00 excluding VAT. It is ready to send.

Verdict: Blocked.

  • Feature needs the Business plan or higher. The quote needs 4 feature(s) that start with the Business plan, but the Basic plan is quoted.

2. Plan and feature tiers: The agent resubmits after fixing the errors

The agent's request. Please quote a Severa subscription for 60 users on the Business plan, for a team that needs the REST API, resourcing and work planning, travel expenses and the proposal tool. The quote states a monthly total of €2,340.00 excluding VAT. It is ready to send.

Verdict: Allowed.

  • Order summary. 60 users at €39.00 per user per month, monthly total of €2,340.00 excluding VAT at list prices.

3. Platinum and Enterprise features: Business plan quoted for a team that needs Platinum and Enterprise features

The agent's request. Please quote a Severa subscription for 180 users on the Business plan, for a team that needs custom fields, automated invoicing, revenue recognition, multi-currency and single sign-on. The quote states a monthly total of €7,020.00 excluding VAT. It is ready to send.

Verdict: Blocked.

  • Feature needs the Platinum plan or higher. The quote needs 4 feature(s) that start with the Platinum plan, but a lower plan is quoted.
  • Feature needs the Enterprise plan. The quote needs 1 feature(s) that are only in the Enterprise plan, but a lower plan is quoted.

4. Platinum and Enterprise features: The agent resubmits after fixing the errors

The agent's request. Please quote a Severa subscription for 180 users on the Platinum plan, for a team that needs custom fields, automated invoicing, revenue recognition, multi-currency and single sign-on. The quote states a monthly total of €8,820.00 excluding VAT. It is ready to send.

Verdict: Blocked.

  • Feature needs the Enterprise plan. The quote needs 1 feature(s) that are only in the Enterprise plan, but a lower plan is quoted.

5. Platinum and Enterprise features: The agent resubmits after fixing the errors

The agent's request. Please quote a Severa subscription for 180 users on the Enterprise plan, for a team that needs custom fields, automated invoicing, revenue recognition, multi-currency and single sign-on. The quote states a monthly total of €12,420.00 excluding VAT. It is ready to send.

Verdict: Allowed.

  • Order summary. 180 users at €69.00 per user per month, monthly total of €12,420.00 excluding VAT at list prices.

6. Large organization and stated total: Platinum plan for over 500 users with a total at the wrong price

The agent's request. Please quote a Severa subscription for 620 users on the Platinum plan, for a team that needs the REST API, custom fields, automated invoicing and revenue recognition. The quote states a monthly total of €24,180.00 excluding VAT. It is ready to send.

Verdict: Blocked.

  • Stated total does not match. The quote states a monthly total of €24,180.00; the list prices give €30,380.00.
  • Over 500 users: contact sales. The quote has 620 users; Severa recommends that organizations over 500 contact its sales team, so a person should confirm the price.

7. Large organization and stated total: The agent resubmits after fixing the errors

The agent's request. Please quote a Severa subscription for 620 users on the Platinum plan, for a team that needs the REST API, custom fields, automated invoicing and revenue recognition. The quote states a monthly total of €30,380.00 excluding VAT. It is ready to send.

Verdict: Needs approval.

  • Over 500 users: contact sales. The quote has 620 users; Severa recommends that organizations over 500 contact its sales team, so a person should confirm the price.
  • Order summary. 620 users at €49.00 per user per month, monthly total of €30,380.00 excluding VAT at list prices.

Narration transcript

Click to expand

The text of the narrated walkthrough, step by step.

  1. Welcome to a demo of Predictika's Validator. An AI sales agent prepares a monthly subscription quote for Visma Severa, a professional services automation product: a plan, a number of users and the features the customer needs. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the published plans and prices and returns a verdict, every reason, a line-item quote and the figures it computed.
  2. I will start with the first request by the agent.
  3. The agent says. Please quote a Severa subscription for 180 users on the Business plan, for a team that needs custom fields, automated invoicing, revenue recognition, multi-currency and single sign-on. The quote states a monthly total of €7,020.00 excluding VAT. The rest of the request is on screen.
  4. Before it goes out, the agent calls the validator.
  5. Blocked, with two findings, all in one answer. The quote needs 4 feature(s) that start with the Platinum plan, but a lower plan is quoted. The quote needs 1 feature(s) that are only in the Enterprise plan, but a lower plan is quoted.
  6. The validator returned two blocking findings in one answer. A check that reads one field at a time would pass most of this; it shows only when the choices in the quote are checked against each other.
  7. What this shows: for features that start at different plans, a rules-based CPQ is error-prone for this.
  8. Now the agent resubmits.
  9. The corrected request. It changes the plan to platinum and the stated monthly total to €8,820.00.
  10. It calls the validator again.
  11. Still blocked, with one finding, all in one answer. The quote needs 1 feature(s) that are only in the Enterprise plan, but a lower plan is quoted.
  12. One finding cleared. Still blocking: feature needs the Enterprise plan.
  13. The agent resubmits once more.
  14. The revised request. It changes the plan to enterprise and the stated monthly total to €12,420.00.
  15. It calls the validator once more.
  16. This time the validator clears it.
  17. The validator also returns the line-item quote, on screen.
  18. The earlier finding is cleared, and the validator's total, €12,420.00, matches the quote.
  19. Two problems caught in one call, fixed in two passes, and a clean €12,420.00 quote. That is the value of Predictika's validator: catching mistakes before they reach the customer. Now you can try the other scenarios yourself.