Time-to-hire is a business metric, not an HR one
Every week a role sits open, the roadmap it was funded to deliver slips. Almost nobody prices that, and it is usually the largest number in the conversation.
Time-to-hire is reported in recruitment dashboards, benchmarked against industry averages, and discussed as a measure of process efficiency. This is a category error. It is a delivery metric that happens to be measured by a different function, and treating it as administrative hides the largest cost attached to it.
A funded role is a commitment the business has already made. The budget is approved, the work is scoped, the roadmap assumes the capacity. Every week the seat is empty, that commitment goes unmet — not in the abstract, but in specific features that do not ship and specific revenue that arrives later or not at all.
The arithmetic nobody performs
Take a role approved in January, filled in June, productive in August. That is seven months of assumed capacity that did not exist, against a plan that was built on the assumption it would. The plan does not adjust; it slips, quietly, while everyone attributes the delay to complexity.
Meanwhile the existing team absorbs the shortfall. They work at a pace that is sustainable for a quarter and corrosive over three, and the resulting attrition creates another vacancy — which is filled on the same timeline, by the same process, with the same result.
What actually moves the number
- Decide what you are optimising. A process designed to eliminate false positives will be slow and will lose good candidates to faster competitors. That may be the right trade, but it should be a choice.
- Compress the calendar rather than the stages. Most elapsed time in hiring is waiting for availability, not interviewing. Scheduling a full panel in one day removes weeks without removing rigour.
- Give one person authority to decide. Consensus hiring is where offers go to die, and the candidate reads the delay accurately as ambivalence.
- Separate roles that must be permanent from capacity that simply must exist. Augmenting for a defined period while a permanent search runs properly is not a compromise; it is how you avoid a rushed hire.
- Measure time-to-productive, not time-to-signed. The offer is a milestone; the delivery is the point.
The conversation worth having
The most useful reframe is to put the number in front of the people whose plans depend on it. When an engineering leader sees that their roadmap assumes capacity arriving in March and the pipeline suggests August, the discussion changes character. It stops being a complaint about recruitment and becomes a planning decision with real options: rescope, resequence, or bring in capacity another way.
All three are legitimate. Pretending the seat will be filled on time is the only option that is not.
Let's build the system your business will run on next.
Tell us where it hurts. We'll bring the architects, engineers, and delivery model to fix it — and scale it.