See how Wabric solves this
30 minutes with someone who understands complex product manufacturing. No pressure, no script.
Talk with Sales →RFQ automation means responding to every request for quotation automatically - with a valid configuration, a real price, and a complete quote document - instead of letting requests queue behind your sales engineers. For manufacturers of configurable products, it is the difference between answering an RFQ in minutes and answering it in two weeks. Or never.
That last word is not an exaggeration. Every manufacturer we talk to has a version of the same confession: some RFQs simply never get answered. Not the big ones. The medium ones, the awkward ones, the ones that arrived on a Friday, the ones from an unfamiliar buyer that would take an engineer half a day to price. They sit in an inbox until they stop mattering.
This article is about those quotes. What they cost, why they pile up, and what actually fixes it.
The quotes you answer late are bad. The ones you never answer are worse
Start with the ones you do answer. Independent research on inbound response has been consistent for over a decade:
- A Harvard Business Review study that audited 2,241 US companies found that firms contacting a lead within an hour were seven times more likely to have a meaningful conversation with a decision maker than firms that waited even one hour longer. The average company took about 42 hours to respond. (HBR, "The Short Life of Online Sales Leads")
- Drift ran a secret-shopper test on 433 B2B companies: only 7% responded within five minutes, and 55% did not respond within five business days. (Drift Lead Response Survey, 2017)
Those studies cover leads in general. Now consider what an RFQ for a configured product looks like next to a generic web lead. The buyer has already done the specification work. They know the dimensions, the material, the quantity, often the delivery window. An RFQ is not interest - it is intent with a deadline attached. And in configure-to-order markets, that buyer sent the same request to two or three of your competitors in the same afternoon.
If the general-purpose data says slow responders lose to fast ones, RFQs sharpen the effect: the first supplier back with a credible number frames the deal. Everyone after that is negotiating against an anchor they didn't set.
Manufacturing-specific data backs this up. Tacton's State of Manufacturing research found that 79% of manufacturers report problems with quote quality and roughly four in ten still quote manually. Their 2026 edition adds that 62% experience at least moderate margin loss between quote and delivery. Slow, manual, error-prone quoting is not an edge case in this industry. It is the median.
Why RFQs go unanswered in engineer-to-order companies
Nobody decides to ignore an RFQ. It happens structurally, and the mechanism is nearly identical everywhere:
1. Every quote needs an engineer. In most ETO and CTO companies, sales cannot price anything non-standard without technical validation. The RFQ goes into the drawing queue behind live projects - and live projects always win, because they have signed contracts and angry site managers.
2. Triage rewards the familiar. When the queue is long, humans prioritize known customers and easy configurations. The unfamiliar buyer with the slightly odd spec - exactly the RFQ most likely to be a new account - gets triaged to the bottom.
3. There is no cost signal. A lost production hour shows up in a report. An unanswered RFQ shows up nowhere. It generates no complaint, no ticket, no metric. The company never learns what the order would have been worth, so the leak never gets priority.
Run the arithmetic on that leak once and it stops being abstract. Take a company receiving 40 RFQs a month at an average order value of €25,000. If 15% go unanswered or answered too late to matter, that is six requests, €150,000 in monthly pipeline, €1.8M a year - evaporating with zero visibility in any dashboard. Your numbers will differ. The point is that you should know your numbers, and most manufacturers don't, because unanswered RFQs are never counted.
What RFQ automation actually means (and what it doesn't)
The term gets used loosely, so it is worth separating three levels:
Level 1: acknowledgment automation. An auto-reply confirming receipt. This is email hygiene, not automation. The buyer still waits days for a number.
Level 2: workflow automation. The RFQ is logged, routed, assigned, and tracked with response-time targets. Better - nothing falls through the cracks - but every quote still consumes engineering hours. You have organized the queue, not removed it.
Level 3: response automation. The system reads the request, builds a valid configuration against your real product rules, prices it, and returns a complete quote - with the buyer or a salesperson only confirming. This is the level where the economics change, because the engineering bottleneck is gone rather than managed.
Level 3 is only possible if your product knowledge lives in software instead of in your engineers' heads. That is CPQ territory: compatibility rules, pricing logic, and engineering constraints encoded once, applied to every request. (New to the category? Start with what CPQ is and how it works.)
The part most CPQ vendors leave out: the quote is not the finish line
Here is where manufacturers of engineered products get burned by generic quoting tools. A fast quote that engineering later has to redraw is not a fast quote. It is a fast promise, and the two-week delay you removed from the front of the process reappears at the back - now with a signed number attached.
Tacton's own 2026 survey data shows why: only 7% of manufacturers define their configuration rules once and reuse them across systems. Everyone else re-translates between sales tools and engineering tools at every handoff, which is exactly where quotes and delivered products drift apart - and where that 62% margin-loss figure comes from.
The fix is structural, not procedural. If the configurator manipulates a real parametric model - actual geometry, actual constraints - then the quote, the bill of materials, and the production drawings are outputs of the same object. There is no translation step to break. When a buyer confirms a configuration in Wabric, the same model that priced the quote emits the DWG for the factory floor and the itemised BOM (bill of materials) for procurement. Answering an RFQ in minutes is safe because the answer is already manufacturable.
What this looks like in practice
Saku Metall, an Estonian door and hatch manufacturer, ran the classic version of this problem: quoting configured products took around two weeks, every quote crossed an engineer's desk, and the queue decided which requests got answered. After moving quoting onto a configurator built on their real product logic:
- Quote cycle went from two weeks to about two hours
- 90-95% of standard orders became self-service - buyers configure and get their number without waiting for anyone
- Order errors fell by roughly 80%, because invalid configurations can't be quoted in the first place
- The engineering team recovered about 520 hours a year previously spent on quote validation
Payback came in under three months. The revealing detail is the self-service number: when buyers could get an instant, valid quote themselves, most of them preferred it. The RFQs that used to die in the inbox now answer themselves.
Where to start
You do not need to automate everything on day one. The practical sequence:
- Count your leak first. Pull three months of inbound RFQs and mark each one: answered within 24h, answered late, never answered. Multiply the last two buckets by your average order value. This number is your business case, and it takes an afternoon to produce.
- Automate your highest-volume product family, not your hardest one. The 80% of requests that follow known patterns are where the hours are. Leave the exotic ETO work with your engineers - for now.
- Insist on production-ready output. If a quoting tool cannot generate the drawing and the BOM from the same configuration it priced, you are buying Level 2 automation with a Level 3 price tag. Ask the vendor to show the DWG.
The quotes you never answer are the most expensive documents in your company precisely because they never appear in any report. Counting them is uncomfortable. Not counting them is worse.
Want to see what your RFQ response time could look like? Book a demo - bring a real RFQ from your inbox and we'll configure it live.
Frequently Asked Questions
RFQ automation is software that turns an incoming request for quotation into a complete, valid quote without manual engineering work. Full automation covers configuration (checking the request against product rules), pricing, and document generation - not just logging and routing the request.
Within hours, ideally within the hour. Harvard Business Review's audit of 2,241 companies found firms responding within an hour were seven times more likely to reach a decision maker than those waiting longer, while the average company took 42 hours. For configured products, buyers typically send the same RFQ to several suppliers, so the first credible response anchors the deal.
Because every non-standard quote needs engineering validation, and RFQs queue behind live production work. Requests from unfamiliar buyers or with unusual specifications get triaged last, and since unanswered RFQs generate no metric or complaint, the loss stays invisible.
CPQ (Configure, Price, Quote) is the underlying software category: encoded product rules, pricing logic, and quote generation. RFQ automation is one of its outcomes - applying that engine to inbound requests so they get answered in minutes. For engineered products, look for CPQ that also outputs production drawings and a BOM from the same configuration, so fast quotes don't create rework downstream.
Most manufacturers don't know, because unanswered requests are never tracked. The audit is simple: classify three months of inbound RFQs as answered on time, answered late, or never answered, then multiply the latter two by average order value. Even a 10-15% leak on moderate volume typically reveals six-figure annual pipeline loss.
