ServicesSalesforce consultingArchitectureImplementationOrg health checkDevelopmentIntegrations and APIsData migrationTesting and QAManaged supportSpecialist supportMarketing Cloud auditDeliverability
SolutionsMarketing Cloud EngagementMarketing Cloud NextSalesforce + BrazeAccount EngagementData Cloud (Data 360)Identity resolutionInsights and segmentsAgentforce and AIMCP integrationsSales and Service CloudReal-time personalisationIntegration solutionsEnterprise AI integrationBy industry
ArchitectureSalesforce CRMData 360Salesforce + BrazeAgentforceCustomer 360API-led integrationEvent-drivenMCP host, client and serverIdentity and consentMCP securityData governanceCI/CD and releasesOur public MCP server
ResourcesEngineering journalDecision guidesSolution blueprintsSalesforce productsProjects and achievementsSales ROI calculatorWhere we workChecklists and templatesPlanning toolsReadiness assessmentGlossaryAbout GeekMidstOur approachOur expertiseContact
CompanyAbout GeekMidstOur approachDelivery methodologyTrust and evidenceProjectsAchievementsBook a consultationContactWhere we workSecurity and data
Book a Consultation

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.

Type
Product guide
Topic
CRM and service
Reading time
4 min
Updated
Author
GeekMidst Team
Reviewed by
Site owner
Billing specialist scanning a signed contract while a colleague checks a blurred quote

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.

Quote document with product line items and totals, built from a product catalogue, with a pricing rule and an approval chain marked approved

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

CapabilityWhat it does
Single data modelPricing, quoting, contracts and billing share one model
Attribute-based catalogDefine products by attributes rather than many separate SKUs
Constraint BuilderRules for valid product configurations
Asset and subscription managementTrack what customers own, amendments and renewals
Order orchestrationCoordinate fulfilment steps after an order is placed
Tableau Next dashboardsRevenue 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

  1. Catalogue first. Decide how products, attributes and bundles will be modelled before building any rules.
  2. Pricing logic. Document every discount, approval and price rule, then remove the ones nobody uses.
  3. Contract lifecycle. Agree how amendments, renewals and cancellations should work.
  4. System of record. Decide what lives in Salesforce and what stays in ERP or billing.
  5. 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.

Workflow diagrams

Explore how the pieces fit together. Select a step to read what happens there.

Workflow

Product configuration workflow

Open full size
Product configuration workflowA sales rep adds a bundle to a quote and selects options in the configurator; product rules validate the configuration and send the rep back with a message if it is invalid, and valid configurations are priced by price rules and saved as quote lines.Product configuration workflowSales repConfiguratorQuoteYesNoAdjustAdds a bundle: From the product catalogue. The rep picks a bundle product on the quote. Bundles group the options that are sold together, so the catalogue design decides how easy this step feels.Adds a bundleFrom the productcatalogueConfigurator: Shows the options. The configurator shows the bundle's features and options, with defaults and required items already set. Good defaults cut most configuration errors.ConfiguratorShows the optionsSelects options: Attributes and quantities. The rep chooses options, quantities and attribute values. Fewer, clearer choices usually beat a long list that relies on rules to catch mistakes.Selects optionsAttributes andquantitiesProduct rules run: Validation, selection, filter. Validation rules block invalid combinations, selection rules add or remove options and filter rules narrow what can be picked. Too many overlapping rules become hard to maintain.Product rules runValidation, selection,filterConfiguration valid?. All validation rules must pass before the configuration can be saved. The check runs on the whole bundle, not on each option alone.Configurationvalid?Rule message: Explains what to change. The rep sees why the configuration failed. Clear rule messages written in sales language save a lot of support requests.Rule messageExplains what tochangePrice rules apply: Bundle and option prices. Price rules set or adjust prices, for example option prices that depend on the bundle. Calculation order matters when several rules touch the same field.Price rules applyBundle and optionpricesQuote lines: Bundle, options, prices. The bundle and its options become quote lines with quantities and prices, ready for discounting, approval and the quote document.Quote linesBundle, options,pricesStartSystem or platformPerson or teamDecisionAlert or exceptionEnd or outcomeOriginal GeekMidst explanatory diagram, not an official Salesforce reference.

Select any step in the diagram, or use Step through, to see what happens at that point and why.

