Why Cost-per-Hire Doesn't Tell the Whole Story
Cost-per-hire is one of the most widely used metrics in recruitment. It's easy to calculate, easy to report, and gives finance teams a clear number to track over time. But as a measure of whether your hiring is actually working, it has significant limitations.
On its own, cost-per-hire tells you what you spent to fill a role. It doesn't tell you how long the role was vacant, whether the hire stayed, whether they performed, or what the business lost in the meantime. For companies managing technical and engineering hiring at scale, those gaps matter - and they often matter more than the headline figure.
Key takeaways
- Cost-per-hire measures spend per role filled - it doesn't capture time-to-hire, quality of hire, or the cost of vacancies
- Time-to-hire has a direct financial impact in STEM roles where productivity, project delivery, and compliance depend on headcount
- Quality of hire - retention, performance, and ramp time - is rarely captured in standard recruitment reporting
- Capacity constraints in the hiring function itself can inflate true cost and extend time-to-fill without appearing in cost-per-hire
- RPO gives finance teams a more complete picture: consolidated spend, predictable cost structures, and metrics that reflect actual business impact
What cost-per-hire actually measures
Cost-per-hire adds up internal and external recruitment costs - advertising, agency fees, HR time, onboarding - and divides by the number of hires made. As a benchmark it's useful: it allows year-on-year comparison, highlights where spend is concentrated, and gives procurement and finance a consistent number to report.
What it doesn't capture is everything that happened around the hire. A role filled quickly with a candidate who stayed two years looks identical in cost-per-hire terms to a role that took four months to fill, was covered by agency spend, and resulted in an early leaver. The metric records the cost of the transaction. It doesn't record the value - or the loss.
The cost of time
In engineering, technical, and STEM roles, vacancy time has a direct financial consequence. A delayed hire can mean projects running behind schedule, overtime costs on the remaining team, compliance headcount gaps, or contract penalties where delivery timelines are tied to resource.
A role vacant for 90 days doesn't just cost what it costs to fill - it costs what the business couldn't do, or had to pay more to do another way, for those 90 days.
Time-to-hire rarely appears in cost-per-hire reporting, but it's one of the most financially significant variables in the hiring process. Businesses that track only cost-per-hire can appear efficient on paper while absorbing significant vacancy costs that never show up in the recruitment budget.
Quality of hire - the metric most businesses don't track
Quality of hire looks at what happens after the offer is accepted: how quickly the new hire becomes productive, how they perform against the expectations the role was hired for, and whether they stay. It's the metric most directly connected to whether a hire was actually a good use of the money spent - and it's the one most recruitment reporting ignores.
The reason is largely practical: quality of hire requires data from across the business - line manager feedback, performance review outcomes, retention figures - that doesn't sit within the recruitment function. It takes longer to measure and is harder to attribute. But for finance teams trying to understand the real return on recruitment spend, it's the number that matters most.
A hire made quickly at low cost-per-hire who leaves within six months, or who doesn't perform to the level the role required, costs significantly more than the headline figure suggests. Replacement cost, re-advertising spend, lost productivity during the gap, and the management time spent on a poor-fit hire all compound a number that cost-per-hire never captured.
Hiring capacity as a hidden cost
Cost-per-hire assumes your recruitment function has the capacity to hire efficiently. When volume increases - during growth phases, project ramp-ups, or seasonal peaks - the assumption often breaks down. Internal teams stretched beyond capacity don't just slow down: they cut corners, reduce screening quality, and push more spend toward agencies as a release valve.
The resulting cost-per-hire figure may look similar to a quieter period, but the inputs are different. More agency spend, lower screening quality, and longer time-to-fill hidden behind a broadly consistent average. Capacity constraints in the hiring function itself are a cost that standard recruitment metrics don't surface.
What a more complete picture looks like
The metrics that give finance teams a more accurate view of recruitment performance sit alongside cost-per-hire, not instead of it:
- Time-to-fill and time-to-hire - how long roles are vacant, and how long the process takes from first contact to offer accepted
- Offer acceptance rate - a low rate indicates process, speed, or employer brand issues that inflate true cost
- First-year retention rate - the clearest indicator of quality of hire at scale
- Agency spend as a percentage of total recruitment cost - a rising figure often signals capacity or process problems
- Hiring manager satisfaction - captures whether the hire met the brief, not just whether a role was filled
Together, these metrics give a picture of what recruitment is actually costing the business - including the costs that don't appear in any budget line.
Where RPO changes the equation
Recruitment Process Outsourcing gives finance teams something that fragmented, multi-agency hiring rarely does: consolidated visibility. A single partner, a single commercial model, and reporting built around the metrics that matter - not just cost-per-hire.
For businesses with technical and engineering hiring at scale, RPO also addresses the capacity problem directly. Rather than absorbing demand spikes through agency spend and reduced process quality, the RPO function scales with the business - maintaining consistency in hiring standards, time-to-hire, and candidate experience regardless of volume.
The result is a cost structure that's predictable, a process that's consistent, and a reporting framework that gives finance the full picture - not just the part that fits neatly into a single metric.
Find out how Owen Daniels RPO gives finance and procurement teams the cost visibility, process consistency, and hiring performance data that cost-per-hire alone can't provide.
View our RPO Solution & Download the RPO Guide
FAQs
What is cost-per-hire and how is it calculated?
Cost-per-hire is the total internal and external recruitment spend divided by the number of hires made in a given period. It includes advertising costs, agency fees, HR and recruiter time, and onboarding costs. It is a widely used benchmark for comparing recruitment efficiency year-on-year, but it doesn't capture vacancy time, quality of hire, or the cost of capacity constraints.
Why is cost-per-hire not enough on its own?
Cost-per-hire only records what was spent to fill a role - it doesn't capture how long the role was vacant, whether the hire stayed, or whether they performed to the level the business needed. In STEM and engineering roles, those gaps carry direct financial consequences that never appear in the cost-per-hire figure.
What is quality of hire and how do you measure it?
Quality of hire measures what happens after the offer is accepted - productivity ramp time, performance outcomes, and retention. It's typically measured through first-year retention rates, hiring manager satisfaction scores, and time-to-full-productivity. It's the metric most directly linked to the return on recruitment spend, and the one most businesses don't systematically track.
How does RPO improve recruitment cost visibility?
RPO consolidates recruitment spend under a single commercial model, replacing fragmented agency fees with a predictable cost structure. It also introduces reporting across the full hiring funnel - including time-to-hire, offer acceptance rates, and retention - giving finance teams a complete picture of what recruitment is actually costing the business, not just what was spent per hire.
What recruitment metrics should finance teams track alongside cost-per-hire?
The metrics that give the most complete picture are time-to-fill, offer acceptance rate, first-year retention rate, agency spend as a percentage of total recruitment cost, and hiring manager satisfaction. Together they surface the costs - vacancy time, poor-fit hires, capacity constraints - that cost-per-hire alone doesn't capture.
What is the true cost of a bad hire?
The true cost of a bad hire includes the original recruitment spend, replacement recruitment costs, lost productivity during the vacancy gap, management time spent on a poor-fit hire, and the impact on team performance during the period. Estimates typically put the total cost of a bad hire at between one and three times the annual salary of the role.
