Predictika · Salesforce edition, add-on and Revenue Cloud quote rules

An AI sales agent's Salesforce quote, checked before it goes to the customer

An AI sales agent assembles a Salesforce quote from the editions, user counts and add-ons a customer asks for, and says it is ready to send. Before it goes out, the agent sends it to Predictika's validator, which checks it against the published edition, add-on and billing rules together and reports every problem it finds in one pass, with the list-price total.

Scope: Salesforce quotes that combine Sales Cloud, Service Cloud, Revenue Cloud and the Free, Starter and Pro Suites, with add-ons, Premier Success, discounts and Flex Credits, checked against Salesforce's published list prices and edition rules as recorded in the validator's knowledge base. Published list prices only; not an official Salesforce quote. See everything this validator covers

This validator checks any quote built from these editions and add-ons against the rules below, not just the scenarios shown.

  • Editions and customers — legacy editions closed to new customers, user caps on the Free Suite and billing terms by suite.
  • Revenue Cloud — the Sales or Service license each Revenue Cloud user needs, and the add-ons that need a higher Revenue Cloud edition.
  • Add-ons — add-ons on the right cloud line, ones already included in an edition, quantities that exceed the users on the line, and add-ons that need another add-on on the same quote.
  • Premier Success and credits — bundled Premier Success, Flex Credits and Agentforce licenses whose allocations Salesforce does not publish.
  • Totals — the annual list price, discount, Premier Success and net annual total, computed on every call.

Any Salesforce quote that touches these rules is in scope, not only the scenarios pictured here. Not checked: negotiated prices, taxes, contract terms, implementation services, and the accuracy of the facts the caller states. Prices are published list prices as recorded in the knowledge base; Salesforce does not publish some prices, and the validator says so.

The AI sales agentAssembles the Salesforce quote from the customer's request and says it is ready to send.
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 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
One quote with several problems at onceOnly with workarounds
Validation rules usually stop at the first failing field, so a seller fixes the user cap, then meets the billing rule, then the next error.
All the findings come back together, whatever order the choices arrived in.
Rules that depend on each otherOnly with care
A dispatcher requirement, a license count and a user count on the same line are separate rules that someone must keep consistent by hand.
Editions, users, add-ons and billing are in one request and re-evaluated together on every call.
A rule that depends on the editionOnly with care
Free, Starter and Pro Suites allow different billing terms and user caps, so the rule list multiplies with every edition.
The edition's attributes are data in the model, and each rule reads them.
A total that follows the fixOnly with workarounds
Price rules and validation rules run in separate passes, so the total can lag behind the corrected quote.
The list-price total is recomputed in the same call as the findings.

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.

1Sales Cloud Unlimited (legacy) closed to new customers on Sept 3, 2026. Quote Sales Cloud Core, Advanced or Max instead.
2Free Suite allows at most 2 users; the Service line has 3.
3Pro Suite is billed annually only. Monthly billing is offered on the Free and Starter Suites.
4Revenue Cloud Growth requires a Sales Cloud or Service Cloud license at Core or Enterprise level or above. This quote has Pro Suite and no Service edition.
5Revenue Cloud Advanced has 40 users, but only 25 users on the quote hold a qualifying Core or Enterprise-level Sales or Service license. Each Revenue Cloud user needs one.
6Sales Cloud Core includes Premier Success but Pro Suite does not. Salesforce does not publish whether one bundled plan covers the whole org. Add Premier on the Service line or confirm coverage.
7Tableau Next for Sales is already included in Sales Cloud Core. Remove the line or the customer pays twice.
8Agentforce User License is not sold on Pro Suite. It needs a higher edition.
9Knowledge Read/Write has 40 licenses but the Service line has only 30 users.
10Field Service Contractor requires a Field Service Dispatcher license on the same quote.
11The Agentforce User License consumes Flex Credits, and Salesforce does not publish how many credits Service Cloud Core includes. Add a Flex Credits pack or get the allocation in writing.
12Sales Cloud Advanced and Service Cloud Max each include Flex Credits per org per year. Salesforce does not publish whether the two allocations add up in one org, so this quote counts only the larger, 2750000 credits.
13Salesforce does not publish a price for Dynamic Revenue Orchestration. It is left out of the total and needs a Salesforce quote.
14Enter a quantity for Agentforce User License.
15Agentforce for Service (unmetered) is on the Service line, but the quote has no Service edition.
16Knowledge Read/Write is a Service add-on and cannot go on the Sales line.

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. A new clinic group on the Suites: A suite quote that breaks two rules

The agent's request. Please check this quote for Brightwater Dental Group, a new customer: Pro Suite for 12 Sales users and Free Suite for 3 Service users, billed monthly. It is ready to send to the customer.

