CPQ Implementation in 2026: What Changes Now That CPQ Is Retired Posted by
Greg ParashisThe short answer: If you are planning a CPQ implementation in 2026, the product you will actually implement is Agentforce Revenue Management (ARM), because Salesforce CPQ stopped being sold to new customers in March 2025. The good news: everything that made CPQ implementations succeed or fail (catalog design, pricing policy, adoption) still applies, and the new platform removes several of the old failure modes.
“CPQ implementation” is still what most people search, because configure-price-quote is the business problem and CPQ is the name everyone knows. But the implementation you would scope today looks different from one scoped two years ago. Here is what changed, what has not, and how to set an implementation up to succeed.
The 2026 reality: you can no longer implement Salesforce CPQ
Salesforce CPQ reached end of sale on March 19, 2025. Existing customers keep running it with support, but new licenses are not sold, so a net-new “CPQ implementation” on Salesforce today means implementing Revenue Cloud, now Agentforce Revenue Management. That is not a downgrade: ARM covers the same configure-price-quote ground plus contracts, orders, billing, and revenue recognition, natively on the platform. If you are comparing options beyond Salesforce, our guide to CPQ alternatives covers the field.
What does a quoting implementation involve now?
- Discovery and catalog modeling. Define the products, bundles, options, and attributes you actually sell. This is the foundation everything else inherits, and it deserves the most senior attention in the project.
- Pricing design. Translate your price book, tiers, and discount policy into ARM’s declarative pricing procedures, and use the project to simplify: implementation is when bad pricing complexity is cheapest to remove.
- Quoting experience. Guided configuration for reps, approval thresholds that protect margin without stalling deals, and quote documents your customers actually understand.
- Integrations. ERP for orders and invoicing, e-signature for execution, document generation where needed. ARM’s API-first design makes these cleaner than the old CPQ package allowed.
- Testing and rollout. Scenario testing against real deals, then a phased rollout by team or segment with training built around how reps actually quote, not around feature tours.
The implementation principles that never changed
Two decades of CPQ projects, on every platform, teach the same lessons. Simple catalogs outperform clever ones: every exception you encode becomes maintenance forever. Discounting policy is an executive decision, not a configuration detail; if leadership will not agree on approval thresholds, no tool fixes that. And adoption is the real deliverable: a technically perfect quoting system that reps route around (because the old spreadsheet is faster) delivers nothing. We structure implementations around those three truths first and the software second.
What makes implementations fail?
Failure mode What it looks like The fix Catalog sprawl Thousands of SKUs modeled one-to-one from a legacy price file Model what you sell going forward, not what you ever sold Pricing exceptions as rules Every historical one-off deal encoded into logic Policy for the 95 percent, approvals for the rest Big-bang rollout Every team, product line, and region cut over at once Phase by sales motion; earn trust with the first team IT-only ownership Sales and finance see the system at go-live for the first time Sales ops and finance co-own catalog and pricing decisions
Working with an implementation partner
The honest case for a partner is pattern recognition: knowing which catalog structures age well, which pricing designs stay maintainable, and where ARM’s newer capabilities change old assumptions. CloudMasonry has implemented quoting platforms across the CPQ era and the ARM era, including for the manufacturers and technology companies featured below. Our revenue platform practice handles scoping through hypercare, and if you are moving off legacy CPQ rather than starting fresh, our migration guide covers that path. Contact us to pressure-test your implementation plan.
Frequently Asked Questions
Can I still implement Salesforce CPQ?
Not as a new customer: Salesforce CPQ reached end of sale in March 2025. New implementations use Agentforce Revenue Management, which covers configure-price-quote plus contracts, orders, billing, and revenue recognition.
How long does a CPQ implementation take?
It depends on catalog and pricing complexity more than anything else. Focused implementations for a single sales motion move fastest; enterprise deployments with heavy integration take longer. A scoping assessment gives a real answer; treat any timeline quoted before one skeptically.
Can we implement it ourselves?
Strong Salesforce teams can, especially for straightforward catalogs. Partners earn their keep on catalog and pricing design decisions that are expensive to reverse later, and on knowing the newer platform’s patterns before your team has had time to learn them.
What is the most common CPQ implementation mistake?
Treating the catalog and pricing design as configuration details instead of business decisions. Complexity encoded during implementation becomes permanent maintenance, so the simplification conversation has to happen before the build, with sales and finance in the room.
Greg ParashisThe short answer: If you are planning a CPQ implementation in 2026, the product you will actually implement is Agentforce Revenue Management (ARM), because Salesforce CPQ stopped being sold to new customers in March 2025. The good news: everything that made CPQ implementations succeed or fail (catalog design, pricing policy, adoption) still applies, and the new platform removes several of the old failure modes.
“CPQ implementation” is still what most people search, because configure-price-quote is the business problem and CPQ is the name everyone knows. But the implementation you would scope today looks different from one scoped two years ago. Here is what changed, what has not, and how to set an implementation up to succeed.
The 2026 reality: you can no longer implement Salesforce CPQ
Salesforce CPQ reached end of sale on March 19, 2025. Existing customers keep running it with support, but new licenses are not sold, so a net-new “CPQ implementation” on Salesforce today means implementing Revenue Cloud, now Agentforce Revenue Management. That is not a downgrade: ARM covers the same configure-price-quote ground plus contracts, orders, billing, and revenue recognition, natively on the platform. If you are comparing options beyond Salesforce, our guide to CPQ alternatives covers the field.
What does a quoting implementation involve now?
- Discovery and catalog modeling. Define the products, bundles, options, and attributes you actually sell. This is the foundation everything else inherits, and it deserves the most senior attention in the project.
- Pricing design. Translate your price book, tiers, and discount policy into ARM’s declarative pricing procedures, and use the project to simplify: implementation is when bad pricing complexity is cheapest to remove.
- Quoting experience. Guided configuration for reps, approval thresholds that protect margin without stalling deals, and quote documents your customers actually understand.
- Integrations. ERP for orders and invoicing, e-signature for execution, document generation where needed. ARM’s API-first design makes these cleaner than the old CPQ package allowed.
- Testing and rollout. Scenario testing against real deals, then a phased rollout by team or segment with training built around how reps actually quote, not around feature tours.
The implementation principles that never changed
Two decades of CPQ projects, on every platform, teach the same lessons. Simple catalogs outperform clever ones: every exception you encode becomes maintenance forever. Discounting policy is an executive decision, not a configuration detail; if leadership will not agree on approval thresholds, no tool fixes that. And adoption is the real deliverable: a technically perfect quoting system that reps route around (because the old spreadsheet is faster) delivers nothing. We structure implementations around those three truths first and the software second.
What makes implementations fail?
| Failure mode | What it looks like | The fix |
|---|---|---|
| Catalog sprawl | Thousands of SKUs modeled one-to-one from a legacy price file | Model what you sell going forward, not what you ever sold |
| Pricing exceptions as rules | Every historical one-off deal encoded into logic | Policy for the 95 percent, approvals for the rest |
| Big-bang rollout | Every team, product line, and region cut over at once | Phase by sales motion; earn trust with the first team |
| IT-only ownership | Sales and finance see the system at go-live for the first time | Sales ops and finance co-own catalog and pricing decisions |
Working with an implementation partner
The honest case for a partner is pattern recognition: knowing which catalog structures age well, which pricing designs stay maintainable, and where ARM’s newer capabilities change old assumptions. CloudMasonry has implemented quoting platforms across the CPQ era and the ARM era, including for the manufacturers and technology companies featured below. Our revenue platform practice handles scoping through hypercare, and if you are moving off legacy CPQ rather than starting fresh, our migration guide covers that path. Contact us to pressure-test your implementation plan.
Frequently Asked Questions
Can I still implement Salesforce CPQ?
Not as a new customer: Salesforce CPQ reached end of sale in March 2025. New implementations use Agentforce Revenue Management, which covers configure-price-quote plus contracts, orders, billing, and revenue recognition.
How long does a CPQ implementation take?
It depends on catalog and pricing complexity more than anything else. Focused implementations for a single sales motion move fastest; enterprise deployments with heavy integration take longer. A scoping assessment gives a real answer; treat any timeline quoted before one skeptically.
Can we implement it ourselves?
Strong Salesforce teams can, especially for straightforward catalogs. Partners earn their keep on catalog and pricing design decisions that are expensive to reverse later, and on knowing the newer platform’s patterns before your team has had time to learn them.
What is the most common CPQ implementation mistake?
Treating the catalog and pricing design as configuration details instead of business decisions. Complexity encoded during implementation becomes permanent maintenance, so the simplification conversation has to happen before the build, with sales and finance in the room.
Client Success Stories
Cappstone
A commercial cleaning and facility maintenance company serving 950+ businesses. Read how CloudMasonry migrated quoting, contracts, and vendor management from Salesforce CPQ to Revenue Cloud Advanced.
ZELUS
A 3D scanning and reality capture company. Read how CloudMasonry rebuilt eight years of Excel pricing logic in Salesforce Revenue Cloud Advanced.
One Identity
A cybersecurity company specializing in unified identity security. Read how CloudMasonry is carving out a dedicated Salesforce environment and migrating legacy CPQ to Revenue Cloud Advanced.
Brava Roof Tile
A premium composite roofing manufacturer. Read how a Salesforce CPQ transformation reduced waste, improved processes, and set their quoting up to scale.