CPQ Software: What It Is and How to Choose a CPQ Tool

What CPQ Software Does

CPQ is an acronym for Configure, Price, Quote. The software automates the path from product catalog to signed quote. A rep selects products. The configuration engine checks which combinations are valid and blocks the ones that are not. The pricing engine applies volume discounts, customer tiers, and multi-year ramp schedules without a finance lookup. The approval engine routes the deal to the right approver based on discount depth, deal size, and product mix. The output is a clean, policy-compliant quote that becomes a proposal and then a contract.

Each of those stages fails quietly when it is done by hand. Configuration rules buried in a spreadsheet get ignored. Pricing tiers turn into a Slack message to finance. Approvals happen in a hallway conversation that never gets logged. A CPQ tool replaces all of that with enforced logic, so a quote that used to take 45 minutes takes 10, and finance stops auditing every deal because the system already enforces the policy.

If your CRM is the system of record for deals, the CPQ sits one layer in, between the opportunity and the contract. For the broader stack it fits into, see the CPQ category page and the full sales tech stack guide.

The Three Tiers of CPQ Solutions

The CPQ market is not one category. It is three, and they barely compete with each other.

Built-in quoting is the entry tier. HubSpot's native quoting handles the use case most B2B companies actually have: pick products, apply a line-item discount, get manager approval, send for signature. For teams with one to three pricing tiers and no configuration rules, it is enough, and it is included with Sales Hub at no extra cost.

Mid-market CPQ is where no-code tools live. DealHub is the reference point here. Sales ops builds and maintains the product catalog, pricing rules, and approval routing without engineering, and changes that take a sprint in enterprise CPQ take an afternoon. This tier fits the majority of B2B companies: 20 to 200 reps, moderate product complexity, no manufacturing-grade configuration.

Enterprise CPQ is built for product complexity, not company size. A SaaS business selling three tiers does not need it. A manufacturer quoting configured equipment with 500 interdependent components does. Salesforce CPQ dominates this tier for Salesforce shops. Conga (formerly Apttus) handles extreme configuration depth. Oracle CPQ serves companies with massive catalogs in the Oracle ecosystem. See the full best CPQ software guide for ranked picks, plus the Salesforce CPQ guide and the HubSpot CPQ guide for platform-native shortlists.

What CPQ Software Costs

CPQ cost has two parts, and most buyers underweight the second one.

Software pricing runs from nothing (HubSpot built-in quoting, included with Sales Hub) to roughly $40 to $80 per user per month for DealHub based on market data, up to $75 to $200 per user per month for Salesforce CPQ, Conga, and Oracle CPQ. Always confirm current pricing on the vendor's own page, because list rates shift.

Implementation is where the real gap appears. HubSpot quoting is an afternoon of setup. DealHub typically goes live in two to six weeks with the customer's own ops team doing the work. Salesforce CPQ runs three to six months and $50K to $200K in consulting for mid-market companies. Conga and Oracle CPQ run four to nine months and $100K to $500K or more. These are standard timelines for products that require deep configuration, not worst cases.

The ROI math holds when you can quantify what manual quoting costs you. Take a 50-rep team where quoting errors leak 2% of margin on $20M in revenue. That is $400K a year. A $150K CPQ investment pays back in roughly four and a half months. For a broader view of stack budgeting, see sales stack budget planning.

How to Choose a CPQ Tool

Start with product catalog complexity, not vendor demos. Under 50 SKUs with simple tiers points to HubSpot's built-in quoting. Fifty to 500 SKUs with approval workflows and some pricing rules points to DealHub. Over 500 SKUs with nested configuration logic, multi-currency global pricing, or manufacturing bills of materials points to Salesforce CPQ or Conga. Oracle CPQ sits at the far end for tens of thousands of SKUs.

Then check the integration chain. Quote data should flow back to the CRM automatically. Approved quotes should connect to e-signature and contract management. Completed contracts should feed billing and revenue recognition. A CPQ that wins the demo but only syncs one direction to your CRM creates more manual work than it removes.

Finally, separate CPQ from adjacent tools. If your pricing fits on a single rate card and reps never configure products, a proposal tool or your CRM's quoting is enough. CPQ earns its cost only when configuration rules, complex pricing, or slow approvals are the thing keeping reps in spreadsheets.