07 Hiring Analytics
What Hiring ROI
Actually Means
Hiring ROI is more practical than people think.
The hiring ROI system
Cost
Total investment in the search and hire
Contribution
Value generated by the hire in role
Speed
Time from hire to productive contribution
Business value
Net impact over the hire's tenure
Hiring ROI is not a finance exercise. It is a decision quality tool — for understanding whether hiring investment is creating proportional business value.
Why this matters
Hiring ROI sounds abstract until you calculate it — then it becomes one of the most actionable numbers in the business.
Most founders think of hiring ROI in vague terms: did the hire work out? Are they contributing? Do we still think it was the right decision? This level of analysis produces nothing useful. It doesn't improve future hiring decisions, it doesn't help resource allocation, and it doesn't create any learning about what makes hiring work.
Practical hiring ROI is simpler than it sounds. It is the ratio of the value a hire creates to the total cost of getting them into productive contribution. When that ratio is calculated consistently, patterns emerge: which roles produce the highest ROI, which search approaches are most cost-efficient, which hiring decisions compound positively and which don't.
The goal is not financial precision for its own sake. It is decision clarity — the ability to make better hiring investment decisions based on something more reliable than instinct.
Founder reality
Build the ROI calculation before the next significant hire:
What is the total cost of this hire — including search fees, internal time, onboarding investment, and the first 90 days of salary before full contribution?
What specifically will this person produce that the business currently can't — and what is the business value of that production?
How long do we expect it to take from start date to full productive contribution — and what is the cost of that ramp period?
If this hire performs as expected for 2 years, what is the cumulative business value created versus the cumulative cost?
Are we making this decision based on a clear value thesis — or on an instinct that more people means more output?
The ROI calculation doesn't need to be precise to be useful. An order-of-magnitude estimate changes decision quality significantly.
The framework
Four components of practical hiring ROI
Calculate each component before the hire and revisit at 90 days, 6 months, and 12 months.
01
Total hiring cost — the full investment from search to productive contribution
Include: recruiter or agency fees, internal time spent on sourcing and interviewing (estimated at hourly rate), onboarding investment, and the salary cost during the ramp period before full contribution. The true cost of a hire is typically 20–30% higher than the headline recruitment fee. Underestimating it produces inflated ROI calculations.
02
Contribution value — what the hire produces that the business couldn't before
Define this specifically: revenue generated, product velocity increased, operational capacity added, technical capability unlocked. Avoid vague framings ('adds value to the team'). Specific contribution definitions produce measurable ROI — and hold the hiring decision accountable to a clear thesis.
03
Ramp time — the period between start date and full contribution
A hire who takes 6 months to reach full contribution has a significantly different ROI profile than one who reaches it in 8 weeks. Ramp time is partly a function of the hire's capability and partly a function of the onboarding investment. The companies with the best hiring ROI tend to have the most structured onboarding — because it directly reduces ramp time.
04
Tenure value — the compounding contribution over the hire's full time in role
A hire who performs well and stays for 3 years produces dramatically more ROI than one who performs equally well and leaves after 10 months. Retention is a hiring ROI multiplier. Hiring decisions that factor in expected tenure and invest accordingly in retention are higher ROI decisions — even when the initial cost is higher.
Common mistakes
01
Calculating only the recruitment cost, not the total hiring cost
Agency fees are one component. Internal time, onboarding investment, and ramp cost often double the true cost of a hire. Underestimating total cost produces systematically inflated ROI — and under-investment in the search quality that reduces ramp time.
02
No contribution thesis before the hire
A hire without a specific, measurable contribution thesis has no ROI to calculate. If you can't describe specifically what this person will produce that the business currently can't, the ROI of the hire is undefined — and probably lower than expected.
03
Never revisiting the ROI calculation after the hire
The pre-hire ROI estimate and the post-hire ROI actuals rarely match exactly. The learning is in the gap: where did the estimate prove wrong, and why? This is the feedback loop that improves future hiring ROI decisions.
04
Treating all roles as having equivalent ROI potential
Some roles produce dramatically higher ROI than others. A revenue-generating hire in a high-growth market, a technical hire who unlocks a product capability, or a leadership hire who increases team output — all have different ROI profiles. Understanding which roles have the highest ROI potential helps prioritise the search investment.
Example scenario
A cybersecurity startup, 45 people. Debating between two engineering hires: a senior backend engineer (€130K) and a DevOps engineer (€110K). Limited budget. Both felt necessary.
The ROI comparison
Backend engineer: would accelerate feature development. Contribution value estimated at €15K/month after 3-month ramp. Total hiring cost: €45K. Break-even: 3 months post-ramp (6 months from start). 12-month net ROI: €90K.
DevOps engineer: would reduce deployment friction and on-call load. Contribution value: €8K/month in time saved plus an estimated €20K in avoided incidents over 12 months. Total hiring cost: €38K. Break-even: 5.5 months. 12-month net ROI: €58K.
Decision: backend engineer hired first. DevOps hire queued for Q3 when runway allowed.
The outcome
Backend engineer at 6 months: contributing at the estimated rate. Feature velocity measurably increased. ROI tracking on schedule. DevOps hire made 4 months later — with more specific contribution thesis based on the patterns that had emerged in the interim.
Takeaway
Hiring ROI is a decision tool, not a finance report.
Calculate total cost, define the contribution thesis, estimate ramp time, factor in tenure. Revisit the estimate at 90 days and 6 months. The comparison between prediction and actuals is where the learning is.
Related thinking
Continue reading
Hiring Speed vs Hiring Quality