Predictika · Cross-brand software subscription quotes

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

An AI sales agent prepares a subscription quote that spans TIBCO, Jaspersoft, Spotfire, Citrix and NetScaler products: license metric, quantity, environments, deployment, migration from an older product, term and discount. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the metric, capacity, migration and discount rules and returns a verdict and every reason.

Scope: subscription quotes for TIBCO BusinessWorks, Jaspersoft, Spotfire, Citrix and NetScaler: metrics, bundle limits, migration, co-term and discounts. See everything this validator covers
  • License metrics — Cores or vCPUs for TIBCO BusinessWorks and Jaspersoft, named users for Spotfire and Citrix, and Gbps for NetScaler, checked against the quantity the deployment needs.
  • Quantity against deployment — Units are computed from sockets and cores, vCPUs or users, and compared with what the quote licenses and with the requirement the quote states.
  • Non-production use — Production-only licenses against quotes that cover non-production environments.
  • Citrix bundles — Capacity limits of the Universal Hybrid Multi-Cloud bundle, the private-cloud restriction, and overlap with separately sold NetScaler capacity.
  • NetScaler — Pooled capacity, licensing delivery, instances and throughput.
  • Spotfire — License type (Analyst, Business Author, Consumer) against the intended use.
  • Migration, renewal and co-term — Trade-up grace period, overlap days, co-terming only with an existing subscription, short stub terms, and downsizing at renewal.
  • Discount authority — What a rep can give by term, what needs approval, and what is refused.

Any quote in these product families that touches these topics is in scope, not only the scenarios pictured here. Not covered: prices. No public price list exists for these products, so this validator has no prices and produces no price build-up or line-item quote. Assumptions: the discount limits (10, 15 and 30 percent) and the stub-term length are placeholders; the 90-day trade-up grace period comes from the vendor's public licensing page.

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
Units the deployment needs differ from the units quoted, and the quote also states a requirement that is wrongOnly with care
The need is derived from sockets, cores per socket or vCPUs. A validation rule can recompute it only if those inputs are fields on the quote and the stated figure is one too.
The need is computed from the deployment on every call and compared with both the quantity and the stated requirement.
Production-only license on a quote that covers non-production environmentsOnly with care
One more rule per product and license type, kept in step as license types change.
The environment and license type travel with the quote and are checked together.
Citrix bundle that already includes NetScaler, quoted with separate NetScaler capacity, or a deployment above the bundle limitsOnly with workarounds
Bundle limits sit in a different record from the second quote line, so a rule has to reach across lines and be rewritten when the bundle changes.
Both products are on the request; the bundle limits come from the product record and are compared with the deployment.
Trade-up from an older product: overlap days against the grace period, with the old and new metricOnly with workarounds
The old subscription lives in the install base, so its metric, quantity and overlap must be copied onto the quote before a rule can compare them.
The legacy metric, quantity and overlap travel with the request and are compared with the grace period in the policy record.
Discount authority that depends on term, deal type and the license mixOnly with care
Approval matrices are usually separate objects, and a rule must pick the right row for each combination.
The rep limit for the term and the approval ceiling are looked up from the policy record 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.

1Co-terming needs an existing subscription; a new customer has none to align with.
2Co-terming leaves only 2 months on the term; a short stub term needs approval.
3The quote licenses 64 units but the deployment needs 96.
4The quote states a requirement of 64 units; the validator computes 96 from the deployment.
5Non-production environments are in scope but the license type is Production only; non-production use needs the ProdPlus license type.
6The deployment needs 1,400 Gbps of NetScaler throughput; this bundle includes up to 1,000 Gbps.
7The deployment needs 1,100 NetScaler instances; this bundle includes up to 999.
8The Universal Hybrid Multi-Cloud bundle already includes NetScaler; adding NetScaler Fixed Capacity as well needs a review for overlapping capacity.
9The Spotfire Consumer license does not allow the intended use; a more capable Spotfire license type is needed.
10The old and new products overlap for 150 days; the trade-up grace period is 90 days.
11A discount of 35.0 percent is above the 30.0 percent ceiling that anyone can approve.
12A discount of 20.0 percent is above the 15.0 percent a rep can give on this term; approvable up to 30.0 percent.
13A discount of 12.0 percent is above the 10.0 percent a rep can give on this term; approvable up to 30.0 percent.

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. Core metric and non-production use: Cores undercounted, non-production on a Production license

The agent's request. Please quote a new subscription of TIBCO BusinessWorks for 64 cores, for virtual machines with 96 vCPUs, on a Production-only license, on premises, covering production and non-production environments, a 3-year term with a 12 percent discount. The quote states a requirement of 64 units. It is ready to send.

Verdict: Blocked.

  • Not enough license units. The quote licenses 64 units but the deployment needs 96.
  • Stated requirement does not match. The quote states a requirement of 64 units; the validator computes 96 from the deployment.
  • Non-production needs ProdPlus. Non-production environments are in scope but the license type is Production only; non-production use needs the ProdPlus license type.

2. Core metric and non-production use: The agent resubmits after fixing the errors

