Hiring Now vs Waiting For The Right Person: The Honest Math
The honest math almost always favors making a good-enough move now over waiting for the right person, because the cost of waiting compounds and the cost of a good-enough move is capped. The comparison owners actually run in their heads is different: they compare a perfect future hire against an imperfect present one, and the perfect one wins every time. That comparison is rigged. The real alternative to hiring now is not hiring perfectly later. It is the empty seat, every week, until later arrives.
Three versions of the same block
On the coaching calls this material comes from, "waiting for the right person" shows up in three costumes. Waiting for the right hire. Waiting for the right tool ("one more SaaS will finally do it"). Waiting for the right proof ("I'll wait until somebody proves it works"). The founder experiences them as three different, sensible decisions. From the outside they are one decision, made three times: keep the seat empty until certainty shows up.
Certainty does not show up. The right candidate is right in the interview and average by month three. The right tool has a gap you only find after onboarding. The right proof is always from a business slightly unlike yours. Meanwhile the seat stays empty, and the bill keeps running. What is the waiting tax covers why that bill is so easy to ignore.
The comparison owners actually run
Here is the mental math I hear, stripped to its structure:
"If I hire the available person now, I get 70 percent of what I need and I might have to redo it. If I wait, I get the right person and do it once."
Two problems. First, "do it once" assumes the right person exists, is findable, and will accept. Second, and more important, the comparison leaves out the cost of the gap between now and "when I find them." That gap is the entire waiting tax, and it is missing from the equation.
The honest comparison, as a method
I am not going to plug in numbers for you. Use yours. Set up two columns and fill them from your own inputs.
| Move now (good-enough) | Wait for the right person | |
|---|---|---|
| Weekly cost of the empty seat | Stops the week the move lands | Continues every week until the hire starts |
| Expected weeks to fill | Days for an agent on the repeatable part; weeks for an available human | Your honest estimate, then double it, because that is how long the last one took |
| Cost of the move itself | Agent setup time plus a good-enough salary or contractor | The right salary, later |
| Cost of being wrong | Capped: a reversible agent config, a contractor you release, a hire you re-scope | Also real: the right person on paper who is wrong in practice, discovered after months of waiting |
| Compounding produced | Starts now: recorded calls, output data, a process that improves weekly | Zero until the start date |
The weekly cost of the empty seat is the number you computed in what an unfilled role actually costs you every week. Multiply it by your honest weeks-to-fill in the waiting column. That product is what you are paying for the privilege of the perfect candidate. Most owners have never looked at it as a single figure. When they do, the waiting column stops looking prudent.
The move that changes the math entirely
The reason this is not a close call in 2026 is that "move now" no longer means "hire a mediocre person." It means something better: put an agent on the repeatable portion of the role this week, and re-scope the human hire around what remains.
Walk through the seat you are waiting to fill. List its recurring tasks. Mark each one as rule-based (same inputs, same steps, same output) or judgment-based. In the roles I see founders stall on, the rule-based share is large: triage, scheduling, first drafts, reporting, follow-up, data entry, summaries. That work can be owned by an agent in days, if the access exists. Which is why the first homework in the course is the Access Audit. Fifteen minutes of logins and permissions is what actually unblocks most stalled teams. We are not blocked by tech, we are blocked by admin.
Once the repeatable share is running, three things happen to your hiring decision:
- The empty-seat cost drops sharply, because most of the work now has an owner.
- The human role shrinks to the judgment core, which is a more attractive job, so the right person becomes easier to find.
- You stop needing the hire to be perfect, because the agent carries the volume and the human carries the decisions.
The "wait for the right person" column was always built on the assumption that the role was indivisible. It is not.
What about the cost of being wrong?
This is the honest objection, so take it seriously. A bad hire is expensive. A badly configured agent produces junk. Both are true. But look at the shape of the downside.
A good-enough move made now is reversible on a short cycle. An agent on one task, checked by a human for a week, is either producing acceptable output or it is not, and you know by Friday. A contractor can be released. A re-scoped hire can be re-scoped again. The downside is capped and the feedback is fast.
Waiting feels like it has no downside, which is the trick. Its downside is the whole waiting tax, paid weekly, with no feedback loop at all, because nothing is happening that could generate feedback. You are not avoiding risk. You are choosing the one risk that never reports back.
Borrow the confidence for this one decision
If you have read this far and still feel the pull to wait, notice that the pull is not coming from the math. It is coming from a sentence. "I'll be the one who breaks it." "I'm not really a tech person." "I'll plan this out for the quarter first." Every one of those is a block I have heard from a real founder, and every one has a reframe.
So borrow mine for a week. Pick the seat. Split it. Run the Access Audit. Put an agent on the single most repeatable task, with a human checking it. Decide now what "it worked" looks like. By next week you will have evidence that is yours, from your business, and you can make the hiring decision from that instead of from a hope about a candidate who has not applied yet. The decisions that compound is the next thing to read, because this is one of them.
FAQ
Is it ever right to wait for the right person?
Yes, for the judgment core of a role, once the repeatable work already has an owner. If an agent is running the volume and the empty-seat cost has dropped, you can afford to be patient about the human who will make the hard calls. What is rarely right is leaving the entire role empty while you wait.
What if the available person is clearly not good enough?
Then do not hire them for the whole role. Split the role first. Put an agent on the rule-based tasks this week, hire a contractor or a junior for what is left of the routine, and keep searching for the judgment hire with a much smaller, more attractive job description. Good-enough now does not mean settling for the full seat.
How do I estimate weeks-to-fill honestly?
Look at how long your last comparable hire actually took from decision to start date, not how long you expected it to take. Then assume this one will be similar. Owners consistently guess short on this number, and the waiting column of the comparison is only as honest as this one input.
Does putting an agent on part of the role make the hire harder?
It makes it easier. The remaining role is smaller, more interesting, and clearer, because the repetitive work is gone. You are no longer asking one person to be both the engine and the pilot. Candidates who can exercise judgment prefer jobs that are mostly judgment.