Predictika · Data platform consumption-commit quotes
An AI sales agent prepares a consumption-commit quote for a cloud analytics platform customer: package, primary and compute cluster sizing, block and object storage, term, support level, discount, on-premises migration credit and renewal. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the packaging and commit rules and returns a verdict, every reason and the annual commit it computed.
This validator models consumption-commit quotes for a cloud analytics platform sold in three packages — not just the scenarios shown below.
Any consumption-commit quote for these packages that touches sizing, storage, term, support, discount, migration credit or renewal is in scope — not only the scenarios pictured here. The validator computes an annual commit total from public list rates, but it produces no line-item quote. Not covered: negotiated rates, flexible on-demand usage, other products, taxes and any vendor CPQ platform. Assumptions: the minimum commitments, credit rules, discount limits, renewal threshold and the compute-cluster size limit are invented illustrative values; list rates are estimates, not quotes.
6 scenarios in 3 groups · each group runs from the agent’s first attempt to the outcome · click one to switch
Illustrative agent statement. The validator receives the structured request below.
Proposing agent: AI sales agent (scripted)
Before sending, the agent must call Recorded run
What this means
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 caught | Typical rules-based CPQ | Predictika |
|---|---|---|
| Unit rates that depend on package, cluster type and size, rolled into an annual commit | Only with care A price rule per package and size works, but each new size or package adds rules, and the commit total is easy to get out of step with the unit table. | Rates sit on the package record; units and the annual commit are computed on every call. |
| A stated annual commit that differs from the computed one | Only with care A validation rule can compare them, but only if the stated figure is a field on the quote, which it rarely is. | The stated commit travels with the quote and is compared with the computed commit on every call. |
| Migration credit eligibility that depends on package, term, migration status and renewal together | Only with workarounds Each condition tends to become its own rule with its own message, and combinations (such as a credit on a renewal) are easy to miss. | All credit conditions are checked together and every failing one is listed. |
| Storage minimums tied to node count and a renewal compared with the prior commit | Only with workarounds Cross-field and prior-contract checks usually live outside the quote or in custom code. | Block storage per node and the prior commit are quote fields compared in the same pass. |
| Every problem returned in one answer | Only 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, ordered by severity. |
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.
| 1 | Migration credits are not available with VantageCloud Lake Standard. |
| 2 | Support level 2 was requested but VantageCloud Lake Standard includes level 1 (1 basic, 2 premier cloud, 3 white-glove). |
| 3 | Medium compute clusters are not offered with VantageCloud Lake+; compute clusters come in XSmall and Small. |
| 4 | The quote states an annual commit of $1,500,000, but the computed annual commit is $703,260. |
| 5 | An annual commit of $23,914 is below the $50,000 minimum annual commitment for VantageCloud Lake Standard. |
| 6 | A 4 year term is outside the 1 to 3 year range for committed capacity. |
| 7 | 2 TB of block storage is below the 1 TB per primary cluster node required for 4 nodes. |
| 8 | A 30 percent discount is above the 25 percent limit that anyone can approve. |
| 9 | A migration credit was requested but the customer is not migrating from on-premises Vantage. |
| 10 | A migration credit needs a term of at least 2 years; this quote has 1. |
| 11 | A 21 percent migration credit is above the 20 percent maximum. |
| 12 | Migration credits apply to new commitments only, not renewals. |
| 13 | The renewal commit of $166,350 is more than 20 percent below the prior commit of $250,000; confirm the reduction with the customer. |
| 14 | A 20 percent migration credit is above the 10 percent a sales rep can offer; it needs approval. |
| 15 | A 16 percent discount is above the 15 percent a sales rep can give; it needs sales management approval. |
| 16 | The annual commit of $52,498 is within 10 percent of the $50,000 minimum for VantageCloud Lake Standard; confirm sizing with the customer. |
| 17 | 9000 compute cluster hours a year per cluster is not valid; it must be between 1 and 8,760 when compute clusters are quoted. |
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.
The agent's request. Please quote a three-year VantageCloud Lake Standard commitment for a customer migrating from on-premises Vantage: a Medium primary cluster of 4 nodes with 6 TB of block storage and 100 TB of object storage, 2 Small compute clusters running 1,500 hours a year each, and premier cloud support, with a 10 percent migration credit. The quote states an annual commit of $411,276. It is ready to send.
Verdict: Blocked.
The agent's request. Please quote a three-year VantageCloud Lake commitment for a customer migrating from on-premises Vantage: a Medium primary cluster of 4 nodes with 6 TB of block storage and 100 TB of object storage, 2 Small compute clusters running 1,500 hours a year each, and premier cloud support, with a 10 percent migration credit. The quote states an annual commit of $502,860. It is ready to send.
Verdict: Allowed.
The agent's request. Please quote a two-year VantageCloud Lake+ commitment: a Large primary cluster of 4 nodes with 6 TB of block storage and 200 TB of object storage, 2 Medium compute clusters running 2,000 hours a year each, and white-glove support. The quote states an annual commit of $1,500,000. It is ready to send.
Verdict: Blocked.
The agent's request. Please quote a two-year VantageCloud Lake+ commitment: a Large primary cluster of 4 nodes with 6 TB of block storage and 200 TB of object storage, 2 Small compute clusters running 2,000 hours a year each, and white-glove support. The quote states an annual commit of $847,260. It is ready to send.
Verdict: Allowed.
The agent's request. Please quote a two-year VantageCloud Lake commitment as a renewal of a $500,000 annual commit: a Large primary cluster of 4 nodes with 2 TB of block storage and 50 TB of object storage, 3 XSmall compute clusters running 3,000 hours a year each, and premier cloud support, and a 30 percent discount. The quote states an annual commit of $476,126. It is ready to send.
Verdict: Blocked.
The agent's request. Please quote a two-year VantageCloud Lake commitment as a renewal of a $500,000 annual commit: a Large primary cluster of 4 nodes with 4 TB of block storage and 50 TB of object storage, 3 XSmall compute clusters running 3,000 hours a year each, and premier cloud support, and a 10 percent discount. The quote states an annual commit of $617,364. It is ready to send.
Verdict: Allowed.
The text of the narrated walkthrough, step by step.