Salesforce CPQ implementation
Salesforce CPQ projects succeed or fail on the product catalog and rules, not the software install. One 2026 fact changes the planning: Salesforce no longer sells CPQ to new customers. Existing customers still extend and re-implement it, while new buyers implement Revenue Cloud Advanced. The phases, pitfalls and testing below apply to both.
- CPQ or Revenue Cloud?
- Phases
- Data and testing
- Phased rollout
CPQ or Revenue Cloud?
Per Salesforce (July 2026), Salesforce CPQ is end of sale, not end of life. Existing customers can renew, add users and get support, but new customers can't buy CPQ licenses, and new features go to Revenue Cloud Advanced (RCA).
- Existing CPQ customer re-implementing or expanding? You can stay on CPQ, but weigh the cost of a rebuild against moving to RCA, since the catalog and rule cleanup is the same work.
- New buyer? You'll implement RCA. Salesforce cites 3–6 months for a typical CPQ-to-RCA migration, longer when the logic is complex.
- Certified admins: the CPQ Administrator certification retires February 1, 2027, and Salesforce points candidates to the Revenue Management Consultant exam.
Phases
| Phase | What happens |
|---|---|
| Discovery | Products, pricing, discount policy, approvals, quote documents, integrations |
| Catalog | Products, bundles, features, options and attributes |
| Pricing | Price books, discount schedules, price rules |
| Rules | Product rules (classic CPQ) or constraint-based configuration rules (RCA) |
| Approvals | Advanced Approvals (CPQ) or flow-based approvals (Revenue Cloud) |
| Documents | Quote templates and output |
| Data and integrations | Migration, ERP, contracts, billing |
| Test and train | Real deals, edge cases, user training |
Pitfalls
- Migrating a messy catalog instead of rationalizing it first.
- Encoding every exception as a rule, which makes the model hard to maintain.
- Leaving quote documents until late.
- Skipping real-deal testing.
- Having no owner for the catalog and rules after go-live.
- Porting classic CPQ price rules and scripts one-for-one into RCA instead of redesigning them. Salesforce notes that CPQ-specific objects, custom fields, price rules and scripts don't map directly.
Sizing the catalog
12 product families, 340 SKUs (95 active in the last 24 months)
48 product rules (17 haven't fired in a year), 22 price rules, 3 approval chains
Plan: retire the 245 inactive SKUs and 17 dormant rules before building
→ the build scope drops by roughly two-thirds, and so does test scope
Pull these counts from your org (or your quoting spreadsheets) in week one. They drive the estimate more than anything else.
The hidden workstream
Most CPQ projects underestimate data work. Products need consistent attributes for rules and guided selling, price books need to reflect real pricing, and historical quotes or contracts may need migration. Start a data workstream in the first week: inventory the product catalog, define the attributes each rule will need, assign owners and clean the data in parallel with configuration. A configuration built on messy data passes testing on sample products and fails in production.
What to test
Build test scripts from real historical quotes, including the strange ones. If last year's most complex quote cannot be recreated, the configuration is not ready.
- Every bundle with valid and invalid combinations.
- Pricing: list, discounts, tiers, contracted prices and currency.
- Approvals for each threshold and approver path.
- Quote documents for every template and language.
- Integration: orders, contracts and renewals flowing to ERP or billing.
- Performance on large quotes with many lines.
Ownership
Plan for an owner who maintains products, rules and pricing after launch, with a change process and a sandbox for testing. CPQ systems drift quickly when changes are made directly in production without testing.
Phasing the rollout
Large implementations go better in phases. A first release might cover the core product families, standard pricing, basic approvals and quote documents for one sales team. Later phases add renewals and amendments, complex pricing, partner access, visual configuration and deeper ERP integration. Each phase should go live and be used before the next one starts, so lessons from real users shape the later work. Trying to launch every requirement at once is a common reason CPQ projects slip and lose sponsor support.
Preparing users
Train reps on the quotes they actually build, using their products, and provide quick reference guides for common tasks. Support should be easy to reach in the first weeks after launch.
Where visual configuration fits
For configurable products, reps and buyers benefit from seeing the configuration as they build it. A visual layer depends on the same product attributes and rules, so plan it with the catalog work, not after go-live. RenderDraw provides 2D and 3D configurators and workflows that hand off to CPQ, pricing and Salesforce. Available integrations depend on implementation. Book a demo.
Show the product. Keep the rules and approvals intact.
RenderDraw adds guided, visual product configuration to Salesforce-centered quote workflows: buyers and reps make choices, rules explain conflicts, and a validated selection moves into pricing and the configured quote or proposal workflow.
- Guided configuration. Sections, controls and attributes arranged into a clear buying path.
- Rules with explanations. Invalid combinations are shown and held, not silently passed.
- Pricing handoff. A validated selection carries into the designated pricing system.
- Salesforce CPQ and Revenue Cloud. RenderDraw works alongside them as a visual layer.
Scope an evaluation
Bring one configurable product and its rules. Results depend on rule coverage, source-data quality and integration design.
RenderDraw does not publish accuracy percentages or time-saved claims. Test it on your own plan set.
Questions estimators ask.
Can I still buy Salesforce CPQ?
Not as a new customer. Salesforce CPQ is end of sale for new customers. Existing customers can renew and add users.
What are the phases of a Salesforce CPQ implementation?
Discovery, catalog, pricing, rules, approvals, quote documents, data and integrations, then testing and training.
How long does an implementation take?
It depends on product complexity, data quality and integrations. Salesforce cites 3–6 months for a typical CPQ-to-RCA migration, and longer for complex catalogs.
What causes CPQ projects to struggle?
Messy catalogs, too many rules, quote documents left until late, too little real-deal testing, and no owner after go-live.
Should visual configuration be part of the project?
Plan it with the catalog, because it depends on the same attributes and rules.
Who should own CPQ after go-live?
A named catalog and rules owner, with a change process and a sandbox for testing.
Plan the visual layer with your CPQ project.
Book a demo to see how RenderDraw fits a Salesforce quote workflow.
- Pick one representative product, rule set or RFP.
- Walk it through configuration, pricing and review with RenderDraw.
- Decide on next steps with real output in front of you.
Where these numbers come from
We checked this guide against the standards, manufacturer documents and industry references below (last reviewed November 2026). Figures marked as rules of thumb are typical ranges, not requirements; your project documents, local code and your own cost history govern.