Revenue Cloud Consulting

We help you plan and implement Revenue Cloud, and decide when and how to move from Salesforce CPQ, which is end of sale but not end of life.

Banner for the GeekMidst service “Revenue Cloud Consulting”, covering Names you will see and CPQ end of sale: what Salesforce says

Revenue Cloud is Salesforce's product for pricing, quoting, contracts and billing on a single data model. GeekMidst helps teams design and implement it remotely from India, and helps existing Salesforce CPQ customers plan a move without rushing. For a product overview, see Revenue Cloud.

Names you will see

Revenue Cloud is the current name on Salesforce's product page. Related and earlier names include:

  • Revenue Lifecycle Management (RLM), which Salesforce calls "an earlier product name".
  • Revenue Cloud Advanced (RCA), the successor Salesforce names for CPQ.
  • Agentforce Revenue Management, from the October 2025 rebrand, still seen in Winter '27 newsroom copy.
  • Revenue Cloud Billing.

Which of these appears on your order form affects scope, so we confirm it with your account team before design starts.

CPQ end of sale: what Salesforce says

Salesforce states that "Salesforce CPQ is end of sale, not end of life." In practice:

  • Existing customers can keep using CPQ, add users and renew.
  • New customers can't buy it.
  • CPQ gets support and critical fixes, but no new features.
  • No end-of-life date has been announced, and Salesforce's page gives no end-of-sale date.
  • The successor is Revenue Cloud Advanced.
  • The page doesn't cover Salesforce Billing's status, so check that separately.

So there is no forced deadline today. The question is when the features you need, or growing customisation debt, make a move worthwhile. Our post on CPQ end-of-sale planning covers the decision, and the CPQ to Revenue Cloud Advanced migration plan sets out the phases.

What Revenue Cloud offers

Salesforce lists an attribute-based catalog with Constraint Builder, asset and subscription management, order orchestration and Tableau Next dashboards. Winter '27 adds up to 15,000 transaction lines per deal, admin setup enhancements and agent enhancements for self-service, partner and renewal quoting (status not stated).

What's included

AreaWhat we cover
Product catalogAttribute-based catalog design and Constraint Builder rules
Pricing and quotingPrice logic, discounting, approvals and quote documents
Contracts and assetsSubscriptions, amendments and renewals
Orders and billingOrder orchestration and the handover to billing or ERP
CPQ assessmentAn inventory of your CPQ configuration, custom code and integrations

How we work

  1. 01

    Discovery

    We review your quote-to-cash process, catalog, pricing rules and current CPQ or billing setup.

  2. 02

    Design

    We map products, attributes and pricing onto the Revenue Cloud data model and agree what to simplify.

  3. 03

    Build

    We configure the catalog, pricing, quoting and approvals in a sandbox.

  4. 04

    Test

    We test quotes, amendments and renewals against real deals, including the edge cases finance cares about.

  5. 05

    Launch

    We move data and cut over in phases where that lowers risk.

  6. 06

    Support

    We fix issues, then help you retire old CPQ customisation in stages.

Prerequisites and licences

Revenue Cloud and its billing capabilities are licensed separately from Sales Cloud, so confirm which products your contract covers. Agent features need Agentforce enabled. A move from CPQ also needs an agreed plan for quotes, contracts and subscriptions.

Who it suits

Companies selling configurable products or subscriptions, CPQ customers reviewing their options, and teams whose quoting has outgrown spreadsheets.

Common mistakes

  • Treating end of sale as a deadline and migrating in a hurry.
  • Recreating every CPQ price rule instead of simplifying first.
  • Leaving billing and ERP integration until quoting is built.

Quoting depends on clean opportunity data, so see Sales Cloud implementation. For ERP links and history, see MuleSoft integration services and data migration.

Questions we hear

Do we have to leave Salesforce CPQ?
Not today. Salesforce says CPQ is end of sale, not end of life. Existing customers can keep using it, add users and renew, and no end-of-life date has been announced.
What is Revenue Cloud Advanced?
It is the successor Salesforce names for CPQ. We confirm with your account team how it appears in your contract alongside the Revenue Cloud name.
Does CPQ still get fixes?
Yes. Per Salesforce it gets support and critical fixes, but no new features.
Can we move in phases?
Usually. Moving one product line or region at a time often lowers risk, and we plan the order in discovery.

Plan your Revenue Cloud or CPQ next step

Tell us how you quote and bill today, and we will suggest whether to optimise, migrate or wait.

Request a consultation →

Next step: Revenue Cloud Consulting

  1. We read it A practitioner reads your message and replies by email.
  2. Short call We confirm goals, constraints and what success looks like.
  3. Written scope You get a scope and estimate before any work starts.

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