Salesforce Revenue Cloud is a native platform that unifies product catalog, pricing, CPQ, contracts, orders and billing on one system. It replaces legacy CPQ with an API-first architecture built for scale.
Salesforce confirmed the end of sale for Salesforce CPQ in 2025. Every team still quoting through that managed package now has a deadline sitting behind their migration plans, whether they’ve acknowledged it or not.
Revenue Cloud replaced it with something structurally different. Instead of bolting CPQ onto Sales Cloud through a managed package, Salesforce rebuilt the entire quote-to-cash process natively on its core platform.
That single decision removed the ceiling teams kept hitting with CPQ, the one that forced custom code for approvals, separate SKUs for contracts and endless workarounds for anything beyond basic pricing. Revenue Cloud absorbed all of it into one connected system.
Key Takeaways
- Native Salesforce platform connecting catalog, pricing, CPQ, contracts, orders and billing
- Evolved from CPQ to Revenue Lifecycle Management to Revenue Cloud Advanced to Agentforce Revenue Management
- API-first design supports any sales channel and revenue model
- Agentforce agents generate quotes and manage renewals from natural language input
- Built-in Tableau Next dashboards remove the need for a separate reporting tool
A Brief History of Revenue Cloud
Revenue Cloud carries three names depending on when you encounter it and each rename reflects a real shift in the product:
From Salesforce CPQ to Revenue Lifecycle Management
Salesforce CPQ launched in 2009 through the acquisition of SteelBrick and it ran as a managed package on top of Sales Cloud. It handled configuration, pricing and quoting well. But it needed extra packages for approvals and contract management, which added cost.
Salesforce confirmed the end of sale for CPQ as a standalone product. Existing customers keep support and can renew, but new investment moved to the successor platform.
From RLM to Revenue Cloud Advanced
Revenue Lifecycle Management launched in the Spring ’24 release as the direct replacement for CPQ’s core function. Salesforce renamed it Revenue Cloud Advanced at Dreamforce ’24 and both names still appear across documentation and community threads. Revenue Cloud Advanced runs on the core Salesforce platform instead of a managed package. That removes the technical ceiling that limited CPQ customizations.
Revenue Cloud Becomes Agentforce Revenue Management
In 2025, Salesforce renamed Revenue Cloud again to Agentforce Revenue Management. The rename signals a shift toward AI agents handling quote generation, renewal management and consumption monitoring inside the same platform. The underlying capabilities stayed the same. The branding now reflects where Salesforce wants revenue operations to head next.
Salesforce Revenue Cloud Modules Explained for Your Team
Revenue Cloud connects several modules that used to run as separate products or paid add-ons on your org. Each one covers a stage of your revenue lifecycle, from defining a product to collecting payment:
Product Catalog Management
Product Catalog Management gives you one place to define products, build bundles and set dependencies. Salesforce CPQ never handled catalog complexity well, so Revenue Cloud built this module around dynamic attributes instead of forcing you to create one SKU per variation.
A single catalog also serves every B2B channel you sell through, with guided selling and attribute-based search built in. You’ll organize products through a few core building blocks:
- Catalogs group your products by category for easier browsing
- Attributes and categories get defined once, then reused across every product that needs them
- Product classifications work like templates, useful when your products share specs, like laptops with the same processor and RAM options
- Products can be simple or bundled and either fixed or configurable at the point of sale
- Qualification rules decide which products your customer sees, based on their location or account details
Pricing and Discounting
Pricing Procedures replace the rigid pricing rules you built inside CPQ. A declarative designer lets you build tiered, volume-based, or usage pricing without writing custom code and you can run calculations inside a simulator before anything goes live.
Every quote line shows you the full price waterfall on hover, so you see exactly how a final number was calculated. That transparency removes the guesswork that used to slow down your deal reviews.
Configure, Price, Quote (CPQ)
The CPQ experience inside Revenue Cloud replaces your old managed package configurator entirely. You configure complex bundles with nested options and the summary updates in real time as you add items.
Salesforce built the configurator as a Screen Flow, so you can customize it with standard and custom components. The Transaction Line Editor replaced your old Quote Line Editor with an Excel-style interface that supports column freezing, sorting and filtering, with no cap on how many columns you add.
A newer Constraint Builder, generally available with the Summer ’25 release, handles larger transactions and more complex configuration rules. You can run the standard rules engine and the Constraint Builder side by side and choose whichever fits the deal in front of you.
Contract Lifecycle Management
Contract Lifecycle Management (CLM) covers work that used to require a separate SKU or a third-party tool. Your legal team manages templates and clause libraries directly inside the platform and generative AI helps draft clauses faster.
Your sales team can create contracts at any stage and collaborate on redlines without leaving the CRM. Obligation tracking is built in, so you confirm compliance after a contract activates instead of tracking it in a spreadsheet.
Order and Subscription Management
Once your order activates, the Dynamic Revenue Orchestrator (DRO) breaks it into a fulfillment plan. Complex products often split into multiple fulfillment order products and DRO maps that breakdown automatically based on rules your admin sets up in advance.
Your order managers follow each fulfillment step through swimlanes, complete manual steps where needed and review errors as they come up. Subscriptions live as assets you can amend, renew, or cancel at any point and every change shows up in the Asset Lifecycle tab.
Consumption Management
Consumption Management handles usage-based selling, which has grown fast since generative AI pricing models became common. The module monitors consumption, generates usage summaries, forecasts future usage and applies rollover policies for your unused grants.
You can bill on the platform directly or pass consumption data to an external billing system, depending on how your finance stack works.
Billing and Invoicing
Revenue Cloud Advanced includes basic invoicing, but Revenue Cloud Billing is a separate SKU built for teams that need more control. It generates invoices from an account, order, or list of billing schedules and it supports proration, cancellations and custom billing structures across subscription, one-time and usage models.
Billing also functions as a general ledger for dual-entry accounting, so your finance team logs transactions directly in Salesforce instead of exporting data to a separate system.
How Does Agentforce Power Revenue Cloud?
Every module above can run manually, but Agentforce adds AI agents on top of the same data. The quoting agent, available in pilot since Spring ’25, takes natural-language input and creates a quote or applies a discount in seconds instead of the minutes a rep would spend doing it by hand.
Agentforce Adoption and Growth Across Salesforce
Agentforce adoption across the broader Salesforce platform is accelerating fast and it now shows up everywhere from sales pipelines to service queues rather than sitting off as a pilot project. Salesforce has also unified its agent ecosystem into AgentExchange, giving teams one place to find vetted agents and integration partners instead of stitching something together from scratch.
What the Quoting Agent Does Inside Revenue Cloud
Inside Revenue Cloud specifically, the quoting agent runs with a small set of custom actions and teams can extend it. For example, having it create the opportunity before it builds the quote. Salesforce also exposes invocable actions across the platform, such as one that triggers an order once a quote exists, so teams can build custom agents beyond the out-of-the-box quoting skill.
Revenue Cloud Analytics
Revenue Cloud ships with dashboards built on Tableau Next. Here’s what each dashboard tracks:
| Dashboard | What It Tracks |
| Subscription revenue | ARR, MRR, churn, renewal rates |
| Pricing | Discount trends, margin impact, waterfall analysis |
| Order fulfillment | Bottlenecks, fallout rates, delivery speed |
| Billing | Invoice health, collection efficiency |
Customizing these dashboards requires a Salesforce Foundations Viewer license and a Tableau Next Creator license. Factor that into your budget before you plan a rollout.
Salesforce CPQ vs Revenue Cloud
Teams evaluating a move from CPQ often ask what actually changes underneath the surface. Here’s a side-by-side breakdown:
| Factor | Salesforce CPQ | Revenue Cloud |
| Platform | Managed package | Native to Salesforce core |
| Approvals | Separate paid add-on | Included from the start |
| Contract management | Third-party tool or extra SKU | Built in as CLM |
| Configurator | JavaScript-heavy customization | Screen Flow, point-and-click |
| Pricing visibility | Limited waterfall detail | Full price waterfall on every line |
| AI quoting | Not available | Agentforce quoting agent |
Top Benefits of Revenue Cloud
Here’s what changes operationally once the platform is live:
- Faster deal cycles: Automated quoting and approvals cut down time reps spend on admin work
- Consistent pricing everywhere: One catalog and pricing engine serves direct sales, partner channels and self-service
- Quicker go-to-market: Product and pricing changes deploy without waiting on IT
- Real-time visibility: Built-in dashboards replace manual reporting across the revenue lifecycle
- Lower compliance risk: Native support for ASC 606 and IFRS 15 reduces manual revenue-recognition errors
Conclusion
Every quarter your teams spend reconciling quotes, contracts and invoices across separate tools is a quarter you’re not closing new revenue. Revenue Cloud removes that reconciliation work by keeping sales, finance and operations on one shared record.
If your current CPQ setup forces workarounds for approvals, contracts, or usage billing, that friction only grows as your catalog expands. Start with a scoping conversation about where your revenue process breaks down today. Then map which Revenue Cloud modules fix it first.
Frequently Asked Questions
Is Salesforce Revenue Cloud the same as CPQ?
No. Revenue Cloud includes CPQ functionality, but it also covers catalog management, contracts, order fulfillment and billing on the native Salesforce platform.
Why did Revenue Cloud change its name so many times?
The product moved from Revenue Lifecycle Management to Revenue Cloud Advanced to Agentforce Revenue Management as Salesforce added AI agents and repositioned the platform around them. The core capabilities stayed consistent through each rename.
Do I need Revenue Cloud Billing as a separate purchase?
Yes, for full invoicing control. Revenue Cloud Advanced includes basic invoicing, but Revenue Cloud Billing adds dual-entry accounting, custom billing schedules and general ledger functionality as its own SKU.
Can Revenue Cloud handle usage-based pricing?
Yes. Consumption Management tracks usage, applies pricing tiers, forecasts future consumption and handles rollover policies for unused grants.
What does Agentforce actually do inside Revenue Cloud?
Agentforce agents take natural-language requests and turn them into quotes, discounts, or other actions. The quoting agent is available in pilot and teams can build custom agents on top of invocable actions across the platform.
Is Revenue Cloud available to existing Salesforce CPQ customers?
Yes. Salesforce has confirmed CPQ customers keep support and renewal options even as new investment shifts to Revenue Cloud. Teams typically migrate in phases, moving CPQ functions first and adding billing or CLM later.
