Guide

What Is Salesforce Revenue Cloud (Formerly Agentforce Revenue Management)?

A Complete Guide for Salesforce CPQ Customers

$150 / $200
Growth / Advanced, per user per month
Mar 2025
Salesforce CPQ end of sale
12–18 mo
Full rebuild from CPQ, in practice
Dec 2026
Migration assistant, roadmap target

By Kuldip HillyerPublished Jul 10, 2026Updated Nov 3, 202614 min read

What Is Salesforce Revenue Cloud? A Complete Guide for Salesforce CPQ Customers

Your Salesforce org (native package) versus External platform Where the revenue data lives decides everything else. A Salesforce-native package keeps every transaction record as a standard or managed object inside your org; an external platform keeps its own copies and syncs a subset back. Your Salesforce org (native package)Product2 / Price Book (standard)Quote & Quote LineOrder & Order LineInvoice, Payment, ShipmentContract, Subscription, AssetReports, Flow, Agentforce see all of itExternal platformVendor product catalogVendor quote storeVendor pricing engineSync connector / APIVendor reportingsync
Figure 1. Where the revenue data lives decides everything else. A Salesforce-native package keeps every transaction record as a standard or managed object inside your org; an external platform keeps its own copies and syncs a subset back.

Revenue Cloud is Salesforce's successor product to Salesforce CPQ, covering configuration, pricing, quoting, orders and contracts, priced at $200 per user per month for the Advanced edition (RCA) and $150 for Growth. Billing is a separate product, Revenue Cloud Billing. Revenue Cloud launched as Revenue Lifecycle Management in June 2024, was renamed Revenue Cloud that September, and was marketed as Agentforce Revenue Management (ARM) from October 2025 until Salesforce restored the Revenue Cloud name on September 14, 2026. Most vendors and consultants still use the names interchangeably. For the neutral side-by-side, see Salesforce CPQ vs Revenue Cloud Advanced, side by side.