Verdict: Blocked.

  • Free Suite over its user cap. Free Suite allows at most 2 users; the Service line has 3.
  • Pro Suite billed monthly. Pro Suite is billed annually only. Monthly billing is offered on the Free and Starter Suites.
  • List-price total. Annual list 14400 USD, discount 0 USD, Premier Success 0 USD, net annual total 14400 USD. Published list prices only.

2. A new clinic group on the Suites: The agent resubmits after fixing the errors

The agent's request. Please check this quote for Brightwater Dental Group, a new customer: Pro Suite for 12 Sales users and Free Suite for 2 Service users, billed monthly. It is ready to send to the customer.

Verdict: Blocked.

  • Pro Suite billed monthly. Pro Suite is billed annually only. Monthly billing is offered on the Free and Starter Suites.
  • List-price total. Annual list 14400 USD, discount 0 USD, Premier Success 0 USD, net annual total 14400 USD. Published list prices only.

3. A new clinic group on the Suites: The agent resubmits after fixing the errors

The agent's request. Please check this quote for Brightwater Dental Group, a new customer: Pro Suite for 12 Sales users and Free Suite for 2 Service users, billed annually. It is ready to send to the customer.

Verdict: Allowed.

  • List-price total. Annual list 14400 USD, discount 0 USD, Premier Success 0 USD, net annual total 14400 USD. Published list prices only.

4. A field service quote: Field service licenses without a dispatcher

The agent's request. Please check this quote for Lakeshore HVAC Services, a new customer billed annually: Service Cloud Core for 30 Service users, 60 Field Service Technician licenses, 10 Field Service Contractor licenses, 40 Knowledge Read/Write licenses. It is ready to send to the customer.

Verdict: Blocked.

  • More licenses than users. Knowledge Read/Write has 40 licenses but the Service line has only 30 users.
  • Needs a Field Service Dispatcher. Field Service Contractor requires a Field Service Dispatcher license on the same quote.
  • Needs a Field Service Dispatcher. Field Service Technician requires a Field Service Dispatcher license on the same quote.
  • List-price total. Annual list 238800 USD, discount 0 USD, Premier Success 0 USD, net annual total 238800 USD. Published list prices only.

5. A field service quote: The agent resubmits after fixing the errors

The agent's request. Please check this quote for Lakeshore HVAC Services, a new customer billed annually: Service Cloud Core for 30 Service users, 60 Field Service Technician licenses, 10 Field Service Contractor licenses, 30 Knowledge Read/Write licenses. It is ready to send to the customer.

Verdict: Blocked.

  • Needs a Field Service Dispatcher. Field Service Contractor requires a Field Service Dispatcher license on the same quote.
  • Needs a Field Service Dispatcher. Field Service Technician requires a Field Service Dispatcher license on the same quote.
  • List-price total. Annual list 229800 USD, discount 0 USD, Premier Success 0 USD, net annual total 229800 USD. Published list prices only.

6. A field service quote: The agent resubmits after fixing the errors

The agent's request. Please check this quote for Lakeshore HVAC Services, a new customer billed annually: Service Cloud Core for 30 Service users, 60 Field Service Technician licenses, 10 Field Service Contractor licenses, 30 Knowledge Read/Write licenses and 10 Field Service Dispatcher licenses. It is ready to send to the customer.

Verdict: Allowed.

  • List-price total. Annual list 250800 USD, discount 0 USD, Premier Success 0 USD, net annual total 250800 USD. Published list prices only.

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 assembles a Salesforce quote from the editions, user counts and add-ons a customer asks for, and says it is ready to send. Before it goes out, the agent sends it to Predictika's validator, which checks it against the published edition, add-on and billing rules together and reports every problem it finds in one pass, with the list-price total.
  2. I will start with the first request by the agent.
  3. The agent says. Please check this quote for Lakeshore HVAC Services, a new customer billed annually: Service Cloud Core for 30 Service users. It is ready to send to the customer. The rest of the request is on screen.
  4. Before it goes out, the agent calls the validator.
  5. Blocked, with three findings, all in one answer. Knowledge Read/Write has 40 licenses but the Service line has only 30 users. Field Service Contractor requires a Field Service Dispatcher license on the same quote. Field Service Technician requires a Field Service Dispatcher license on the same quote.
  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. What this shows: for rules that depend on each other, a rules-based CPQ is error-prone for this.
  8. Now the agent resubmits.
  9. The corrected request. It changes the Knowledge Read/Write to 30.
  10. It calls the validator again.
  11. Still blocked, with two findings, all in one answer. Field Service Contractor requires a Field Service Dispatcher license on the same quote. Field Service Technician requires a Field Service Dispatcher license on the same quote.
  12. One finding cleared. Still blocking: needs a Field Service Dispatcher.
  13. The agent resubmits once more.
  14. The revised request. It sets the Field Service Dispatcher to 10.
  15. It calls the validator once more.
  16. This time the validator clears it.
  17. The earlier finding is cleared.
  18. Three 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. Now you can try the other scenarios yourself.