Insights
How do you scope a CPQ project without starting from the license count?
By Franck Berthelot · August 2026
A CPQ project should be scoped from the product catalog and pricing logic first, not from a license count. The number of seats tells you nothing about how complex your bundles, discount rules, or contract terms actually are.
Start with the catalog
List every product and service actually sold today, including the ones sold as exceptions or side agreements. A CPQ that only models the clean 80% of your catalog will get bypassed for the other 20%, which usually generates the most support tickets.
Then the pricing rules
Discount tiers, approval chains, bundle dependencies: write down the actual logic before choosing any tool configuration. This is also where most of the ambiguity in a CPQ project comes from.
Then the contract cycle and dependencies
Renewals, amendments, and upsells depend on how the original contract was structured in CPQ. Getting this wrong at scoping time is expensive to fix later, since it touches every renewal that follows.
What to prepare
- Full product and service catalog, including exceptions
- Written discount and approval logic
- Examples of renewals and amendments from existing contracts
- List of systems the quote needs to sync with (CRM, billing, ERP)
Limits of this guide
This defines a coherent first scope, not the full solution design: the detailed configuration still depends on the CPQ platform chosen and your existing Salesforce setup.