Salesforce CPQ Is Past End of Sale. Here Is What That Means in Practice

Let's clear one thing up first. On 19 March 2025, Salesforce CPQ entered the end-of-sale. A lot of people heard that and assumed the product was being switched off. It isn't. End of sale simply means new customers can't buy it anymore. It's not the end of life. If you already run CPQ, you can continue using it, and Salesforce will continue supporting it.

So is there nothing to worry about? Mostly, yes. But there's something worth thinking about. When a vendor stops selling a product, it tells you where its attention is going. Here, it’s Agentforce Revenue Management. You'll still hear plenty of people call it Revenue Cloud, which was its name until the rebrand.

What's actually different

Think about how quoting works in a typical CPQ org. Quotes happen in one corner. Billing happens somewhere else. Renewals follow their own process, and a few spreadsheets quietly hold it all together. Most finance teams know that feeling. It works, but only because one or two people understand how.

Agentforce Revenue Management is built natively on the Salesforce platform. Your catalog, pricing, orders, and billing data share one structure instead of being stitched together.

Here's a simple example. A customer wants 50 extra seats halfway through their term. In a patched-together setup, someone amends the contract. Someone else updates billing. Finance sorts out the numbers at month-end and hopes nothing was missed. In a connected setup, the change just flows through. Fewer hand-offs means fewer mistakes. It also means fewer awkward emails explaining an invoice that looks wrong.

Why people are looking at it now

Selling has got messier. Buyers want subscriptions, usage-based pricing, bundles, and custom terms. Sometimes they ask for all of it in a single deal. Many CPQ orgs were designed for simpler times, so years of custom code got piled on top. That's fine until an admin leaves or a big release lands. Then nobody's quite sure what will break.

AI plays a part too. Salesforce is building its platform around agents, and agents are only as good as the data they can see. If revenue data sits next to customer data, things like guided selling and deal analysis have something solid to work with.

Where projects tend to go wrong

It's rarely the technology. It's usually one of these four things.

• The catalog. Rules, exceptions, and one-off bundles often live in the heads of two or three people. If nobody writes them down, they get rebuilt wrong, or not rebuilt at all.
• Pricing. Discount approvals, partner rates, regional adjustments and contract-specific prices all need careful mapping. A small slip doesn't shout. It quietly leaks revenue for months before anyone spots it.
• Data. Active contracts, subscriptions and amendment history need to move across cleanly. If they don't, your first renewal cycle turns into a clean-up job.
• People. If reps find the new system slower than the old one, they'll find ways around it. Training needs real time. A slide deck the week before go-live won't cut it.

A sensible way to tackle it

Start with discovery. Don't open the configuration screen yet. Write down how quote-to-cash really works today, including the workarounds everyone pretends not to use. Then ask which steps you truly need. Some only exist because the old tool forced them, and you can usually retire a few without anyone noticing.

Next, pick your pace. Some companies move everything at once. Others begin with one product line or business unit and grow from there. Going in phases lowers the risk and gives people time to learn. Just make sure you have a clear plan for how the old and new processes will coexist.

And bring finance in early. These projects tend to start in sales, but many of the real wins are in billing accuracy and a quicker month-end close. If finance hears about it at go-live, you'll miss some of them.

Choosing who helps you

This platform is newer, and the migration path isn't always obvious, so experience counts. If you're planning a Revenue Cloud Advanced implementation look for a partner who asks about your business model before they talk about features. Ask how they handle catalog design and billing schedules. Ask whether they'll tell you when a simpler design is the better option. A good partner will.