Predictika · Experience management subscription quotes

An AI sales agent's experience management subscription quote, checked before it goes out

An AI sales agent prepares an annual subscription quote for a Qualtrics XM platform plan with modules, add-ons, a support level, a region and a discount. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the plans and returns a verdict, every reason and the totals it computed.

Scope: Annual subscription quotes for the four Qualtrics XM plans (CoreXM, XM for Customer Experience, XM for Employee Experience, XM for Strategy & Research) with modules, add-ons, support, region, term and discount. See everything this validator covers

This validator models Qualtrics XM subscription quotes, not just the scenarios shown below.

  • Plans and volume — the four plan names Qualtrics publishes, with interaction-based sizing and a size limit on CoreXM.
  • Modules and add-ons — employee, customer-experience and conjoint modules that belong to one plan each, plus Text iQ, single sign-on and a sandbox.
  • Support, region, term and discount — Premium and Elite support, the FedRAMP and other regions, a one-to-three-year term, quarterly billing and discount approval.
  • Stated total — the total the quote states against the total computed over the term.

Any Qualtrics XM subscription quote that touches these rules is in scope — not only the scenarios pictured here. Qualtrics pricing is quote-only: the plan names are public, but the rules and the dollar amounts in this validator are modeled from comparable products and are not published by Qualtrics. Not covered: other Qualtrics products, services and implementation fees, taxes, and negotiated terms.

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.

6 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
A module that belongs to one plan onlyOnly with care
Each module needs a rule that checks the plan it is quoted on, and the list grows with every module.
The plan and every module are in one request and checked together on every call.
Features that a smaller plan does not includeOnly with care
A product rule is needed for each feature on the smaller plan and it is easy to miss one.
Plan, add-ons and volume are fields of one request, compared on every call.
A region that needs a particular plan and support levelOnly with workarounds
The region rule depends on two other choices, so it has to be repeated beside each of them.
Region, plan and support level are checked together on every call.
A stated total that must match the computed totalOnly with workarounds
The total is built from many lines and discounts, so a separate rule is needed to recompute it and compare it with the stated figure.
The stated total is a field of the request and is compared with the computed total over the term on every call.
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.

1CoreXM is quoted for up to 250 thousand interactions a year; this quote has 251 thousand. Move to a larger plan.
2The quote has 0 thousand interactions; at least 1 thousand is needed.
3Engagement, Lifecycle and 360 modules belong to XM for Employee Experience only.
4Website feedback and Contact center modules belong to XM for Customer Experience only.
5The Conjoint module belongs to XM for Strategy & Research only.
6XM for Employee Experience is quoted for at least 100 employees; this quote has 99.
7Single sign-on and Text iQ are not part of CoreXM.
8A FedRAMP region deployment needs a public-sector specialist to confirm.
9The FedRAMP region is quoted only on the three XM plans with Premium or Elite support.
10A term of 4 years is outside the 1 to 3 year range.
11A term of 0 years is outside the 1 to 3 year range.
12A discount of 11 percent is above 10 percent; a sales manager should approve it.
13A discount of 25 percent is above 10 percent; a sales manager should approve it.
14A discount of 26 percent is outside the 0 to 25 percent range.
15Quarterly billing instead of annual upfront needs finance approval.
165,001 thousand interactions is above the largest modeled volume band; a person should price it.
17The quote states a total of 52,981 dollars; the modeled rates give 52,982 dollars.
18The quote states a total of 52,983 dollars; the modeled rates give 52,982 dollars.
19A discount of 15 percent is above 10 percent; a sales manager should approve it.
20The quote states a total of 100 dollars; the modeled rates give 58,729 dollars.

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. Region, support, module and term: A customer experience quote for the FedRAMP region with Conjoint and single sign-on, quarterly billing and a four-year term

The agent's request. Please quote XM for Customer Experience with 800,000 interactions per year, adding Website feedback, Conjoint, single sign-on, Standard support, the FedRAMP region, quarterly billing, a 4-year term and a 15 percent discount, for a total of $293,080. It is ready to send.

