Predictika · ITSM, ITOM and ITAM subscription quotes: tiers, capabilities, seats, renewals and AI use
An AI sales agent prepares an IT Workflows subscription quote (ITSM, ITOM and asset management) for a fictional company, with the first-year total it expects. Before the quote goes out, the agent sends it to Predictika’s validator, which derives the tier each capability needs, checks seats, bundles, renewals and AI use, compares the total the agent states with the one it computes, and returns a verdict with every reason. All prices are Predictika estimates in US dollars, not ServiceNow list prices.
This validator checks and prices IT Workflows subscriptions under the Foundation, Advanced and Prime packaging. It handles any quote built from the tiers, capabilities and seats below, not just the scenarios shown.
It does not cover other ServiceNow products such as CRM, HR, Security or CPQ, real list or negotiated prices, or any real customer.
8 scenarios in 4 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 or Revenue Cloud) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.
| What the validator catches | Typical rules-based CPQ | Predictika |
|---|---|---|
| The lowest tier that covers every capability | Only with workarounds Each capability maps to a minimum tier, so choosing the tier means scanning every selected item, and the product rules multiply with the catalog. | The tier is derived from the capability list, and each capability checks itself against the chosen tier. |
| A tier chosen by hand that is too low | Only with care A rule is needed per capability and tier, and a message that names the capability has to be written for each. | Each capability reports itself, so the finding names it. |
| Seat, bundle and subscription-unit dependencies | Only with care Asset-manager seats, the Service Ops bundle and ITOM units each depend on other fields, so each is a separate validation rule. | Each dependency is its own finding, returned together. |
| Renewal from an older plan | Only with workarounds Mapping an old plan to what the new tier drops is a per-plan lookup with its own acknowledgement rule. | The old plan’s dropped items are catalog data, and the acknowledgement is one rule. |
| Volume bands and term discounts that reconcile to a total | Only with care Several discount layers (fulfiller bands, unit bands, bundle, term) have to add up to the quote total, which is easy to get out of step. | The same computed figures feed the line items and the total. |
| Expected AI use against the bundled pool | Only with workarounds A usage forecast is outside the usual quote fields, so a top-up and its approval are custom rules. | The forecast is a set of request fields, and the top-up is computed and returned as an approval item. |
| The total the agent states | Only with workarounds Comparing a stated figure with a computed one means a separate rule per quote layout, and price rules rarely run on stated figures. | The stated total is a field in the request and is checked against the computed total. |
| Every problem returned in one answer | Only with workarounds Rules tend to fire as the quote is saved, so a rep often fixes one error and meets the next. | All findings come back together, whatever order the choices arrived in. |
Every rule is checked on every call, in whatever order the choices arrive, and one problem never hides another. Blocking findings stop the quote; approval findings need a person to sign off; everything else is computed.
| Rule | Effect | What it checks |
|---|---|---|
| 1 | block | Each requested capability needs a minimum ITSM tier (Foundation, Advanced or Prime) or ITOM tier (Advanced or Prime) |
| 2 | computed | If no tier is chosen, the lowest tier covering every requested capability is picked for ITSM and for ITOM |
| 3 | block, note | A chosen tier below what a capability needs is blocked, and a chosen tier higher than needed is noted |
| 4 | block | Software or Hardware Asset Management needs at least one asset-manager seat |
| 5 | block | The Service Ops bundle needs an ITOM tier, and ITSM and ITOM at the same tier (Advanced or Prime) |
| 6 | block | ITOM is priced by subscription units from servers, PaaS resources, containers and agent-managed devices, and needs at least one |
| 7 | block, note | A renewal from an older plan to ITSM Foundation drops capabilities and needs a signed acknowledgement; DevOps Change Velocity is only in Prime |
| 8 | computed | Volume discount bands, bundle and term discounts and seat prices follow the price book |
| 9 | approval | Expected AI use above the bundled assist pool is priced as a top-up whose rate needs agreement |
| 10 | block | The first-year total the agent states must match the validator figure within USD 1 |
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. An ITSM Foundation subscription for 120 fulfillers including Change Management, one-year term. First-year total USD 112,608.00. Ready to send.
Verdict: Blocked.
The agent's request. An ITSM subscription for 120 fulfillers including Change Management, one-year term. First-year total USD 161,568.00. Ready to send.
Verdict: Allowed.
The agent's request. A renewal of the customer’s ITSM Professional plan onto ITSM Foundation for 80 fulfillers with Incident Management, one-year term. First-year total USD 88,320.00. Ready to send.
Verdict: Blocked.
The agent's request. A renewal of the customer’s ITSM Professional plan onto ITSM Foundation for 80 fulfillers with Incident Management, one-year term, with the customer’s acknowledgement of the capability change recorded. First-year total USD 88,320.00. Ready to send.
Verdict: Allowed.
The agent's request. An ITSM subscription for 100 fulfillers with Change Management and Software Asset Management, one-year term, planning about 800 small, 400 medium and 150 large Now Assist actions a month. First-year total USD 224,640.00. Ready to send.
Verdict: Blocked.
The agent's request. An ITSM subscription for 100 fulfillers with Change Management and Software Asset Management and 3 asset-manager seats, one-year term, planning about 800 small, 400 medium and 150 large Now Assist actions a month. First-year total USD 225,619.20. Ready to send.
Verdict: Needs approval.
The agent's request. An ITSM subscription for 120 fulfillers with Incident Management, Change Management and Problem Management, one-year term. First-year total USD 137,332.80. Ready to send.
Verdict: Blocked.
The agent's request. An ITSM subscription for 120 fulfillers with Incident Management, Change Management and Problem Management, one-year term. First-year total USD 161,568.00. Ready to send.
Verdict: Allowed.
The text of the narrated walkthrough, step by step.