Predictika · Data subscription quotes

An AI sales agent's Orbis subscription quote, checked before it goes out

An AI sales agent prepares a named-user subscription quote for Orbis, the company-data platform from Moody's, with add-on modules. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the published user-tier prices, module percentages and minimum term, and returns a verdict, every reason and the total it computed.

Scope: Orbis named-user subscriptions: user-count price tiers, percentage add-on modules, modules with no published price and the 12-month minimum term. See everything this validator covers

This validator models Orbis named-user subscription quotes as published in the UK G-Cloud 14 Orbis pricing document, not just the scenarios shown below.

  • User tiers — the base price depends on the number of named users, from 98,000 GBP for 1 user to 4,250,000 GBP for up to 5,000 users; unlimited reports, searches and alerts are included.
  • Add-on modules — each module is priced as a percentage of the base price (for example Beneficial Ownership 15%, ESG score predictor 10%, DEI score 5%, API 20%); Risk Flags is priced between 20% and 40%.
  • No published price — customised data feeds, the Shell Company Indicator and Sanctions 360 are price on application, so a person has to obtain their price.
  • Term and stated total — the minimum contract period is 12 months; the total the quote states is compared with the total computed from the published prices (GBP a year, excluding VAT).

Any Orbis named-user quote that touches these rules is in scope — not only the scenarios pictured here. Not covered: negotiated discounts, VAT, other Moody's products, other price lists and any change to the published prices after the May 2024 version of the document. The prices are the published ones, not an offer.

The AI sales agentBuilds the subscription 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
Module prices that are percentages of a tier-dependent baseOnly with care
Each module adds a percentage of a base that itself depends on the user tier, so the quote total is a chain of lookups and sums that must be rebuilt in price rules.		The user count, the modules and the stated total are in one request; the total is computed on every call.
A module whose percentage must stay inside a published rangeOnly with care
A range check on one line that only applies when the module is selected is one more validation rule to write and keep in step with the price list.		The module choice and its percentage are checked together on every call.
A stated total that disagrees with the published pricesOnly with workarounds
The total is derived from a tier and several modules; checking a stated figure against it takes extra price rules and formulas that interact with the rest.		The stated total is a field in the request and is compared with the computed one.
Modules that have no published priceOnly with care
A price-on-application item has to be kept out of the total and routed to a person, which usually means a separate approval path.		Such a module raises an approval finding while the rest of the quote is still checked and totalled.
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.

    
1The quote has 5,001 named users; the published Orbis price table covers 1 to 5,000 named users.
2The quote has 0 named users; the published Orbis price table covers 1 to 5,000 named users.
3The Risk Flags module is priced at 20 to 40 percent of the base price, but the quote uses 15 percent.
4The Risk Flags module is priced at 20 to 40 percent of the base price, but the quote uses 45 percent.
5The quote has a 6-month term; the minimum contract period is 12 months.
6The quote states a total of 244,000 GBP a year, but the base price and module percentages come to 317,200 GBP.
7The quote states a total of 330,000 GBP a year, but the base price and module percentages come to 317,200 GBP.
8The quote states a total of 776,250 GBP a year, but the base price and module percentages come to 911,250 GBP.
9The quote includes a module that has no published price (price on application: customised data feeds, Shell Company Indicator or Sanctions 360); a person must obtain its price, which is not in the total.
10The quote states a total of 1 GBP a year, but the base price and module percentages come to 360,000 GBP.
11The quote has 6,000 named users; the published Orbis price table covers 1 to 5,000 named users.
12The quote has a 3-month term; the minimum contract period is 12 months.

  

  

    
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. Risk Flags and term: A 30-user quote with Risk Flags at 15 percent on a 6-month term

    
The agent's request. Please quote an Orbis subscription for 30 named users with Beneficial Ownership (with T-Rank), ESG score predictor and Risk Flags (Grid) at 15 percent, on a 6-month term. The quote states a total of GBP 777,000 a year, excluding VAT. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Term shorter than the minimum. The quote has a 6-month term; the minimum contract period is 12 months.
    • 
      
  • Risk Flags percentage outside its range. The Risk Flags module is priced at 20 to 40 percent of the base price, but the quote uses 15 percent.
    • 
    

    
