What is CPQ? Configure, Price, Quote explained for usage and AI pricing
Written by Arnon Shimoni
✓ Expert
Last updated on:
CPQ stands for Configure, Price, Quote. It is the first stage of quote to cash: the step where a sales rep assembles a deal from a product catalog, applies the company's pricing rules to it, gets whatever approvals the discount requires, and produces a quote the customer can sign.
The reason CPQ exists as a category is that all three steps go wrong when they live in a spreadsheet. Configurations get built that the product cannot deliver. Prices get quoted that the pricing committee never approved. Quotes go out with arithmetic errors. CPQ software encodes the catalog and the policy so the rep cannot produce a deal the business would not honour.
Field | Detail |
|---|---|
Stands for | Configure, Price, Quote |
What it does | Turns a product catalog plus a pricing policy into an approved, signable quote |
Stage | First of eight in quote to cash |
Owned by | Sales and RevOps, with pricing policy set by finance or a deal desk |
Typical tools | Salesforce CPQ, DealHub, PandaDoc, Conga, Oracle CPQ, plus native CPQ inside billing platforms |
Common failure | The quote and the resulting invoice disagree, because quoting and billing hold two different rate cards |
Breaks when | Pricing is consumption-based and the quote has to express meters, commits and overage rather than fixed line items |
The three steps
Configure. The rep selects products, quantities, terms and options. The configuration engine enforces what is actually sellable: this add-on requires that base plan, this tier caps at that volume, these two modules cannot be sold together. The output is a valid bill of materials rather than a wish list.
Price. The system applies the rate card, contract term, currency, and any customer-specific pricing. Discounts get applied within policy, and anything outside policy triggers an approval. This is where the pricing strategy stops being a document and becomes a rule that executes.
Quote. The priced configuration becomes a document. It needs to be legible to a procurement team, mathematically correct, and specific enough that the eventual invoice matches it. See quoting for what the document itself has to contain.
CPQ versus quote to cash
CPQ is one stage. quote to cash is the whole process: CPQ, then contract execution, order management, provisioning, billing, invoicing, collection, and revenue recognition.
The distinction matters when buying software. A CPQ tool produces a beautiful quote and then hands off. Whether that quote becomes a correct invoice depends entirely on how well it connects to the system that bills. Most of the pain companies attribute to CPQ is actually the handoff.
CPQ | Quote to cash | |
|---|---|---|
Scope | Configure, price, quote | Quote through recognized revenue |
Ends at | A signable quote | Cash collected and recognized |
Primary owner | Sales | Sales, finance and RevOps jointly |
Fails as | Unapprovable or unsellable quotes | Quote-to-invoice mismatch, leakage, restatement |
Why usage-based and AI pricing break traditional CPQ
Classic CPQ assumes a deal is a set of line items with quantities and unit prices. Multiply, sum, discount, sign. That assumption holds for perpetual licences and seat subscriptions. It does not hold for consumption.
A modern AI or infrastructure contract has to express things a line item cannot:
Meters, not quantities. The deal specifies a rate per unit of metered usage, and nobody knows the quantity at signature.
Commitments with drawdown. A minimum commit is prepaid or contracted spend that usage consumes over the term, with rules for rollover and expiry.
Tiered and banded rates. The unit price changes as volume crosses thresholds. See tiered usage-based pricing.
Ramps. The commit steps up across years, and each step has its own rate card.
Credit wallets. The customer buys credits that different actions consume at different rates.
Overage rules. What happens above the commit, at what rate, and whether it is capped. See overage charges.
Hybrid structure. A platform fee plus seats plus usage plus an outcome component, all in one agreement. See hybrid pricing models.
Teams try to force these into line-item CPQ and end up with a quote that describes the deal in prose, a spreadsheet that models it properly, and a billing system configured by hand from the spreadsheet. Three representations of one contract, drifting apart from the day it is signed.
The quote-to-invoice gap
The single most expensive CPQ failure is quoting something the billing system cannot execute. It happens when the two systems hold separate definitions of the same rate card.
The symptoms are recognizable. The first invoice after a big deal needs manual adjustment. Finance keeps a list of accounts that are billed by hand. A discount that was supposed to expire after twelve months is still being applied in year three. Nobody can answer what the effective rate on an account actually is without opening the contract PDF.
This is revenue leakage and margin leakage in their most common form. The fix is architectural rather than procedural: the quote and the invoice should read from one pricing model, so that quoting a deal configures billing rather than describing it.
What good looks like
One catalog. Products, meters and rate cards defined once, referenced by both quoting and billing.
Policy as rules. Discount thresholds, approval routing and floor prices encoded rather than remembered.
Quotes that configure. Accepting a quote provisions the contract in the billing system without a human retyping it.
Consumption modelling. The rep can show the customer a projected bill at expected volume, not just a rate table. See price estimation.
Expiry built in. Every discount, ramp and promotional rate carries an end date the system enforces.
An audit trail. Who approved what, at what price, on what date, tied to the contract that resulted.
Where Solvimon fits
Solvimon holds the product catalog, rate cards, commitments and meters in one model, so a quoted structure and a billed structure are the same object rather than two systems kept in sync by hand. Ramps, commits, credit wallets and tiered rates are native contract shapes rather than workarounds, and accepting a deal configures billing directly.
That closes the quote-to-invoice gap without replacing the CRM. Teams keep quoting where their reps already work, and the pricing logic lives in the system that has to honour it. See our comparison of quote to cash platforms.
Frequently Asked Questions
What does CPQ stand for?
Configure, Price, Quote. It describes the three steps of turning a product catalog and a pricing policy into a quote a customer can sign.
What is CPQ software used for?
It enforces what can be sold and at what price. The configuration engine prevents invalid product combinations, the pricing engine applies approved rates and discounts, and the quoting layer produces the document. Without it, those rules live in spreadsheets and rep memory.
Is CPQ the same as quote to cash?
No. CPQ is the first stage of quote to cash. Quote to cash continues through contracting, provisioning, billing, invoicing, collection and revenue recognition.
Why does traditional CPQ struggle with usage-based pricing?
Traditional CPQ models a deal as line items with fixed quantities and unit prices. Usage-based deals have meters instead of quantities, commitments that draw down over time, tiered rates, and overage rules. Those structures do not fit a line item, so teams model them in spreadsheets instead.
Do I need a separate CPQ tool?
Not always. If your deals are mostly standard and your billing platform can express your contract shapes, native quoting in the billing system avoids the handoff entirely. Dedicated CPQ earns its place when product configuration is genuinely complex or approval workflows are elaborate.
What causes quotes and invoices to disagree?
Two systems holding two copies of the rate card. The quote is generated from one, the invoice from another, and any change to pricing has to be made twice. The gap shows up as manual invoice adjustments and discounts that never expire.
Who owns CPQ?
Sales operations usually owns the tool, finance owns the pricing policy it enforces, and a deal desk arbitrates exceptions. When nobody owns the policy, approval rules decay into rubber stamps.
Related
Quote to cash. The full eight-stage process CPQ starts.
Quoting. The quote document itself, and what it must contain.
Deal management. Approvals, thresholds and the deal desk.
Price configuration. Modelling rate cards and customer-specific pricing.
Hybrid pricing models. The contract shapes modern CPQ has to express.
Best quote to cash platforms. How the tools in this category compare.
Ready for billing v2?
Solvimon is monetization infrastructure for companies that have outgrown billing v1. One system, entire lifecycle, built by the team that did this at Adyen.
