Predictika · Cloud marketplace subscription orders

An AI sales agent's cloud subscription order, checked before it goes out

An AI sales agent prepares a subscription order for a cloud marketplace: the plan, the billing term, the tenants and seats, add-on services such as cloud management, premium support, Azure deployment and branded invoices, and the partner discount. Before the order goes out, the agent sends it to Predictika, which checks it against a declarative model of what each plan and service allows and returns a verdict, every reason and the seat total it computed.

Scope: Microsoft 365 Business, E3 and E5, Windows 365 Business and Enterprise and Acronis Cyber Protect Cloud seats ordered through the ALSO Cloud Marketplace, with its value-added services: plan limits, billing term, add-on prerequisites, seat totals and discount. See everything this validator covers

This validator models cloud marketplace subscription orders for these plans and services, not just the scenarios shown below.

  • Plan and term — Business plans have a per-tenant user cap, a three-year term applies only to Microsoft 365 plans, and Windows 365 Enterprise needs a base license on the order.
  • Add-on services — Cloud Management Service and Premium Support apply from a minimum order size, Azure deployment needs an Azure subscription, and white labeling needs the Billing Service.
  • Seat totals — the total the order states is compared with the total computed from tenants and seats per tenant.
  • Discount and size — a partner discount above 15 percent needs a manager and one above 30 percent is blocked, and a very large order needs a capacity and credit check.

Any subscription order that touches these rules is in scope — not only the scenarios pictured here. Not covered: hardware distribution, financing and Azure consumption pricing. Plan and service names follow public ALSO, Microsoft and Acronis pages. No prices are modeled, and the limits, minimums and approval thresholds are modeled from comparable cloud marketplace practice, not published by ALSO.

The AI sales agentBuilds the subscription order from the conversation with the customer and says it is ready.
Predictika validatorChecks every rule at once and returns the verdict, each finding, and the computed figures.

6 scenarios in 2 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
Add-on services with prerequisitesOnly with care
Cloud management, premium support, Azure deployment and branded invoices each depend on something else on the order, so a dependency rule is needed for every add-on and is easy to leave out when one is added.		Every add-on is checked against the rest of the order on every call.
Plan, term and size limits togetherOnly with workarounds
Which term a plan allows, the user cap on Business plans and the minimum size for a service are separate rules that depend on several choices at once.		The plan, term and size are checked in the same pass, and each finding says which one was missed.
A seat total reconciled with a stated oneOnly with workarounds
The total comes from tenants and seats per tenant, and a separate calculation is needed to compare it with the figure the order states.		The total is computed inside the model and compared with the stated one on every call.
Discount and large-order thresholdsOnly with care
A discount has a sign-off level and a blocking level, and a large order is an approval rather than an error, so the rules must be ordered and kept apart.		Every threshold is checked in the same pass, and each finding says whether it blocks or needs a person.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the order is saved or a step is completed, so a person 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 order; approval findings need a person to sign off; everything else is computed.

    
1Business and Windows 365 Business plans are limited to 300 users per tenant; the order has 301 per tenant.
2A three-year term is modeled only for Microsoft 365 plans; this plan is offered monthly or annually.
3Windows 365 Enterprise needs a qualifying Windows/Microsoft 365 base license on the order.
4Cloud Management Service is modeled for orders of 25 seats or more; the order has 20.
5Microsoft Azure Deployment needs an Azure subscription on the order.
6Premium Support is modeled for orders of 50 seats or more; the order has 40.
7Branded invoices and white labeling need the ACMP Billing Service on the order.
8The order states 180 seats in total; the tenants and seats give 200.
9A partner discount of 16 percent is above 15 percent and needs a manager to approve.
10A partner discount of 31 percent is above the 30 percent ceiling.
11The order has 0 seats per tenant; at least 1 is needed.
12An order of 5,000 seats needs a manager to confirm capacity and credit.

  

  

    
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. Windows 365 Enterprise order with add-ons: Windows 365 Enterprise order with a three-year term, add-on services and a partner discount

    
The agent's request. Please place a three-year Windows 365 Enterprise subscription order for 2 tenants with 10 seats each, with Cloud Management Service, Premium Support, Microsoft Azure Deployment and white labeling, at a partner discount of 20 percent. The order states 20 seats in total. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Three-year term not available. A three-year term is modeled only for Microsoft 365 plans; this plan is offered monthly or annually.
    • 
      
  • Windows 365 Enterprise needs a base license. Windows 365 Enterprise needs a qualifying Windows/Microsoft 365 base license on the order.
    • 
      
  • Cloud Management Service minimum. Cloud Management Service is modeled for orders of 25 seats or more; the order has 20.
    • 
      
  • Azure Deployment needs an Azure subscription. Microsoft Azure Deployment needs an Azure subscription on the order.
    • 
      
  • Premium Support minimum. Premium Support is modeled for orders of 50 seats or more; the order has 20.
    • 
      
  • White label needs the Billing Service. Branded invoices and white labeling need the ACMP Billing Service on the order.
    • 
      
  • Discount to approve. A partner discount of 20 percent is above 15 percent and needs a manager to approve.
    • 
    

    
