Skip to content

Blog / Architecture and integration

What is CPQ? The four parts, and how it fits your CRM and ERP

CPQ means configure, price, quote. What its four parts do, how a quote moves through them, how it differs from a CRM, and how it connects to your ERP.

Simon Cole avatar

Simon Cole

The short answer. CPQ stands for configure, price, quote. It is the software that turns a sales opportunity into an approved, accurate quote. It has four parts: a price book that holds every list price, a quote builder that configures products and quantities from it, pricing rules that check each discount and name who must approve it, and a quote document the customer can sign. A CRM tracks the deal. CPQ decides what is on the quote and what it costs.

CPQ meaning: configure, price, quote

Each word names a job.

  • Configure means choosing what goes on the quote: products, plans, add-ons, quantities and term, only in combinations you actually sell.
  • Price means applying list prices, volume tiers and discounts to that configuration, and checking the result against policy.
  • Quote means producing the document the customer reviews and signs, and keeping a record of every version.

A small company can do all three in a spreadsheet. CPQ software exists for the point where the spreadsheet stops being trustworthy: too many products, too many people quoting, too many discounts to remember.

The four parts of a CPQ

The Helix guide to building a CPQ tool describes the same four parts, and they are a useful way to check any CPQ product or custom build.

  1. A price book. Products, plans and add-ons with list prices, units and volume tiers, kept in one place and edited by one team. Every quote reads from it. If list prices live anywhere else, quotes will disagree.
  2. A quote builder. A step-by-step flow to configure products, price them, review the document and submit. Each quote is versioned, and each version keeps the prices it was built with, so a later price change never rewrites a quote already sent.
  3. Pricing rules and an approval path. The discount guardrails by product, depth and deal size, checked as the numbers change, with the approver each breach needs. A discount inside the rules goes through. One outside them becomes a request to the deal desk.
  4. A quote document. A branded, printable document generated from the approved version: line items, totals, terms, a validity date, and the names of both parties.

The first part decides whether the other three can be trusted. A price book nobody owns gives you fast, well-formatted wrong quotes. If you run a CPQ product today, the guides to pricing guardrails for quotes and quote document generation show how to connect parts three and four to your CRM, e-signature and ERP.

One quote through the four parts

The numbers below are invented, to show the mechanics.

A rep at a software company is quoting a 150-person customer. Price book: the Professional plan lists at $40 per user per month, the platform fee at $12,000 a year, and the analytics add-on at $8,000 a year.

Quote builder: the rep picks the plan, 150 users and a 12-month term. The builder prices the lines from the price book:

LineList priceDiscount askedQuote price
Professional plan, 150 users, 12 months$72,00010%$64,800
Platform fee$12,0000%$12,000
Analytics add-on$8,00025%$6,000
Total$92,00010% overall$82,800

Pricing rules: the company’s rules say a rep can give up to 10%, a manager up to 20%, and anything deeper needs a VP. The plan line is inside the rep’s limit. The 25% on the add-on is not, and the rule fires the moment the rep types it, naming the breach and the approver. The rep does not find out at submission.

The rep submits. The request carries the full economics: the line, the rule it breaks, the overall discount of 10%, and the total of $82,800. The VP approves the add-on discount in a few minutes, from the request itself, without opening another system.

Quote document: the system generates a branded quote from the approved version. It shows the lines, the $82,800 total, the terms and the date the offer expires. The customer signs, and the signed total matches the approved total to the dollar.

That last point is what the whole thing is for. The price came from one source, the discount was checked before it was offered, and the approval is recorded on the quote.

CPQ vs CRM

A CRM and a CPQ both touch the same deal, which is why people confuse them. They own different things.

CRMCPQ
OwnsThe relationship and the pipelineThe offer and its price
Core recordsAccounts, contacts, opportunities, activitiesPrice book, quotes, quote versions, approvals
AnswersWho is the buyer, what stage is the deal, what will we close this quarterWhat is on the quote, what does it cost, is this discount allowed
Main usersSellers, sales managers, marketingSellers, deal desk, sales finance, revenue operations
OutputForecast and pipeline reportsAn approved quote document

