Revenue Cloud overview: scope, names, cost, SAP

Revenue Cloud is Salesforce’s quote-to-cash product on core platform objects: product catalog, configurator, pricing, quotes, orders, contracts and, as an add-on, billing. For a manufacturer it pays off when quotes combine many variants, service contracts or subscriptions and change often after the first order. If a quote is a price lookup in SAP for standard items, Sales Cloud quotes and an ERP interface are usually enough. At list price Revenue Cloud Growth costs €150 and Revenue Cloud Advanced €200 per user and month, on top of Sales Cloud. Before a partner builds anything, settle four points: price master, configurator owner, invoice owner and how long CPQ keeps running.

What does Revenue Cloud cover?

Revenue Cloud is the route from product catalog to invoice, built on standard objects of the Salesforce platform instead of a managed package. The Trailhead module Agentforce Revenue Management Foundations (opens in a new tab) lists its components:

Component	What it does for a manufacturer
Product Catalog Management	One product model with classifications and attributes, which Trailhead calls “the single source of truth for product data”
Salesforce Pricing	Pricing policies and discounts, defined by pricing designers
Rate Management	Rates by consumption, for example for usage-based services
Product Configurator	Valid combinations of options and attributes
Transaction Management	Quotes and order capture across channels
Configure, Price & Quote	A spreadsheet-like quote editor that groups products
Asset Lifecycle Management	The installed base of what was sold, with recurring revenue
Salesforce Contracts	Contracts, obligations and digitised legacy contracts
Dynamic Revenue Orchestrator	Everything after the order, up to fulfilment
Invoice Management	Invoices for delivered products and services

The product page (opens in a new tab) sums it up as one product that “unifies pricing, quoting, contracting, and billing on a single data model”, with “a single, attribute-based catalogue” across all channels. Trailhead adds that composable APIs let other clouds use the catalog and pricing, with Agentforce Manufacturing as the example. For Winter ’27, the release highlights (opens in a new tab) name up to 15,000 transaction lines per deal and agents for buyer self-service, partner quoting and renewal preparation.

For the first decision, two points matter. Revenue Cloud is a different product from Salesforce CPQ, which the CPQ end-of-sale page (opens in a new tab) describes as a managed package around seller-led quoting, with Revenue Cloud Advanced as its successor “built natively on the Salesforce platform”. And Salesforce no longer sells CPQ licences to new customers, so a new project chooses between Revenue Cloud, a partner product and a custom approach.

When does Revenue Cloud pay off for a manufacturer?

I look for these signals in the current quoting process:

Signal	How you recognise it
Variants with rules	Machines with dozens of options that require or exclude each other. A configurator that checks combinations saves rework in order processing.
Service on the same quote	A spare parts package, a maintenance contract and a remote monitoring subscription sold together with the machine.
Changes after the sale	Upgrades, renewals and cancellations that run through quote and order again, based on what the customer already has.
Large quotes	Plant projects with hundreds of lines, grouped by section of the plant.
Several channels on one catalog	Sales desk, dealers and a store selling the same products.

Two or three of these together justify a closer look. One alone rarely does. The full list of signals for and against, with a cost frame, is in Revenue Cloud for manufacturers: when is it worth it?.

Revenue Cloud, RLM, Revenue Management: one product, several names

All of them mean the same product, and the sources were updated at different times. As of late October 2026:

Source	What it calls the product
salesforce.com	Shows “Revenue Cloud” as the heading of the product page, last modified on 22 October 2026, and of the pricing page, with the editions Revenue Cloud Growth and Revenue Cloud Advanced (RCA).
The Developer Guide	For Winter ’27 is titled Revenue Management Developer Guide (opens in a new tab) and says: “Revenue Cloud is now Revenue Management. You may see references to Revenue Cloud in our application and documentation.”
Trailhead	Titles its basic module Agentforce Revenue Management Foundations.
The CPQ end-of-sale page	Calls Revenue Lifecycle Management (RLM) “an earlier product name” and places RCA in “the Agentforce Revenue Management suite”.

Partner blogs report that the Agentforce name came with Dreamforce 2025 and that Salesforce quietly went back to Revenue Cloud around September 2026. I have found no formal announcement for either step, so I treat it as reported. The Agentforce label runs through the whole portfolio; the chapter on terms and the map of my AI masterclass sorts those names.

One older meaning causes real misunderstandings. In November 2020 Salesforce introduced Revenue Cloud (opens in a new tab) as a suite that “brings together CPQ and Billing, Partner Relationship Management and B2B Commerce capabilities”. Quoting and billing in that suite were the CPQ and Billing packages. A partner with “30 Revenue Cloud projects” may mean projects on the CPQ package. Ask which data model the references used.

For contracts my rule is simple: the order form names the edition, every add-on and the SKUs from the Salesforce quote, never just “Revenue Cloud”. The timeline and the search tips are in Revenue Cloud, RLM, RCA: which product name applies?.

What does Revenue Cloud cost?

The pricing page (opens in a new tab) lists two editions per user and month, billed annually:

Edition	List price	Contains
Revenue Cloud Growth	€150 / $150	Quoting and configurator, order capture, subscriptions
Revenue Cloud Advanced	€200 / $200	Growth plus contracts and orders, consumption and invoicing, AI and analytics

The FAQ on that page says Revenue Cloud is a paid add-on to a Sales Cloud subscription. The comparison table marks four add-ons as “Available for purchase”: Contract Lifecycle Management for Growth, and Dynamic Revenue Orchestration, Invoice Management and External User Support for Advanced. The two in the middle carry the note “Freemium access available”, without saying what is included. Revenue Cloud Billing has no published list price. According to the Billing rate sheet from February 2026 (opens in a new tab), it consumes one Billing Event per $50 of invoice amount, with no rollover past the order end date.

