Configure-Price-Quote (CPQ)
The system and workflow reps use to configure valid product bundles, apply governed pricing, and generate accurate quotes — turning what could be sold into a document a customer can sign.
Key facts
- In one sentence
- The system and workflow reps use to configure valid product bundles, apply governed pricing, and generate accurate quotes — turning what could be sold into a document a customer can sign.
- Primary owner
- RevOps / CPQ admin
- Workflow
- 8 steps, from “Model the product catalog” to “Maintain the catalog and price book”
- North-star metric
- Quote turnaround time — typical target: same-day for standard configurations
What is configure-price-quote (cpq)?
Configure-price-quote (CPQ) is the process — and usually the software — that lets a rep turn a set of customer requirements into a priced, valid, on-brand quote without reinventing pricing logic or product rules deal by deal. "Configure" enforces that the bundle of products and options is actually sellable (no incompatible combinations, no missing prerequisites); "price" applies the list price, discount bands, currency, and any usage or ramp logic; "quote" renders the result into a document the customer can review and sign.
Before CPQ, this logic lives in reps' heads, in spreadsheets, and in tribal knowledge about which discounts a particular deal desk contact will approve. That works at a handful of SKUs and a handful of reps. It breaks down as the catalog grows — multi-product bundles, tiered plans, usage-based add-ons, regional price lists — because every rep is now independently solving a pricing and packaging problem that should have one answer. CPQ centralizes that answer: the catalog, the price book, and the approval rules live in one system, and every quote a rep produces is consistent with it by construction.
CPQ is narrower than quote-to-cash, which continues past the signed quote into order management, provisioning, billing, and revenue recognition — CPQ owns everything up to "quote sent" (and, in most implementations, through signature). It also sits underneath deal desk rather than replacing it: CPQ encodes the standard rules and the discount bands, and automatically routes anything outside them to the deal desk's approval process. Good CPQ shrinks how often that routing has to happen; it doesn't remove the need for human judgment on genuine exceptions.
When to implement
Introduce CPQ once the catalog outgrows a flat price list — multiple products with compatibility rules, tiered or usage-based pricing, multi-currency deals, or bundle-dependent discounting. Prerequisites: a documented product catalog, a published price book with discount authority levels, and standard contract/order-form templates. Below that complexity, a well-maintained pricing spreadsheet with manual review is often the right-sized tool — CPQ implementations are not small projects and shouldn't be started to solve a problem three SKUs don't have.
Step-by-step workflow
- 1
Model the product catalog
Owner: RevOps / Product / Pricing
Define every sellable SKU, bundle, and option, along with the rules that make a configuration valid: prerequisites, mutually exclusive options, quantity constraints, and feature entitlements each item grants downstream in provisioning. This model is the foundation everything else sits on — errors here surface as bad quotes months later.
- Define product hierarchy: core products, add-ons, bundles, packaging tiers
- Encode compatibility rules (prerequisites, exclusions, min/max quantities)
- Map each SKU to the entitlements it grants for provisioning and billing
- Version the catalog with effective dates so historical quotes stay reproducible
- 2
Publish the price book
Owner: Pricing / Finance
List prices by product and packaging tier, discount bands by segment and deal size, and multi-currency or regional price lists where relevant. This is the same price book deal desk uses to define "standard" — CPQ is where it becomes an enforced default rather than a reference document.
- Publish list prices per SKU, tier, and region/currency
- Set self-serve discount authority by role (rep, manager, desk) feeding deal desk thresholds
- Encode ramp, multi-year, and usage-tier pricing logic where applicable
- 3
Build guided selling and approval rules
Owner: RevOps + Sales Ops
Configure the workflows reps actually use: guided flows for common deal shapes, validation that blocks invalid configurations before they reach a customer, and approval triggers wired to the deal desk's matrix so anything outside the standard box routes automatically rather than by someone remembering to ask.
- Build guided flows for the most common deal patterns first
- Wire discount and term thresholds to deal desk approval routing
- Add real-time validation so invalid configurations can't be quoted
- 4
Rep configures and generates the quote
Owner: Sales rep / AE
The rep selects products and options through the configurator; pricing, discounts, and taxes calculate automatically; the system renders an on-brand quote document from an approved template. The rep's job shrinks to describing what the customer needs — the system guarantees the output is valid and correctly priced.
- Configure products/options via guided selling, not a blank quote line
- Review auto-calculated pricing and any flagged deviations before sending
- Generate the quote document from the approved template — no manual edits to pricing logic
- 5
Route exceptions to deal desk
Owner: CPQ system + Deal Desk
Any configuration or pricing outside the standard box — deeper discount, non-standard term, unusual bundle — is flagged automatically and routed into the deal desk approval process rather than left to the rep's judgment or a side-channel Slack message.
- Auto-route by threshold, not by rep memory
- Block quote generation on required approvals until they clear
- Log every exception on the opportunity for the renewal and analytics trail
- 6
Send for signature
Owner: AE + Legal / CLM
Approved quotes flow into the order form and contract, using standard clause templates from the CLM library. Non-standard clauses follow the same exception routing as pricing — legal reviews deviations, not every contract from scratch.
- Generate order form/contract from approved templates
- Route non-standard legal terms through the CLM fallback library
- Send for e-signature directly from the CPQ/CLM workflow
- 7
Sync the closed-won quote downstream
Owner: RevOps / Systems
On signature, the quote's line items, pricing, and terms flow into the CRM opportunity, billing system, and provisioning — without manual re-entry, which is where quote data and invoiced reality most often diverge. This handoff is the start of quote-to-cash's order management stage.
- Sync line items and pricing to CRM and billing automatically
- Trigger provisioning/entitlement activation from the same record
- Reconcile sync failures immediately — silent drift here breaks revenue recognition later
- 8
Maintain the catalog and price book
Owner: RevOps / Pricing
Quarterly: retire unused SKUs and configuration paths, review discount trends and configuration error rates, update price books for new pricing strategy, and encode any renewal price stepping so it fires automatically rather than being renegotiated by hand every year.
- Audit catalog for unused or confusing SKUs and rules quarterly
- Review configuration error and quote revision rates for friction points
- Update price books and discount bands on the pricing team's cycle
Roles & responsibilities
| Role | Responsibility |
|---|---|
| RevOps / CPQ admin | Owns system configuration, catalog model, guided selling logic, and integrations to CRM/billing. |
| Pricing / Finance | Owns the price book, discount bands, margin guardrails, and currency/regional pricing. |
| Sales Ops | Designs guided selling flows and quote templates; trains reps on the tool. |
| Sales rep / AE | Configures and sends quotes within guardrails; escalates genuine exceptions early. |
| Deal Desk | Reviews and approves configurations or pricing routed outside the standard box. |
| Legal | Owns contract templates and the clause fallback library referenced at quote-to-signature. |
Tool stack
CPQ platform
Salesforce CPQ · DealHub · Subskribe · Nue · PandaDoc — catalog model, price book, guided selling, and approval workflow
CRM
Salesforce · HubSpot — opportunity record the quote is generated from and synced back to
CLM / e-signature
Ironclad · LinkSquares · DocuSign · Dropbox Sign — contract templates, clause fallbacks, and execution
Billing / subscription management
Zuora · Chargebee · Stripe Billing — receives synced quote line items for invoicing and revenue recognition
Analytics
BI on CPQ/CRM data — quote funnel, error rate, and discount reporting
Key metrics
| Metric | Definition | Formula | Typical target |
|---|---|---|---|
| Quote turnaround time | Time from configuration start to a sendable quote. | Quote-sent timestamp − configuration-start timestamp (median) | same-day for standard configurations |
| Quote-to-close conversion rate | Share of sent quotes that convert to signed deals. | Signed quotes ÷ quotes sent | trend-stable or improving; investigate drops by segment |
| Configuration error rate | Share of quotes requiring correction after generation — the system's accuracy proxy. | Quotes revised for a config/pricing error ÷ quotes generated | < 5% |
| List price realization | Realized price vs. list, weighted across closed deals. | Sold price ÷ list price, weighted by deal value | trend-stable or improving; watch for discount creep |
| Quote revision count | Average number of edits a quote goes through before signature — a proxy for configurator and pricing clarity. | Total revisions ÷ signed quotes | < 2 |
| Exception routing rate | Share of quotes requiring deal desk approval — the size of the non-standard surface CPQ hasn't absorbed. | Quotes routed to approval ÷ quotes generated | declining over time |
Common failure points
| Failure | Symptom | Fix |
|---|---|---|
| Catalog sprawl | Hundreds of SKUs and legacy configuration paths; reps guess which bundle applies and often guess wrong. | Quarterly catalog audit; retire unused SKUs and rules; constrain reps to guided flows for the common cases. |
| Shadow quoting | Reps build pricing in spreadsheets or email because the tool is slower or missing a needed configuration, bypassing every guardrail it exists to enforce. | Fix the specific friction reps are routing around; disable manual pricing overrides outside the system; measure shadow quoting directly by comparing signed contracts to CPQ records. |
| Approval rules out of sync with deal desk | CPQ auto-approves what deal desk would reject, or routes routine deals into unnecessary review. | Co-design and jointly own the approval matrix between CPQ admin and deal desk; test thresholds against real deal mix before rollout, not after complaints. |
| Stale price book | List prices, currency rates, or discount bands haven't been updated in a year; quotes reflect pricing strategy that no longer applies. | Tie price book updates to the pricing team's review cycle; alert on price book age. |
| Silent integration drift | CRM, CPQ, and billing disagree on what was actually sold; revenue recognition breaks discovering it after close. | Monitor sync jobs actively, alert on failures immediately, and reconcile CPQ-to-billing records on a schedule, not only when finance complains. |
| Configurator too rigid for real deals | Legitimate but slightly unusual requests get hard-blocked; reps escalate every deal manually, defeating the point of guided selling. | Build a fast, visible exception path alongside hard blocks; collect rep feedback on false-positive blocks and loosen rules that fire too often. |
| No renewal price stepping | Ramp and multi-year discounts don't step up automatically at renewal; each renewal becomes a fresh manual negotiation the system should have handled. | Encode renewal pricing logic into the original quote so it fires from the contract terms, not from someone remembering to renegotiate. |
Frequently asked questions
- What's the difference between CPQ and deal desk?
- CPQ is the system that encodes standard catalog, pricing, and approval rules and lets reps self-serve within them; deal desk is the judgment layer that reviews and structures whatever falls outside those rules. CPQ routes exceptions to deal desk automatically — the two are designed to work together, not as alternatives to each other.
- Do we need CPQ if we're small?
- Not usually. Below roughly a handful of SKUs with simple, flat pricing, a well-maintained spreadsheet with manual review covers the same ground with far less implementation overhead. CPQ earns its cost once the catalog has real compatibility rules, tiered or usage pricing, or multiple currencies — the point where manual consistency starts failing.
- Which CPQ tool should we choose?
- Salesforce CPQ (now part of Revenue Cloud) is the default for Salesforce-native orgs with complex enterprise catalogs; DealHub, Subskribe, and Nue are commonly chosen for faster implementation and stronger usage-based/subscription pricing support; PandaDoc CPQ suits simpler catalogs prioritizing quote-document speed. Evaluate against your actual catalog complexity and billing system, not brand recognition — CPQ migrations are expensive to redo.
- How does CPQ relate to billing and revenue recognition?
- CPQ hands off the signed quote's line items, pricing, and terms to the billing system, which is where quote-to-cash continues into invoicing and revenue recognition. Any manual re-entry or sync failure at that handoff is the single most common source of rev-rec errors — the integration between CPQ and billing deserves as much design attention as the configurator itself.
- How long does a CPQ implementation take?
- For a moderately complex catalog, commonly 2–4 months for the initial rollout — catalog modeling and price book setup are usually the long pole, not the software configuration. Phasing in guided flows for the highest-volume deal types first, rather than modeling the entire catalog before launch, gets reps live faster and surfaces catalog problems on real deals instead of in a spreadsheet.
Download the SOP
The standard operating procedure for this process — purpose, roles, step-by-step procedure with checklists, metrics, and failure modes — is available as a Markdown file you can drop into Notion, Confluence, or any wiki and adapt.
↓ Configure-Price-Quote (CPQ) SOP (.md)Related processes
- Deal DeskA cross-functional function and approval process that structures, prices, and approves non-standard deals — keeping discounts governed, terms clean, and sales cycles fast.
- Quote-to-Cash (QTC)The end-to-end revenue pipeline from configuring a quote through contracting, order management, billing, collections, and revenue recognition — where deals become dollars.
- RevOps ReportingThe system of record for go-to-market performance: one metric dictionary, one funnel, and a reporting cadence that gives leadership numbers they can trust and act on.
Cite this page
“Configure-Price-Quote (CPQ): definition, workflow, roles, metrics & SOP.” b2bprocess.com, updated 2026-07-31. https://b2bprocess.com/configure-price-quote