A founder I advise called me on a Thursday afternoon. Not to ask for advice. To tell me he had finally done it — he had let someone go. The relief in his voice was unmistakable. So was the math he walked me through afterward.
Nine months. That was how long it had taken. From the first moment he knew the hire was not working to the afternoon he actually ended it. Nine months of one-on-ones that went nowhere. Nine months of KPIs he quietly adjusted so the dashboard would look better. Nine months of telling himself it was probably just a rough quarter.
He did not waste nine months on the exit. The exit took forty-five minutes.
He wasted nine months on the knowing.
The Gap Between Knowing and Acting
This is the conversation I have had more than any other with founders and senior operators. Not about how to let someone go. About how long they waited after they already knew.
The conventional assumption is that bad hires get caught at 90 days. That is what the onboarding literature says. That is what most companies plan for. A review cycle with structured check-ins and clear expectations.
But the actual pattern tells a different story. The average bad hire does not exit at 90 days. They exit at six months. Sometimes twelve. And the gap between the first clear signal and the final conversation is almost always measured in quarters, not weeks.
That gap is the cost. Not the severance. Not the recruiting fees. The months of deferred clarity are what drain companies — and what quietly erode the trust of everyone around the person you are managing.
Why Operators Wait
Part of it is optimism. You hired this person. You told your team you believed in them. Reversing that takes something most leaders underestimate: the willingness to be publicly wrong.
Part of it is ambiguity. The signals in month one are never perfectly clean. The person is still finding their footing. The role is still being shaped. It is easy to find reasons to give it more time.
But mostly? Operators wait because they do not have a forcing function. There is no structure that makes the truth undeniable at 30 days instead of 90. No designed mechanism to separate "this person is new" from "this person is not a fit."
And without that mechanism, the default is always to wait.
The Part No One Talks About
Here is what makes this pattern harder to break than it looks.
Most onboarding frameworks focus on output: what did this person ship, what numbers did they move, are they executing against the role. Those are the easy things to measure. They fit cleanly into a spreadsheet. You can point to them in a review.
But the majority of hires that do not work out — by a significant margin — do not fail because of output. They fail because of something that is much harder to surface on a dashboard. And because most onboarding processes are not designed to make that thing visible, it stays invisible until it is everywhere.
The best operators I know have figured this out. Not through better instincts. Through better structure. They have built their process so that the things that actually predict failure become observable in the first 30 days — not discoverable at month nine, after the rest of the team has already adapted around the problem.
What the Signal Looks Like
The founder I mentioned told me something I keep coming back to.
"I saw it in week two," he said. "I just didn't know what I was looking at."
That is usually how it goes. The signal was present early. The hire did not hide it. There was simply no framework that made the signal legible as a signal rather than noise.
The operators who avoid the nine-month tax are not more decisive. They are more deliberate about what they build before someone's first day. They know that clarity at 30 days is not a function of how well the hire performs in the first month. It is a function of how well the environment was designed to surface truth.
The difference is structural, not intuitive. And it is available to anyone willing to design it in before the hire starts, not reconstruct it afterward when the pattern is already clear to everyone except the spreadsheet.
The Compounding Cost of Inaction
There is a version of this story that ends at the exit. The founder lets the person go, the team resets, you move on.
But that is not how it usually plays out. The more common version is that the team adjusts. They route around the problem. They learn which conversations to avoid, which projects to keep out of the person's lane, which decisions require extra coordination. They adapt.
And then when the hire finally exits, you discover that the team has been carrying a structural workaround for months. That workaround has calcified into how things get done. And now the problem you thought was one person is woven into the system.
The cost of a bad hire is not just the hire. It is the culture that forms around them while you wait.
The most expensive part of a wrong hire is almost never the severance. It is the months you spent managing around a truth you already knew.
The First 30 Days Are the Whole Game
The founders who get this right share one orientation: they treat the first 30 days as the entire investment thesis for the hire. Not a ramp. Not an adjustment period. A signal collection window.
They design that window deliberately. They know exactly what they are looking for — and it is not output. By the time most operators realize a hire is not working, the signal was already there in week two. They just did not have the right frame to read it.
The exit is not where the work happens. It is the last thing that happens, after a process that either surfaced the truth in time or did not.
If you work with operators who have learned to read the signals that compound — across hires, relationships, and teams — Revolv was built for that kind of thinking.
