There is a specific moment in every growing service business when the founder concludes that the answer to the current strain is to hire. The team is stretched. Deadlines are slipping. The founder is working longer hours than they want to. And the intuitive fix, the one every founder considers first, is to bring in another person. If the strain is coming from too much work for too few people, then more people should absorb the work. The maths seems obvious. The maths is almost always wrong.
What the founder is experiencing as a capacity problem is usually not, in fact, a capacity problem. It is an operational structure problem that shows up as strain, and the difference matters because the two have completely different solutions. A genuine capacity problem is fixed by adding people. A structural problem is not fixed by adding people, and often gets worse when a hire arrives, because the new person adds their own coordination overhead to a business that was already overloaded by coordination.
This is one of the most consistent commercial mistakes in growing service businesses, and it is worth being direct about why founders make it. The strain is real. The intuition to hire is honest. And the arrival of a new person does produce a short-term feeling of relief, because the immediate load gets spread. What the founder does not see, until several months later, is that the underlying problem has not gone away and the total operational load has actually grown. The hire that was supposed to fix the capacity problem has quietly become another instance of the same problem, and the founder is back where they started, plus one salary. As covered in the piece on how to build a business that runs without you in the room, the structural conditions for a business to genuinely absorb more work are specific, and none of them are “add another person.”
What actually causes the strain
If the strain in a growing service business is not really about capacity, it is worth being specific about what it actually is. Five structural pressures produce the sensation of being under-resourced, and none of them are fixed by hiring.
The first is decision routing. In most growing businesses, decisions that could be made by someone other than the founder are still routing to the founder, because there is no clear structure for who owns which decision. The founder becomes the bottleneck, and the team spends significant time waiting on decisions rather than doing work. When a new hire arrives, they slot into the same structure, which means either they wait on decisions like everyone else, or they become another layer of coordination the founder has to manage. Either way the strain does not lift.
The second is coordination overhead. Growing service businesses run on informal coordination for longer than they should. Meetings, chat threads, quick check-ins between team members, and constant reprioritisation eat a meaningful percentage of everyone’s day. This overhead scales worse than linearly with headcount, because every additional person adds not just their own coordination need but also more possible pairings with everyone else. Adding a person to a business that is coordination-heavy does not reduce the coordination burden. It increases it.
The third is unclear ownership. In many growing businesses, the same piece of work has multiple people who are partly responsible and no one who is fully responsible. This produces the specific pattern of work being touched by several people, requiring reconciliation, and often being done twice because two people did overlapping parts of it. Adding a new person to a business with unclear ownership adds another partial owner to some pieces of work, which makes the pattern worse rather than better.
The fourth is manual operational work that should not be human work at all. As covered in the piece on how Power Automate actually helps a small service business, a meaningful percentage of the work being done in most growing businesses is repetitive coordination that a system should be doing. When that work is not automated, it sits on the humans, and the humans feel understandably stretched. Adding another human to do the manual work is a strictly worse fix than automating the work, because the new human costs a salary, adds coordination overhead, and eventually leaves. The automation does not.
The fifth is unclear priorities. Growing businesses often carry a portfolio of work where nothing is genuinely deprioritised. Everything is somewhat urgent, everything is somewhat important, and the team is trying to make progress on all of it simultaneously. This produces the sensation of always being behind, because no matter how much gets done, more things sit in the queue with unclear priority. Adding a person to this environment produces more work being done at low priority, which does not reduce the sensation of being behind, because the queue is not the constraint. The absence of a real prioritisation structure is.
Any one of these five would produce meaningful strain. All five operating together, which is the common case in a growing business, produce exactly the felt-capacity problem that founders experience. And none of them are solved by hiring.
What a hire actually does when the structure is wrong
When a new person joins a business with any of the five structural issues in place, the outcome is predictable. In the first weeks the founder feels short-term relief, because the new person absorbs immediate load and the team’s calendars have some breathing space. In the next couple of months, the new person starts becoming part of the same operational dynamic. They wait on decisions. They participate in the coordination overhead. They pick up work whose ownership was unclear, which either duplicates existing effort or creates new unclear ownership. They do manual work that should not exist. And they add their own priorities to a portfolio that already had too many.
Six months in, the founder looks at the total operational picture and realises the strain is back to where it was, plus one more salary. This is not because the hire was bad. Most of the time the hire is capable and hard-working. It is because the operational structure they joined was already producing the strain, and adding a person did not change the structure. It just added another instance of it.
The founder often responds to this by concluding that they hired the wrong person, or that they need to hire again. Sometimes both. Neither response addresses the underlying problem, which is that the operational structure needs to be rebuilt before headcount can genuinely produce capacity. The businesses that recognise this and do the structural work first can absorb the same or more workload with the same or fewer people, and the felt strain drops materially without a single new hire being made.
What the structural fix actually is
The alternative to hiring is not doing nothing. It is doing the operational work that would let the current headcount actually deliver at its true capacity, which is almost always higher than the current strained state suggests. Four specific pieces of work usually produce most of the recovery.
Defining clear decision authority for anything that does not require the founder specifically. Pricing within defined bands, scope decisions within defined parameters, client communication within defined norms. The team decides, the founder reviews the pattern, and the queue of decisions waiting on the founder shrinks. This alone often reduces perceived strain by a meaningful amount.
Building operational systems that hold the coordination that people are currently holding in their heads and their meetings. The CRM, the project management system, the workflow automations. When the system holds the state, the team does not need to reconstruct it through constant coordination.
Defining ownership at the level of work rather than the level of task. Each piece of work has a single named owner responsible for the outcome, and the owner has the authority to make the decisions that piece of work requires. Overlap gets resolved by structure rather than reconciliation.
Automating the operational work that should not be human work. This is usually the fastest single move to recover capacity, because it takes work off the team without any change in headcount, and the freed capacity can be redirected to work that actually requires human attention.
These four together typically produce enough capacity recovery that the felt need to hire disappears. The team can absorb more work than they thought they could, the founder’s time gets freed for strategic work, and the business runs more calmly at the same or higher output. The hire that was going to happen becomes optional rather than urgent, and the business is now in a much stronger position to hire when a genuine capacity need does emerge, because the new person will be joining a coherent operational structure rather than an overloaded one.
When hiring is actually the right answer
None of this is to say hiring is never correct. It sometimes is. But the honest sequence is structural work first, hiring second, because the structural work reveals whether the felt capacity problem was real or whether it was the operational structure producing the sensation of one.
A business that has done the structural work and still has more demand than the current team can genuinely absorb has a real capacity problem, and hiring is the right response. A business that has not done the structural work has no way of knowing what its actual capacity is, because the current output is being suppressed by structural friction. Hiring in that state is very likely to solve nothing and cost quite a lot.
The founders who successfully scale their businesses are almost always the ones who did the structural work first, hired second, and used the resulting hires to build meaningful capacity on top of a foundation that could support them. The founders who struggle are usually the ones who hired first, hoped the capacity would arrive, and discovered that another person in the same broken structure just produced more of the same strain.
If your spreadsheet has become the system, tell me what it does and I will tell you whether it is worth replacing. Start a conversation, or see what I build.