When I sold my second local service business, I did a rough accounting of every hiring mistake I’d made over the years, and the first hire stood out as by far the most expensive lesson. I hired someone to take bookkeeping and admin off my plate because I hated doing it — a completely understandable instinct. Eighteen months later I’d cycled through two people in that role, spent roughly $14,000 in salary and severance on hires that didn’t work out, and I still hadn’t solved my actual problem, which was that my business had no one who could sell or deliver work when I wasn’t personally in the room.
The mistake wasn’t hiring for admin work specifically — it was hiring based on what I disliked doing rather than what was actually constraining the business’s growth. That distinction sounds subtle, but it’s the difference between a first hire that multiplies what you can produce and one that just makes your life marginally more comfortable while the business stays exactly the same size.
Key Takeaways
- Hire your first employee to remove the bottleneck constraining revenue growth, not the task you personally dislike most — those are frequently different things.
- A first hire who can’t operate without you constantly available doesn’t actually free up your time; it just adds a training burden on top of your existing workload.
- Underpaying your first hire to “test the waters” attracts candidates who won’t stay once a better offer appears, and you’ll rehire for the same role within a year.
- Write down what decisions this person can make without you before you post the job; ambiguity about authority is the top reason first hires quietly fail.
Hire for the Bottleneck, Not the Annoyance
Every task on an owner’s plate falls into one of two categories: things that are unpleasant but not actually limiting growth, and things that are genuinely capping how much revenue the business can generate. Owners overwhelmingly hire to escape the first category, because it’s the pain they feel every day, while the second category — the actual bottleneck — often isn’t something they consciously notice because they’ve been quietly absorbing it themselves.
In my case, bookkeeping was unpleasant but wasn’t actually capping revenue — I was slow at it and resented it, but the business would grow the same amount whether I did it in three hours or someone else did it in one. The real bottleneck was that I was the only person who could close a sale or run a job site without daily supervision, which meant the business’s capacity was hard-capped at whatever I personally could deliver in a week. My first hire should have been someone who could take over client delivery or sales, freeing my own time to work on the business rather than in it. Instead I automated away an annoyance and left the actual ceiling on growth completely untouched.
What actually works: Before hiring, list every recurring task you do in a typical month and mark which ones, if you personally couldn’t do them for two weeks, would actually stop the business from generating revenue. Hire for those first — the annoying-but-non-critical tasks can wait, or be handled with a part-time contractor instead of a full hire.
A Hire Who Needs You Constantly Isn’t Actually Freeing You Up
The second mistake I made was hiring someone into a role with no real decision-making authority, so every non-trivial situation still required my input. This is incredibly common with first hires — owners are (rightly) nervous about handing over control, so they keep every meaningful decision funneled through themselves “just for now.” The problem is that “just for now” rarely ends, and the owner ends up training and managing someone whose actual output barely reduces their own workload, because they’re still the bottleneck for every decision that matters.
A café owner I advised hired her first assistant manager specifically to run morning shifts independently. But she’d never actually defined what the assistant manager could decide on her own — could they comp a customer’s order, adjust a schedule for a sick call-out, handle a vendor issue? Every time one of these came up, the assistant manager texted the owner, who was supposed to be off that morning. Six months in, the owner was still getting interrupted nearly every shift, and she genuinely couldn’t tell if the hire had helped at all. We sat down and explicitly wrote out a decision authority list — a specific dollar threshold for comps, standing rules for schedule adjustments, a simple escalation path for vendor issues — and gave it to the assistant manager in writing. Interruptions dropped by more than 80% within a month, because the ambiguity, not the person, had been the actual problem.
What actually works: Write down explicitly what decisions your first hire can make entirely on their own before you ever post the job. If you can’t answer that question yourself, you’re not ready to hire — you’re ready to write a much clearer job description first.
Underpaying Your First Hire Almost Always Costs You Twice
Owners frequently underpay their first hire because cash is tight and the position feels like an experiment — “let’s see how it goes before I commit to a real salary.” I understand the instinct completely; I did exactly this with my first bookkeeping hire, offering a rate about 15% below market because I told myself I was “trying it out.” She stayed four months before taking a better-paying role elsewhere, and I was back to square one, having spent that entire ramp-up period training someone who then left with all that institutional knowledge.
The math rarely works out the way owners hope. A below-market hire either leaves as soon as a fair offer appears — meaning you eat the full training cost with nothing to show for it — or stays but resents the arrangement in ways that show up in effort and reliability. Either way, you frequently end up rehiring for the same role within a year, at which point you’ve paid the recruiting and training cost twice for one filled position.
What actually works: Pay market rate for your first hire even if it’s uncomfortable, or scale the role down (part-time, contractor) to something you can afford at a fair rate, rather than hiring full-time at a discount. A smaller commitment at a fair price outperforms a full commitment at an unfair one almost every time.
Build the Onboarding Before You Need It, Not While You’re Drowning
The last mistake worth naming is treating onboarding as something you’ll figure out once the person actually starts. Most first-time small business owners have never onboarded anyone, so there’s no existing process to lean on — which means the new hire’s first weeks are usually improvised, inconsistent, and heavily dependent on the owner’s limited spare time to explain things, exactly when the owner is least able to spare that time because they’re still doing both jobs.
I’ve since learned that even a rough written onboarding outline — the five things a new hire needs to know in week one, who to ask for what, the two or three most common situations they’ll encounter and how to handle them — cuts ramp-up time dramatically and reduces the number of times they need to interrupt you with basic questions. It doesn’t need to be polished. It needs to exist before day one, not get written reactively during it.
What actually works: Draft a one-page onboarding outline before you post the job listing, not after you’ve hired someone. It forces you to think through the role clearly, and it gives your new hire something concrete to reference instead of relying entirely on your limited availability during their first weeks.
Frequently Asked Questions
Q: How do I figure out what my actual bottleneck is if I’m too busy to step back and think about it?
A: Block two hours, ideally away from your usual workspace, and list every recurring task from the last month. For each one, ask: if I couldn’t do this for two weeks, would revenue actually stop or slow down? The tasks that pass that test are your bottleneck candidates — everything else is discomfort, not constraint.
Q: Should my first hire be full-time or should I start with a contractor?
A: If the bottleneck task is ongoing and central to the business, full-time is usually right, provided you can pay a fair rate. If it’s more sporadic or specialized, a contractor lets you address the bottleneck without the fixed cost and management overhead of a full employee before you’re sure of the role’s shape.
Q: How much decision-making authority should I really give a brand-new employee?
A: Start narrower than feels comfortable, but write it down explicitly and expand it on a set schedule — say, a review at 30 and 90 days — rather than leaving it permanently vague. The problem isn’t starting narrow; it’s never defining the boundary at all, which forces every decision back through you indefinitely.
Q: What if I genuinely can’t afford market rate for my first hire?
A: Reduce the scope of the role to match your budget at a fair hourly or salaried rate — part-time, or a narrower set of responsibilities — rather than hiring full scope at a below-market rate. A well-paid part-time hire who stays outperforms a full-time hire at a discount who leaves in four months.
Q: How do I know if my first hire isn’t working out versus just needing more time?
A: Compare it against the decision-authority and onboarding clarity you gave them. If they’re struggling despite clear authority and a real onboarding process, that’s a fit issue worth addressing directly. If authority was never clearly defined and onboarding was improvised, give it real structure before concluding the person is the problem.
Your first hire sets the pattern for every hire after it — the mistakes compound if you don’t catch them early. Hire for the bottleneck actually capping your growth, define what they can decide without you, pay a fair rate, and give them something to onboard from besides your limited attention. Get this one right and the second hire gets dramatically easier.