The most important thing to understand about Revenue Cloud isn't the name — it's the architecture. Ecosystem analysts describe RCA as descended from Salesforce's Vlocity acquisition rather than the SteelBrick codebase behind Salesforce CPQ; Salesforce itself describes it as built on the core platform. Either way, moving from CPQ is a re-implementation of your quoting logic, not an upgrade — Salesforce has no first-party migration tool yet — it has announced a migration assistant with a December 2026 target — and until then points customers to partner-built accelerators (Forsys RevRamp, IdeaHelix, Prodly). Its Winter '27 release also puts new buyer, partner and renewal quoting into Revenue Cloud, not into Salesforce CPQ (what Winter '27 means for CPQ customers).

This guide covers what Revenue Cloud includes, what it costs, what the migration actually involves, who it fits — and how Salesforce-native alternatives like Kugamon compare for teams that want to stay in Salesforce without a rebuild-scale project.

One Product, Several Names

Name Era Notes
Revenue Lifecycle Management (RLM) GA June 2024 Launched on the Salesforce core platform
Revenue Cloud Renamed in Winter '25 (September 2024) Same product, renamed
Agentforce Revenue Management (ARM) From Dreamforce, October 2025 Marketing name aligned to Agentforce
Revenue Cloud Name restored September 14, 2026 Current name; sold as Revenue Cloud Growth and Revenue Cloud Advanced (RCA)
Revenue Management Salesforce's developer guide and Help, 2026 Documentation name: the developer guide says "Revenue Cloud is now Revenue Management"

Salesforce CPQ is not on this list. It is the predecessor product, the SteelBrick managed package Salesforce acquired in 2015, and it has been end of sale since March 2025. Revenue Cloud is a separate product, not a new name for CPQ. If a vendor or consultant uses RLM, RCA, and ARM interchangeably, they're all describing the same successor product. The renames matter for one practical reason: content and training you find under the old names may be outdated. Salesforce has not settled on one name yet either: its price list says Revenue Cloud, while its developer guide and Help pages call the platform Revenue Management. Search for both.

What Revenue Cloud Includes

Where Revenue Cloud keeps quote-to-cash records, next to Kugamon Revenue Cloud: Quotes: in your Salesforce org (Quote + Revenue Cloud objects); Orders: in your Salesforce org (Order; DRO add-on decomposes); Subscriptions: in your Salesforce org (managed as Assets); Invoices: in your Salesforce org (Revenue Cloud Billing (quote-only)); Payments: in your Salesforce org (Billing records; gateway charges); Revenue recognition: in your Salesforce org (Billing subledger; ERP recognizes). 0 sync points. Kugamon: all six records in your Salesforce org, no sync. Your Salesforce orgRevenue Cloud: Salesforce core platformQuotesQuote + Revenue Cloud objectsOrdersOrder; DRO add-on decomposesSubscriptionsmanaged as AssetsInvoicesRevenue Cloud Billing (quote-only)PaymentsBilling records; gateway chargesRevenue recognitionBilling subledger; ERP recognizesKugamonevery record in your orgQuotesKugamon Quote objectOrdersKugamon Order objectSubscriptionsContract and Subscription linesInvoicesInvoice recordsPaymentsPayment records; gateway chargesRevenue recognitionRevenue records (add-on)
Revenue Cloud: 6 in your org only · 0 sync pointsKugamon: 6 in your org · 0 sync points
Figure 2. Where the records live: Revenue Cloud and Kugamon. Both keep every quote-to-cash record in your org, with nothing to sync. The difference is the data model: Revenue Cloud’s new standard objects, pricing procedures and constraint models versus Kugamon’s package on the standard Product and Price Book. Invoices and payments need Revenue Cloud Billing, sold separately (Salesforce); revenue recognition is handed to the ERP. Checked October 2026.

Salesforce sells Revenue Cloud as building blocks on its core platform, and the pricing page marks which ones each edition includes. Under the hood it is a new data model, not the CPQ price rules you have today (see how the Revenue Cloud Advanced data model is laid out).

Building blockWhat it doesGrowth ($150)Advanced ($200)
Product Catalog ManagementAttribute-based catalog, product selling models (one-time, evergreen, termed), bundles and qualification rules; up to 200 attributes per product since Summer '25IncludedIncluded
Salesforce PricingDeclarative pricing procedures, price waterfall, adjustment schedules and decision tables, run on the serverIncludedIncluded
Product ConfiguratorConstraint-based configuration, written in Constraint Modeling Language (CML)IncludedIncluded
Price and quote, order managementQuotes and orders on the standard Quote and Order objects, with ramp deals, groups and cloningIncludedIncluded
Subscription and asset lifecycleAmendments, renewals and cancellations made on AssetsIncludedIncluded
Advanced Approvals, Advanced Doc Gen, Usage SellingApproval chains, quote and contract documents, selling usage products on a quoteIncludedIncluded
Contract Lifecycle ManagementContracts from quotes, clause library, AI clause generation, redliningAvailable for purchaseIncluded
Revenue Management Intelligence, Agentforce templatesPricing, subscription and order analytics; prebuilt agent templates—Included
Dynamic Revenue Orchestration, Invoice Management, External User SupportOrder decomposition and fulfilment plans; invoicing inside Revenue Cloud; partner and customer users—Available for purchase
Revenue Cloud BillingUsage rating, digital wallet, invoicing engine, payments, collections, accounting subledgerA separate product, quoted separately

Revenue recognition is not on the list: Salesforce hands billing data to your ERP for it. Salesforce also describes the platform as API-first and headless, so the same pricing and quoting can run from a partner portal, a self-service page, Slack or an AI agent, not only from the Salesforce screen (Salesforce).

What Revenue Cloud Costs

Cost component Revenue Cloud Advanced Kugamon (Mid-Market CPQ)
License $200/user/month, plus required Sales Cloud licenses $65/user/month, published on the AppExchange listing
Implementation Re-implementation project; no published price. Our estimate for a 50-user rebuild: about $375,000 Typically ¼–⅓ of annual licensing; admin-led, no SI required for most deployments
Timeline 12–18 months in practice 4–8 weeks typical
Migration tooling from Salesforce CPQ Partner accelerators today (Forsys RevRamp, IdeaHelix, Prodly); a Salesforce migration assistant is on the roadmap for December 2026. Quoting logic is still redesigned Native objects carry over; catalog and price books stay in Salesforce

On our 50-user, three-year model, Revenue Cloud Advanced comes to about $897,000 with license, implementation and admin, against about $143,500 for Kugamon CPQ. The Revenue Cloud figures are estimates: the midpoint of the low and high cases in our October 2026 competitor research. Run your own seat count through the ROI calculator — it models Revenue Cloud Advanced, Conga, DealHub, Nue, and Kugamon side by side.

Three things sit outside the per-user price. First, Revenue Cloud is an add-on: it needs a Sales Cloud, Service Cloud or CRM licence underneath, at Enterprise level or above, and Premier Success support is 30% of net licence fees on the Enterprise edition. Salesforce has announced new Core ($195), Advanced ($395) and Max ($550) editions, but they are not yet available for purchase (Salesforce). Any Salesforce-native CPQ, Kugamon included, sits on top of a Salesforce licence; the difference is what goes on top. Second, Revenue Cloud Billing, Dynamic Revenue Orchestration and Invoice Management are quoted separately. Third, Salesforce said in September 2026 that agentic MCP and API calls will consume Flex Credits, at a rate it had not yet published (SalesforceBen). The full breakdown is on our Revenue Cloud pricing page.

What Changed in Revenue Cloud, 2025–2026

Revenue Cloud has moved quickly, which is worth knowing whether you buy it or not: a gap a reviewer complained about last year may be closed now.

WhenWhat changed
Summer '25Agentforce quoting: create and update quotes in plain language in Salesforce or Slack; Salesforce reports 75% less quoting time on its own sales team (Salesforce). Up to 200 attributes per product, from 15 (release notes).
Summer '26Deep Clone copies a whole quote or order; Salesforce Help sets a limit of 6,000 records per cloned transaction and asks customers to contact their account executive above 1,000 lines (Salesforce Help).
July 1, 2026Salesforce completes its purchase of m3ter, a metering and rating engine for consumption billing (Salesforce).
September 3, 2026Salesforce announces Core ($195), Advanced ($395) and Max ($550) editions; they are not yet available for purchase (Salesforce).
September 14, 2026The Revenue Cloud name is restored on Salesforce's website (The Next Web).
September 16, 2026 (Dreamforce)Salesforce says Revenue Cloud customers grew more than 300% in a year, without giving the base, and announces a migration assistant for the CPQ managed package with a December 2026 target (Salesforce+ keynote).
October 12, 2026 (Winter '27)Agent features for buyer self-service, partner quoting and renewal packages, shipping in Revenue Cloud, not in Salesforce CPQ (Salesforce).

The Dreamforce keynote also put promotions and quotes of up to 15,000 lines in the October 2026 release (Salesforce+), and partners' recaps put the first m3ter capabilities in Revenue Cloud in the first half of 2027, a roadmap date (Atrium).

Who Uses Revenue Cloud

Salesforce does not publish a Revenue Cloud customer count. What it does say: about 15% of Revenue Cloud Advanced customers moved from Salesforce CPQ (Salesforce), and, on its Dreamforce 2026 keynote stage, that Revenue Cloud customers grew more than 300% in twelve months, without giving the base (Salesforce+). Its public stories are few. Genius Sports runs Revenue Cloud Advanced with Revenue Cloud Billing, moved from custom objects to standard ones, and passes invoices to its ERP automatically (Salesforce). On the Dreamforce 2026 stage, Workday's CIO said Workday reimplemented Salesforce with Revenue Cloud in seven months with Accenture, and that a transformation like that generally takes a year to 18 months (Salesforce+). Salesforce also says it was named a Leader in Gartner's January 2026 Magic Quadrant for CPQ Applications (Salesforce).

The Migration Reality

1. It's a rebuild, not an upgrade

Your price rules, product rules, and quote templates don't transfer. Each must be redesigned in Revenue Cloud's model. Plan discovery, build, testing, and retraining like a new implementation — because it is one. Salesforce's own Help puts it plainly: treat the move as a redesign rather than a direct migration of existing configurations (Salesforce Help). The migration assistant announced for December 2026 is still a roadmap date; Salesforce has not said what it will leave behind or whether it is included in your licence.

2. Your admin skills don't fully transfer

Revenue Cloud administration differs meaningfully from CPQ administration. Configuration needs specialist skills (Constraint Modeling Language, pricing procedures, context definitions), and reviewers cite documentation gaps. Budget for training or new certification time, and expect a period where your team is slower than it is today.

3. The product is still evolving

Revenue Cloud ships new capabilities each release — which is good — but it also means the product you demo today isn't the product you'll administer in a year. Ask for the roadmap in writing for any feature you depend on.

4. The timeline you hear first is the shortest one

Salesforce's end-of-sale page says a typical migration runs 3–6 months from discovery to go-live (Salesforce). Treat that as a best case. Forsys, a Revenue Cloud implementation partner, says a manual CPQ migration typically runs about twelve months (Forsys), and Workday's CIO put a transformation like Workday's at a year to 18 months. A full rebuild runs 12–18 months in practice.

Who Revenue Cloud Fits

Revenue Cloud is a reasonable path for large enterprises that are committed to Salesforce's full revenue suite, have the budget for an implementation we estimate at about $375,000 for a 50-user rebuild, and want the Agentforce roadmap. It's a harder fit for SMB and mid-market teams: the per-user price is high, the rebuild runs 12–18 months in practice, and the value of the AI layer depends on the underlying data being fully migrated first.

Where Revenue Cloud is strong:

  • Breadth from one vendor: contract lifecycle management with redlining, order decomposition and consumption billing, with high-volume metering from m3ter targeted for the first half of 2027.
  • Channels beyond the sales rep: partner portals, self-service, ecommerce and agents can all quote from the same catalog and pricing.
  • Salesforce's investment: it is where Salesforce's revenue roadmap goes, and Salesforce CPQ gets no new features.
  • An easy approval inside companies that buy only from Salesforce.

Where it is a harder fit:

  • Cost: $150–$200 per user per month on top of the base licence, with billing, orchestration and invoicing quoted separately.
  • Time: a re-implementation, not an upgrade.
  • Skills: Constraint Modeling Language, pricing procedures and context definitions are new to most CPQ admins.
  • Evaluation: there is no free trial; Salesforce offers hands-on workshops instead.

Questions to Ask Before Committing

  • What's the total first-year cost — licenses, implementation, consulting, training — in writing?
  • Can my current Salesforce admin administer Revenue Cloud without new certification?
  • Which of the CPQ features we use today exist in Revenue Cloud now, versus on the roadmap?
  • What migration tooling exists for our quote history and price rules?
  • What happens to our timeline if the implementation slips past renewal?
  • Is the December 2026 migration assistant included in our licence, and what will it not convert in our org?
  • What is our all-in price per user: base edition, Revenue Cloud, Revenue Cloud Billing and any add-ons?
  • How many Flex Credits will our agent and API use consume, and at what rate?
  • Can you name two customers our size live on Revenue Cloud, and how long they took?

The Salesforce-Native Alternative

If what you want is quoting, orders, subscriptions, and billing inside Salesforce — without a rebuild — a native managed package is the middle path. Kugamon uses Salesforce's own Product and Price Book objects, so native reporting works, admin skills transfer, and implementations run weeks. It's rated #1 on the AppExchange for Quote-to-Cash and Subscription Management and is trusted by 150+ companies. See the head-to-head at Kugamon vs Salesforce Revenue Cloud, the broader context in Salesforce CPQ Is End-of-Sale, and the practical steps in How to Migrate Off Salesforce CPQ.

Frequently Asked Questions

Q: Is Agentforce Revenue Management the same as Revenue Cloud Advanced?

In practice, yes. Agentforce Revenue Management was the name Salesforce used for Revenue Cloud from Dreamforce in October 2025 until it restored the Revenue Cloud name on September 14, 2026. Revenue Cloud Advanced is the higher of Revenue Cloud's two editions (Growth and Advanced). The product launched as Revenue Lifecycle Management in June 2024 and was renamed Revenue Cloud that September.

Q: Is Revenue Cloud an upgrade of Salesforce CPQ?

No. Moving means re-implementing your quoting logic on a new data model — ecosystem analysts trace RCA to Salesforce's Vlocity acquisition rather than the SteelBrick codebase behind Salesforce CPQ.

Q: What does Revenue Cloud cost?

$200 per user per month for the Advanced edition ($150 for Growth), on top of required Sales Cloud licenses. Revenue Cloud Billing is quoted separately. Implementation is a separate project that Salesforce doesn't price; our estimate for a 50-user rebuild is about $375,000, and about $897,000 over three years with license and admin. Both are estimates: the midpoint of the low and high cases in our October 2026 competitor research.

Q: Is there a migration tool from Salesforce CPQ to Revenue Cloud?

Not from Salesforce yet. At Dreamforce 2026 Salesforce announced a migration assistant for the CPQ managed package, configuration included, with a December 2026 target. Until it ships, Salesforce points customers to partner-built accelerators (Forsys RevRamp, IdeaHelix, Prodly). Either way, price rules, product rules, and templates still need redesign in Revenue Cloud.

Q: Do I have to move to Revenue Cloud when my CPQ contract ends?

No published deadline requires it. Existing CPQ customers can still renew. Moving to Revenue Cloud is a commercial negotiation and a project decision — make it deliberately.

Q: Will my Salesforce admin be able to run Revenue Cloud?

Not without new learning. Revenue Cloud administration differs from CPQ administration: configuration needs specialist skills (Constraint Modeling Language, pricing procedures, context definitions), and reviewers cite documentation gaps. Budget training time into the project.

Q: What is the difference between Revenue Cloud and Revenue Cloud Billing?

Revenue Cloud (Growth or Advanced) covers the catalog, pricing, configuration, quoting, orders and the asset lifecycle, and on Advanced, contracts. Revenue Cloud Billing is a separate product with no published price: usage rating and a digital wallet, an invoicing engine, payments, collections and an accounting subledger. Advanced can also add Invoice Management for invoicing inside Revenue Cloud. Revenue recognition stays in your ERP.

Q: How does Kugamon differ from Revenue Cloud?

Kugamon is a Salesforce-native managed package using Salesforce's own Product and Price Book objects, with published pricing from $65 per user per month (on the AppExchange listing) and typical 4–8 week implementations. Revenue Cloud is Salesforce's enterprise product with a new data model, $200 per user per month for Advanced, and a full rebuild that runs 12–18 months in practice. The right choice depends on your size, budget, and appetite for a long project.

Next Steps

Model the real numbers against what the move costs, explore Kugamon CPQ, or schedule a demo. We're not the only option, and we don't pretend to be — but if a weeks-long native deployment beats a months-long rebuild for your team, the math will show it. If you're already on RCA, there's a migration playbook from Revenue Cloud Advanced.

Common questions

Frequently asked questions

In practice, yes. Agentforce Revenue Management was the name Salesforce used for Revenue Cloud from Dreamforce in October 2025 until it restored the Revenue Cloud name on September 14, 2026. Revenue Cloud Advanced is the higher of Revenue Cloud's two editions (Growth and Advanced). The product launched as Revenue Lifecycle Management in June 2024 and was renamed Revenue Cloud that September.

No. Moving means re-implementing your quoting logic on a new data model — ecosystem analysts trace RCA to Salesforce's Vlocity acquisition rather than the SteelBrick codebase behind Salesforce CPQ.

$200 per user per month for the Advanced edition ($150 for Growth), on top of required Sales Cloud licenses. Revenue Cloud Billing is quoted separately. Implementation is a separate project that Salesforce doesn't price; our estimate for a 50-user rebuild is about $375,000, and about $897,000 over three years with license and admin. Both are estimates: the midpoint of the low and high cases in our October 2026 competitor research.

Not from Salesforce yet. At Dreamforce 2026 Salesforce announced a migration assistant for the CPQ managed package, configuration included, with a December 2026 target. Until it ships, Salesforce points customers to partner-built accelerators (Forsys RevRamp, IdeaHelix, Prodly). Either way, price rules, product rules, and templates still need redesign in Revenue Cloud.

No published deadline requires it. Existing CPQ customers can still renew. Moving to Revenue Cloud is a commercial negotiation and a project decision — make it deliberately.

Not without new learning. Revenue Cloud administration differs from CPQ administration: configuration needs specialist skills (Constraint Modeling Language, pricing procedures, context definitions), and reviewers cite documentation gaps. Budget training time into the project.

Revenue Cloud (Growth or Advanced) covers the catalog, pricing, configuration, quoting, orders and the asset lifecycle, and on Advanced, contracts. Revenue Cloud Billing is a separate product with no published price: usage rating and a digital wallet, an invoicing engine, payments, collections and an accounting subledger. Advanced can also add Invoice Management for invoicing inside Revenue Cloud. Revenue recognition stays in your ERP.

Kugamon is a Salesforce-native managed package using Salesforce's own Product and Price Book objects, with published pricing from $65 per user per month (on the AppExchange listing) and typical 4–8 week implementations. Revenue Cloud is Salesforce's enterprise product with a new data model, $200 per user per month for Advanced, and a full rebuild that runs 12–18 months in practice. The right choice depends on your size, budget, and appetite for a long project.

Next step

Ready to see it inside Salesforce?

Thirty minutes on your data with someone who has done this before. No pitch — just honest guidance.