Predictika · Enterprise Agreement and Splunk licensing quotes

An AI sales agent's Enterprise Agreement quote, checked before it goes out

An AI sales agent prepares a software agreement for a customer: a multi-portfolio Enterprise Agreement, a Secure Choice security agreement or a Splunk licensing quote. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the program rules and returns a verdict, every reason and the figures it computed.

Scope: Enterprise Agreement 3.0, Secure Choice Enterprise Agreement and Splunk licensing quotes. See everything this validator covers

This validator models Enterprise Agreement, Secure Choice and Splunk licensing quotes, not just the scenarios shown below.

Where the figures come from. The multi-suite discount schedule (5, 10, 15, 18 and 20 percent for 2, 3, 4, 5 and 6 or more suites), the 20 percent Secure Choice growth allowance and the two-suite and 100-user minimums follow Cisco's published Secure Choice Enterprise Agreement FAQ. Counting eligible Cisco telemetry at half weight follows Splunk's published “Integrated Enterprise Value for Cisco data” page, which applies it to the Splunk Enterprise and Splunk Cloud Platform ingest licenses. Predictika model assumptions, not Cisco or Splunk policy: sending workload licensing to approval, and checking Splunk on its own licensing rules rather than as a suite inside an Enterprise Agreement.

  • Enterprise Agreement 3.0 — Minimum contract value, 3 or 5 year terms, entry rules across portfolios (Partial Commit security suites need a Full Commit suite, Services need an underlying suite), growth allowance by portfolio, co-terming of added orders, start date window, no scaling down, cross-suite value shift conditions, partner rules and the multi-suite discount.
  • Secure Choice — Two-suite minimum (or one plus a qualifying suite from another agreement), 100 security users, the 5 to 20 percent multi-suite discount schedule, the 20 percent growth allowance and the rule that value shifts only within a suite.
  • Splunk licensing — Which licensing models go with Splunk Cloud Platform and Splunk Enterprise, billable ingest with Cisco telemetry at half weight, and Enterprise Security Premier features.

Any Enterprise Agreement, Secure Choice or Splunk licensing quote that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices (neither Cisco nor Splunk publishes Enterprise Agreement or enterprise list prices, so this validator produces no price build-up or line-item quote), Catalyst switching quotes, other Cisco agreements and Cisco Commerce itself. Assumptions: Splunk is checked on its own licensing rules, not as a suite inside an Enterprise Agreement; workload licensing goes to approval because sizing by search load is not modeled; Enterprise Agreement multi-suite discount percentages are not published, so any stated figure goes to pricing approval.

The AI sales agentBuilds the agreement 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

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
Multi-suite discount that depends on how many suites are bought (5, 10, 15, 18 or 20 percent), and a quote that states its own discountOnly with care
A discount table can be built, but a stated discount is usually a free-entry field, so a rule has to compare it with the table and be kept in step when the schedule changes.		The stated discount travels with the quote and is compared with the earned discount on every call.
Growth allowance that differs by agreement and portfolio (none in some portfolios, 15 percent in others, 20 percent in Secure Choice)Only with care
One rule per agreement and portfolio, each tied to a growth figure the rep types in. Works, but every new exception is another rule to maintain.		The allowance is computed from the agreement and portfolio and compared with what the quote asks.
Entry rules that depend on what else is in the agreement: Partial Commit security suites need a Full Commit suite elsewhere, Services need an underlying suiteOnly with workarounds
Each rule looks across lines in different portfolios. In a line-by-line product rule set, this takes cross-line checks that interact with each other.		All suites are in one request and every entry rule is checked together.
An added order that must co-term with an agreement already in force, with a final-year exceptionOnly with workarounds
The months remaining live on the existing agreement, not on the new order, so a rule needs that figure copied onto the quote.		The months remaining travel with the request and are compared with the order term.
Splunk billable ingest where Cisco telemetry counts at half weight, and which licensing models each deployment offersOnly with care
A weighted-sum rule is possible, but the stated billable figure has to be a field on the quote to be checked at all.		The stated figure is compared with the weighted sum computed from the two ingest volumes.
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.

    
1an Enterprise Agreement needs at least $100,000 net contract value; the quote has $85,000.
2Enterprise Agreement terms are 3 or 5 years; the quote has 4 years.
3Partial Commit security suites need a Full Commit suite in Networking, Applications or Collaboration, or a Full Commit security suite; the quote has 2 Partial Commit security suite(s) and no Full Commit suite.
4a Services suite is sold only with an underlying suite; the quote has 1 Services suite(s) and no underlying suite.
5the quote asks 20 percent growth at no charge; the allowance for this agreement and portfolio is 15 percent.
6an added order must co-term with the agreement; the order runs 36 months and the agreement has 22 months left.
7the requested start date can be at most 90 days after the order; the quote asks 120 days.
8quantities cannot be scaled down once the agreement is entered.
9cross-suite value shift needs at least 60 days notice before the True Forward event and suites bought from the same partner on the initial order.
102 partners in one portfolio is allowed only as an exception and can forfeit some EA benefits.
11Secure Choice needs at least 100 security users; the quote has 50.
12the quote states a 15 percent multi-suite discount; 3 suites earn 10 percent.
13in Secure Choice, unused license value can shift only within the same suite, not across suites.
14Splunk Enterprise is offered on ingest or workload licensing; activity-based licensing is a Splunk Cloud Platform option.
15the quote states 600 GB per day of billable ingest; 400 GB of other data plus 200 GB of Cisco telemetry at half weight gives 500 GB.
16SOAR and UEBA come with Enterprise Security Premier; the quote has the Essentials edition.

  

  

    
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. Enterprise Agreement structure: Partial Commit security suites with no Full Commit suite

    
The agent's request. Please quote a 5-year Cisco Enterprise Agreement with a net contract value of $1,250,000: 3 Partial Commit security suites and one Services suite, with one partner. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Security suites need a Full Commit suite. Partial Commit security suites need a Full Commit suite in Networking, Applications or Collaboration, or a Full Commit security suite; the quote has 3 Partial Commit security suite(s) and no Full Commit suite.
    • 
    

    
