Predictika · Core banking subscription quotes

An AI sales agent's Temenos Core banking quote, checked before it goes out

An AI sales agent prepares an annual subscription quote for Temenos Core banking, with a Core variant, a deployment on premise, in the cloud or on Temenos SaaS, optional modules, Temenos Exchange solutions, a support tier, a go-live date, a term and a discount. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the variants, modules and quote limits and returns a verdict, every reason and the annual total it computed.

Scope: Temenos Core banking annual subscription quotes: the Core variants, the Digital, Financial Crime Mitigation, Payments and Data and AI modules, Temenos Exchange solutions, deployment, support, go-live, term, discount and the annual total. See everything this validator covers

This validator models Temenos Core banking subscription quotes, not just the scenarios shown below.

  • Variants and capacity — the Retail, Wealth, Community and Inclusive, Islamic, Payments, Business and Corporate variants, each with the number of customers it is modeled to cover.
  • Modules, deployment and support — the Digital, Financial Crime Mitigation, Payments and Data and AI modules and the dependencies between them, Temenos Exchange solutions, on-premise, cloud or Temenos SaaS deployment with its minimum go-live and term, regulated jurisdictions, and the support tier.
  • Discount and total — the discount limit and the sign-off it needs, and the annual total the quote states, which must match the total computed from the list rates.

Any Temenos Core subscription quote that touches these rules is in scope — not only the scenarios pictured here. Not covered: Temenos Transact licensing and other Temenos products. The variant, module and deployment names, the Temenos Exchange solution count and the 90-day SaaS go-live follow Temenos's public Core factsheet; the prices, customer capacities, module dependencies, jurisdiction cap, go-live minimums, minimum terms and discount thresholds are modeled from comparable products and are not published by Temenos, so all figures are illustrative. Amounts are in thousands of US dollars (K dollars) a year.

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.

6 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
Customer capacity that differs by variantOnly with care
Each Core variant covers a different number of customers, so each needs its own limit that the customer count is checked against.		The variant and the customer count are in one request and checked together on every call.
Module dependencies and exclusionsOnly with workarounds
Payments needs Financial Crime Mitigation, Data and AI needs Digital, and the Payments variant already includes payments, so rules must refer to the variant and the other modules.		The variant and the module choices are in the request, so each dependency and exclusion is checked on every call.
Go-live and term minimums that depend on the deploymentOnly with workarounds
The earliest go-live and the shortest term differ for on-premise, cloud and Temenos SaaS, so a rule must read the deployment first.		The deployment, the go-live days and the term are all in the request and compared on every call.
A discount that is a share of the list total, with a block limit and an approval bandOnly with workarounds
The list total changes with the variant, customers, modules and support, so the limits must be recalculated for every quote.		The discount is compared with the computed list total on every call and returns a block, an approval or nothing.
A stated annual total that must match the computed totalOnly with workarounds
The total is built from the variant, customers, modules, deployment, support and discount, so a separate rule must recompute it and compare it with the stated figure.		The stated total is a field of the request and is compared with the computed total on every call.
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.

    
11,001 hundred-thousand customers is outside the 1 to 1,000 this Temenos Core variant is modeled to cover.
221 hundred-thousand customers is outside the 1 to 20 this Temenos Core variant is modeled to cover.
351 hundred-thousand customers is outside the 1 to 50 this Temenos Core variant is modeled to cover.
40 hundred-thousand customers is outside the 1 to 1,000 this Temenos Core variant is modeled to cover.
5Temenos Core Payments already includes payments; the separate Payments module is not added to it.
6Payments processing in this model needs the Financial Crime Mitigation module.
7The Data and AI module in this model needs the Digital module.
80 regulated jurisdictions is outside the 1 to 35 modeled for Temenos SaaS.
935 regulated jurisdictions needs a regional compliance review.
1036 regulated jurisdictions is outside the 1 to 35 modeled for Temenos SaaS.
1116 regulated jurisdictions needs a regional compliance review.
12Mission-critical support is modeled for cloud and Temenos SaaS only, not on-premise.
13A go-live in 89 days is sooner than the 90 days modeled for this deployment.
14A go-live in 149 days is sooner than the 150 days modeled for this deployment.
15A go-live in 239 days is sooner than the 240 days modeled for this deployment.
16Temenos SaaS is modeled with a minimum term of 3 years; the quote has 2.
17A term of 8 years is longer than 7 years and needs sign-off.
18150 Temenos Exchange solutions is a large integration set; delivery should confirm the plan.
19151 Temenos Exchange solutions is more than the 150 pre-integrated solutions listed.
20A discount of 627 K dollars is over 15 percent of the 4,175 K dollar list total and needs sales management sign-off.
21A discount of 1,253 K dollars is over 30 percent of the 4,175 K dollar list total.
22The quote states 4,075 K dollars a year; the modeled list rates give 4,175 K dollars.
23The quote states 4,176 K dollars a year; the modeled list rates give 4,175 K dollars.
24A go-live in 60 days is sooner than the 90 days modeled for this deployment.
2580 hundred-thousand customers is outside the 1 to 50 this Temenos Core variant is modeled to cover.
26A discount of 2000 K dollars is over 30 percent of the 4,275 K dollar list total.
27A discount of 846 K dollars is over 15 percent of the 4,700 K dollar list total and needs sales management sign-off.
2840 Temenos Exchange solutions is a large integration set; delivery should confirm the plan.
2920 regulated jurisdictions needs a regional compliance review.
30160 Temenos Exchange solutions is more than the 150 pre-integrated solutions listed.
31The quote states 5,000 K dollars a year; the modeled list rates give 6,500 K dollars.

  

  

    
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. Modules, go-live, term and stated total: A Payments-variant quote on Temenos SaaS with the Payments module, Data and AI without Digital, a 60-day go-live and a 2-year term

    
The agent's request. Please quote Temenos Core Payments on Temenos SaaS for 40 hundred-thousand customers in 12 regulated jurisdictions, with Payments and Data and AI modules, 5 Temenos Exchange solutions, premium support, a go-live in 60 days, a 2-year term and no discount, for an annual total of 5,025 K dollars. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Payments module on the Payments variant. Temenos Core Payments already includes payments; the separate Payments module is not added to it.
    • 
      
  • Payments needs Financial Crime Mitigation. Payments processing in this model needs the Financial Crime Mitigation module.
    • 
      
  • Data and AI needs Digital. The Data and AI module in this model needs the Digital module.
    • 
      
  • Go-live too soon. A go-live in 60 days is sooner than the 90 days modeled for this deployment.
    • 
      
  • SaaS term too short. Temenos SaaS is modeled with a minimum term of 3 years; the quote has 2.
    • 
      
  • Stated annual total does not match. The quote states 5,025 K dollars a year; the modeled list rates give 5,175 K dollars.
    • 
    

    
