Predictika · Email and collaboration security subscriptions

An AI sales agent's Proofpoint security subscription quote, checked before it goes out

An AI sales agent prepares a quote for a Proofpoint Collaboration Security package (Core, Tier 2, Tier 3 or Prime) with add-ons such as Account Takeover Protection, ZenGuide, Email Fraud Defense, Secure Email Relay, Adaptive Email DLP and Email Encryption. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the packages and returns a verdict, every reason and the figures it computed.

Scope: Proofpoint Collaboration Security packages (Core, Tier 2, Tier 3, Prime) with add-ons: users, term, deployment, included versus add-on products, discount. See everything this validator covers

This validator models Proofpoint package subscription quotes, not just the scenarios shown below.

  • Packages and what each includes — each package builds on the one before: Core Email Protection, Tier 2 adds account takeover and supplier protection and security for messaging tools, Tier 3 adds automated training, Prime adds domain fraud prevention and hosted email authentication. Add-ons for products a package already includes are caught.
  • Needs the package must meet — messaging protection, hosted email authentication (DMARC, DKIM, SPF) and the add-ons that can fill the gap.
  • Deployment, users and term — Adaptive Email DLP through the API deployment, Email Encryption at the gateway, minimum users per package, DLP users within licensed users, and a term of 1 to 5 years.
  • Discount and approvals — a discount ceiling, sales-management approval above a threshold that depends on the term, very large deployments, and the stated user count against the licensed users.

Any Proofpoint package subscription quote that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices (none are modeled, so this validator produces no price build-up or line-item quote), Proofpoint Essentials plans, archiving and other product lines, and professional services. Package names and what each package adds come from Proofpoint's public pages; the minimum users, term limits, discount thresholds and deployment dependencies are modeled from comparable security subscriptions and are not Proofpoint's published rules.

The AI sales agentBuilds the subscription quote from the customer's security needs 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

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 product that one package already includes and another sells as an add-onOnly with care
A product rule per add-on that compares the package with the add-on; it works, but it must be kept in step as packages change.
Included-versus-add-on is checked for every add-on on every call.
A need that only some packages or add-ons meet: messaging protection, hosted email authenticationOnly with workarounds
The need sits on one line and the product that satisfies it on another, so a cross-line rule is needed per need.
The needs, package and add-ons are in one request and checked together.
Add-ons that depend on how the service is deployedOnly with workarounds
DLP through the API and encryption at the gateway are conditions between a deployment choice and an add-on; each is another rule.
Deployment and add-ons are checked against each other with the rest.
A discount threshold that depends on the termOnly with care
Approval limits that vary by term are usually a table of rules that someone has to maintain.
The threshold is derived from the term and applied with every other check.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as a step is saved, 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.

1The customer needs protection for messaging tools such as Teams and Slack; the Core package covers email only.
2Account Takeover Protection is already included in Tier 2 and above; remove the add-on.
3ZenGuide training is already included in Tier 3 and above; remove the add-on.
4Email Fraud Defense is already included in Prime; remove the add-on.
5Secure Email Relay is already included in Prime; remove the add-on.
6The customer needs hosted email authentication (DMARC, DKIM, SPF); that comes with Prime or the Email Fraud Defense add-on, and the quote has neither.
7Adaptive Email DLP works through the API deployment; the quote uses the gateway (SEG) only.
8The quote covers 600 users with Adaptive Email DLP but only 500 users are licensed.
9Email Encryption is applied at the gateway (SEG); the quote uses the API deployment only.
10The quote has 99 users; this package needs at least 100.
11The quote has 200 users; this package needs at least 250.
12The quote states 450 users; the licensed users are 500.
13The term is 6 years; this model allows 1 to 5 years.
14The discount is 36 percent; the most this model allows is 35 percent.
15The discount is 35 percent; discounts above 20 percent for this term need sales-management approval.
16The discount is 11 percent; discounts above 10 percent for this term need sales-management approval.
17The quote covers more than 10,000 users; a person should confirm the deployment plan and support arrangements.
18Prime is quoted on a one-year term; a person should confirm the customer does not want a longer commitment.

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. Package fit: A Core quote where the customer also needs messaging protection and hosted authentication

The agent's request. Please quote the Core package for 500 users on a 3-year term with API and gateway deployment and a 10 percent discount. The customer needs protection for Teams and Slack and hosted email authentication. The quote states 450 users. It is ready to send.

