CPQ (Configure, Price, Quote)
The system governing how products are configured, priced and quoted, enforcing rules about what may be sold and at what discount.
The problem it solves
CPQ — configure, price, quote — is the system that turns a product selection into a priced, approved, legally consistent quote. It exists because the alternative is a spreadsheet per rep, and the spreadsheet produces quotes with invalid configurations, unapproved discounts and terms nobody in finance has seen.
The three letters are three distinct problems. Configure enforces which options can be sold together. Price applies the correct rate, currency and discount rules. Quote produces the document and routes it for approval. A business can genuinely need one of these and not the others.
CPQ codifies your pricing; it does not fix it
When it is justified
Count how many quotes per month contain an error caught after they reached the customer. If the answer is near zero, the case is weak regardless of company size.
Measure quote turnaround time. If deals wait days for pricing approval, the bottleneck is the approval routing rather than the document, and that is the part to automate first.
Check discount variance across reps for comparable deals. Wide variance with no approval trail is the clearest signal that pricing control is the problem.
Establish whether your product actually has configuration constraints. A single-SKU subscription business needs pricing and approval, not configuration.
Decide the pricing rules before selecting a tool. Implementations fail far more often on undecided rules than on software.
Where it goes wrong
It is frequently bought to solve a discounting problem that is actually a compensation problem. If the plan rewards closing at any price, CPQ becomes an obstacle reps route around.
Over-constrained configuration blocks legitimate deals, and the workaround — quotes produced outside the system — destroys the control the project was for.
CPQ projects tend to expose that nobody owns pricing. That is a valuable finding and a common reason implementations stall.
The effort is usually underestimated because the work is rule definition rather than configuration, and rule definition requires decisions across sales, finance and product.
RELATED TERMS
Sales Cycle Length
The elapsed time from an opportunity's creation to its close. The time dimension underneath capacity planning and forecasting.
Process Automation
Replacing manual steps with system-executed ones, so the process runs the same way every time.
Paper Process
The contractual, legal, security and procurement steps between verbal agreement and a signed contract.
Compensation Plan
The document defining how a seller earns variable pay: what is measured, at what rates, with what accelerators, caps and clawbacks.
Deal Desk
A cross-functional function reviewing non-standard deals — pricing exceptions, unusual terms, complex structures — before they are committed.
COMMON QUESTIONS
- What is CPQ?
- Configure, price, quote: the system that turns a product selection into a priced, approved quote. Configure enforces which options can be sold together, price applies the correct rates and discount rules, and quote produces the document and routes it for approval. These are three distinct problems and a business may need only one of them.
- When does a company need CPQ?
- When quotes are reaching customers with errors, when deals wait days for pricing approval, or when discount variance across reps for comparable deals is wide and untracked. Company size is a poor trigger on its own — a large single-SKU subscription business may need approval routing and no configuration at all.
- Does CPQ fix discounting?
- Only if discounting is a control problem. If the compensation plan rewards closing at any price, CPQ becomes an obstacle reps work around rather than a constraint they accept — quotes get produced outside the system and the control is lost. Look at the comp plan before buying software to enforce pricing discipline.
- Why do CPQ implementations fail?
- Almost always because the pricing rules were never decided, not because the software was wrong. The real project is getting sales, finance and product to agree what can be sold together, at what price, with whose approval — and that agreement is usually absent, which is why the implementation surfaces it. Decide the rules first.
Learn how to apply this: CRM Admin 101
Definitions are the vocabulary. The courses are where you learn to operate it, with the interactive audit tools.
See the course