Predictika · hyperconverged server nodes, software license editions, purchase programs, core count per node, options and subscription years

An AI sales agent's cloud infrastructure cluster quote, checked before it goes out

An AI sales agent prepares a cloud infrastructure cluster quote for a fictional customer. Before it goes out, the agent sends it to Predictika’s validator, which checks it against the product and contract rules, compares the net total the agent states with the one it computes, and returns a verdict with every reason.

Scope: cloud infrastructure cluster quotes for the Cloud Infrastructure Clusters product line. See everything this validator covers

This validator models cloud infrastructure cluster quotes in the style of Nutanix: four server node types, three software license editions and three purchase programs. It handles any quote made of these products and contracts, not just the scenarios shown below.

  • Server nodes and license editions — A single-socket hybrid, a dual-socket hybrid, a dual-socket all-NVMe and a quad-socket high-memory all-NVMe node, with a Starter, a Pro or an Ultimate software license edition, including the editions that do not include the NVMe storage features the all-NVMe nodes need.
  • Cores per node — A licensed core count per node, checked against the node rating and the edition rating, with a licensing desk review above 96 cores per node.
  • Options and purchase programs — A GPU acceleration kit by node type and a disaster recovery add-on license, and list purchase, partner volume program and enterprise license agreement programs with their node minimums and discounts.
  • Subscription term, cluster size and stated total — Terms from 1 to 5 years that co-term the licenses and support, a finance review above 3 years, a cluster design review above 8 nodes, an approval band above 12 percent total discount, a limit at 20 percent, a deal desk review above USD 1,200,000, and a check that the net total the agent states matches the total the validator computes.

It does not cover other Nutanix products such as database, file or Kubernetes platform services, real list prices, sizing and architecture decisions, or tax and multi-currency quoting.

The AI sales agentBuilds the quote from the conversation and says it is ready.
Predictika validatorChecks the quote against the product and contract rules and returns every finding it has.

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 or Revenue Cloud) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.

    
What the validator catchesTypical rules-based CPQPredictika
Server node and Software license edition compatibilityOnly with workarounds
A pairwise compatibility between two catalogs usually becomes one rule per combination.		Compatibility is a property of the items, checked on every call.
Core count per node against two limitsOnly with care
A number that must fit two limits spans several validation rules.		Both limits and the review band are evaluated together.
Options by server nodeOnly with care
Option availability differs by item, so option rules multiply.		Each option is checked against the item property directly.
Purchase program minimums and discountsOnly with workarounds
A contract with its own minimum and discount interacts with volume discounts and approval rules.		The minimum, the contract discount and the total are all evaluated.
The total the agent statesOnly with workarounds
Comparing a stated total with a computed one means a separate rule per quote layout, and price rules rarely run on stated figures.		The stated net total is a field in the request and is checked against the computed total.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the quote 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
Click to expand
    
Every rule is checked on every call, in whatever order the choices arrive, and one problem never hides another. Blocking findings stop the quote; approval findings need a person to sign off; everything else is computed.

    
RuleEffectWhat it checks
Quantityblock1 to 16 nodes
Contract minimumblockAt least the purchase program minimum nodes
Core count per node vs server nodeblock1 to the item maximum
Core count per node vs software license editionblockNot above the package limit
Compatibilityblockthe package does not include the NVMe storage features the all-NVMe nodes need.
Gpu acceleration kitblockOnly on items that offer it
Disaster recovery add-on licenseblockOnly on items that offer it
Contract yearsblock1 to 5 years
Total discount limitblockAbove 20 percent
Stated net totalblockAgent-stated net total differs from the computed total by more than USD 1
Core count per node reviewneeds approvalAbove 96: a licensing desk core count review is required
Long contractneeds approvalAbove 3 years needs finance approval
Large quantityneeds approvalAbove 8 nodes: a cluster design review is required
Discount approvalneeds approvalTotal above 12 percent within the limit
Large orderneeds approvalAbove USD 1200000 needs deal desk review

  

  

    
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. Cores and options: Single-socket, 48 cores

    
The agent's request. 3 single-socket hybrid nodes with the Pro license edition for 48 cores per node, plus the GPU acceleration kit. List purchase, 2-year term. Net total USD 196,800. Ready to send.

    
Verdict: Blocked.

    
    
      
  • Core Count Per Node Limit. A core count per node of 48 is outside the 1 to 32 range of the Single-socket hybrid node.
    • 
      
  • Gpu Acceleration Kit. The GPU acceleration kit is not available on the Single-socket hybrid node.
    • 
    

    
