A rep at a discrete manufacturer gets an RFQ on Monday morning. The customer wants a quote by end of day. It's a configurable product, a few options to nail down, freight that depends on destination, and a customer-tier discount the rep looks up from a spreadsheet on someone's desktop.
By 4:45 p.m., the quote is still waiting on a manager's approval. The quote goes out at 6 p.m., six hours after the RFQ hit the inbox, with a pricing error in line 3 that nobody caught.This isn't a made-up scenario. One manufacturer described spending nearly six hours quoting a single job and still getting errors. Most discrete manufacturers with configurable or assembled-to-order products have a version of this playing out in their own building every week.
The answer isn't the software. It's the workflow underneath it. Most manufacturing quoting involves at least three separate knowledge holders: the rep who knows the customer, the engineer or operations lead who knows which configurations are actually valid, and the manager who controls pricing authority. When those people don't share a single system, every quote becomes a coordination problem.
The steps look roughly like this. The rep receives the RFQ and opens a configuration spreadsheet to check compatibility. If something isn't clear, they call engineering. They build a line-item list by hand, look up freight in a separate tab, apply the customer's discount from memory or from an email thread, and send the draft to their manager for approval. The manager reviews it after their last meeting. If they have questions, the loop runs again.
No single step is obviously broken. The bottleneck is the handoffs between them.
Discrete manufacturers tend to have a few people who hold a disproportionate share of product knowledge. One manufacturer's team described it directly: there's one person who knows where every bolt lives. That person is the de facto validation layer for any non-standard configuration. The rep builds the quote, the expert reviews it, the rep revises, and the cycle runs until it's right. On a standard job, that's ninety minutes. On a complicated one, it's the whole afternoon.
Pricing follows the same pattern. When there's no enforced list price, every rep decides what margin to apply. The pricing logic lives in too many places, which is why errors still make it onto the quote even after hours of work. The rep doesn't know what they don't know until the manager catches it, and sometimes the manager doesn't catch it either.
A CPQ system for discrete manufacturers doesn't replace the product knowledge. It captures it. The configuration rules that live in the expert's head become validation logic in a shared product library. Compatible options are selectable; incompatible ones aren't available to build. The rep doesn't need to call engineering to confirm a compatibility question, because the system won't allow an invalid configuration in the first place.
Pricing works the same way. Customer-tier discounts live in price books, not in spreadsheets on a shared drive. Volume thresholds trigger automatic pricing adjustments. Freight calculates from the destination and ship method. The rep sees the complete total, including margin, before the quote goes anywhere.
Approval workflows compress the manager bottleneck without removing the oversight. If a quote exceeds the rep's discount threshold, the approval routes automatically. The manager gets a notification, reviews the deal, and approves or returns it with a note. The quote doesn't sit in an inbox waiting for a meeting to clear.
At manufacturers running this workflow, quote time drops from hours to under thirty minutes for a standard configuration. A complex job takes longer, but the handoffs are sequential and tracked rather than scattered across email threads and phone calls.
The realistic target for manufacturing quoting isn't "as fast as email." Configurable products take time because they require decisions, and the pricing depends on those decisions. That's not a flaw to engineer away.
The reasonable goal is a quote out the same day the RFQ arrives, without requiring three people to be simultaneously available. Half an hour, end of day, is an honest and achievable number for most standard configurations. A rep hitting that target consistently is running a process that lets deals move forward. A rep spending six hours on a quote that still has an error in it is rebuilding the same quote multiple times over.
Manufacturing CPQ earns its place by replacing the coordination overhead that turns thirty minutes of real work into an all-day problem. When configuration knowledge, pricing logic, and approval routing all live in the same system, the rep builds the quote once and it goes out correctly.