Predictika · IT management subscription orders

An AI sales agent's Kaseya 365 Endpoint order, checked before it goes out

An AI sales agent prepares an order for Kaseya 365 Endpoint: the Pro or Express edition, the number of endpoints, the RMM module, whether the customer needs managed detection and response and how much endpoint backup storage. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the editions and licensing terms Kaseya publishes and returns a verdict, every reason and the figures it computed.

Scope: Kaseya 365 Endpoint orders: Pro or Express edition, MDR, RMM module, new-customer minimum, upgrade license counts, committed term and shared backup storage. No prices are modeled. See everything this validator covers

This validator models orders for Kaseya 365 Endpoint as Kaseya publishes its editions and product terms, not just the scenarios shown below.

  • Editions and components — Pro includes all components including managed detection and response (MDR); Express has all components except MDR. An order that asks for MDR on Express is blocked.
  • RMM module — one subscription includes one of Datto RMM, VSA 10 or VSA 9, and VSA 9 is available only to current VSA 9 users.
  • Counts and term — a new customer must start with at least 50 endpoints; an existing customer's upgrade must match the component with the highest endpoint count and include current RocketCyber licenses; licenses cannot be decreased during the committed service term.
  • Backup storage — the subscription includes 5 TB of shared endpoint backup storage; a need above it goes to a person, because additional charges apply.

Any Kaseya 365 Endpoint order that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices (Kaseya does not publish them for this product, so the page shows no price build-up), Kaseya 365 User and Ops, other Kaseya products, partner tiers and the CORE program. Assumptions: the upgrade rule is read literally as an exact match, and the 5 TB is read as shared across the whole subscription.

The AI sales agentBuilds the endpoint order 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
MDR requested on the edition that excludes itOnly with care
A product rule per edition that has to be kept in step with the component list.		The edition and the need for MDR are in one request and checked on every call.
A minimum that applies only to new customersOnly with care
The 50-endpoint minimum depends on whether the customer already has components, so it needs a conditional rule on customer history.		Customer status and the endpoint count are compared on every call.
Upgrade counts tied to the customer's existing componentsOnly with workarounds
The count must match the highest existing component and include current RocketCyber licenses, so rules have to read several existing-licence fields at once.		The existing counts and the order are in one request and compared together.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the order 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.

    
1The order asks for managed detection and response, but the Express edition has all components except MDR; the Pro edition includes it.
2The order has 0 endpoints; at least 1 is needed.
3A new customer who does not subscribe to any components must start with at least 50 endpoints, but the order has 49.
4A new customer who does not subscribe to any components must start with at least 50 endpoints, but the order has 1.
5VSA 9 is available only to current VSA 9 users and cannot be bought as a new license.
6For an existing customer the license count of the upgrade must match the component with the highest endpoint count (250), but the order has 249.
7For an existing customer the license count of the upgrade must match the component with the highest endpoint count (250), but the order has 251.
8Current RocketCyber subscribers must include their existing 120 licenses in the upgrade, but the order has 100 endpoints.
9The number of Kaseya 365 licenses cannot be decreased for the rest of the committed service term, but the order has 100 against 120 now.
10The order needs 6 TB of endpoint backup storage, but the subscription includes 5 TB shared across the endpoints, and additional charges apply above that.
11The order needs 40 TB of endpoint backup storage, but the subscription includes 5 TB shared across the endpoints, and additional charges apply above that.
12A new customer who does not subscribe to any components must start with at least 50 endpoints, but the order has 20.

  

  

    
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. Edition and minimum: A new customer with 30 endpoints on Express, with MDR

    
The agent's request. Please quote Kaseya 365 Endpoint Express for 30 endpoints with Datto RMM, including managed detection and response and 3 TB of endpoint backup storage. The customer is new to Kaseya. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • New customer below the 50-endpoint minimum. A new customer who does not subscribe to any components must start with at least 50 endpoints, but the order has 30.
    • 
      
  • MDR needs the Pro edition. The order asks for managed detection and response, but the Express edition has all components except MDR; the Pro edition includes it.
    • 
    

    
