.png)
The first instinct when RFQ volume exceeds quoting capacity is always the same: hire another quoting member to your team.
It's the default answer because it has been the historical answer. More work, more people. It is also often a response that is wrong in ways that cost EMS companies millions of dollars a year in unrecoverable margin and pipeline.
Here's why headcount is often the wrong lever, and what's actually limiting your quoting throughput.
Most EMS quoting teams can spend somewhere between 60%-75% of their working hours on tasks that don't require specialized skills. The specific breakdown varies by organization, but the pattern is consistent:
Only the remaining 25-40% is what the role actually exists to do: apply engineering judgment, assess margin and risk, and price the opportunity appropriately.
Hiring another quoting headcount doesn't change this ratio. It just gives you another person spending 60-75% of their time on administrative tasks.
A fully-loaded quoting member in the US salary, benefits, overhead, tooling typically costs a mid-market EMS company $130,000-$180,000 per year. Assume the midpoint of $150K.
At the industry-average ratio, that new engineer will spend:
You are, in effect, paying $97,500 per hire to scale your manual data-entry capacity. That's before you factor in the 3-6 months it typically takes a new hire to reach full productivity on your product lines and supplier relationships.
For the same $97,500, you could automate the entire pre-quote pipeline across your existing team and keep doing so for every person you hire in the future. This allows you to re-allocate your team members time on activity that impacts the bottom line of your business.
There's a second issue with the headcount approach that's harder to see until you've experienced it.
Adding a quoting manager adds linear capacity: one more person, one more throughput unit. But RFQ volume doesn't grow linearly, it grows with market activity, customer expansion, and industry cycles, all of which move in bursts. When Q2 volume spikes 40% above the Q1 baseline, a team that just hired one person is still capacity-constrained. They hire again. By the time the new hire ramps up, volume has shifted again.
This is the fundamental structural issue. You can't hire your way out of a bandwidth mismatch between volume and capacity when the volume is volatile and the ramp time is long. The best you can do is run perpetually behind, accepting the 40% unanswered rate as a cost of doing business.
Except it isn't a cost of doing business. It's a cost of running the business on infrastructure that wasn't designed for the volume.
The EMS companies closing the 40% gap aren't doing it with headcount. They're doing it by automating the non-judgment work so their existing quoting engineers can focus on the part of the job that actually requires them.
The capacity math inverts when this happens. An engineer whose pre-work was consuming 65% of their time now spends only 15% on it. Their effective capacity for actual quoting roughly doubles without hiring, without overtime, without burnout.
And the capacity is elastic. When RFQ volume spikes, the automation scales with it. When it contracts, there's no overhead to cut. The bandwidth ceiling moves up, and it moves with market conditions.
This isn't an argument against ever hiring another quoting engineer. It's an argument for being deliberate about what you're hiring them to do.
If the job description is "process more RFQs" then don't hire another person. Automate.
If the job description is "bring deep expertise to complex quoting decisions, customer relationships, and margin strategy" absolutely hire. That's the work that doesn't automate, and it's the work that actually drives win rates.
If you want to see how much revenue your current RFQ response rate is leaving on the table, there's a free 30-second calculator that will tell you: https://www.breadboard.com/quotation-calculator
Enter your monthly RFQ volume and average deal size. It returns your annualized RFQ Revenue Gap the money that's currently leaving your inbox for competitors because your team's bandwidth ran out before the quote got built.