How to implement CPQ
How to implement CPQ in manufacturing, one product family at a time.
CPQ implementations in manufacturing tend to stall for the same reasons: too much scope at once, rules nobody wrote down, and no one who owns the data afterwards. This checklist keeps the first rollout small enough to finish, with quotes your estimators can reproduce, explain and maintain.
Updated
1. Agree on the pilot and its owner
Write down the product family, the person responsible for its rules, and the quoting task you want to improve. Record a baseline using representative customer requests: time to prepare a quote, corrections, and expert reviews. Decide what improvement would justify continuing. Keep the target specific enough that the result can be assessed after a small trial.
2. Inventory the source data
List the price books, size grids, adders, footnotes and rule sheets. Identify units, missing prices, N/A cells and sheets that are only explanatory notes. Write down the rules that live only in someone’s head or in a macro, such as label limits or combinations you never sell. For ReadyVariant, recalculate and save Excel workbooks before uploading; title rows, blank corners and footnotes can stay where they are. Saved values are imported; formulas, macros and external links are not run.
3. Prepare reference cases
Gather five to ten quotes you already sent, plus an invalid combination, a boundary size and a case that needs engineering review, each with the expected result. ReadyVariant publishes a catalog only when every saved reference passes, including rejected and review cases, and each confirmed grid and footnote is covered by one. That proves the selected examples, not every possible combination; review more representative cases during your pilot.
4. Walk through the complete customer task
Have the intended estimator import a real schedule, resolve its exceptions, select a customer, issue the quote and send it. Observe where they pause or ask for help. Review terminology, units, keyboard use, and readability on the screen they actually use. Keep a list of the tasks that still happen outside the product, such as ERP order entry, shop drawings and freight.
5. Rehearse the next price-book update
Change a price or an option in a copy of the source file, upload it as a revision, and check the references again. Confirm that the published version and the quotes issued from it stay unchanged. Ask the person who will own maintenance to perform the update themselves. Do this before deciding the workflow is ready for routine quoting.
6. Decide whether to expand
Compare the pilot with your baseline. Record mismatches, remaining manual work, and the time needed to prepare and maintain the files. Expand only after the expected configurations and prices agree and the estimators can complete the task. Use the next product family to test a new requirement rather than adding the entire catalog at once.
A sample four-week pilot plan
Week 1: choose the product family, name the owner, and collect the price book, one recent schedule and five to ten quotes you already sent. Week 2: import and confirm the price book, save the historical quotes as references, and resolve every mismatch. Week 3: have an estimator quote a live schedule from upload to sent quote while you time it. Week 4: rehearse a price update, compare the results with the baseline, and decide whether to expand. Adjust the pace to your team; the order matters more than the calendar.
Why CPQ implementations stall
Modeling the whole catalog before one quote works. Starting with the ERP or CRM integration instead of the pricing. Rules that exist only in a senior estimator’s head or a spreadsheet macro. No owner for price updates. Success criteria nobody wrote down. Each is avoidable with a small pilot, a written list of rules, a named owner and a baseline measured before the pilot starts.
Common questions
How long does a CPQ implementation take for a manufacturer?
It depends on scope. A pilot on one product family, with its price book and a handful of historical quotes, can be planned in weeks; modeling a full catalog with CAD and ERP integration is a longer project. Start small and expand once the first family reproduces your quotes.
Who should own CPQ at a manufacturer?
Someone who already maintains the price book or approves pricing, usually in sales operations, estimating or product management. They confirm conversions, keep the reference quotes current and publish price updates.
What data do we need before implementing CPQ?
The price book as you publish it (size grids, adders, footnotes and rules), a list of combinations you never sell, and five to ten historical quotes with their totals, including at least one rejected or engineering-review case.
See it with your own data.
Start with one spreadsheet and a result you already know.