2. Enterprise Agreement structure: The agent resubmits after fixing the errors

    
The agent's request. Please quote a 5-year Cisco Enterprise Agreement with a net contract value of $1,250,000: one Full Commit Networking suite, 3 Partial Commit security suites and one Services suite, with two partners in the security portfolio. It is ready to send.

    
Verdict: Needs approval.

    
    
      
  • Second partner needs approval. 2 partners in one portfolio is allowed only as an exception and can forfeit some EA benefits.
    • 
      
  • Agreement summary. Enterprise Agreement for 5 years with 1 Full Commit suite(s) outside security and 0 Full Commit and 3 Partial Commit security suite(s); growth allowance 0 percent.
    • 
    

    
3. Enterprise Agreement structure: The agent resubmits after fixing the errors

    
The agent's request. Please quote a 5-year Cisco Enterprise Agreement with a net contract value of $1,250,000: one Full Commit Networking suite, 3 Partial Commit security suites and one Services suite, with one partner. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Agreement summary. Enterprise Agreement for 5 years with 1 Full Commit suite(s) outside security and 0 Full Commit and 3 Partial Commit security suite(s); growth allowance 0 percent.
    • 
    

    
4. Secure Choice terms: Discount and growth misstated

    
The agent's request. Please quote a 3-year Cisco Secure Choice Enterprise Agreement with 4 security suites for 4,200 security users, with a 20 percent multi-suite discount and 25 percent growth at no charge. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Growth allowance exceeded. The quote asks 25 percent growth at no charge; the allowance for this agreement and portfolio is 20 percent.
    • 
      
  • Quoted discount does not match. The quote states a 20 percent multi-suite discount; 4 suites earn 15 percent.
    • 
    

    
5. Secure Choice terms: The agent resubmits after fixing the errors

    
The agent's request. Please quote a 3-year Cisco Secure Choice Enterprise Agreement with 4 security suites for 4,200 security users, with a 15 percent multi-suite discount and 20 percent growth at no charge. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Agreement summary. 4 Secure Choice suites earn a 15 percent multi-suite discount and a 20 percent growth allowance.
    • 
    

    
6. Splunk licensing: Billable ingest misstated and SOAR on the wrong edition

    
The agent's request. Please quote Splunk Cloud Platform on ingest licensing for 1,200 GB per day of other data and 800 GB per day of Cisco telemetry, with Enterprise Security Essentials, including SOAR and UEBA. The quote states 2,000 GB per day of billable ingest. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Billable ingest does not match. The quote states 2,000 GB per day of billable ingest; 1,200 GB of other data plus 800 GB of Cisco telemetry at half weight gives 1,600 GB.
    • 
      
  • SOAR and UEBA need Premier. SOAR and UEBA come with Enterprise Security Premier; the quote has the Essentials edition.
    • 
    

    
7. Splunk licensing: The agent resubmits after fixing the errors

    
The agent's request. Please quote Splunk Cloud Platform on ingest licensing for 1,200 GB per day of other data and 800 GB per day of Cisco telemetry, with Enterprise Security Premier, including SOAR and UEBA. The quote states 1,600 GB per day of billable ingest. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Agreement summary. 1,200 GB per day of other data plus 800 GB of Cisco telemetry at half weight is 1,600 GB of billable ingest per day.
    • 
    

  

  

    
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 software agreement for a customer: a multi-portfolio Enterprise Agreement, a Secure Choice security agreement or a Splunk licensing quote. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the program rules and returns a verdict, every reason and the figures it computed.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. Please quote a 5-year Cisco Enterprise Agreement with a net contract value of $1,250,000: 3 Partial Commit security suites and one Services suite, with one partner. It is ready to send.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with one finding, all in one answer. Partial Commit security suites need a Full Commit suite in Networking, Applications or Collaboration, or a Full Commit security suite; the quote has 3 Partial Commit security suite(s) and no Full Commit suite.
    6. 
      
  6. The validator returned one blocking finding 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. 
      
  7. What this shows: for entry rules that depend on what else is in the agreement: Partial Commit security suites need a Full Commit suite elsewhere, Services need an underlying suite, a rules-based CPQ can do this only with workarounds.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the Full Commit suites outside security to 1 and the partners in the portfolio to 2.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. Not blocked, but held for a person.
    12. 
      
  12. The one blocking finding is cleared; one approval remains for a person: second partner needs approval.
    13. 
      
  13. The agent resubmits once more.
    14. 
      
  14. The revised request. It changes the partners in the portfolio to 1.
    15. 
      
  15. It calls the validator once more.
    16. 
      
  16. This time the validator clears it.
    17. 
      
  17. The earlier finding is cleared.
    18. 
      
  18. One problem caught in one call, fixed in two passes, 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.
    19.