A calculation at list price, as an assumption: 50 users who create quotes get Revenue Cloud Advanced, which is 50 × €200 × 12 = €120,000 a year. If they do not have Sales Cloud yet, Sales Cloud Core at €195 per user and month according to the Sales Cloud pricing page (opens in a new tab) adds €117,000. Implementation, the SAP integration and operations come on top.

The number of users moves the budget more than the edition does. I group users by what they do with quotes: create, approve, only read, maintain the catalog, or quote as a dealer.

Add-ons, Billing Events and the licence forecast are in Revenue Cloud pricing: Growth, Advanced and add-ons, and an independent check of a quote is part of make-or-buy and licence forecasts.

These tasks stay in SAP

In a manufacturing company SAP stays, and three tasks usually stay there:

• Pricing conditions. Customer and dealer prices maintained as conditions for years should not be rebuilt in a second system. Salesforce fetches the net price through an API instead.
• Variant configuration. If machines are configured in SAP variant configuration today and the order needs that result, the Revenue Cloud configurator only covers the selling view or stays empty.
• The machine invoice. Delivery, down payments and customs live in SAP. The invoice for a one-off machine sale belongs there too.

The closest documented pattern is use case 3a of the MuleSoft Accelerator for SAP (opens in a new tab). It states that “SAP S/4HANA is the system of record pricing conditions”, fetches the net price per quote line from SAP and creates the order in SAP from Salesforce. Two limits: it covers Sales Cloud and Salesforce CPQ, not Revenue Cloud, and it explicitly leaves out SAP Variant Configuration. The pattern carries over; the design for Revenue Cloud is your partner’s work and needs a review on your side.

My default split per process step:

Step	Default owner	When it moves
Material master, units, status	SAP	never
Catalog for selling, attributes	Revenue Cloud
Configuration	Revenue Cloud	stays in SAP if the rules live in variant configuration
Customer prices	one master, usually SAP	Revenue Cloud for subscriptions and bundles sold only in Salesforce
Quote and approval	Revenue Cloud
Sales order for delivery	SAP, created from Salesforce
Invoice	SAP	Revenue Cloud Billing for recurring revenue sold and changed in Salesforce

If invoices do move, Revenue Cloud Billing (opens in a new tab) can “function as a sub-ledger while synchronizing journal entries” to the ERP. Finance then has to agree on legal entities, accounting periods and account mapping. Three cuts and an owner per object are in Revenue Cloud and SAP: who owns what in quote to cash?, and the interfaces themselves are my work in Salesforce integration.

Where does Revenue Cloud end?

Three other Salesforce products touch the same deals:

• Manufacturing Cloud measures run-rate business: sales agreements with plan against actuals, account forecasts and rebates. A configured quote from Revenue Cloud can become a sales agreement. That side is covered in the chapter agreements and forecasting of the Manufacturing Cloud masterclass.
• B2B Commerce lets dealers and customers reorder known items in a store. For rule-based prices, configurable bundles and Request for Quote, Salesforce Help (opens in a new tab) names a Commerce Growth or Advanced licence together with Revenue Cloud Advanced. When a store pays off is in the chapter is B2B Commerce worth it?.
• Field Service maintains the installed machines. Revenue Cloud keeps what was sold as assets, Field Service works on the machine with its serial number. How the two meet is part of chapter 3.

The overlaps are catalog, price and quote. One catalog, one price master and one quote model, with exactly one product leading each process step. The decision table is in Revenue Cloud, Manufacturing Cloud or B2B Commerce?.

When is Salesforce the wrong answer?

For some manufacturers Revenue Cloud is too much:

• The quote is an SAP price lookup. Sales picks material numbers, SAP calculates. Salesforce then only needs an interface to SAP.
• Few products, few variants. A range of 200 items without options does not need a constraint-based configurator.
• Rules live elsewhere and stay there. If variant rules sit in SAP or in the heads of application engineers and nobody will maintain them twice, the configurator stays empty.
• No recurring revenue. If every sale is a one-off machine and the invoice stays in SAP, the strongest parts go unused.

The alternatives are Sales Cloud quotes with an ERP interface, a CPQ product from a partner, or a custom approach on the platform. I describe the last route in from quote to sales agreement.

Worked example: 25 base models with remote monitoring

A maker of packaging machines with SAP S/4HANA sells 25 base models with options, plus spare parts packages and a remote monitoring subscription per machine. 60 people work in sales; 20 of them create project quotes. Spare parts prices are SAP conditions per customer. All details are assumptions.

I would license Revenue Cloud Advanced for the 20 quote creators: €48,000 a year at list price. Catalog, configurator and quote for machines and subscriptions move to Revenue Cloud. Spare parts on the same quote get their net price from SAP, and the subscription stays an asset in Salesforce for renewals:

Invoices stay in SAP in year one; Billing becomes a question once subscriptions are a business of their own.

First step: price, rules and invoice into the decision log

Partners ask about features. The decisions that drive cost and timeline belong to the company:

Decision	What it includes
Price master	SAP conditions or Salesforce Pricing, per price type, never both for the same price.
Configurator owner	Who maintains variant rules after go-live, and in which system.
Invoice owner	SAP or Revenue Cloud Billing. Finance decides, not the CRM team.
CPQ coexistence	Existing CPQ customers are under no time pressure: the CPQ page says “There is no forced migration”, but also that CPQ “will not receive new features”. A typical migration runs three to six months according to the same page. The details are in chapter 5, from CPQ to Revenue Cloud.

Write these four answers into the decision log before you ask for estimates. They are part of my work on Salesforce architecture. With them settled, chapter 2 on catalog, configurator and pricing covers how the products and prices are modelled; all chapters are on the overview page.