Predictika · EDA license bundle quotes

An AI sales agent's EDA license bundle quote, checked before it goes out

An AI sales agent prepares a license quote for a chip-design team: a tool bundle, a seat pool or pay-per-use credits (or both), delivery, term, any co-term with an existing agreement, an Ansys cross-portfolio add-on and a discount. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the bundle and licensing rules and returns a verdict, every reason and the entitlement figures it computed.

Scope: EDA tool bundle license quotes: seat pools versus pay-per-use credits, term and co-term, managed SaaS versus bring-your-own-compute, and Synopsys plus Ansys cross-portfolio bundles. See everything this validator covers

This validator models license quotes for EDA tool bundles — not just the scenarios shown below.

  • Bundles — digital implementation and signoff, verification, analog and custom design, photonic design, emulation, and an Ansys multiphysics signoff bundle, each with its tool count, seat maximum and minimum term.
  • License model — a term-based seat pool, pay-per-use credits, or a hybrid of both; which bundles can be bought which way.
  • Delivery — managed SaaS or bring-your-own-compute, where each bundle is offered.
  • Term and co-term — minimum and maximum term, and whether the term ends in the month of an existing agreement being co-termed.
  • Cross-portfolio — whether Ansys tools can be attached to a Synopsys bundle, and the review that requires.
  • Discount authority and stated figures — what a sales rep can give, what needs management approval and what no one can approve, and the tool count the quote itself states.

Any bundle license quote touching these products or actions is in scope — not only the scenarios pictured here. Not covered: prices (none are published, so this validator produces no price build-up or line-item quote), contract terms beyond those listed, and any vendor CPQ platform. Assumptions: the bundle composition, seat maximums, minimum terms, delivery and add-on eligibility and discount limits are invented illustrative values.

The AI sales agentBuilds the license quote from the conversation and says it is ready.
Predictika validatorChecks every rule at once and returns the verdict, each finding, and the computed entitlement figures.

6 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
A term that must end in the same month as an existing agreement (co-term)Only with workarounds
The existing end date has to be a field on the quote and the contract end computed from the start and the term; otherwise the check lives outside the quote.
The existing agreement date travels with the quote and is compared with the computed contract end on every call.
Which bundles can be bought as pay-per-use, a seat pool or a hybrid, and where each is offered as managed SaaSOnly with care
Each bundle-and-model pair is its own product rule. It works, but every new bundle adds rules that someone must keep in step.
Eligibility comes from the bundle record, so a new bundle is a new row, not a new rule.
A quote that states a tool count different from the bundleOnly with care
A validation rule can compare a stated figure with the bundle, but only if the stated figure is a field on the quote, which it rarely is.
The stated tool count travels with the quote and is compared with the bundle on every call.
Cross-portfolio review plus discount approval in one passOnly with care
Approval rules are easy one at a time. Several reasons at once usually mean several approval rules firing separately, each with its own message.
Every approval reason is listed together with the block reasons, in order of severity.
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.

1Emulation (ZeBu Cloud) cannot be bought with pay-per-use credits; it is offered as a term-based seat license only.
2the Ansys cross-portfolio add-on cannot be attached to Verification (VCS + Verdi).
3Emulation (ZeBu Cloud) is not offered as a managed SaaS environment; it is bring-your-own-compute only.
40 seats is outside the 1 to 100 seats one quote can carry for this bundle.
5a pay-per-use or hybrid quote needs a credit purchase of at least 1 thousand credits; the quote has 0 thousand.
6a term of 11 months is below the 12 month minimum for a term-based seat license of this bundle.
7a term of 61 months is longer than the 60 month maximum.
8the quote is meant to co-term with an agreement ending 3/2028, but a term of 36 months from 11/2026 does not end in that month.
9the quote states 4 tools in the bundle, but this bundle includes 3.
10a discount of 30 percent is above the 25 percent limit that anyone can approve.
11a discount of 20 percent is above the 10 percent a sales rep can give; it needs sales management approval.
12attaching Ansys cross-portfolio tools to a Synopsys bundle needs a deal desk review of the combined entitlement.
1320 seats leaves under 10 percent headroom below the 20 seat maximum for this bundle; confirm the pool size with the customer.

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. Emulation bundle: Pay-per-use SaaS request for a seat-only bundle

The agent's request. Please quote the Emulation (ZeBu Cloud) bundle as pay-per-use credits (500 thousand credits), a 24 month term starting November 2026, delivered as a managed SaaS environment. The quote states 2 tools in the bundle. It is ready to send.

Verdict: Blocked.

  • Pay-per-use not available for this bundle. Emulation (ZeBu Cloud) cannot be bought with pay-per-use credits; it is offered as a term-based seat license only.
  • Managed SaaS not offered. Emulation (ZeBu Cloud) is not offered as a managed SaaS environment; it is bring-your-own-compute only.
  • Stated tool count does not match. The quote states 2 tools in the bundle, but this bundle includes 1.