2. Windows 365 Enterprise order with add-ons: The agent resubmits after fixing the errors

    
The agent's request. Please place a three-year Microsoft 365 E5 subscription order for 2 tenants with 10 seats each, with Cloud Management Service, Premium Support, Microsoft Azure Deployment and white labeling, and an Azure subscription on the order, and the ACMP Billing Service, at a partner discount of 20 percent. The order states 20 seats in total. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Cloud Management Service minimum. Cloud Management Service is modeled for orders of 25 seats or more; the order has 20.
    • 
      
  • Premium Support minimum. Premium Support is modeled for orders of 50 seats or more; the order has 20.
    • 
      
  • Discount to approve. A partner discount of 20 percent is above 15 percent and needs a manager to approve.
    • 
    

    
3. Windows 365 Enterprise order with add-ons: The agent resubmits after fixing the errors

    
The agent's request. Please place a three-year Microsoft 365 E5 subscription order for 2 tenants with 30 seats each, with Cloud Management Service, Premium Support, Microsoft Azure Deployment and white labeling, and an Azure subscription on the order, and the ACMP Billing Service, at a partner discount of 15 percent. The order states 60 seats in total. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 2 tenant(s) with 30 seats each, 60 seats in total, 15 percent discount.
    • 
    

    
4. Seat total that does not add up: Windows 365 Enterprise order for three tenants whose stated seat total is short

    
The agent's request. Please place an annual Windows 365 Enterprise subscription order for 3 tenants with 150 seats each, at a partner discount of 10 percent. The order states 400 seats in total. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Windows 365 Enterprise needs a base license. Windows 365 Enterprise needs a qualifying Windows/Microsoft 365 base license on the order.
    • 
      
  • Stated seats do not match. The order states 400 seats in total; the tenants and seats give 450.
    • 
    

    
5. Seat total that does not add up: The agent resubmits after fixing the errors

    
The agent's request. Please place an annual Windows 365 Enterprise subscription order for 3 tenants with 150 seats each, with a qualifying base license on the order, at a partner discount of 22 percent. The order states 450 seats in total. It is ready to send.

    
Verdict: Needs approval.

    
    
      
  • Discount to approve. A partner discount of 22 percent is above 15 percent and needs a manager to approve.
    • 
      
  • Order summary. 3 tenant(s) with 150 seats each, 450 seats in total, 22 percent discount.
    • 
    

    
6. Seat total that does not add up: The agent resubmits after fixing the errors

    
The agent's request. Please place an annual Windows 365 Enterprise subscription order for 3 tenants with 150 seats each, with a qualifying base license on the order, at a partner discount of 12 percent. The order states 450 seats in total. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Order summary. 3 tenant(s) with 150 seats each, 450 seats in total, 12 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 subscription order for a cloud marketplace: the plan, the billing term, the tenants and seats, and more. Before the order goes out, the agent sends it to Predictika, which checks it against a declarative model of what each plan and service allows and returns a verdict, every reason and the seat total it computed.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. Please place a three-year Windows 365 Enterprise subscription order for 2 tenants with 10 seats each, with Cloud Management Service. The order states 20 seats in total. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with six findings and one approval, all in one answer. A three-year term is modeled only for Microsoft 365 plans; this plan is offered monthly or annually. Windows 365 Enterprise needs a qualifying Windows/Microsoft 365 base license on the order. Cloud Management Service is modeled for orders of 25 seats or more; the order has 20. The other three are on screen.
    6. 
      
  6. The validator returned six blocking findings and one approval 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 order are checked against each other.
    7. 
      
  7. What this shows: for add-on services with prerequisites, a rules-based CPQ is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the plan to Microsoft 365 E5. It sets the Azure subscription on the order to yes and the ACMP Billing Service to yes.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. Still blocked, with two findings and one approval, all in one answer. Cloud Management Service is modeled for orders of 25 seats or more; the order has 20. Premium Support is modeled for orders of 50 seats or more; the order has 20.
    12. 
      
  12. Four findings cleared. Still blocking: Cloud Management Service minimum and Premium Support minimum. One approval also remains for a person: discount to approve.
    13. 
      
  13. The agent resubmits once more.
    14. 
      
  14. The revised request. It changes the seats per tenant to 30, the partner discount to 15 percent and the total seats stated on the order to 60.
    15. 
      
  15. It calls the validator once more.
    16. 
      
  16. This time the validator clears it.
    17. 
      
  17. All three earlier findings are cleared.
    18. 
      
  18. Seven problems caught in one call, fixed in two passes, and a clean order. That is the value of Predictika's validator: catching mistakes before they reach the customer. Now you can try the other scenarios yourself.
    19.