Revenue Cloud and the CPQ change
Revenue Cloud brings pricing, quoting, contracts and billing onto one data model. Here is what it does and what CPQ end of sale means for you.
Revenue Cloud is Salesforce's product for the quote-to-cash process: configuring products, pricing them, quoting, contracting, ordering and billing. You will also see it called Revenue Lifecycle Management (RLM), which Salesforce describes as an earlier product name, and Revenue Cloud Advanced (RCA). After October 2025 it was marketed as "Agentforce Revenue Management", a name that still appears in some Winter '27 newsroom copy.
What it is for
Revenue Cloud is for businesses whose pricing and contracts are too complex for simple opportunity products: bundles, configurable options, subscriptions, usage, amendments and renewals. Its main idea is a single data model that covers pricing, quoting, contracts and billing, so each step does not need its own copy of the data.
What CPQ end of sale means
For existing CPQ customers this means there is no forced deadline, but also no new capability. Plan a move when it suits your business, for example around a pricing change or a contract renewal, rather than in a rush. Salesforce's end-of-sale page does not cover the status of Salesforce Billing, so check that directly with Salesforce.
Core capabilities
Revenue Cloud capabilities
| Capability | What it does |
|---|---|
| Single data model | Pricing, quoting, contracts and billing share one model |
| Attribute-based catalog | Define products by attributes rather than many separate SKUs |
| Constraint Builder | Rules for valid product configurations |
| Asset and subscription management | Track what customers own, amendments and renewals |
| Order orchestration | Coordinate fulfilment steps after an order is placed |
| Tableau Next dashboards | Revenue analytics on the Salesforce Platform |
| Large deals (Winter '27) | Up to 15,000 transaction lines per deal |
| Agent enhancements (Winter '27) | Agents for self-service, partner and renewal quoting |
How it connects with other Salesforce products
- Sales Cloud opportunities flow into quotes, and closed deals become contracts and orders.
- Service Cloud and Field Service and Operations use the assets and entitlements Revenue Cloud records.
- Tableau Next provides dashboards; Data 360 can add usage data from outside systems.
- ERP and finance systems usually stay the book of record for accounting, so plan the integration carefully.
Who it suits
B2B companies selling configurable products, subscriptions or usage-based services, and manufacturers or telecoms with complex catalogues. If your quotes are a handful of fixed products, Sales Cloud alone may be enough.
Planning an implementation
- Catalogue first. Decide how products, attributes and bundles will be modelled before building any rules.
- Pricing logic. Document every discount, approval and price rule, then remove the ones nobody uses.
- Contract lifecycle. Agree how amendments, renewals and cancellations should work.
- System of record. Decide what lives in Salesforce and what stays in ERP or billing.
- CPQ migration path. If you run Salesforce CPQ, inventory your customisations and decide what to rebuild, simplify or drop.
Common mistakes
- Migrating every CPQ price rule as-is instead of simplifying.
- Designing quoting without involving finance and billing.
- Underestimating data migration for active contracts and assets. Our migration runbook template helps.
- Testing only new quotes and forgetting amendments and renewals.
How GeekMidst can help
We can help you assess a CPQ estate, model a catalogue and plan the migration as part of our Salesforce architecture consulting. Our data migration services cover moving contracts and assets, and our integration services connect quoting to ERP and billing.
Questions we hear
Do we have to leave Salesforce CPQ?
Can new customers buy Salesforce CPQ?
Is Revenue Lifecycle Management a separate product?
How large can a Revenue Cloud deal be?
Related reading
Sales Cloud guide
Pipeline, forecasting and seller productivity
→Designing a data model that scales
Avoiding rework as you grow
→Migration runbook template
Planning cut-over step by step
→SaaS on Salesforce
Subscription and renewal patterns
→Planning for CPQ end of sale
Options and a plan for Revenue Cloud Advanced
→CPQ to Revenue Cloud Advanced blueprint
A phased migration plan
→Sources
Weighing a move from CPQ?
Tell us about your catalogue, pricing rules and billing setup, and we will help you plan the next step.
