When should you hire your first employee in a service business?

Hire when there is a defined seat for the person to stand in. That means a slice of the work with a written standard, a way to tell good from bad, and a boundary where your judgment starts. Volume is what makes a bad first hire feel urgent, which is why being busy is a poor signal to act on.

What is the cautionary tale, and why does everyone repeat it?

There is a story that circulates in every founder community I have ever been near, and it goes roughly like this.

A capable operator builds something real. He grows it. He hires, he adds overhead, he takes on the payroll and the management and the calls at nine at night, and after a few years he looks up and finds he has traded a good life for a bigger business he does not enjoy. So he unwinds it. He goes back to working alone, or nearly alone, makes less money, and reports that he is happier. Then he tells the next founder who asks: what you give up to make the money is not worth it.

That story is honest. I want to be clear about that, because the easy move here is to treat the man as a cautionary example and move on, and he does not deserve that. He is describing something that actually happened to him and he is trying to save somebody else from it. He is also usually right about his own case.

But there is almost always a second sentence, and almost nobody quotes it.

I watched a version of this play out on a legal forum this month. A solo lawyer asked whether he should grow. The thread split into the two camps it always splits into, and one man who had actually built the bigger firm and walked away told him not to bother. Then someone pushed him one step, and he added, on the record, that he had not done it right, that he had not been effective at delegating.

Everybody quotes the warning. Nobody quotes the diagnosis, and the diagnosis was sitting two comments underneath it.

Was it growth that broke him, or the way he grew?

Ask what changed when the business got bigger, and the answer is usually not the size.

A business where every decision routes through one person has a specific failure curve. At six clients it is invisible, because a competent founder can hold six sets of context in his head and still be home for dinner most nights. At sixteen it is uncomfortable. At forty it is a full-time job that consists entirely of being interrupted, and the founder is now the highest-paid dispatcher in his own company. The structure never changed. Only the load did.

So when that founder shrinks back to six clients, the relief is real and the conclusion is wrong. What he discovered was that his particular architecture only worked at one size, and he found the ceiling by hitting it. Shrinking to fit under the ceiling is a legitimate choice. It is just not the same thing as evidence that the ceiling is universal.

There is a third build, and the people living it are quiet, which is part of the problem. In that same thread there was one lawyer who had hired a paralegal and a part-time clerk specifically so she could have her mornings with her kids before school started. She hired in order to get time back. Nobody in the thread asked her a single question about it. The two loud camps were arguing about appetite, and the one person with a structural answer went unread.

I have written elsewhere about why a record year can leave a founder wrecked, and the short version is that structure has to exist before the weight arrives. The first hire is where most founders first meet that requirement, and it is where most of them discover they never built one.

What does the research say about founders who hold on?

It says holding on is common, expensive, and mostly involuntary in the end.

Noam Wasserman studied 212 American start-ups founded around the turn of the century and published the results in the Harvard Business Review. His findings are worth sitting with:

By the end of year three, 50% of founders were no longer CEO. By year four, only 40% still were, and fewer than 25% led their own company's IPO.
Four out of five founder-CEOs are eventually forced to step down. Most of them resisted the idea when it was raised.
Founders who give up more equity to attract cofounders, non-founding hires and investors build more valuable companies, and end up with a more valuable slice personally, than founders who part with less.

