What CPQ actually does
CPQ stands for configure, price, quote. It exists to solve a specific problem: a company sells a product with many valid configurations, the combinations are governed by rules, and salespeople get them wrong. A CPQ system holds the option model, enforces which choices are compatible, derives a price from the resulting configuration and generates a quote document.
The classic examples are enterprise software licensing, telecoms bundles, industrial equipment with option packages, and vehicles. In each case there is a catalogue, there are rules, and there is a correct price for any valid combination. CPQ is genuinely valuable there and it saves companies a great deal of money in mispriced deals.
What CRM actually does
CRM software holds the customer relationship: the accounts, the contacts, the conversations, the open opportunities and the activity history. Its organising object is the deal, and its native question is where each deal sits and what happens next.
A general CRM is deliberately industry-agnostic, which is its strength and its limitation. It will hold anything you tell it to hold, and it knows nothing in particular about any of it. A quote in a general CRM is typically a document with line items and a total, not a cost buildup with material yields, setup minutes and outside-service vendor quotes.
Why a job shop fits neither category cleanly
A job shop does not have a product catalogue. It has a print that arrived this morning for a part nobody has made before. There is nothing to configure, no option rules to enforce, and no price to derive from a configuration — the price comes from an estimator deciding how the part will be made on your machines with your people.
So CPQ, in its pure form, has nothing to work with. And a general CRM has nowhere to put the four cost columns, the quantity breaks, the drawing revision, the outside-service vendor quote and the revision chain that a manufacturing quote actually needs.
This is why so many shops end up with a CRM that holds the customer and a spreadsheet that holds the quote. The arrangement is not stupid; it is a rational response to two products that each solve half the problem. It fails at the seam — the quote leaves as a PDF and stops being a record, so there is no revision history, no follow-up cadence and no way to prove what Rev 2 said.
The distinction that actually decides it
Ask one question: does your price come from a configuration or from an estimate?
If a competent person can derive the price by selecting valid options from a catalogue, you have a configuration problem and CPQ is the right category. If the price requires somebody to decide how the thing will be made — what material to buy, how it will be held, how many setups, which operations are bought out — you have an estimating problem and CPQ has nothing to offer you.
Manufacturers sometimes have both. An equipment builder with a standard machine and an option list has a configuration problem for the base machine and an estimating problem for the custom handling that goes around it. In that case the honest answer is that you need estimating depth with alternates and options, not a full option-rule engine.
What a manufacturing CRM adds
A manufacturing CRM is a CRM whose native objects are the ones a manufacturer works with. The RFQ is a record with line items, materials, processes and a drawing revision. The quote is a cost buildup rather than a document template. Revisions form a chain you can diff. Acceptance locks a revision. The purchase order is matched against what was accepted, and the confirmed order is handed to production.
It does not configure a product, so it is not CPQ. It does not schedule or cost a job on the floor, so it is not an ERP. What it does is hold the customer-facing half of a manufacturing business in a form that matches how that half actually works.
How to choose between the three
Buy CPQ if you sell configurable products from a catalogue and your salespeople produce invalid or mispriced configurations. That is a real and expensive problem and CPQ solves it directly.
Buy a general CRM if your requirement is genuinely relationship and pipeline management, your quoting is simple, and you have someone in-house who will own the configuration if you need to extend it.
Buy a manufacturing CRM if your work arrives as customer drawings, your quoting needs a cost buildup, and you argue with buyers about what a previous revision said. And in all three cases, keep your ERP — none of these categories runs a shop floor, and any vendor suggesting otherwise is selling you an ERP under a different name.
A note on terminology drift
The word CPQ has broadened in marketing usage to mean almost any quoting software, which makes the category label less useful than it was. Several products sold as manufacturing CPQ have no configurator at all and are cost-buildup quoting tools, which is a perfectly good thing to be but is not what CPQ originally meant.
When evaluating, ignore the label and ask a concrete question: show me how you price a part I send you as a drawing, with no catalogue entry, three operations and one outside process. The answer separates the categories faster than any feature comparison.