Text version: every step in order
  1. Adds a bundle Sales repFrom the product catalogue

    The rep picks a bundle product on the quote. Bundles group the options that are sold together, so the catalogue design decides how easy this step feels.

    Next: Configurator

  2. Configurator ConfiguratorShows the options

    The configurator shows the bundle's features and options, with defaults and required items already set. Good defaults cut most configuration errors.

    Next: Selects options

  3. Selects options Sales repAttributes and quantities

    The rep chooses options, quantities and attribute values. Fewer, clearer choices usually beat a long list that relies on rules to catch mistakes.

    Next: Product rules run

  4. Product rules run ConfiguratorValidation, selection, filter

    Validation rules block invalid combinations, selection rules add or remove options and filter rules narrow what can be picked. Too many overlapping rules become hard to maintain.

    Next: Configuration valid?

  5. Configuration valid? Configurator

    All validation rules must pass before the configuration can be saved. The check runs on the whole bundle, not on each option alone.

    Next: Yes: Price rules apply; No: Rule message

  6. Price rules apply ConfiguratorBundle and option prices

    Price rules set or adjust prices, for example option prices that depend on the bundle. Calculation order matters when several rules touch the same field.

    Next: Quote lines

  7. Rule message QuoteExplains what to change

    The rep sees why the configuration failed. Clear rule messages written in sales language save a lot of support requests.

    Next: Adjust: Selects options

  8. Quote lines QuoteBundle, options, prices

    The bundle and its options become quote lines with quantities and prices, ready for discounting, approval and the quote document.

    End of the flow.

A sales rep adds a bundle to a quote and selects options in the configurator; product rules validate the configuration and send the rep back with a message if it is invalid, and valid configurations are priced by price rules and saved as quote lines. Original GeekMidst explanatory diagram; not an official Salesforce reference architecture.

Workflow

Pricing and discount approvals

Open full size
Pricing and discount approvalsA sales rep edits a discount; price rules recalculate the quote and, if the discount is over the approval limit, the quote goes to approvers; approved or within-limit quotes are locked and sent, while rejected quotes return to the rep to revise.Pricing and discount approvalsSales repRevenue CloudApproversNoYesYesNoReviseEdits a discount: On quote lines or header. The rep changes a discount or a negotiated price. Allowing discounts only in agreed fields keeps the approval logic simple and auditable.Edits a discountOn quote lines orheaderPrice rules run: List to net price. Price rules and discount schedules recalculate each quote line from list price to net price, so approvers see the real effect of the discount.Price rules runList to net priceOver approval limit?. Approval rules compare the discount, margin or deal terms with the limits your business has set. Keeping the limits in data, not code, makes them easy to change.Over approvallimit?Approver reviews: Manager, finance. Approvers are chosen by rule, for example a manager first and finance for deeper discounts. Each approver sees the quote, the discount and the reason given.Approver reviewsManager, financeApproved?. Each approver approves or rejects with a comment. A rejection at any step ends the chain, so the rep is not left waiting on later approvers.Approved?Returned to rep: With the approver comment. The rep sees the comment and can revise the discount or the deal terms. Resubmitting starts the approval checks again from the new numbers.Returned to repWith the approvercommentQuote approved: Locked for the document. The approved quote is locked so prices cannot change after approval. Later edits reopen the quote and send it back through the checks.Quote approvedLocked for thedocumentQuote sent: Document to the customer. The rep generates the quote document and sends it. Approval history stays on the quote for later audits and win-loss reviews.Quote sentDocument to thecustomerStartSystem or platformDecisionPerson or teamAlert or exceptionEnd or outcomeOriginal GeekMidst explanatory diagram, not an official Salesforce reference.

Select any step in the diagram, or use Step through, to see what happens at that point and why.

Text version: every step in order
  1. Edits a discount Sales repOn quote lines or header

    The rep changes a discount or a negotiated price. Allowing discounts only in agreed fields keeps the approval logic simple and auditable.

    Next: Price rules run

  2. Price rules run Revenue CloudList to net price

    Price rules and discount schedules recalculate each quote line from list price to net price, so approvers see the real effect of the discount.

    Next: Over approval limit?

  3. Over approval limit? Revenue Cloud

    Approval rules compare the discount, margin or deal terms with the limits your business has set. Keeping the limits in data, not code, makes them easy to change.

    Next: No: Quote approved; Yes: Approver reviews

  4. Approver reviews ApproversManager, finance

    Approvers are chosen by rule, for example a manager first and finance for deeper discounts. Each approver sees the quote, the discount and the reason given.

    Next: Approved?

  5. Quote approved Revenue CloudLocked for the document

    The approved quote is locked so prices cannot change after approval. Later edits reopen the quote and send it back through the checks.

    Next: Quote sent

  6. Approved? Approvers

    Each approver approves or rejects with a comment. A rejection at any step ends the chain, so the rep is not left waiting on later approvers.

    Next: Yes: Quote approved; No: Returned to rep

  7. Quote sent Sales repDocument to the customer

    The rep generates the quote document and sends it. Approval history stays on the quote for later audits and win-loss reviews.

    End of the flow.

  8. Returned to rep ApproversWith the approver comment

    The rep sees the comment and can revise the discount or the deal terms. Resubmitting starts the approval checks again from the new numbers.

    Next: Revise: Edits a discount

