Predictika · Solara hospital contract quotes
An AI sales agent quotes add-ons, extensions, upgrades and renewals for Solara Medical Instruments' hospital contracts, in US dollars. Before a quote goes out, the agent sends it to Predictika, which prices it from each contract's own terms (its proration method, price ramp, upgrade paths and renewal terms), compares the total the quote states with the computed one, and returns every finding together with the line-item quote. Solara, its hospitals, contracts and prices are fictional test data.
This validator checks AI-drafted quotes and amendments against Solara Medical Instruments' hospital contracts for patient monitors, infusion pumps, monitoring software and service plans. It handles any add-on, extension, upgrade or renewal built from those parts, not only the scenarios shown on this page. It does not price any other product line, and it does not decide clinical suitability.
8 scenarios in 4 groups · each group runs from the agent’s first attempt to the outcome · click one to switch
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 |
|---|---|---|
| Add-on co-termed to the contract end, prorated by the contract’s own method | Only with care CPQ co-terms amendment lines to the contract end date, but subscription proration is a single setting for the whole org. A contract negotiated with Day proration and another with Month cannot both be priced right without a manual adjustment. | The proration method is a field on each contract. The same model prices both contracts correctly, and every answer shows what the other method would have charged. |
| Term extension that re-prorates every line on the contract | Only with workarounds A CPQ amendment co-terms to the contract’s existing end date. Moving the end date means an early renewal or custom work, and then re-quoting the add-on against the new term. | The extension and the add-on are one quote, priced in one pass; each recurring line already on the contract computes its own extension. |
| Upgrade in place at the contract’s negotiated step, priced year by year | Only with workarounds CPQ cannot change the product on a multi-dimensional quantity line in an amendment. The workaround is cancel-and-replace, which loses the link to the original line and leaves the ramp pricing to hand work. | One line replaces the contract line and points back to it. The rest of the term is priced contract year by contract year, with the credit and the charge shown. |
| Renewal on per-line terms with an uplift cap | Only with care CPQ supports a renewal method and an uplift percentage. A cap on the uplift, and different methods on different lines of one contract, need custom fields and price rules or Apex to enforce. | Each contract line declares its own method, uplift and cap, and the renewal is computed from them with the uplift compounding by year. |
| Total that the agent states must match the computed one | Only with workarounds A validation rule can compare a stated figure with a calculated one only if the stated figure is a field on the quote, which it rarely is. | The stated total travels with the quote and is compared with the computed total on every call; a mismatch is its own block. |
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 | An add-on line is priced at the contract net price when the contract has the product, and at list price when it does not. |
| 2 | A subscription line added mid-term is co-termed: it runs to the contract end date and is prorated by that contract’s own method, Day or Month, with the other method reported alongside. |
| 3 | The quote date must fall inside the contract term; a quote dated after the contract ended is blocked, because there is nothing to co-term to. |
| 4 | A subscription line on a quote with no contract is blocked, because it cannot be co-termed. |
| 5 | A new contract end date must be later than the current one; an earlier date is blocked as not being an extension. |
| 6 | When the term is extended, every recurring line already on the contract is extended for the added days in the same pass; one-time hardware adds nothing. |
| 7 | An upgrade replaces a contract line in place and must go to the product that line allows; any other replacement is blocked. |
| 8 | An upgrade is priced contract year by contract year: a credit at the old line’s year prices and a charge at the old price plus the contract’s upgrade step. |
| 9 | A renewal is priced line by line from each contract line’s own method, Uplift, Fixed or Same, with the uplift applied to the net price, capped, and compounded by year. |
| 10 | A first-year discount is billed in year 1 only and never becomes the renewal base. |
| 11 | A line priced as a percent of another line renews at that percent of the other line’s renewed price, so the uplift is applied once. |
| 12 | The total the agent states must match the computed total to within one dollar; otherwise the quote is blocked. |