CPQ — Configure, Price, Quote — is software that turns a rep’s intent to sell into an accurate, approved quote a customer can sign. It does three jobs in order: configure enforces which products, components, and add-ons can be sold together; price applies the price book, tiered and volume rules, and discount approvals; quote produces the branded document with line items and terms. It sits between the CRM opportunity and the order-and-billing system, so what the rep sells is exactly what finance invoices — no spreadsheet in the middle.
CPQ is not a CRM and it is not a billing system. Your CRM — Salesforce, HubSpot — owns the account and the opportunity; CPQ reads from it and writes the finished quote back, but it does not own the customer record. Billing, invoicing, and revenue recognition happen downstream; CPQ hands the signed quote off as an order. It is also not a contract-lifecycle (CLM) or e-signature tool, though the larger suites now bundle those. And it is not something every company needs: if you sell one or two SKUs at list price, a quote template inside your CRM does the job and a CPQ platform is pure overhead.
Where CPQ sits in quote-to-cash
Quote-to-cash is the chain from a qualified opportunity to collected revenue: configure → price → quote → sign → order → invoice → payment → revenue recognition. CPQ owns the first three links. Everything after the signature belongs to billing and finance systems. This boundary is the source of most CPQ pain: a quote that configures cleanly but can’t be handed to billing without re-keying has solved the sales half and left the finance half broken.
The reason CPQ exists as its own category is that the three steps are coupled. A discount the rep offers has to respect the approval matrix; a bundle the customer wants has to be a legal configuration; the price on the quote has to be the price that flows to the invoice. Do those by hand across Google Sheets and Slack approvals and you get quote errors, margin leakage, and a finance team that interprets what was sold instead of reading it.
When a RevOps team actually needs it
Most teams should not start with CPQ. You quote inside the CRM until quoting becomes the bottleneck. The signals that you have crossed that line are concrete:
- Product and rule complexity. You sell more than roughly 10-15 SKUs, or products have dependency rules (X requires Y, A can’t ship with B), or bundles with their own pricing.
- Pricing that isn’t list. Tiered, volume, subscription, or region-specific pricing that reps get wrong from memory.
- Approvals that live in chat. Discount sign-off routes through Slack or email, and nobody can tell you which version of the quote is final.
- A downstream accuracy gap. Finance re-keys the quote to invoice, or bills something different from what was sold.
Hit two or more of those and CPQ pays for itself as a governance layer between sales creativity and revenue accuracy. Hit none of them and it is a six-month implementation solving a problem you don’t have.
The vendor landscape in 2026
The biggest shift is at Salesforce. The standalone Salesforce CPQ managed package (originally SteelBrick) reached end-of-sale on March 27, 2025 — no new customers can license it. Existing customers keep renewing and receive support, but no new features ship, and Salesforce has not published an end-of-life date. Its successor is Revenue Cloud Advanced, which folds quoting and configuration into a broader revenue platform that also handles billing. Salesforce-native teams on legacy CPQ face a migration decision, not a renewal.
Beyond Salesforce, DealHub targets faster deployment — vendor and partner reports put live dates at 4-8 weeks against 3-6 months for legacy Salesforce CPQ — in the $60-100 per-user/month range. Conga (formerly Apttus) leans into the hardest pricing scenarios, with per-user pricing near $75-100/month and implementations that run $100K-400K at mid-market to enterprise scale. PROS and Vendavo lead with pricing science for businesses whose prices move constantly. For SMB, HubSpot’s built-in quoting covers the low end before a dedicated CPQ is worth the cost.
Common pitfalls
Buying CPQ to fix a pricing-strategy problem. CPQ enforces a pricing policy; it does not invent one. Deploy it over an undefined discount matrix and you automate the chaos.
Guard: Write the price book and the approval thresholds first. CPQ configuration is the last step, not the strategy.
Modeling every edge case in the initial build. Trying to encode every exotic deal is how a CPQ project slips from three months to nine.
Guard: Configure the 80% of deals that follow standard rules; handle the rare configurations as manual exceptions until the volume justifies automating them.
Treating the quote document as the finish line. A beautiful quote that can’t cross into billing without re-keying has solved the visible problem and left the expensive one.
Guard: Map the quote-to-order-to-invoice integration before you sign the CPQ contract, not after go-live.
Related
- Salesforce — the CRM most CPQ deployments attach to, and the vendor whose legacy CPQ end-of-sale is reshaping the market
- HubSpot — built-in quoting that covers SMB needs before a dedicated CPQ earns its cost
- Forecast categories explained — what happens to the pipeline after the quote is signed and the deal moves to commit