A sales rep edits a discount; price rules recalculate the quote and, if the discount is over the approval limit, the quote goes to approvers; approved or within-limit quotes are locked and sent, while rejected quotes return to the rep to revise. Original GeekMidst explanatory diagram; not an official Salesforce reference architecture.

Workflow

Quote-to-contract workflow

Open full size
Quote-to-contract workflowAn approved primary quote produces a quote document that the customer reviews; requested changes send the rep back to issue a new quote version, while a signed quote closes the opportunity and generates a contract with subscriptions, which is then activated.Quote-to-contract workflowCustomerRevenue CloudSales repYesNoNew versionQuote approved: The primary quote. Only the primary quote on the opportunity flows into the contract, so marking the right quote as primary matters when several versions exist.Quote approvedThe primary quoteQuote document: From quote template. A template turns the quote lines, terms and totals into a document. Keeping terms in template sections avoids editing text by hand for each deal.Quote documentFrom quote templateCustomer reviews: Email or e-signature. The document goes to the customer for review or signature. The signed copy is stored on the quote so everyone works from the same version.Customer reviewsEmail or e-signatureAccepted?. The customer either accepts the quote as sent or asks for changes. Any change, even a small one, should produce a new quote version rather than an edited PDF.Accepted?Rep revises quote: New quote version. The rep clones or edits the quote, and pricing and approval checks run again. Version history shows the customer exactly what changed.Rep revises quoteNew quote versionSigns the quote: Signed copy stored. The signed document is saved on the quote. The rep then closes the opportunity as won with this quote as primary, which is the usual trigger for the contract.Signs the quoteSigned copy storedContract created: Subscriptions and assets. Subscription quote lines become subscription records on the contract, and one-off products become assets. These records drive renewals and amendments later.Contract createdSubscriptions andassetsContract active: Term dates set. An active contract with correct dates is the base for co-terminated amendments and renewal quotes, so date errors here cause trouble for years.Contract activeTerm dates setStartSystem or platformChannel or touchpointDecisionPerson or teamProcess stepEnd or outcomeOriginal GeekMidst explanatory diagram, not an official Salesforce reference.

Select any step in the diagram, or use Step through, to see what happens at that point and why.

Text version: every step in order
  1. Quote approved Sales repThe primary quote

    Only the primary quote on the opportunity flows into the contract, so marking the right quote as primary matters when several versions exist.

    Next: Quote document

  2. Quote document Revenue CloudFrom quote template

    A template turns the quote lines, terms and totals into a document. Keeping terms in template sections avoids editing text by hand for each deal.

    Next: Customer reviews

  3. Customer reviews CustomerEmail or e-signature

    The document goes to the customer for review or signature. The signed copy is stored on the quote so everyone works from the same version.

    Next: Accepted?

  4. Accepted? Customer

    The customer either accepts the quote as sent or asks for changes. Any change, even a small one, should produce a new quote version rather than an edited PDF.

    Next: Yes: Signs the quote; No: Rep revises quote

  5. Signs the quote CustomerSigned copy stored

    The signed document is saved on the quote. The rep then closes the opportunity as won with this quote as primary, which is the usual trigger for the contract.

    Next: Contract created

  6. Rep revises quote Sales repNew quote version

    The rep clones or edits the quote, and pricing and approval checks run again. Version history shows the customer exactly what changed.

    Next: New version: Quote document

  7. Contract created Revenue CloudSubscriptions and assets

    Subscription quote lines become subscription records on the contract, and one-off products become assets. These records drive renewals and amendments later.

    Next: Contract active

  8. Contract active Revenue CloudTerm dates set

    An active contract with correct dates is the base for co-terminated amendments and renewal quotes, so date errors here cause trouble for years.

    End of the flow.

An approved primary quote produces a quote document that the customer reviews; requested changes send the rep back to issue a new quote version, while a signed quote closes the opportunity and generates a contract with subscriptions, which is then activated. Original GeekMidst explanatory diagram; not an official Salesforce reference architecture.

Questions we hear

Do we have to leave Salesforce CPQ?
Not immediately. Salesforce says CPQ is end of sale, not end of life, and no end-of-life date has been announced. It will not get new features.
Can new customers buy Salesforce CPQ?
No. Salesforce has stopped selling CPQ to new customers and points them to Revenue Cloud.
Is Revenue Lifecycle Management a separate product?
Salesforce describes Revenue Lifecycle Management as an earlier product name. The current name is Revenue Cloud.
How large can a Revenue Cloud deal be?
Winter '27 supports up to 15,000 transaction lines per deal, according to Salesforce.

Weighing a move from CPQ?

Tell us about your catalogue, pricing rules and billing setup, and we will help you plan the next step.

Talk to us →

Tell us what you are trying to fix.

Share your Salesforce setup, goals and constraints. A practitioner reads every message and replies with questions, first thoughts or an honest view of whether you need outside help at all.

Talk to a Salesforce Expert
Book a Consultation