Most CPQ products run inside or beside a CRM, because a quote starts from an opportunity and the quote total goes back onto it. A CRM can hold a simple quote. It stops working when pricing needs rules, products need configuring, or discounts need an approval path. The CRM can store the quote, but nothing in it can say whether the quote is allowed.

How CPQ connects to your ERP and billing

A quote does not end the process. Once the customer signs, the deal has to become an order, and the order has to reach the ERP and billing system without anyone retyping it.

This is where deals break after the CPQ has done its job. The approved quote says one thing, the contract changes slightly in signature, and the order is booked by hand from whichever record is open. The first invoice goes out wrong.

A sound hand-off has three habits:

  • Book on the signature event. The order is created when the signing tool says the document is signed, instead of when someone checks.
  • Map every product to an ERP item. A new bundle in the price book that does not exist in the ERP fails at booking, so block the quote until the mapping exists.
  • Carry the quote ID through. Put it on the order and the invoice, so every booked figure traces back to its approval.

The tray.ai guides cover each step: quote to order and CPQ to ERP sync, with the thinking behind them in where signed deals stall and the order-to-cash process.

Who uses CPQ, and signs you need it

CPQ touches four roles:

  • Sellers build quotes and want the right one to be the easiest one to send.
  • Deal desk and sales finance approve discounts and non-standard terms, and want the full economics in front of them.
  • Revenue operations owns the price book and the rules.
  • Finance books the order and wants it to match what was signed.

You probably need CPQ if any of these are true:

  • Quotes are built by copying the last one, and nobody is sure the price list is current.
  • Discounts are approved in Slack or email, and nothing on the quote records who agreed.
  • Quote totals do not match booked orders, and finance spends time finding out why.
  • Deal desk is a bottleneck because every request arrives without the context to decide it.
  • You cannot say what your average discount is, or which discounts won deals.

Having none of these is a good reason to wait. A company with five products and one seller does not need CPQ.

Build or buy

CPQ has traditionally been bought, usually per seat, which means the bill grows with headcount and not with how many quotes you send. A different option has appeared: because the four parts are small and well understood, a team can build its own with an AI assistant and run it on a platform that handles deployment, access and governance.

Neither choice is right for everyone. Buying fits companies with deep manufacturing configurators, very large catalogs with complex bundling rules, or nobody to own an internal app. Building fits companies with a clear price book, discount rules they can write down, and someone in revenue operations to own the result. You can start on the Tray AI Orchestration Platform for $50 a month with Tray Helix Builder Edition, plus usage, and Tray Helix has no per-user fees.

The argument is laid out in why build your own CPQ. For the cost side, see what CPQ costs to buy and to build. If you are reacting to a vendor change, the Salesforce CPQ end-of-sale is the trigger most teams are working from.

Whichever route you take, the CPQ has to connect to your CRM and ERP, and Tray handles that connection.

Frequently asked questions

What does CPQ stand for?

+

CPQ stands for configure, price, quote. It is software that builds a valid quote from a product catalog, applies pricing and discount rules, and produces a quote document the customer can sign.

What is the difference between CPQ and CRM?

+

A CRM owns the relationship: accounts, contacts, opportunities and the forecast. A CPQ owns the offer: which products are on the quote, what they cost, which discounts are allowed and who must approve them. The CRM records that a deal exists, and the CPQ decides what the deal is worth.

Does CPQ replace a CRM or an ERP?

+

No. CPQ sits between them. It reads the opportunity from the CRM, produces the approved quote, and hands the signed quote to the ERP or billing system as an order.

Who uses CPQ?

+

Sellers build the quotes. Deal desk and sales finance approve discounts. Revenue operations owns the price book and the rules. Finance relies on the output when it books the order.

When does a company need CPQ?

+

When quotes are built in spreadsheets, discounts are approved in chat threads, price lists drift out of date, or finance books orders that differ from what the customer signed. Any one of these is a sign the quote has outgrown the CRM.

Connect your CPQ to the CRM and ERP

Tray connects the quote to the order, so a signed deal books exactly as it was approved.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.

Quote to order, step by step