← Back to Field Notes

Quoting

January 6, 2026 · The Bloomfield Team

How a 5-Day Quote Cycle Quietly Kills Your Win Rate

A purchasing manager at a Tier 2 automotive supplier sends four RFQs on Monday for a bracket assembly. Two shops respond by Wednesday with detailed quotes. The purchasing manager reviews both, asks one clarifying question, and issues a PO Thursday afternoon. The other two shops submit Friday. They never hear back.

Those two shops did the estimating work, checked material prices, consulted with the floor, built the cost model, and sent a professional quote. All of it wasted because someone else moved faster.

This pattern repeats across thousands of job shops every week. The damage accumulates in ways most shop owners never measure.

The Decay Curve of a Quote

Quoting has a half-life. The moment an RFQ lands in your inbox, its value starts declining. Shops responding within two days win roughly 35% of submitted bids. At five days or later, that drops to around 12%. A 65% drop in conversion from three extra days of turnaround.

The mechanics are simple. Buyers work from short timelines. A procurement team managing 200 active part numbers does not wait for the slowest bidder. They evaluate what they have, make a decision, and move on. Your quote arriving on day five competes against a decision already made on day three.

The damage is invisible. You never see the bids lost to timing. The buyer does not call to say they went with someone faster. The RFQ goes silent, and the estimator moves to the next one in the queue.

Where Five Days Actually Comes From

No estimator takes five days to build a single quote. The five-day cycle is a queuing problem built from small delays that stack across a backlogged workflow.

Day one: the RFQ arrives. The estimator is working on two other quotes and has a call about a job that shipped wrong last week. The new RFQ sits in the inbox.

Day two: the estimator opens the RFQ, reviews the drawing, starts pulling information. Material costs require an email to the steel supplier. Checking for similar past jobs means searching the ERP, which returns 40 results, none matching perfectly. Forty-five minutes of scrolling through job histories.

Day three: material pricing comes back. The estimator needs to check a tolerance callout with the lead machinist, who is running a job and cannot talk until second shift. Another quote gets worked in the meantime.

Day four: machinist input received, cost model finished, sent to the sales manager for review. Sales manager is in meetings until 3 PM.

Day five: sales manager approves with one margin adjustment. Updated quote goes out at 2 PM.

Nobody was slow. Nobody was negligent. The process has too many serial dependencies, too many information bottlenecks, and too much reliance on people being available at the right moment.

The Revenue You Cannot See

A shop submitting 50 quotes per month at a five-day turnaround with 12% win rate wins six jobs monthly. At an average job value of $18,000, that is $108,000 in monthly bookings from quoting activity.

The same shop at two-day turnaround with 35% win rate: 17 wins instead of six. $306,000 monthly.

The difference is $198,000 per month. Over a year, $2.37 million in revenue that was available and went to a competitor who responded sooner. Real RFQs that arrived at the shop, were evaluated, and lost to speed. The demand existed. The capability existed. The speed did not.

The Compound Damage

Lost bids are the first-order cost. The second-order costs are harder to see and often more expensive.

Estimator burnout. When the quote queue is perpetually full and win rate is low, estimators spend their days on research-intensive work that rarely converts to revenue. The effort-to-reward ratio degrades their engagement over time. Experienced estimators, the ones carrying decades of pricing knowledge, start looking for jobs where their work actually leads to orders.

Customer relationship decay. A buyer who sends three RFQs and gets slow responses on all three stops sending the fourth. You lose that customer through a pattern of being the shop that always takes a week. After six months, you are off the approved vendor list without ever knowing it happened.

Margin pressure. When win rates are low, sales teams compensate by cutting prices. The logic is understandable: if only 12% of bids win, maybe pricing is too high. So margins shrink to chase volume, and the shop wins slightly more work at significantly worse economics. A shop winning 35% at healthy margins has far more pricing power than one winning 12% and discounting to survive.

Capacity misallocation. A slow quoting process means the shop cannot be selective about which work it takes. When every win matters because wins are scarce, the shop accepts jobs that clog the schedule, require excessive setup time, or carry thin margins. A shop with a higher win rate can afford to prioritize jobs that fit its equipment, capacity windows, and target margins.

What the Fix Actually Looks Like

Adding another estimator does not solve this. Adding headcount to a broken process gives you two people navigating the same bottlenecks instead of one.

The fix is collapsing the information-gathering phase of quoting. Today, an estimator spends 60 to 70% of quoting time on research: finding past jobs, checking material prices, consulting the floor, searching for setup time references. Actual pricing and decision-making, the part requiring human judgment, takes 30 to 40%.

A custom quoting tool built around your shop's data compresses the research phase from hours to minutes. When the estimator opens an RFQ, the system has already matched the part to similar historical jobs, pulled current material pricing from the most recent supplier quotes on file, and flagged tolerances that historically required additional operations.

The estimator still makes every decision. They still set the price, adjust for customer relationship, account for current shop loading. They do it with complete context instead of partial context, in 90 minutes instead of two days.

The Flywheel Effect

Shops that cut their quote cycle to under two days see effects beyond immediate win rate improvement.

The quoting backlog clears. Estimators handle more volume, which means the shop pursues more opportunities without adding headcount. Sales can be more aggressive about requesting RFQs from target customers because the front office has capacity to respond.

Quote data accumulates in a structured format. Instead of pricing knowledge living in the estimator's head and a collection of spreadsheets, every quote becomes a searchable record. Six months of structured data reveals patterns: which customers convert at the highest rates, which part families carry the best margins, which work the shop consistently loses and should stop pursuing.

Quote quality improves because the estimator works from better data. When similar jobs surface automatically with actual costs and margins, pricing accuracy goes up. Fewer underpriced jobs go out the door. Fewer overpriced quotes scare off good customers.

Over 12 to 18 months, the shop quoting in one day has a fundamentally different business than the shop quoting in five. More volume. Better margins. Stronger customer relationships. A front office running on data instead of memory.

Measuring Your Own Cycle

Before anything changes, you need to know where you stand. Pull the last 60 days of RFQ activity and answer three questions.

First: what is your average time from RFQ receipt to quote submission? Not the fastest or slowest. The average across all quotes in the last two months.

Second: what is your win rate? Divide POs received by quotes submitted. If you cannot answer precisely, that itself is a finding worth acting on.

Third: of the quotes you lost, how many went to a competitor who responded faster? This requires asking your sales team or the buyers directly. Most purchasing managers will tell you if you ask.

If your average cycle is above three days and win rate is below 20%, you are leaving substantial revenue on the floor. The math on what that costs fits on a napkin, and the number is almost always large enough to justify immediate attention.