2. Emulation bundle: The agent resubmits after fixing the errors

The agent's request. Please quote the Emulation (ZeBu Cloud) bundle as a term-based seat license (6 seats), a 24 month term starting November 2026, using bring-your-own-compute delivery. The quote states 1 tool in the bundle. It is ready to send.

Verdict: Allowed.

  • Bundle summary. Emulation (ZeBu Cloud) (tools in bundle: 1). Seat pools are limited to 10 seats per quote with a 24 month minimum term; entitlements: 6 tool licenses at 6 seats; contract 24 months from 11/2026.

3. Co-term to an existing agreement: Large digital order that does not end with the existing agreement

The agent's request. Please quote the Digital Implementation and Signoff bundle as a term-based seat license (120 seats), a 36 month term starting November 2026, delivered as a managed SaaS environment, co-terming with our existing agreement that ends March 2028, with a 10 percent discount. The quote states 4 tools in the bundle. It is ready to send.

Verdict: Blocked.

  • Term does not end with the existing agreement. The quote is meant to co-term with an agreement ending 3/2028, but a term of 36 months from 11/2026 does not end in that month.
  • Stated tool count does not match. The quote states 4 tools in the bundle, but this bundle includes 3.

4. Co-term to an existing agreement: The agent resubmits after fixing the errors

The agent's request. Please quote the Digital Implementation and Signoff bundle as a term-based seat license (120 seats), a 17 month term starting November 2026, delivered as a managed SaaS environment, co-terming with our existing agreement that ends March 2028, with a 10 percent discount. The quote states 3 tools in the bundle. It is ready to send.

Verdict: Allowed.

  • Bundle summary. Digital Implementation and Signoff (Fusion Compiler + Design Compiler + PrimeTime) (tools in bundle: 3). Seat pools are limited to 150 seats per quote with a 12 month minimum term; entitlements: 360 tool licenses at 120 seats; contract 17 months from 11/2026.

5. Cross-portfolio bundle: Multiphysics hybrid request with a discount no one can approve

The agent's request. Please quote the Multiphysics Signoff (Ansys RedHawk-SC, Totem, HFSS) bundle as a hybrid of seats and pay-per-use credits (30 seats and 200 thousand credits), a 12 month term starting November 2026, delivered as a managed SaaS environment, with a 30 percent discount. The quote states 3 tools in the bundle. It is ready to send.

Verdict: Blocked.

  • Pay-per-use not available for this bundle. Multiphysics Signoff (Ansys RedHawk-SC + Totem + HFSS) cannot be bought with pay-per-use credits; it is offered as a term-based seat license only.
  • Term below the minimum. A term of 12 months is below the 24 month minimum for a term-based seat license of this bundle.
  • Managed SaaS not offered. Multiphysics Signoff (Ansys RedHawk-SC + Totem + HFSS) is not offered as a managed SaaS environment; it is bring-your-own-compute only.
  • Discount above the maximum. A discount of 30 percent is above the 25 percent limit that anyone can approve.

6. Cross-portfolio bundle: The agent resubmits after fixing the errors

The agent's request. Please quote the Multiphysics Signoff (Ansys RedHawk-SC, Totem, HFSS) bundle as a term-based seat license (30 seats), a 24 month term starting November 2026, using bring-your-own-compute delivery, with a 20 percent discount. The quote states 3 tools in the bundle. It is ready to send.

Verdict: Needs approval.

  • Discount needs approval. A discount of 20 percent is above the 10 percent a sales rep can give; it needs sales management approval.
  • Bundle summary. Multiphysics Signoff (Ansys RedHawk-SC + Totem + HFSS) (tools in bundle: 3). Seat pools are limited to 40 seats per quote with a 24 month minimum term; entitlements: 90 tool licenses at 30 seats; contract 24 months from 11/2026.

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 license quote for a chip-design team: a tool bundle, a seat pool or pay-per-use credits (or both), delivery, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the bundle and licensing rules and returns a verdict, every reason and the entitlement figures it computed.
  2. I will start with the first request by the agent.
  3. The agent says. Please quote the Emulation (ZeBu Cloud) bundle as pay-per-use credits (500 thousand credits), a 24 month term starting November 2026, delivered as a managed SaaS environment. The quote states 2 tools in the bundle. 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. Emulation (ZeBu Cloud) cannot be bought with pay-per-use credits; it is offered as a term-based seat license only. Emulation (ZeBu Cloud) is not offered as a managed SaaS environment; it is bring-your-own-compute only. The quote states 2 tools in the bundle, but this bundle includes 1.
  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 which bundles can be bought as pay-per-use, a seat pool or a hybrid, and where each is offered as managed SaaS, a rules-based CPQ is error-prone for this.
  8. Now the agent resubmits.
  9. The corrected request. It changes the license model to term-based seat license, the delivery to bring your own compute and the stated tools in bundle to 1. It sets the seats to 6. It removes the credits.
  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.