2. Edition and minimum: The agent resubmits after fixing the errors

    
The agent's request. Please quote Kaseya 365 Endpoint Pro for 60 endpoints with Datto RMM, including managed detection and response and 3 TB of endpoint backup storage. The customer is new to Kaseya. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 60 endpoints, with 5 TB of shared backup storage included and 3 TB needed.
    • 
    

    
3. RMM and backup storage: A 120-endpoint order with VSA 9 and 8 TB of backup

    
The agent's request. Please quote Kaseya 365 Endpoint Pro for 120 endpoints with VSA 9, including managed detection and response and 8 TB of endpoint backup storage. The customer is new to Kaseya. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • VSA 9 is for current VSA 9 users only. VSA 9 is available only to current VSA 9 users and cannot be bought as a new license.
    • 
      
  • Backup storage above the included amount. The order needs 8 TB of endpoint backup storage, but the subscription includes 5 TB shared across the endpoints, and additional charges apply above that.
    • 
    

    
4. RMM and backup storage: The agent resubmits after fixing the errors

    
The agent's request. Please quote Kaseya 365 Endpoint Pro for 120 endpoints with VSA 10, including managed detection and response and 8 TB of endpoint backup storage. The customer is new to Kaseya. It is ready to send.

    
Verdict: Needs approval.

    
    
      
  • Backup storage above the included amount. The order needs 8 TB of endpoint backup storage, but the subscription includes 5 TB shared across the endpoints, and additional charges apply above that.
    • 
      
  • Order summary. 120 endpoints, with 5 TB of shared backup storage included and 8 TB needed.
    • 
    

    
5. RMM and backup storage: The agent resubmits after fixing the errors

    
The agent's request. Please quote Kaseya 365 Endpoint Pro for 120 endpoints with VSA 10, including managed detection and response and 5 TB of endpoint backup storage. The customer is new to Kaseya. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 120 endpoints, with 5 TB of shared backup storage included and 5 TB needed.
    • 
    

    
6. Upgrading a customer: An existing customer upgrading with 150 endpoints

    
The agent's request. Please quote Kaseya 365 Endpoint Pro for 150 endpoints with Datto RMM, including managed detection and response and 4 TB of endpoint backup storage. The customer already subscribes to Kaseya components, the largest at 200 endpoints, and has 120 RocketCyber licenses. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Upgrade count must match the highest component. For an existing customer the license count of the upgrade must match the component with the highest endpoint count (200), but the order has 150.
    • 
    

    
7. Upgrading a customer: The agent resubmits after fixing the errors

    
The agent's request. Please quote Kaseya 365 Endpoint Pro for 200 endpoints with Datto RMM, including managed detection and response and 4 TB of endpoint backup storage. The customer already subscribes to Kaseya components, the largest at 200 endpoints, and has 120 RocketCyber licenses. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 200 endpoints, with 5 TB of shared backup storage included and 4 TB needed.
    • 
    

  

  

    
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 an order for Kaseya 365 Endpoint: the Pro or Express edition, the number of endpoints, the RMM module, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the editions and licensing terms Kaseya publishes 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 Kaseya 365 Endpoint Express for 30 endpoints with Datto RMM, including managed detection and response and 3 TB of endpoint backup storage. The customer is new to Kaseya. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with two findings, all in one answer. A new customer who does not subscribe to any components must start with at least 50 endpoints, but the order has 30. The order asks for managed detection and response, but the Express edition has all components except MDR; the Pro edition includes it.
    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 a minimum that applies only to new customers, a rules-based CPQ is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the edition to pro and the endpoints to 60.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. This time the validator clears it.
    12. 
      
  12. Both earlier findings are cleared.
    13. 
      
  13. 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.
    14.