Predictika · SD-WAN and SASE subscription quotes

An AI sales agent's SD-WAN subscription quote, checked before it goes out

An AI sales agent prepares a quote for an SD-WAN subscription with a feature tier, a bandwidth tier, add-ons and a headend. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the licensing rules and returns a verdict, every reason and the figures it computed.

Scope: Versa Secure SD-WAN subscription quotes (Prime SD-WAN, Prime Secure, Premier Secure and Premier Elite) with bandwidth tiers, add-ons, HA pairs and headend capacity. See everything this validator covers

This validator models Versa Secure SD-WAN subscription quotes, not just the scenarios shown below.

Tiers and bandwidth — the four feature tiers, the WAN bandwidth tiers from 10 Mbps to 100 Gbps, and subscription terms of 1, 3 or 5 years.
Add-ons — ZTNA, Identity Engine and XoT Fingerprinting need a secure tier; Data Protection and Cloud ATP Sandboxing need Premier Elite; Advanced Logging Service is sold in 1 TB increments.
Licenses and headend — every device, including each standby in an HA pair, needs its own license; stateful HA needs a tier with firewall capabilities; headend sizes are fixed lists for on-premises and hosted dedicated headends.

Any Versa Secure SD-WAN subscription quote that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices (Versa does not publish list prices, so this validator produces no price build-up or line-item quote), the newer SASE and Titan packages, VANI and hosted shared bucket pricing. Assumptions: the rule that licenses may not exceed headend capacity is generic logic, and the 10 Gbps threshold for confirming bandwidth sizing is a guideline set by this model, not a Versa rule.

The AI sales agentBuilds the subscription quote from the conversation and says it is ready.

Predictika validatorChecks every rule at once and returns the verdict, each finding, and the computed figures.

7 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

Proposing agent: AI sales agent (scripted)

Before sending, the agent must call Recorded run

Predictika validator

Waiting for the call.

What this means

Run the validator to see the outcome

The explanation appears here once the validator returns.

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 caught	Typical rules-based CPQ	Predictika
License counts that must cover every device, including each standby in an HA pair	Only with care The count depends on two quantities on different lines; a rule can compare them, but each new pairing option adds another rule to maintain.	Sites and HA sites travel in one request and the needed licenses are computed and compared on every call.
Add-ons that exist only on some tiers	Only with care A product rule per add-on and tier. It works, but every new tier or add-on is another set of rules to maintain.	Tier and every add-on are in one request and every availability rule is checked together.
Stateful HA that needs a firewall tier	Only with workarounds The requirement links the tier on one line with the HA setting on another, so it needs a cross-line rule that interacts with the others.	The tier and the HA sites are in one request and the requirement is checked with the rest.
Fixed lists of bandwidth tiers, terms and headend sizes	Only with workarounds A value that is not on the list is usually caught only when the quote is saved or at the end, and different headend types have different lists.	Every value is checked against its list on every call, whatever order the choices arrive in.
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.

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.

1	A WAN bandwidth of 75 Mbps is not an available tier; the tiers are 10, 25, 50, 100, 250 and 500 Mbps and 1, 2, 5, 10, 20, 50 and 100 Gbps.
2	Subscription terms are 1, 3 or 5 years; the quote has 2 years.
3	The on-premises ZTNA add-on is not available with the Prime SD-WAN tier.
4	The Identity Engine add-on is not available with the Prime SD-WAN tier.
5	The XoT Fingerprinting add-on is not available with the Prime SD-WAN tier.
6	The Data Protection add-on is available only with the Premier Elite tier.
7	The Cloud ATP Sandboxing add-on is available only with the Premier Elite tier.
8	Stateful HA needs a tier with next-generation firewall or UTM capabilities; Prime SD-WAN does not include it.
9	6 sites are in an active-standby pair but the quote has only 4 sites.
10	The quote has 40 CPE licenses; 45 are needed, because every device including each standby needs its own license.
11	A headend capacity of 500 CPEs is not an available size for this headend type.
12	The quote has 300 CPE licenses; the selected headend supports 250 CPEs.
13	Advanced Logging Service is sold in 1 TB increments; the quote has 0 TB.
14	2 TB of logging is quoted without the Advanced Logging Service add-on.
15	The bandwidth tier is set from the 95th percentile of monthly usage; a person should confirm the sizing for 10,000 Mbps.