2. Risk Flags and term: The agent resubmits after fixing the errors

    
The agent's request. Please quote an Orbis subscription for 30 named users with Beneficial Ownership (with T-Rank), ESG score predictor and Risk Flags (Grid) at 30 percent, on a 6-month term. The quote states a total of GBP 860,250 a year, excluding VAT. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Term shorter than the minimum. The quote has a 6-month term; the minimum contract period is 12 months.
    • 
    

    
3. Risk Flags and term: The agent resubmits after fixing the errors

    
The agent's request. Please quote an Orbis subscription for 30 named users with Beneficial Ownership (with T-Rank), ESG score predictor and Risk Flags (Grid) at 30 percent, on a 12-month term. The quote states a total of GBP 860,250 a year, excluding VAT. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Price summary. 30 named users priced on the up-to-30 tier at 555 thousand GBP, plus 55 percent for modules, 860,250 GBP a year excluding VAT.
    • 
    

    
4. Stated total: A 50-user quote with Cyber Risk and API modules, with the Cyber module left out of the total

    
The agent's request. Please quote an Orbis subscription for 50 named users with Cyber Risk rating and API, on a 12-month term. The quote states a total of GBP 776,250 a year, excluding VAT. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Stated total differs from the published prices. The quote states a total of 776,250 GBP a year, but the base price and module percentages come to 911,250 GBP.
    • 
    

    
5. Stated total: The agent resubmits after fixing the errors

    
The agent's request. Please quote an Orbis subscription for 50 named users with Cyber Risk rating and API, on a 12-month term. The quote states a total of GBP 911,250 a year, excluding VAT. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Price summary. 50 named users priced on the up-to-50 tier at 675 thousand GBP, plus 35 percent for modules, 911,250 GBP a year excluding VAT.
    • 
    

    
6. Size of the user table: A 6,000-user quote with an extrapolated total

    
The agent's request. Please quote an Orbis subscription for 6,000 named users with Beneficial Ownership (with T-Rank), Financial Strength and API, on a 12-month term. The quote states a total of GBP 7,650,000 a year, excluding VAT. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • User count outside the published price table. The quote has 6,000 named users; the published Orbis price table covers 1 to 5,000 named users.
    • 
      
  • Stated total differs from the published prices. The quote states a total of 7,650,000 GBP a year, but the base price and module percentages come to 0 GBP.
    • 
    

    
7. Size of the user table: The agent resubmits after fixing the errors

    
The agent's request. Please quote an Orbis subscription for 5,000 named users with Beneficial Ownership (with T-Rank), Financial Strength and API, on a 12-month term. The quote states a total of GBP 6,375,000 a year, excluding VAT. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Price summary. 5,000 named users priced on the up-to-5,000 tier at 4,250 thousand GBP, plus 50 percent for modules, 6,375,000 GBP a year excluding VAT.
    • 
    

  

  

    
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 named-user subscription quote for Orbis, the company-data platform from Moody's, with add-on modules. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the published user-tier prices, module percentages and minimum term, and returns a verdict, every reason and the total it computed.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. Please quote an Orbis subscription for 30 named users with Beneficial Ownership (with T-Rank), ESG score predictor and Risk Flags (Grid) at 15 percent, on a 6-month term. The quote states a total of GBP 777,000 a year, excluding VAT. 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. The quote has a 6-month term; the minimum contract period is 12 months. The Risk Flags module is priced at 20 to 40 percent of the base price, but the quote uses 15 percent.
    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 module whose percentage must stay inside a published range, a rules-based CPQ is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the add-on modules to Beneficial Ownership (with T-Rank), ESG score predictor, Risk Flags (Grid) at 30 percent and the stated total as to 860,250.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. Still blocked, with one finding, all in one answer. The quote has a 6-month term; the minimum contract period is 12 months.
    12. 
      
  12. One finding cleared; still blocked on term shorter than the minimum.
    13. 
      
  13. The agent resubmits once more.
    14. 
      
  14. The revised request. It changes the contract term to 12 months.
    15. 
      
  15. It calls the validator once more.
    16. 
      
  16. This time the validator clears it.
    17. 
      
  17. The earlier finding is cleared, and the validator's total, GBP 860,250, matches the quote.
    18. 
      
  18. Two problems 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.
    19.