Read those together and the pattern is that control costs you the business, on a delay. The founders who let go earlier tend to keep more of what they built. (The Founder's Dilemma, HBR, February 2008.)

Gallup then measured the skill itself, and this is the number I would put on a wall.

In a study of 143 Inc. 500 CEOs, those with high Delegator talent posted an average three-year growth rate of 1,751%, which was 112 percentage points higher than CEOs with limited or low Delegator talent. They generated 33% more revenue, $8 million against $6 million, and created 21 jobs in three years against 17. And from a separate nationally representative sample of 1,446 US employer businesses, Gallup found that only one in four business owners has high Delegator talent. Three out of four do not. (Delegating: A Huge Management Challenge for Entrepreneurs, Gallup, 2015.)

That last figure is the one that reframes the cautionary tale. When three quarters of owners are weak at the single skill that growth depends on, a warning built on one owner's experience of growing badly is going to sound true to almost everyone who hears it. It resonates because it describes the majority case. It still is not a law of business.

And the majority case is bigger than most people realise. The US Census counted 29.8 million businesses with no paid employees at all in 2022, out of 35.7 million businesses total — roughly five in six American businesses have never hired anyone (Census Bureau, May 2025). Some of that is deliberate and good. A lot of it is a first hire that got postponed until the founder stopped believing it was possible.

Why does "I'm too busy to hire" get the causality backwards?

Because busy is a symptom of the thing that makes hiring fail.

The founder who is drowning has, by definition, no time to write anything down. So he hires under pressure, hands the new person the overflow, and discovers that the overflow was a pile of unlike tasks held together by his own context and never a job at all, and passing it to someone else does not transfer the context. It just adds a person who has to ask him questions all day.

Six weeks later he concludes that hiring doesn't work for a business like his, lets the person go or lets them drift, and adds the experience to the warning he will give the next founder who asks.

What that sequence tests is whether an undocumented business can absorb a body, and the answer to that has always been no. It says nothing about whether he could have grown.

The trigger is whether a piece of the work has become describable.

What makes a piece of work handable?

Three things, and you can check for all three in an afternoon.

It needs a written standard. Not a process document nobody reads, just a short statement of what a good version looks like, specific enough that two people looking at the same example would agree on whether it passed. If you cannot write that down, you do not know it consciously yet, and you are about to ask someone else to guess at something you have never articulated.

It needs a boundary somebody else can see. The point where the task stops and your judgment starts, named in advance rather than discovered in week three. The most common reason a first hire underperforms is that nobody drew this line, so the new person either escalates everything, which exhausts you both, or escalates nothing, which is worse and takes longer to find out about.

And it needs a way for you to know it went wrong without watching it happen. A number, a checklist, a weekly artifact you can read in five minutes over coffee. If the only way to tell whether the work is good is to observe the work being done, you have simply relocated your attention.

Work that has all three is handable this month. Work that has none of the three is not a job yet, no matter how many hours of it you are personally doing.

That distinction is doing more work in this piece than any of the numbers, so here is the test in one line: write down every decision you made last week, then split them into decisions that genuinely required your judgment and decisions that only came to you because nobody has written down what a good answer looks like. The second pile is your first hire's job description. It is also, right now, your architecture problem.

Where does the first hire sit in the four frameworks?

Underneath Sales, most of the time, and not where founders expect.

The instinct is that the first hire is a delivery hire, someone to help carry the work. Sometimes that is right. But in founder-led service businesses the piece that is most repeatable and least dependent on the founder's judgment is usually the front half: qualification, follow-up, scheduling, the parts of the pipeline that get dropped when delivery gets heavy. That is why the feast and famine cycle exists at all. The founder delivers, the pipeline stops, and the two alternate forever.

The four frameworks are just the four systems every business that outgrows its founder ends up needing. Positioning decides what you take and what you refuse. Marketing produces opportunities without you chasing each one. Sales converts them without living in your head. Lifetime Value keeps and compounds the clients you win. You build your own version of each. You do not adopt somebody else's, and any consultant who hands you a pre-packaged set has sold you a formula rather than a diagnosis.

The first hire is the moment the business finds out how much of itself has been written down, and most founders discover the answer is none of it on the day they can least afford to.

Putting it to work

Do this before you post a job ad.

1. Log a week of decisions. Every question that came to you, every judgment call, every "quick thing." Keep the list on your phone. A week is enough.

2. Split the list in two. Decisions that genuinely needed your judgment, and decisions that reached you because no standard exists. Be honest about the second pile; most founders find it is over half.

3. Take the largest cluster in pile two and write the standard. One page. What good looks like, where the boundary is, what artifact tells you it happened. If you cannot write it in a page, that cluster is not one job and you need to cut it smaller.

4. Do that job yourself for two weeks, against your own written standard. This is the step people skip and it is the one that saves the hire. You will find out immediately whether the standard is real or whether you have been improvising.

5. Now decide what you are buying. Time back, capacity, or coverage while you are away. Those are three different hires. A founder who has not chosen between them tends to hire for all three and get none.

6. Set the number that says it worked. Before the person starts. Ninety days out, what will be true that isn't true today? If the only answer is "I'll feel less busy," you have not defined the seat yet.

What did twenty years of volunteers teach me about this?

That you cannot prevent your way to a good hand-off, and that the thing you actually control is how fast you follow up.

I spent two decades in ministry leadership, which means I spent two decades handing real responsibility to people I could not fire, could not pay, and could not compel. If you have never led under those conditions, the difference is that every ounce of authority you have is whatever you managed to make clear in advance. There is nothing to pull on afterwards. That is a harsh school and it teaches quickly.

What it taught me is that hand-offs go sideways in two directions, and they need opposite things from you.

The first kind is the person who is unsure and will not tell you. Usually they want to prove they belong there, so asking for help feels like admitting they should not have been given it. They hesitate, they guess, and you find out three weeks later. The fix is upstream and it is mostly about you: tell them plainly that asking is welcome, and then live up to that the first time they do it, because they are testing. Better still, go to them. A short check-in that just asks how it went today does more than any policy, because it makes the door visibly open rather than theoretically open.

The second kind is the person who is a little too sure. Confident people make confident mistakes, and no briefing prevents that, because the briefing was heard through the filter of somebody who already knew how to do it. With that person the expectations have to be unmistakable, and some of it can only land as a follow-up. That is not a failure of your preparation. Sometimes there is nothing preemptive available, and that is simply the risk of working with a team rather than working alone.

Which brings me to the one variable that is genuinely yours. Close the gap between finding out and following up. When something goes off the rails, the value of the conversation decays fast. Have it while the incident is fresh in everyone's mind and people are ready to learn from it. Leave it two weeks and you are relitigating a memory, everyone is defensive, and the lesson does not land. That is as true of a first employee as it was of a volunteer, and it is the habit most first-time managers do not have, because the conversation is uncomfortable and postponing it feels like grace. It isn't. It's just later.

The lawyer who warned the younger one off growth was honest about his own experience. He reported a real cost accurately and attributed it to the wrong cause, which is the most common shape of bad advice there is. He said the second sentence himself, out loud, in public. It just did not travel, because "scaling cost me my life" is a story and "I wasn't effective at delegating" is a diagnosis, and stories move further than diagnoses every single time.

Sources

Frequently asked

Can I afford a first hire before the revenue is there?

Usually the question is backwards. If a defined seat exists and it frees your highest-value hours, the hire pays for itself faster than a founder expects. If no seat exists, no amount of revenue makes the hire work, and you will spend the money proving it. Define the seat first and the affordability question gets much easier to answer.

Should my first hire be an assistant, a contractor, or a full-time employee?

Employment type matters less than definition. A well-defined role works as a contractor, a part-timer or an employee; an undefined role fails in all three. Start with the smallest version of the seat that has a written standard, and treat the employment question as a second decision about cost, control and permanence.

What if I genuinely want to stay small?

Then stay small, and build the architecture anyway. You write down what you do so the business can survive you being sick, or away, or bored. Hiring is only one of the things it makes possible. A one-person firm with documented work is a different asset from a one-person firm that exists entirely in one head.

How do I know if I've defined the role well enough?

Do the job yourself against your own written standard for two weeks. If you find yourself making judgment calls the document does not cover, the document is not finished. If you get through two weeks without an undocumented decision, the seat is real and somebody else can sit in it.

Isn't some of this just what running a business feels like?

Some of it, yes. Hard weeks are normal and no structure removes them. What is worth investigating is hard that arrives on a schedule, in the same shape, after every good month. That is a structural signal rather than a stamina one.

Ready to look at the architecture honestly?

If you have been circling the first hire for a year and the reason keeps changing, the constraint is probably not money or timing. Book the conversation. We'll tell you what we see, and whether the work we do fits where you are.

Book the conversation →