Predictika · Enterprise software subscription quotes
An AI sales agent prepares a Red Hat subscription quote for a customer: RHEL servers and guests, OpenShift compute capacity, Ansible managed nodes, support level, co-term. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the public subscription counting rules and returns a verdict, every reason and the subscription counts it computed.
This validator models Red Hat subscription quotes and the counting, bundle and co-term rules that go with them — not just the scenarios shown below.
Any Red Hat quote that touches these products, counting units, support levels or co-term and renewal rules is in scope — not only the scenarios pictured here. Not covered: prices (Red Hat's price list is not modeled here, so this validator produces no price build-up or line-item quote), other Red Hat products and cloud marketplace offerings, partner and channel terms, and the customer's own CPQ platform. Assumptions: the unit sizes follow Red Hat's public subscription guides; the approval limits (10 and 30 percent discount, co-term under 12 months, support downgrade at renewal) are placeholders because those terms are not published.
7 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 |
|---|---|---|
| Socket-pair counting: a four-socket server needs two RHEL Server subscriptions and an eight-socket server needs four | Only with care The count is a calculated field and the stated count has to be a field on the quote before a rule can compare them; each socket size is its own condition. | The count is computed from the servers and sockets on every call and compared with the subscriptions quoted. |
| Guests and virtual datacenters: one subscription per two guests, or one per hypervisor socket pair for unlimited guests | Only with care Two licensing models for the same machines, each with its own rounding; rules have to be kept in step with each other. | Both counts are computed from the inputs and compared with what was quoted. |
| OpenShift capacity: two physical cores or four vCPUs per subscription, rounded up separately, compute nodes only | Only with workarounds The cores and vCPUs live on the customer's clusters, not on the quote, so a rule can check them only if they are copied onto the quote as fields. | Cores and vCPUs travel with the request and the subscription count is derived from them. |
| Bundle overlap: Platform Plus already includes the management, security and registry add-ons, and OpenShift already includes RHEL for its nodes | Only with care One product rule per overlap, tied to an edition. Works, but every new edition or add-on adds rules someone has to maintain. | The overlaps sit on the edition and are checked on every call. |
| Support level scope: self-support only for RHEL on physical systems, never for guests, OpenShift or Ansible | Only with care A cross-product restriction that has to be repeated for each product combination. | One rule over the whole quote, checked with every other rule. |
| Co-term and renewal: months left on the existing subscription, and a renewal that lowers the support level | Only with workarounds The existing subscription lives in the install base, not on the quote, so its end date and support level must be copied onto the quote before a rule can use them. | Months remaining and the prior support level travel with the request and are compared with the quote. |
| 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. |
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 | The quote has 10 RHEL Server subscriptions; 20 are needed to cover the sockets (one subscription covers up to two sockets). |
| 2 | The quote has 4 subscriptions for 9 virtual guests; 5 are needed (one subscription covers two guests). |
| 3 | The quote has 3 RHEL for Virtual Datacenters subscriptions for 8 hypervisor sockets; 4 are needed (one per two sockets). |
| 4 | The quote has 100 OpenShift subscriptions; 128 are needed for the compute capacity (one per two cores or four vCPUs). |
| 5 | Advanced Cluster Management, Advanced Cluster Security and Quay are already included in OpenShift Platform Plus; remove the separate add-on lines. |
| 6 | An OpenShift add-on is quoted above the 128 OpenShift subscriptions it attaches to. |
| 7 | 16 separate RHEL subscriptions are quoted for OpenShift nodes; RHEL for compute nodes is included with OpenShift. |
| 8 | The quote has 2 Ansible Automation Platform subscriptions for 250 managed nodes; 3 are needed (one per 100 nodes). |
| 9 | Self-support is offered only for RHEL on physical systems; this quote has virtual guests, OpenShift or Ansible, which need Standard or Premium support. |
| 10 | A co-term add-on needs the months left on the existing subscription, between 1 and 59; the quote has 0. |
| 11 | Only 8 months remain on the existing subscription; a co-term this short is prorated and needs review. |
| 12 | The renewal lowers the support level from Premium to Standard; a downgrade at renewal needs review. |
| 13 | 20 percent discount is above the 10 percent a rep can give; approvable up to 30 percent. |
| 14 | 35 percent discount is above the 30 percent limit. |
| 15 | 24 RHEL Server subscriptions are quoted but the sockets need only 20; confirm the extra entitlement is intended. |
| 16 | The quote states 18.0 subscription units in total; the validator counts 20. |
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 OpenShift Platform Plus as a new subscription with Standard support, for 192 physical cores and 384 vCPUs of compute: 192 OpenShift subscriptions, 192 Advanced Cluster Management add-on subscriptions, 192 Advanced Cluster Security add-on subscriptions and 24 RHEL subscriptions for the compute nodes. The quote states 600 subscription units in total. It is ready to send.
Verdict: Blocked.
The agent's request. Please quote OpenShift Platform Plus as a new subscription with Standard support, for 192 physical cores and 384 vCPUs of compute: 192 OpenShift subscriptions. The quote states 192 subscription units in total. It is ready to send.
Verdict: Allowed.
The agent's request. Please quote a new subscription on self-support for 40 four-socket physical RHEL servers with 40 RHEL Server subscriptions, and 30 virtual RHEL guests with 30 guest subscriptions. The quote states 95 subscription units in total. It is ready to send.
Verdict: Blocked.
The agent's request. Please quote a new subscription on Standard support for 40 four-socket physical RHEL servers with 80 RHEL Server subscriptions, and 30 virtual RHEL guests with 30 guest subscriptions. The quote states 95 subscription units in total. It is ready to send.
Verdict: Needs approval.
The agent's request. Please quote a new subscription on Standard support for 40 four-socket physical RHEL servers with 80 RHEL Server subscriptions, and 30 virtual RHEL guests with 15 guest subscriptions. The quote states 95 subscription units in total. It is ready to send.
Verdict: Allowed.
The agent's request. Please quote a co-term add-on to an existing subscription, with Standard support, adding OpenShift Container Platform for 64 physical cores and 128 vCPUs of compute (64 OpenShift subscriptions) and Ansible Automation Platform for 700 managed nodes (5 subscriptions). The existing subscription has no months recorded as remaining. The quote states 71 subscription units in total. It is ready to send.
Verdict: Blocked.
The agent's request. Please quote a co-term add-on to an existing subscription with 18 months remaining, with Standard support, adding OpenShift Container Platform for 64 physical cores and 128 vCPUs of compute (64 OpenShift subscriptions) and Ansible Automation Platform for 700 managed nodes (7 subscriptions). The quote states 71 subscription units in total. It is ready to send.
Verdict: Allowed.
The text of the narrated walkthrough, step by step.