Salesforce Revenue Cloud

What it is

Salesforce Revenue Cloud is Salesforce’s native quote-to-cash platform and the designated successor to the legacy Salesforce CPQ managed package. It covers product catalog and pricing, configure-price-quote, contracts, order orchestration, asset lifecycle, usage metering and rating, and billing and invoicing on one data model inside the core Salesforce platform. Salesforce markets it as Agentforce Revenue Management (the rename came at Dreamforce 2025), while the product and pricing pages still say Revenue Cloud; the edition most buyers mean is Revenue Cloud Advanced (RCA), which partners still sometimes call by its earlier name, Revenue Lifecycle Management.

Why it shows up in RevOps stacks

Because legacy CPQ stopped growing. Salesforce CPQ went end of sale in March 2025. Salesforce’s own guidance, updated 10 July 2026, is that this is not end of life: there is no end-of-life date, existing customers can renew and add users, and there is no forced migration. But CPQ is in maintenance, and Dreamforce 2026 (15–17 September) announced zero new features for it. Every new capability lands in Revenue Cloud instead:

• Winter ‘27 (GA 12 October 2026): quotes up to 15,000 lines, promotions with coupons and automated discounts, ramp-deal improvements, and Constraint Studio for solver-guided configuration.
• Headless quoting: pricing and approval logic exposed through APIs and Salesforce MCP, so a seller can quote from Slack, Claude, ChatGPT or Gemini while the rules still execute in Salesforce. A renewal agent that weighs usage, support history and negotiated price caps was shown alongside it.
• Consumption billing: Salesforce closed its acquisition of the metering platform m3ter on 1 July 2026; expanded consumption capabilities from that deal are roadmapped for the first half of 2027.
• CPQ Migration Assistant, targeted for December 2026: moves configuration, not only data, from the CPQ managed package. This is a roadmap date, not a shipped product, and Salesforce has not said how it handles custom Apex, quote calculator plugins or document templates.

Salesforce told the Dreamforce audience Revenue Cloud customers grew 300% and that 80 million quotes were created in the past year. Both are vendor figures with no published base.

Pricing reality

List price is public, which is rare in this category. Revenue Cloud Growth is $150 per user/month (quoting and configurator, order capture, subscriptions). Revenue Cloud Advanced is $200 per user/month and adds contracts and orders, consumption and invoicing, and AI and analytics. Both bill annually; Advanced requires an annual contract. Revenue Cloud is a paid add-on on top of Sales Cloud licenses, not a replacement for them, and Revenue Management Intelligence, Agentforce templates, Dynamic Revenue Orchestration and external-user access are priced separately.

At list, 50 RCA users cost $120,000 a year. VendorBenchmark’s reference set puts the median Revenue Cloud discount at 15% for deals under $250,000 and 26% between $250,000 and $1M, so the same 50 seats realistically land near $100,000. The larger number is services: partners quote implementation at 50% to 150% of first-year license, and CPQ re-implementations at $100,000 to $500,000. Salesforce’s own migration page says a typical migration takes 3–6 months; enterprise projects with multiple entities and currencies run longer.

Best for

A RevOps or revenue-systems lead at a Salesforce-standardized company with 50 or more quoting users that is already on legacy CPQ, wants contracts, orders and billing on the same platform, and would rather migrate inside Salesforce than introduce a second vendor. It wins outright when procurement wants one paper and one support contract, and when the product catalog is complex enough that the 15,000-line quote ceiling and Constraint Studio matter.

Not for

Teams whose CRM is HubSpot or Dynamics — Revenue Cloud does not exist outside Salesforce. Not for fewer than about 20 quoting users who just need clean quote documents; PandaDoc or DealHub do that at a fraction of the services bill. And not for a CPQ customer whose current setup works and who has no billing ambition: end of sale means you can stay, and a migration with no new capability on the other side is cost without return.

Versus the alternatives

• Stay on legacy Salesforce CPQ — the default for anyone whose quoting works today. Pick it if you have no consumption-pricing roadmap and want to wait for the December Migration Assistant to ship and be proven by others. Revisit at your next renewal, not before.
• Conga — the other large installed base, now carrying PROS’ B2B pricing and rebate business after the deal closed in February 2026. Pick Conga when price optimization across a complex configured catalog is the problem. For engineered, manufactured products, Tacton (a Leader in the January 2026 Gartner MQ for CPQ) is the specialist to price.
• DealHub — the fastest-growing entrant: Subskribe acquired November 2025, $100M raised January 2026. Pick it when the CRM is not Salesforce, or when a buyer-facing deal room matters more than order orchestration.
• Nue — Salesforce-native, built for credits, commits and metered usage. Pick it over RCA when hybrid AI pricing is the whole problem and you want to avoid a multi-quarter migration SOW.

Background: what CPQ actually covers, the deal desk that usually owns this decision, and the quote-to-cash stack.

Watch-outs

• Migrating is a rebuild, not an upgrade. RCA uses a different data model; CPQ price rules, Apex plugins and ERP integrations built on CPQ objects have no one-to-one equivalent. Guard: inventory every price rule, product rule, plugin and integration before the SOW, and price the rebuild per item rather than accepting a lump-sum estimate.
• The Migration Assistant is a roadmap date. December 2026 is a target. Guard: do not sign a timeline that depends on it; if a partner’s plan assumes it, require a fallback scope priced without it.
• Configuration lives in data records, not just metadata. Price books, product rules and catalog configuration must move between sandboxes together with metadata, which change-set-only release processes handle badly. Guard: budget a DevOps tool that deploys configuration data and metadata in one package before the first sandbox is built.
• The seat price is the small number. Services at 50–150% of year-one license plus separately priced add-ons decide the total. Guard: get a three-year total that itemizes RCA seats, Sales Cloud dependencies, each add-on and partner services, and make the partner’s go-live date a payment milestone.