The two failure modes of first hires are “the second me” who does what I do twice, and “the senior person” who manages me instead of working. The good first hire does neither. They take work I can’t already do, and they refuse to manage.
This is not a hot take. It’s the version of every founder-hire blog post that founders ignore because they have a specific candidate in mind and the candidate sounds great. Three months later they’re paying twice for the same skill and meeting four times a week to discuss why.
The multiplier hire
A multiplier extends the surface area of what the company can do. You’re a backend engineer; they’re a designer-engineer who can ship a landing page and a Figma in a week. You’re a closer; they’re an integrator who can do the post-sale handoff. You can do half their job, badly. They can do half of yours, decently. The Venn overlap is small, and that’s the point.
The check: ask the candidate to describe a project they did entirely alone, end to end. If the answer fits your current gap, hire. If the answer sounds like “I led a team that…”, stop.
The manager hire
A manager hire is correct exactly once: when you already have three people doing different jobs, you can’t be the bottleneck for all of them, and a person whose primary skill is unblocking other people will replace more of your week than they cost. That moment is later than founders think. It is usually employee five or six, not two.
The check: ask yourself how many people the manager hire would manage on day one. If the answer is “you and one contractor,” the answer is “not yet.”
What to do instead
Hire the second person who can ship something you can’t. Hire the third the same way. Resist the “we need a head of X” instinct until you can clearly point at three people who would have a clear week of work for that person to coordinate.
By then you’re not making the first hire anymore. You’re making the fifth. The decision is much easier when you’re not lonely.