The agent's request. Please quote a new subscription of TIBCO BusinessWorks for 96 cores, for virtual machines with 96 vCPUs, on a Production plus Non-Production (ProdPlus) license, on premises, covering production and non-production environments, a 3-year term with a 12 percent discount. The quote states a requirement of 96 units. It is ready to send.

Verdict: Allowed.

  • Coverage summary. TIBCO BusinessWorks needs 96 units of its license metric for this deployment; the quote licenses 96.

3. Citrix bundle capacity: Deployment exceeds the bundle limits

The agent's request. Please quote a new subscription of Citrix Universal Hybrid Multi-Cloud for 8,000 named users, for a customer with 1,400 Gbps of NetScaler throughput and 1,100 NetScaler instances, on a Production-only license, on premises, a 3-year term with a 12 percent discount. The quote states a requirement of 8,000 units. It is ready to send.

Verdict: Blocked.

  • Bundle throughput exceeded. The deployment needs 1,400 Gbps of NetScaler throughput; this bundle includes up to 1,000 Gbps.
  • Bundle instances exceeded. The deployment needs 1,100 NetScaler instances; this bundle includes up to 999.

4. Citrix bundle capacity: Deployment brought within the bundle limits

The agent's request. Please quote a new subscription of Citrix Universal Hybrid Multi-Cloud for 8,000 named users, for a customer with 900 Gbps of NetScaler throughput and 500 NetScaler instances, on a Production-only license, on premises, a 3-year term with a 12 percent discount. The quote states a requirement of 8,000 units. It is ready to send.

Verdict: Allowed.

  • Coverage summary. Citrix Universal Hybrid Multi-Cloud needs 8,000 units of its license metric for this deployment; the quote licenses 8,000.

5. Spotfire trade-up: Consumer license, long overlap, deep discount

The agent's request. Please quote a migration to a subscription of Spotfire Consumer for 1,200 named users, on a Production-only license, on premises, replacing 1,200 existing named-user licenses with 150 days of overlap, for advanced analysis use, a 3-year term with a 35 percent discount. The quote states a requirement of 1,200 units. It is ready to send.

Verdict: Blocked.

  • License type too limited for the use. The Spotfire Consumer license does not allow the intended use; a more capable Spotfire license type is needed.
  • Trade-up grace period exceeded. The old and new products overlap for 150 days; the trade-up grace period is 90 days.
  • Discount above the maximum. A discount of 35.0 percent is above the 30.0 percent ceiling that anyone can approve.

6. Spotfire trade-up: Right license and overlap, discount still above the rep limit

The agent's request. Please quote a migration to a subscription of Spotfire Analyst for 1,200 named users, on a Production-only license, on premises, replacing 1,200 existing named-user licenses with 60 days of overlap, for advanced analysis use, a 3-year term with a 20 percent discount. The quote states a requirement of 1,200 units. It is ready to send.

Verdict: Needs approval.

  • Discount needs approval. A discount of 20.0 percent is above the 15.0 percent a rep can give on this term; approvable up to 30.0 percent.
  • Coverage summary. Spotfire Analyst needs 1,200 units of its license metric for this deployment; the quote licenses 1,200.

7. Spotfire trade-up: Discount lowered to the rep limit

The agent's request. Please quote a migration to a subscription of Spotfire Analyst for 1,200 named users, on a Production-only license, on premises, replacing 1,200 existing named-user licenses with 60 days of overlap, for advanced analysis use, a 3-year term with a 12 percent discount. The quote states a requirement of 1,200 units. It is ready to send.

Verdict: Allowed.

  • Coverage summary. Spotfire Analyst needs 1,200 units of its license metric for this deployment; the quote licenses 1,200.

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 subscription quote that spans TIBCO, Jaspersoft, Spotfire, Citrix and NetScaler products: license metric, quantity, environments, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the metric, capacity, migration and discount rules and returns a verdict and every reason.
  2. I will start with the first request by the agent.
  3. The agent says. Please quote a new subscription of TIBCO BusinessWorks for 64 cores, for virtual machines with 96 vCPUs, on a Production-only license. The quote states a requirement of 64 units. The rest of the request is on screen.
  4. Before it goes out, the agent calls the validator.
  5. Blocked, with three findings, all in one answer. The quote licenses 64 units but the deployment needs 96. The quote states a requirement of 64 units; the validator computes 96 from the deployment. Non-production environments are in scope but the license type is production only; non-production use needs the ProdPlus license type.
  6. The validator returned three 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 units the deployment needs differ from the units quoted, and the quote also states a requirement that is wrong, a rules-based CPQ is error-prone for this.
  8. Now the agent resubmits.
  9. The corrected request. It changes the quantity on the quote to 96, the license type to ProdPlus and the stated requirement to 96 units.
  10. It calls the validator again.
  11. This time the validator clears it.
  12. All three earlier findings are cleared, and the validator's figure matches the quote.
  13. Three problems caught in one call, fixed in one pass, and a clean quote. That is the value of Predictika's validator: catching mistakes before they reach the customer. Now you can try the other scenarios yourself.