What is CPQ?

Complex offers break spreadsheet quoting. A seller picks a module that needs another one, applies an old price list or gives a discount nobody approved, and the error surfaces at contract review or, worse, on the first invoice. CPQ encodes the rules once, so every seller builds a quote the business can actually deliver and bill. It also gives finance and sales leaders a view of discount depth and margin while deals are still open, instead of after they close.

Northwind Analytics sells a platform with add-on modules, three support tiers and pricing in dollars, euros and pounds. A seller opens the opportunity in the CRM, selects the platform for a German customer and adds an analytics module; the configurator adds the required data connector automatically and pulls euro prices from the regional price book. The seller asks for a discount above their limit, so the quote routes to the regional director, who approves it the same afternoon. The approved quote is generated as a branded proposal and attached to the opportunity.

Most CPQ tools are built from the same parts. Use the list to compare vendors or to decide which parts your quoting process actually needs.

• Product catalog and rules. Every product, option and bundle, with the dependencies and exclusions that decide which combinations are valid.
• Price books. List prices by region, currency and channel, with floor prices that a quote cannot go below.
• Discount guardrails. Limits by role, product and deal size, so sellers can discount within a band without asking anyone.
• Approval workflows. Routing for quotes outside the guardrails, based on margin, discount depth or contract value, with a record of who approved what.
• Quote and proposal generation. Branded documents built from approved templates, with terms that match the configured products.
• CRM and billing connections. Quotes created from the opportunity and passed on to contracting and billing without retyping.

1. Map how quotes are built today. Collect recent quotes, list every spreadsheet and template in use, and note where errors and approval delays happen.
2. Clean the product catalog first. Agree one list of products, options and bundles, retire the ones nobody sells, and write down the dependencies between them.
3. Set price books and guardrails. Load list prices by currency and region, then agree discount bands by role with finance and sales leadership.
4. Design the approval matrix. Decide who approves what, at which threshold, and how long a request can wait before it escalates.
5. Pilot with one team and one product line. Run real quotes through the system for a few weeks and fix the rules that block valid deals.
6. Roll out and retire the old templates. Remove spreadsheet quote templates once the pilot is stable, so CPQ becomes the only way to quote.

• Quote turnaround time: from quote request to a quote sent to the buyer
• Quote accuracy: quotes revised after sending because of configuration or pricing errors
• Discount depth by segment, product and seller, against the approved guardrails
• Approval cycle time for quotes that need sign-off
• Seller adoption: the share of quotes built in CPQ rather than in spreadsheets

• Quote-to-cash (QTC)
• Close plan
• Sales cycle length
• Deal review
• Digital sales room