Verdict: Blocked.

  • Stated users do not match. The quote states 450 users; the licensed users are 500.
  • Messaging protection needs Tier 2 or above. The customer needs protection for messaging tools such as Teams and Slack; the Core package covers email only.
  • Hosted email authentication needs Prime or Email Fraud Defense. The customer needs hosted email authentication (DMARC, DKIM, SPF); that comes with Prime or the Email Fraud Defense add-on, and the quote has neither.

2. Package fit: The agent resubmits after fixing the errors

The agent's request. Please quote the Prime package for 500 users on a 3-year term with API and gateway deployment and a 10 percent discount. The customer needs protection for Teams and Slack and hosted email authentication. The quote states 500 users. It is ready to send.

Verdict: Allowed.

  • Subscription summary. Prime package for 500 users on a 3-year term, Both deployment, 10 percent discount.

3. Add-ons and discount: A Tier 3 quote with a duplicate add-on, DLP on a gateway-only deployment and a deep discount

The agent's request. Please quote the Tier 3 package for 1,200 users on a 3-year term with the gateway (SEG) deployment and a 38 percent discount, adding ZenGuide, Adaptive Email DLP for 800 users. The quote states 1,200 users. It is ready to send.

Verdict: Blocked.

  • ZenGuide already included. ZenGuide training is already included in Tier 3 and above; remove the add-on.
  • Adaptive Email DLP needs API deployment. Adaptive Email DLP works through the API deployment; the quote uses the gateway (SEG) only.
  • Discount above the maximum. The discount is 38 percent; the most this model allows is 35 percent.

4. Add-ons and discount: The agent resubmits after fixing the errors

The agent's request. Please quote the Tier 3 package for 1,200 users on a 3-year term with API and gateway deployment and a 25 percent discount, adding Adaptive Email DLP for 800 users. The quote states 1,200 users. It is ready to send.

Verdict: Needs approval.

  • Discount needs sales-management approval. The discount is 25 percent; discounts above 20 percent for this term need sales-management approval.
  • Subscription summary. Tier 3 package for 1,200 users on a 3-year term, Both deployment, 25 percent discount.

5. Add-ons and discount: The agent resubmits after fixing the errors

The agent's request. Please quote the Tier 3 package for 1,200 users on a 3-year term with API and gateway deployment and a 15 percent discount, adding Adaptive Email DLP for 800 users. The quote states 1,200 users. It is ready to send.

Verdict: Allowed.

  • Subscription summary. Tier 3 package for 1,200 users on a 3-year term, Both deployment, 15 percent discount.

6. Prime and term: A Prime quote with an add-on it already includes and a seven-year term

The agent's request. Please quote the Prime package for 3,000 users on a 7-year term with API and gateway deployment and a 15 percent discount, adding Email Fraud Defense. The customer needs protection for Teams and Slack and hosted email authentication. The quote states 3,000 users. It is ready to send.

Verdict: Blocked.

  • Term outside 1 to 5 years. The term is 7 years; this model allows 1 to 5 years.
  • Email Fraud Defense already included. Email Fraud Defense is already included in Prime; remove the add-on.

7. Prime and term: The agent resubmits after fixing the errors

The agent's request. Please quote the Prime package for 3,000 users on a 5-year term with API and gateway deployment and a 15 percent discount. The customer needs protection for Teams and Slack and hosted email authentication. The quote states 3,000 users. It is ready to send.

Verdict: Allowed.

  • Subscription summary. Prime package for 3,000 users on a 5-year term, Both deployment, 15 percent discount.

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 quote for a Proofpoint Collaboration Security package (Core, Tier 2, Tier 3 or Prime). Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the packages and returns a verdict, every reason and the figures it computed.
  2. I will start with the first request by the agent.
  3. The agent says. Please quote the Core package for 500 users on a 3-year term with API and gateway deployment and a 10 percent discount. The customer needs protection for Teams and Slack and hosted email authentication. The rest of the request is on screen. The quote states 450 users.
  4. Before it goes out, the agent calls the validator.
  5. Blocked, with three findings, all in one answer. The quote states 450 users; the licensed users are 500. The customer needs protection for messaging tools such as Teams and Slack; the Core package covers email only. The customer needs hosted email authentication, such as DMARC and DKIM; that comes with Prime or the Email Fraud Defense add-on, and the quote has neither.
  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 a need that only some packages or add-ons meet: messaging protection, hosted email authentication, a rules-based CPQ can do this only with workarounds.
  8. Now the agent resubmits.
  9. The corrected request. It changes the package to prime and the stated users to 500.
  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.