Most manufacturers don't lose money on CPQ software. They lose it on the workflow they're already running because they haven't put a CPQ in place yet, and that bill arrives every quarter whether anyone notices it or not.
Here's what the current workflow costs your company, in six categories you can probably already see on your own deals.
The clearest way to answer that is to look at what you're paying right now to not have one. Six places the money goes: time per quote, margin given away, accuracy errors that surface after the invoice, deal velocity lost to approval chains, inconsistency across reps, and visibility leadership doesn't have until the quarter closes.
In a typical manufacturer running quotes through HubSpot plus a spreadsheet plus a few inboxes, a rep spends somewhere between two and six hours building a single quote. Multiply that by the number of quotes the team sends in a month, and the cost shows up as either headcount you wouldn't otherwise need or revenue you couldn't get to in time.
The time isn't going into typing. It's going into pricing lookups, configuration questions, approval emails, and revision rebuilds, none of which a rep should be doing manually in 2026. Removing that work from the rep's day is the single largest productivity unlock most quoting teams have available to them.
When reps have free discounting authority, the average discount creeps up over time. Nobody decides to give away margin, but the rep who wants to close this quarter applies a five-point discount the buyer didn't ask for, and the next rep does the same, and the floor moves. Three years in, list price is theoretical and the gap between list and average sell is wider than anyone tracks.
A CPQ with discount thresholds and approval routing turns this from a culture problem into a configuration problem. Reps can still discount within policy, but anything past the threshold needs a real reason and a real sign-off, and the data shows up in reporting rather than disappearing into the deal notes. Manufacturers who implement this kind of governance routinely recover thirty points of margin they were leaving on the table.
Manual quotes generate a particular kind of expensive problem: the price the customer agreed to isn't the price that gets billed. A rep types a number into a Word doc, ops fulfills against a different number in the ERP, and the dispute lands six weeks later in finance.
Each of those disputes costs hours of finance time, sometimes a discount to make the customer whole, and almost always a hit to the trust between sales and ops. A CPQ removes the gap because the quote is generated from the same pricing the order is fulfilled against, with no retyping in between.
A 48-hour wait for a discount approval is the most common deal-velocity leak we see, and it's also the most invisible. The deal looks active in the pipeline, the quote is marked "in review," and meanwhile the customer is hearing from a competitor whose process took an afternoon.
Aptarro cut their negotiation time by 79% after putting their pricing logic and approval routing into a CPQ. That kind of result doesn't come from making reps work harder, it comes from removing the queues their work was sitting in.
When every rep builds quotes their own way, the customer sees five different prices, five different bundle structures, and five different discount patterns across a sales team. Procurement teams pick up on this fast, and once they know which rep gives the best deal, your pricing power compounds downward.
A central pricing engine with shared rules removes the variance. The product list, the configuration logic, and the discount limits all live in one place, so the price a customer gets in February is the price the same customer would get in November, and the price one rep quotes is the price another would quote.
The most expensive cost of running without a CPQ is the one finance and the CEO feel last. Discount-by-discount, deal-by-deal, the margin profile drifts. Without quote-level data captured in a structured way, there's no dashboard that shows the drift in progress, only a P&L that explains it after the fact.
A CPQ produces the data as a byproduct of running the workflow. Margin per deal, discount frequency by rep, approval cycle times, win-rate by configuration — none of that needs a separate reporting effort, because it's already structured the moment the quote is built.
The reason teams put off CPQ is that the cost of buying it is visible and the cost of not buying it is diffuse. The annual software bill is on a line item. The thirty points of margin, the deals lost to slow approvals, the six hours per quote, the disputes that hit finance — those are spread across functions and quarters, so nobody is the person responsible for the total.
Running the number once usually settles it. Add the rep time, the margin recovery, the dispute cost, and the deal velocity lift, and the comparison stops being close. The cost of having a CPQ is paid once. The cost of not having one is paid every quarter, in dollars that don't show up on any invoice.