What Hiring Speed Actually Tells You About a SaaS Business
Embedded headhunters for technology scale-ups
The short answer
Hiring speed is only meaningful once you know how it was achieved. Speed produced by proactive search, mapped markets and clear decision rights is a quality signal. Speed produced by settling for whoever applied is not. Time to shortlist is the diagnostic metric, because it isolates the part of the process a hiring function actually controls.
Quick answer
Hiring speed is a useful signal, but only when you know how the speed was produced. Two companies can both fill a role in 35 days and be in completely different health. One mapped the market, ran a proactive search and made a confident decision from a calibrated shortlist. The other posted the role, waited, and hired the least risky person who applied. The number is identical. The outcome is not. Speed and quality are not opposing forces to be traded against each other. Both are downstream of the same thing, which is process.
Why the speed debate keeps going in circles
One camp argues that time to hire is the clearest early indicator of growth health, because slow hiring exposes unclear priorities, approval bottlenecks and missing pipeline long before revenue suffers. The other camp argues that speed rewards filling seats quickly and quietly punishes quality, because the cost of a mis-hire surfaces months after the metric has been reported as green. Both are describing something real. The disagreement exists because the metric is being asked to do a job it cannot do on its own. Time to hire measures elapsed days. It says nothing about how those days were spent.
Why raw time to hire can be gamed
Any metric that measures only elapsed time can be improved by lowering the bar. Widen the brief, accept the third-best candidate, skip a calibration stage, stop waiting for the person who was not looking, and the number falls. Nothing about the hiring function has improved. Time to hire is also contaminated by things the hiring function does not control, in particular the customer's own interview process. A shortlist delivered in nine days can still take eleven weeks to reach an offer if panels cannot get diaries aligned or if decision rights are unclear. Reporting that as a sourcing problem misdiagnoses the business.
Time to shortlist is the diagnostic metric
Time to shortlist measures the elapsed time between role kickoff and the delivery of a calibrated shortlist, typically three to five candidates assessed against an agreed scorecard. It is the cleanest read on a hiring function because it isolates the part of the process that function owns: market mapping, outreach, assessment and calibration. It cannot be gamed the way time to hire can, because the shortlist is judged on evidence, not on arrival. If time to shortlist is short and the eventual time to hire is long, the friction is in the interview process, not in sourcing. If time to shortlist is long, the market has not been worked. That single split tells a leadership team where to intervene.
Speed as a quality signal, and speed as a warning
The useful question is never how fast, it is how the speed was achieved. Speed achieved through proactive search is a quality signal. It means the market was mapped before the role opened, that the strongest people in that market were approached directly rather than waited for, and that the shortlist reflects the market rather than the applicant pool. Speed achieved by settling is the opposite. It means the brief was loosened, the bar was moved, or the panel accepted a compromise because the seat had been empty too long. The metric looks the same in both cases. The twelve-month outcome does not.
Both speed and quality are downstream of process
Treating speed and quality as a trade-off assumes the process is fixed and the only lever is how much you compromise. In practice the process is the lever. Companies that hire quickly and well share the same underlying mechanics. Roles are defined before sourcing starts, with an agreed scorecard rather than a wish list. Pipeline exists before demand, so no search begins from a cold start. Decision rights are explicit, so approvals do not drift. Interview stages are consistent and calibrated, so feedback arrives in days rather than weeks. Where those conditions hold, speed and quality rise together, because both are symptoms of low friction. Where they do not hold, teams are forced to choose, and the choice is what creates the false trade-off.
What slow hiring is usually telling you
Slow hiring is rarely a recruiter problem. Recruiters sit downstream of role clarity, budget approval, panel availability and decision-making confidence. When hiring slows, the underlying cause is almost always one of a small set: the role was approved before it was defined, sourcing started from zero, the panel is not calibrated, or nobody is empowered to say yes. Each of those adds days that no amount of additional sourcing effort recovers. This is why slow hiring is a genuine early warning signal for the wider business. It exposes coordination problems before those problems reach revenue.
A more honest measurement set
Four numbers read together give an accurate picture where one number in isolation does not. Time to shortlist shows whether the market is being worked. Time from shortlist to decision shows whether the interview process is functioning. Offer acceptance rate shows whether candidates were genuinely engaged or merely available, since a strong acceptance rate is difficult to fake and a weak one usually indicates rushed pre-close or compensation misalignment. Twelve-month retention and ramp show whether the bar held. If speed improved while acceptance and retention held, the process improved. If speed improved while either fell, the bar moved.
Where this leaves the metric
Hiring speed is worth measuring and worth defending. It protects revenue execution, because quota coverage, onboarding capacity and delivery all depend on people being in seat at the right time. It just cannot be read alone, and it should not be the number that gets reported to a board without context. Ask how the shortlist was built. Ask whether the people on it were approached or whether they applied. Ask what the offer acceptance rate looked like. A business that can answer those questions has a hiring process. A business that can only report elapsed days has a number.
Where our model is not the answer
None of this makes a hiring partner the fix for a slow interview process. If shortlists arrive in ten days and offers take twelve weeks, the constraint is internal and no sourcing model resolves it. Equally, a company hiring one or two specialist roles a year does not need embedded capacity. The proactive search discipline still applies, but the commercial shape of a subscription does not. Embedded headhunting earns its place when the volume is ongoing and the constraint is genuinely access to talent rather than internal decision-making.
Frequently asked questions
- Is time to hire a bad metric?
- Not bad, but incomplete. In isolation it can be improved by lowering the bar, and it is contaminated by interview-process speed the hiring function does not control.
- What should we measure instead?
- Time to shortlist as the primary diagnostic, read alongside shortlist to decision time, offer acceptance rate and twelve-month retention.
- Are speed and quality a trade-off?
- No. Both are downstream of process. Where roles are defined, pipeline exists and decision rights are clear, speed and quality rise together.
- When is fast hiring a warning sign?
- When the speed came from settling. If the brief was widened or a calibration stage was skipped, the number improved and the hire did not.
- Why does time to shortlist matter more?
- It isolates the part of the process the hiring function owns, so it shows whether the market has genuinely been worked rather than waited on.
The Saiyō Briefing
Liked this? Get the next one in your inbox.
One short email every Thursday with hiring benchmarks, patterns and frameworks for technology leaders. Unsubscribe anytime.