Predictika · Business banking quotes
An AI sales agent prepares a business checking proposal for a small business: the account, the monthly total it will tell the customer to expect, and what it says about extra fees. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the published account fees and returns a verdict, every reason and the figures it computed.
This validator models proposals for two Bank of America business checking accounts as published in the Business Advantage clarity statements, not just the scenarios shown below.
Any proposal for these two accounts that touches these rules is in scope — not only the scenarios pictured here. Not covered: other Bank of America business accounts, wire transfers, ATM, overdraft, stop payments and other fees, interest, and promotions (including any introductory period without a monthly fee). Assumptions: cash deposits are entered in whole units of $100; the statement cycle is the monthly period shown on the clarity statements; which items count toward the allowance follows the clarity statements and is not itemized here.
7 scenarios in 3 groups · each group runs from the agent’s first attempt to the outcome · click one to switch
Proposing agent: AI sales agent (scripted)
Before sending, the agent must call Recorded run
What this means
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 caught | Typical rules-based CPQ | Predictika |
|---|---|---|
| A fee that is avoided by any one of several conditions | Only with care A rule per waiver path and per account; it works, but the conditions differ between the two accounts (debit card spend counts on one and not the other) and must be kept in step with the clarity statements. | Every path is evaluated together and the monthly fee the proposal should show is computed from them. |
| A total built from a fixed fee plus usage-based fees | Only with care A price rule for each fee, with the item and cash allowances looked up per account. The rep's stated total then has to be compared with the computed one separately. | The monthly fee, excess item fees and cash deposit fees are computed and the stated total is compared in the same pass. |
| Allowances that differ by account and a promise made in the proposal text | Only with workarounds A promise of no extra fees lives in free text; a rule can only catch it if it has been captured as a field first. | The promise is one of the inputs and is checked against the account's included items and cash deposits. |
| Every problem returned in one answer | Only 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. |
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.
| 1 | The quote states a monthly total of $16; the published fees give $46. |
| 2 | The quote promises no extra fees but the customer expects 21 countable items in a statement cycle; the account includes 20. |
| 3 | The quote promises no extra fees but the customer expects $20,100 of cash deposits in a statement cycle; the account includes $20,000. |
| 4 | The quote states a monthly total of $0; the published fees give $122.50. |
| 5 | The quote promises no extra fees but the customer expects 90 countable items in a statement cycle; the account includes 20. |
| 6 | The quote promises no extra fees but the customer expects $30,000 of cash deposits in a statement cycle; the account includes $5,000. |
The text of the narrated walkthrough, step by step.