In engineer-to-order manufacturing, the quote is where you win or lose the order, and it often takes weeks. Most of that time isn't engineering. It's waiting: for clarifications, for the one estimator who knows the product, for an approval sitting in someone's inbox. This post shows you where the time goes, what to automate first, and how to prove it worked.
The short answer
- Measure before you automate: time each quote stage and separate time worked from time waiting.
- Automate in this order: RFQ intake and spec extraction, design reuse, configuration and pricing rules, then AI-assisted spec review.
- Track median turnaround, the slowest 10% of quotes, revision count, and quoted-date accuracy, not just averages.
Why quote speed matters more right now
When lead times are long, customers commit early. Wood Mackenzie's second-quarter 2025 survey put average lead times at 128 weeks for power transformers and 44 weeks for switchgear. Buyers in that market want a credible price and a delivery date they can plan around, and they want it soon.
The problems aren't new. A study of make-to-order firms by Kingsman, Hendry, Mercer and de Souza found weak coordination between sales and production at the enquiry stage, delivery dates quoted without checking the workload, and bid and pricing decisions made by informal rules that were rarely written down. It also noted that firms can't afford to fully specify and cost every enquiry, so they have to decide where to spend estimating effort. All of that still describes many quoting departments today.
The six stages of an ETO quote
- RFQ intake. The request arrives by email or portal with specifications, drawings, and commercial terms, often across several documents.
- Spec review and bid decision. Someone reads the specification, flags deviations and risks, and decides whether to bid.
- Configuration. The requirement is mapped to a product design: ratings, options, accessories.
- Engineering. Design calculations, a preliminary bill of materials, and drawings where needed.
- Pricing. Material and labor cost, margin, and a delivery date.
- Approval. Commercial, technical, and sometimes finance sign-off before the quote goes out.
- 1RFQ intake
Specs, drawings, and terms arrive, often across several documents.
- 2Spec review and bid decision
Deviations and risks flagged; bid or no bid.
- 3Configuration
Ratings, options, and accessories mapped to a design.
- 4Engineering
Calculations, a preliminary bill of materials, and drawings.
- 5Pricing
Material and labor cost, margin, and a delivery date.
- 6Approval
Commercial, technical, and finance sign-off.
Where the time actually goes
Time ten recent quotes through each stage. For each one, record when the work arrived, when someone started, and when it was finished. The difference between arrival and start is queue time. Start to finish is work time.
Then calculate flow efficiency: work time divided by total elapsed time. An illustrative example: a quote takes 15 working days from RFQ to send, and the people involved spent a combined 3 days actually working on it. Flow efficiency is 3 ÷ 15 = 20%. The other 80% is waiting, and that's the part automation and better handoffs can remove fastest.
Patterns to look for:
- Re-keying. Someone copies requirements from a PDF into a spreadsheet, then again into the ERP.
- Single points of knowledge. One senior estimator or engineer handles every unusual quote.
- Blank-sheet engineering. Designs are started from scratch when a close match was built two years ago.
- Clarification loops. Questions to the customer go out late because nobody read the spec closely until engineering started.
- Approval queues. Quotes wait for sign-off from people who are traveling or in meetings.
What to automate first
1. RFQ intake and document extraction
Pull key fields out of incoming specifications automatically: voltage and power ratings, standards, cooling, accessories, delivery terms, penalties. Put them into one structured record that every later stage uses. This removes re-keying and lets a person check extracted values instead of hunting for them. Keep a human check on every extracted field until you've measured the error rate.
2. Design reuse
Make past designs searchable by their key parameters. When a new RFQ arrives, the system suggests the closest previous designs, with their actual costs and any issues found in production. Engineering then starts from a proven design and only works the differences.
3. Configuration and pricing rules
Write down the rules your best estimators use: which options go together, which don't, how ratings drive materials, and how margin varies by customer and risk. Put them in a configure-price-quote tool or a rules engine. Start with your most common product families, where the rules are clearest. Leave true one-off designs to engineers.
4. AI-assisted spec review
A language model can read a long specification and flag clauses that differ from your standard offering: unusual tests, penalties, materials, or standards. It doesn't make the bid decision. It gives the reviewer a short list of things to check, so clarification questions go out on day one instead of week two. Test it on past RFQs where you already know the answer before trusting it on live ones.
5. Approval routing
Set approval thresholds by value, margin, and risk, so routine quotes don't wait for the most senior signer. Route approvals to mobile and set a time limit before they escalate.
How to measure turnaround
| Metric | How to calculate it | Why it matters |
|---|---|---|
| Median turnaround | Median working days from RFQ receipt to quote sent | Averages hide the typical case when a few quotes drag on |
| 90th percentile turnaround | The turnaround that 90% of quotes beat | Shows your slowest, often largest, opportunities |
| Flow efficiency | Work time ÷ total elapsed time | Shows how much is waiting versus working |
| Revisions per quote | Number of reissued quotes before award or loss | Reveals weak spec review or rule gaps |
| Quoted-date accuracy | Share of won orders delivered by the date quoted | Fast quotes with bad dates create problems later |
| Win rate by turnaround band | Win rate for quotes sent in under one week, one to two weeks, and longer | Tests whether speed actually wins orders in your market |
Set a baseline from the last 6 to 12 months of quotes before you change anything.
Common mistakes
- Buying a CPQ tool before the pricing rules are written down. The tool can't encode rules nobody has agreed on.
- Automating a stage that isn't the bottleneck. If quotes wait three days for approval, faster configuration won't help.
- Speeding up the quote without checking delivery dates against real capacity. You'll win orders you can't deliver on time.
- Treating every RFQ the same. Use a quick bid or no-bid screen so your best people spend time on the quotes you can win.
Quoting is rarely the only place time leaks. It's worth checking how your quote turnaround compares with scheduling, supply visibility, and data quality, so you can see where your capacity is being lost before you decide what to fix first.
A checklist for your next quoting review
- Have we timed each stage on at least ten recent quotes, separating queue time from work time?
- Which stage has the longest queue, and who owns it?
- How many times is the same data typed into different systems?
- Can an engineer find the three closest past designs in under five minutes?
- Are our configuration and pricing rules written down anywhere a system could use?
- Do we check quoted delivery dates against actual production load?
- Do we know our win rate by turnaround band?
Where to go from here
Pick one product family and time ten quotes this month. That baseline tells you where to start. If you'd like help mapping your quoting workflow or building the automation, get in touch. We build these systems, so weigh our view accordingly. You can read more about our approach on our Energy Infrastructure page.