2. Cores and options: Dual-socket, 48 cores

    
The agent's request. 3 dual-socket hybrid nodes with the Pro license edition for 48 cores per node, plus the GPU acceleration kit. List purchase, 2-year term. Net total USD 244,800. Ready to send.

    
Verdict: Allowed.

    
3. Contract term and discount: Partner program, 6-year term

    
The agent's request. 4 dual-socket hybrid nodes with the Pro license edition on the partner volume program for 48 cores per node, 6-year term, with a 14 percent extra discount. Net total USD 220,896. Ready to send.

    
Verdict: Blocked.

    
    
      
  • Contract Term. A contract of 6 years is outside the 1 to 5 years allowed.
    • 
      
  • Discount Limit. Total discount of 22 percent exceeds the 20 percent limit.
    • 
    

    
4. Contract term and discount: Partner program, 3-year term

    
The agent's request. 4 dual-socket hybrid nodes with the Pro license edition on the partner volume program for 48 cores per node, 3-year term, with a 4 percent extra discount. Net total USD 230,208. Ready to send.

    
Verdict: Allowed.

    
5. The total the agent states: Stated total below computed

    
The agent's request. 3 single-socket hybrid nodes with the Starter license edition for 24 cores per node, plus the disaster recovery add-on license. List purchase, 2-year term. Net total USD 128,520. Ready to send.

    
Verdict: Blocked.

    
    
      
  • Quoted Net Total. The quoted net total of USD 128520.0 does not match the USD 142800.0 the validator computed.
    • 
    

    
6. The total the agent states: Stated total corrected

    
The agent's request. 3 single-socket hybrid nodes with the Starter license edition for 24 cores per node, plus the disaster recovery add-on license. List purchase, 2-year term. Net total USD 142,800. Ready to send.

    
Verdict: Allowed.

    
7. Review by a person: 9 nodes, 90 cores

    
The agent's request. 9 quad-socket high-memory all-NVMe nodes with the Ultimate license edition, list purchase, for 90 cores per node, 2-year term. Net total USD 1,235,160. Ready to send.

    
Verdict: Needs approval.

    
    
      
  • Large Quantity. A quantity of 9 is above 8 nodes; a cluster design review is required.
    • 
      
  • Large Order. Order value of USD 1235160.0 is above USD 1200000 and needs a deal desk review.
    • 
    

  

  

    
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 cloud infrastructure cluster quote for a fictional customer. Before it goes out, the agent sends it to Predictika’s validator, which checks it against the product and contract rules, compares the net total the agent states with the one it computes, and returns a verdict with every reason.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. 3 single-socket hybrid nodes with the Pro license edition for 48 cores per node, plus the GPU acceleration kit. List purchase, 2-year term. The rest of the request is on screen. Net total USD 196,800.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with two findings, all in one answer. A core count per node of 48 is outside the 1 to 32 range of the single-socket hybrid node. The GPU acceleration kit is not available on the single-socket hybrid node.
    6. 
      
  6. The validator returned two 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. 
      
  7. What this shows: for core count per node against two limits, a rules-based CPQ is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the pa to dual-socket hybrid node and the stated net as to 244800.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. This time the validator clears it.
    12. 
      
  12. The validator also returns the line-item quote. It starts with Dual-socket hybrid node and Pro license edition; the other two lines are on screen.
    13. 
      
  13. Both earlier findings are cleared, and the validator's total, USD 244,800, matches the quote.
    14. 
      
  14. Two 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.
    15.