The real cost of a hire you can't verify
A bad hire is never a single line item. Here's the full bill, including the part nobody puts in the spreadsheet.

Ask a founder what a wrong hire cost them and you'll get a salary number. Three months at $4,000 a month, so twelve grand, painful but survivable. That number is wrong, and it's wrong by a factor most people never calculate, because the expensive part of a bad hire was never the payroll.
What the spreadsheet catches
Salary is the easy part. So is the recruiter fee, the job-board spend, the tooling seat, the onboarding hours. Those are real costs and they show up in a system somewhere, which is exactly why they're the ones people cite. Anything with an invoice attached gets counted.
Together they're maybe a third of the bill.
What it misses
The manager's calendar. A hire who can't do the job doesn't go quiet. It generates work. Clarifying questions that should have been unnecessary. Rework on deliverables that shipped wrong. A weekly check-in that turns into a coaching session. For the eight to twelve weeks before anyone admits the problem, your most expensive person is spending their best hours supervising your least effective one.
The work that didn't happen. A role exists because something needed doing. While the seat is filled by the wrong person, that thing is still not getting done, but now nobody's looking for a solution, because on paper the problem is solved. This is the cost that never appears anywhere: the pipeline that stayed unbuilt, the backlog that stayed unworked, the client who stayed unfollowed-up.
The team's read on the standard. This one compounds. When a team watches someone underperform for a quarter without consequence, they learn what the real bar is, and it's lower than the one in the job description. Your best people notice first. They always do.
The restart. When you finally make the call, you don't return to where you started. You return to where you started, minus a quarter, minus the goodwill you spent on the last search, plus a team that now expects the next hire to be a coin flip too.
Why it happens
Not because anyone was careless. It happens because the standard process collects almost no evidence about the thing it's trying to predict.
A resume is a claim. An interview is a claim delivered verbally, with better lighting. A reference is a claim from someone selected by the candidate. Five rounds of this doesn't produce five times the evidence. It produces the same claim, restated, until repetition starts to feel like verification. Everyone in the room knows this. They also know the alternative is to make the decision anyway, so the rounds continue.
The uncomfortable part: the process is not weakly predictive of performance. On the dimensions that decide whether a hire works (judgment under ambiguity, quality of output, speed without supervision), it's close to uninformative. You are not choosing badly. You are choosing without data and calling it choosing.
The only thing that reliably predicts the work
The work.
Not a take-home that takes eight unpaid hours and tests whether someone has a free weekend. Not a whiteboard exercise that tests whether someone performs well while being watched. A scoped, realistic, time-boxed piece of the actual job, run under conditions that resemble the actual job, scored against a rubric written before anyone saw the submission.
That's what Day One™ is: 90 to 120 minutes, with a real brief and real deliverables. AI allowed and expected, with a required note on how it was used, because pretending your team doesn't use AI doesn't make the evaluation more honest, it just makes it less relevant. What comes out is a scored artifact: what was strong, what was missing, how the person thought when the brief was ambiguous.
You are no longer deciding whether you liked someone in a conversation. You are reading their work and deciding whether it's the standard you want.
What changes on the client side
The question on the first day of an engagement stops being did we get this right? and becomes what should they start on? That shift is the entire product. It's also why we keep the loop running past the placement. Fresh Eyes™ at week two exists so that if the match is wrong, we find out in fourteen days instead of ninety.
Verification is not a nice-to-have layered on top of hiring. It's the only part of hiring that was ever doing any work.
Common questions
This is how we hire, and it's the standard we hold our own team to. The long version lives in our manifesto. If you're hiring, start here. If you're talent, start here.