Verdict: Blocked.

  • Conjoint on the wrong plan. The Conjoint module belongs to XM for Strategy & Research only.
  • FedRAMP region needs a larger plan and paid support. The FedRAMP region is quoted only on the three XM plans with Premium or Elite support.
  • Term out of range. A term of 4 years is outside the 1 to 3 year range.
  • Discount above 10 percent. A discount of 15 percent is above 10 percent; a sales manager should approve it.
  • Quarterly billing. Quarterly billing instead of annual upfront needs finance approval.
  • FedRAMP region. A FedRAMP region deployment needs a public-sector specialist to confirm.

2. Region, support, module and term: The agent resubmits after fixing the errors

The agent's request. Please quote XM for Customer Experience with 800,000 interactions per year, adding Website feedback, single sign-on, Premium support, the EU region, annual billing, a 3-year term and a 10 percent discount, for a total of $162,459. It is ready to send.

Verdict: Allowed.

  • Order summary. Annual subscription of 54,153 dollars after discount; 162,459 dollars over the term.

3. Plan features and volume: A CoreXM quote with single sign-on and Text iQ

The agent's request. Please quote CoreXM with 300,000 interactions per year, adding Text iQ, single sign-on, Premium support, the US region, annual billing, a 1-year term and a 5 percent discount, for a total of $20,273. It is ready to send.

Verdict: Blocked.

  • CoreXM interaction limit. CoreXM is quoted for up to 250 thousand interactions a year; this quote has 300 thousand. Move to a larger plan.
  • Feature not in CoreXM. Single sign-on and Text iQ are not part of CoreXM.

4. Plan features and volume: The agent resubmits after fixing the errors

The agent's request. Please quote XM for Customer Experience with 300,000 interactions per year, adding Text iQ, single sign-on, Premium support, the US region, annual billing, a 1-year term and a 5 percent discount, for a total of $44,099. It is ready to send.

Verdict: Allowed.

  • Order summary. Annual subscription of 44,099 dollars after discount; 44,099 dollars over the term.

5. Employee plan and stated total: An employee experience quote with a contact center module and a total for the quote

The agent's request. Please quote XM for Employee Experience with 200,000 interactions per year and 60 employees, adding Engagement, Contact center, Premium support, the US region, annual billing, a 2-year term and an 8 percent discount, for a total of $100,000. It is ready to send.

Verdict: Blocked.

  • Customer module on the wrong plan. Website feedback and Contact center modules belong to XM for Customer Experience only.
  • Too few employees. XM for Employee Experience is quoted for at least 100 employees; this quote has 60.
  • Stated total does not match. The quote states a total of 100,000 dollars; the modeled rates give 90,434 dollars.

6. Employee plan and stated total: The agent resubmits after fixing the errors

The agent's request. Please quote XM for Employee Experience with 200,000 interactions per year and 150 employees, adding Engagement, Premium support, the US region, annual billing, a 2-year term and an 8 percent discount, for a total of $57,280. It is ready to send.

Verdict: Allowed.

  • Order summary. Annual subscription of 28,640 dollars after discount; 57,280 dollars over the term.

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 an annual subscription quote for a Qualtrics XM platform plan with modules, add-ons, a support level, a region and a discount. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the plans and returns a verdict, every reason and the totals it computed.
  2. I will start with the first request by the agent.
  3. The agent says. Please quote XM for Customer Experience with 800,000 interactions per year, adding Website feedback, Conjoint, single sign-on, Standard support, the FedRAMP region. It is ready to send. The rest of the request is on screen.
  4. Before it goes out, the agent calls the validator.
  5. Blocked, with three findings and three approvals, all in one answer. The Conjoint module belongs to XM for Strategy & Research only. The FedRAMP region is quoted only on the three XM plans with Premium or Elite support. A term of 4 years is outside the 1 to 3 year range.
  6. The validator returned three blocking findings and three approvals 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 a region that needs a particular plan and support level, a rules-based CPQ can do this only with workarounds.
  8. Now the agent resubmits.
  9. The corrected request. It changes the modules and add-ons to website feedback, single sign-on, the support to premium, the region to EU, the billing to annual and the total stated on the quote to $162,459. Two more changes are on screen.
  10. It calls the validator again.
  11. This time the validator clears it.
  12. All six earlier findings are cleared.
  13. Six problems caught in one call, fixed in one pass, and a clean $162,459 quote. That is the value of Predictika's validator: catching mistakes before they reach the customer. Now you can try the other scenarios yourself.