Predictika · cloud subscription quotes, in the style of Atlassian

A cloud subscription quote, checked against the edition, term, add-on and discount rules before it goes to the customer

An AI sales agent prepares a cloud subscription quote (Jira Software, Confluence or Jira Service Management) with the order total it expects. Before the quote goes out, the agent sends it to Predictika's validator, which checks the edition, user count, term, data residency, security add-on, marketplace apps and discount against each other, compares the total the agent states with the one it computes, and returns a verdict with every reason in one pass. All prices and limits are Predictika estimates in US dollars, not Atlassian list prices.

Scope: Cloud subscription quotes for three products (Jira Software, Confluence and Jira Service Management) in Standard, Premium and Enterprise editions: user limits and minimums, annual and monthly terms, regional data residency, the Guard add-on, marketplace apps, volume discounts and approval bands. Prices and limits are illustrative estimates, not Atlassian data; Predictika is not affiliated with Atlassian. See everything this validator covers

This validator checks any quote for these products and editions, not just the scenarios shown below.

  • Products and editions — Jira Software, Confluence and Jira Service Management in the Standard, Premium and Enterprise editions, each with its own user limit and, for Enterprise, a 500 user minimum.
  • Terms — annual and monthly terms, with Enterprise sold on annual terms only and a finance approval for a monthly term above 500 users.
  • Add-ons and residency — regional data residency and the Guard add-on by edition, and marketplace apps with a security review above 10 and a limit of 25 per quote.
  • Discounts and order size — volume discounts, an approval band above 10 percent total discount, a limit at 20 percent and a deal desk review above USD 1,000,000.
  • The total the agent states — the stated net total is compared with the total the validator computes.

Any quote that touches these rules is in scope, not only the scenarios pictured here. Not checked: other Atlassian products, real list prices, tax and multi-currency quoting, and the accuracy of the facts the caller states.

The AI sales agentPrepares the cloud subscription quote for the customer and says it is ready to send.
Predictika validatorChecks every rule at once and returns the verdict, each finding, and the computed figures.

5 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 a rules-based CPQ gets this 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 caughtA rules-based CPQPredictika
Limits that depend on the edition and the termOnly with care
An edition's user minimum, its allowed terms and its add-ons are a table of exceptions, and a quote that breaks two of them is usually reported one at a time.		The edition, user count and term are fields of one request, and every limit is checked against all of them together.
An add-on that an edition does not offerOnly with workarounds
Which edition takes the Guard add-on or regional data residency is a hand-written exclusion for each pair, and it has to be remembered when an edition is added.		The add-ons allowed for each edition are part of the model and checked against the edition in the same request.
Discount bands that stackOnly with care
A requested discount adds to a volume discount, and the approval band and the hard limit apply to the sum, which is easy to get out of step.		The volume discount and the requested discount are added, and the sum is checked against the approval band and the limit.
The total the agent statesOnly with workarounds
Comparing a stated figure 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: 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.

    
1Each edition has a user limit (5,000 for Standard, 20,000 for Premium, 50,000 for Enterprise), and Jira Service Management is limited to 3,000 users.
2The Enterprise edition has a minimum of 500 users.
3The Enterprise edition is sold on annual terms only.
4A monthly term above 500 users needs finance approval.
5Regional data residency is not available on the Standard edition.
6The Guard add-on is not available on the Standard edition.
7A quote may include at most 25 marketplace apps; more than 10 need a security review.
8A user count above 90 percent of the edition limit needs sales engineering to confirm the edition.
9Volume discounts apply from 1,000 users (5 percent) and 5,000 users (10 percent).
10A total discount over 10 percent needs the sales director; over 20 percent is blocked.
11An order value over USD 1,000,000 needs a deal desk review.
12The net total stated in the quote must match the total computed from the line items.

  

  

    
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 edition for a small, monthly buyer: Enterprise edition for 200 users on a monthly term

    
The agent's request. Please check this quote for Brightwater Logistics: Jira Software Enterprise for 200 users on a monthly term, with global data residency and no add-ons. The total for the order is USD 59,136.00. The quote is ready to send.

    
Verdict: Blocked.

    
    
      
  • Below the user minimum. There are 200 users, below the 500 user minimum of the Enterprise edition.
    • 
      
  • Enterprise is annual only. The Enterprise edition is sold on annual terms only.
    • 
    

    
2. Enterprise edition for a small, monthly buyer: The agent resubmits after fixing the errors

    
The agent's request. Please check this quote for Brightwater Logistics: Jira Software Enterprise for 300 users on an annual term, with global data residency and no add-ons. The total for the order is USD 80,640.00. The quote is ready to send.

    
Verdict: Blocked.

    
    
      
  • Below the user minimum. There are 300 users, below the 500 user minimum of the Enterprise edition.
    • 
    

    
3. Enterprise edition for a small, monthly buyer: The agent resubmits after fixing the errors

    
The agent's request. Please check this quote for Brightwater Logistics: Jira Software Enterprise for 600 users on an annual term, with global data residency and no add-ons. The total for the order is USD 161,280.00. The quote is ready to send.

    
Verdict: Allowed.

    
4. Discount above the limit: A 16 percent extra discount on 1,500 users

    
The agent's request. Please check this quote for Northgate Credit Union: Jira Software Premium for 1500 users on an annual term, with a 16 percent extra discount. The total for the order is USD 216,144.00. The quote is ready to send.

    
Verdict: Blocked.

    
    
      
  • Discount over the limit. The total discount of 21 percent exceeds the 20 percent limit.
    • 
    

    
5. Discount above the limit: The agent resubmits after fixing the errors

    
The agent's request. Please check this quote for Northgate Credit Union: Jira Software Premium for 1500 users on an annual term, with a 2 percent extra discount. The total for the order is USD 254,448.00. The quote is ready to send.

    
Verdict: Allowed.

  

  

    
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 subscription quote (Jira Software, Confluence or Jira Service Management) with the order total it expects. Before the quote goes out, the agent sends it to Predictika's validator, which checks the edition, user count, term, data residency, security add-on, marketplace apps and discount against each other, compares the total the agent states with the one it computes, and returns a verdict with every reason in one pass. All prices and limits are Predictika estimates in US dollars, not Atlassian list prices.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. Please check this quote for Brightwater Logistics: Jira Software Enterprise for 200 users on a monthly term, with global data residency and no add-ons. The total for the order is USD 59,136.00. 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. There are 200 users, below the 500 user minimum of the Enterprise edition. The Enterprise edition is sold on annual terms only.
    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 limits that depend on the edition and the term, a rules-based CPQ is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the users to 300, the term to annual and the net total stated by the agent to $80,640.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. Still blocked, with one finding, all in one answer. There are 300 users, below the 500 user minimum of the Enterprise edition.
    12. 
      
  12. One finding cleared. Still blocking: below the user minimum.
    13. 
      
  13. The agent resubmits once more.
    14. 
      
  14. The revised request. It changes the users to 600 and the net total stated by the agent to $161,280.
    15. 
      
  15. It calls the validator once more.
    16. 
      
  16. This time the validator clears it.
    17. 
      
  17. The validator also returns the line-item quote, on screen.
    18. 
      
  18. The earlier finding is cleared, and the validator's total, USD 161,280.00, matches the quote.
    19. 
      
  19. Two problems caught in one call, fixed in two passes, and a clean $161,280 quote. That is the value of Predictika's validator: catching mistakes before they reach the customer. Now you can try the other scenarios yourself.
    20.