"I Want to Hire Them Myself." Which Part, Exactly?

There's a version of "we hire our own people" that is one of the smartest instincts a founder can have, and there's a version that quietly costs you a quarter. Most founders can't tell which one they're running until the bill comes due.

Let's begin where the good CEOs live, because that's the honest place to look.

The instinct is right. Guard it.

If you're building a company where software is the product, controlling your talent pipeline isn't a nice-to-have. It's arguably the job. The best CEOs interview obsessively and know their engineers as people. They set the standard for who gets in and who doesn't, and they treat culture as something built one hire at a time rather than something announced on a wall. That isn't overhead. It's work.

So when a founder says "I want to hire them myself," the instinct deserves no argument. It deserves a narrower question. Which part of hiring them yourself is the part you actually want? There are two things hiding inside that sentence, and they have almost nothing to do with each other.

Two things are hiding in that sentence

The first is control over the people. It's the ability to interview someone, decide they fit, put them in your stand-up tomorrow, watch how they think, correct course on a Tuesday afternoon, and build a relationship deep enough that they stay for years instead of quarters. This is real, and it's the thing great founders are protecting. You should never give it away.

The second is control over the process. It's posting the role and waiting, screening the flood, standing up or renting an HR function to run the funnel, scheduling loops, chasing candidates who already have three other offers, and losing weeks while a competitor ships. This one isn't control at all. It's a chore to wear a control jacket.

Here's the trap. Founders reach for the second one believing they're buying the first, and the market charges a specific, measurable price for the confusion.

Ninety days is the real number

Hiring a senior software engineer in the US takes about 90 days from the day you post the role to the day they start. That's the real number, not the brochure number. The requisition alone sits open around sixty days before an offer is even accepted, and the senior people you actually want take more than twice as long to land as juniors, because they already have jobs and are fielding two to four competing offers at once. These calendars are getting longer every year, not shorter.

Now put a number on the wait, because finance teams already have. Take annual salary, multiply by the value the role produces, divide by working days. A $150,000 engineer producing twice their salary in value runs roughly $1,150 a day. Every day that seat sits empty, that's what you lose. It doesn't show up as a bill you can see. It shows up as sprints that don't happen, decisions that get deferred, and a roadmap that slips.

Run the multiplication and it stops being abstract. Ninety days on one senior role is more than a hundred thousand dollars in lost output before you pay a single recruiting fee, and that figure doesn't count what it costs when the initiative tied to that role slips a quarter or dies because the team could never staff it. Meanwhile the one candidate you were waiting to land stays on the market for about ten days. Your ninety-day process was never going to choose them. It was only ever going to lose them.

Ninety days doesn't sound violent, so translate it into your own language. If you run two-week sprints, ninety days is six or seven sprints burned looking for a person. That's six or seven cycles you could have spent shipping, competing, and winning the actual point of the business.

And notice what you did not buy with those ninety days. You didn't buy deeper control over your people. You bought a longer wait for the chance to start building the relationship. The expensive part came first, and it bought you nothing.

No culture was ever built by the recruiting funnel

The best case against all of this is a good one, so here it is plainly. A team on your own payroll gives you direct oversight, fast feedback, and the ability to reprioritize in real time. When technology is your core differentiator, when the domain is deep and the roadmap is long, in-house ownership is genuinely the right model. Culture, retention through shared history, knowledge that stays inside the walls, these are real advantages, and anyone who tells you otherwise is selling something.

But read that argument again and find the word that isn't there. Nowhere does it say the culture is built by the recruiting funnel. Culture is built by who's in the room and how you lead them once they're there. The three-month wait to find the person contributes nothing to it. It's pure cost with no cultural return. The mistake isn't wanting an in-house team. The mistake is bundling a thing worth protecting — the people, the leadership, the daily closeness — with a thing worth eliminating — the search — and defending the bundle as if the two couldn't be pulled apart. They can, and that's the entire point.

Keep the control. Drop the wait.

So pull them apart. Keep the control that was always worth having, and stop paying for the one that was only ever a chore. Keep interviewing like it's your most important job, because it is. Keep deciding who's in the room, and keep leading them once they're there, correcting courses on Tuesday afternoon and building the relationship that makes people stay. That's the control that makes a company yours.

The posting, the funnel, the ninety days of standing still, none of that was ever the part that made your company yours. It was only ever the part that made you slow. You can have the team, the culture, and the control without buying the wait to get them.

That last line is the entire reason Abet exists, but the principle stands on its own, whoever you build with. The founders who win the next decade won't be the ones who controlled the most. They'll be the ones who were precise about which control was worth keeping.