2. Modules, go-live, term and stated total: The agent resubmits after fixing the errors

    
The agent's request. Please quote Temenos Core Payments on Temenos SaaS for 40 hundred-thousand customers in 12 regulated jurisdictions, with Digital, Financial Crime Mitigation and Data and AI modules, 5 Temenos Exchange solutions, premium support, a go-live in 120 days, a 5-year term and no discount, for an annual total of 5,575 K dollars. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Quote summary. List total 5,575 K dollars a year, discount 0 K dollars, net 5,575 K dollars a year for 40 hundred-thousand customers.
    • 
    

    
3. Capacity, Exchange solutions and stated total: A Community and Inclusive quote for 80 hundred-thousand customers with 160 Temenos Exchange solutions

    
The agent's request. Please quote Temenos Core Community and Inclusive in the cloud for 80 hundred-thousand customers in 3 regulated jurisdictions, with Digital and Data and AI modules, 160 Temenos Exchange solutions, premium support, a go-live in 200 days, a 5-year term and no discount, for an annual total of 7,100 K dollars. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Customers over the variant capacity. 80 hundred-thousand customers is outside the 1 to 50 this Temenos Core variant is modeled to cover.
    • 
      
  • Too many Exchange fintechs. 160 Temenos Exchange solutions is more than the 150 pre-integrated solutions listed.
    • 
      
  • Stated annual total does not match. The quote states 7,100 K dollars a year; the modeled list rates give 7,300 K dollars.
    • 
    

    
4. Capacity, Exchange solutions and stated total: The agent resubmits after fixing the errors

    
The agent's request. Please quote Temenos Core Community and Inclusive in the cloud for 30 hundred-thousand customers in 3 regulated jurisdictions, with Digital and Data and AI modules, 20 Temenos Exchange solutions, premium support, a go-live in 200 days, a 5-year term and no discount, for an annual total of 3,700 K dollars. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • Quote summary. List total 3,700 K dollars a year, discount 0 K dollars, net 3,700 K dollars a year for 30 hundred-thousand customers.
    • 
    

    
5. Support, discount and stated total: A Corporate on-premise quote with mission-critical support and a very large discount

    
The agent's request. Please quote Temenos Core Corporate on premise for 10 hundred-thousand customers in 2 regulated jurisdictions, with Digital modules, 5 Temenos Exchange solutions, mission-critical support, a go-live in 300 days, a 5-year term and a discount of 2,000 K dollars, for an annual total of 3,775 K dollars. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Mission-critical support on-premise. Mission-critical support is modeled for cloud and Temenos SaaS only, not on-premise.
    • 
      
  • Discount over the limit. A discount of 2000 K dollars is over 30 percent of the 5,475 K dollar list total.
    • 
      
  • Stated annual total does not match. The quote states 3,775 K dollars a year; the modeled list rates give 3,475 K dollars.
    • 
    

    
6. Support, discount and stated total: The agent resubmits after fixing the errors

    
The agent's request. Please quote Temenos Core Corporate on premise for 10 hundred-thousand customers in 2 regulated jurisdictions, with Digital modules, 5 Temenos Exchange solutions, premium support, a go-live in 300 days, a 5-year term and a discount of 900 K dollars, for an annual total of 4,075 K dollars. It is ready to send.

    
Verdict: Needs approval.

    
    
      
  • Discount needs sign-off. A discount of 900 K dollars is over 15 percent of the 4,975 K dollar list total and needs sales management sign-off.
    • 
      
  • Quote summary. List total 4,975 K dollars a year, discount 900 K dollars, net 4,075 K dollars a year for 10 hundred-thousand customers.
    • 
    

  

  

    
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 annual subscription quote for Temenos Core banking, with a Core variant, a deployment on premise. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the variants, modules and quote limits and returns a verdict, every reason and the annual total it computed.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. Please quote Temenos Core Payments on Temenos SaaS for 40 hundred-thousand customers in 12 regulated jurisdictions, with Payments and Data and AI modules. It is ready to send. 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, all in one answer. Temenos Core Payments already includes payments; the separate Payments module is not added to it. Payments processing in this model needs the Financial Crime Mitigation module. The Data and AI module in this model needs the Digital module. The other three are on screen.
    6. 
      
  6. The validator returned six 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 and against the stated total.
    7. 
      
  7. What this shows: for a stated annual total that must match the computed total, a rules-based CPQ can do this only with workarounds.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the digital module to yes, the Financial Crime Mitigation module to yes, the payments module to no, the go-live to 120 days, the term to 5 years and the annual total stated on the quote to 5,575 K dollars.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. This time the validator clears it.
    12. 
      
  12. All six earlier findings are cleared.
    13. 
      
  13. Six 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.