For close to two years, a one-man trades business turned down more work than it took on, because taking on a second pair of hands felt like too big a leap. That's not an unusual story — it's close to the default for solo trades and small service businesses — and looking back, the delay wasn't caution. It was fear wearing a sensible-sounding disguise, and it cost more than the eventual hire ever did.
The maths that got done wrong for two years
The reasoning for waiting always sounded rational at the time: what if the work dries up after I've taken someone on? What if I can't afford a bad month with a wage to pay regardless? Every one of those questions is worth asking. The mistake was that they got asked as reasons never to hire, rather than as risks to actually plan around — and the maths never got done properly on the other side of the ledger: the value of the jobs being turned away every month because there simply wasn't the capacity to take them on.
What turning down work actually costs
Every job declined for lack of hands doesn't just disappear quietly — it goes to a competitor, who may well keep that client for years afterwards. Add up a couple of turned-down jobs a month, at a decent margin, over two years, and the total dwarfs what a modest apprentice or labourer's wage would have cost across the same period. That comparison — the wage of a hire versus the value of the work refused — is the one that should have been done from month one, and wasn't, because the wage was a concrete number sat right in front of me and the lost work was an abstract 'we're just very busy' feeling that never got costed out.
The wage of a first hire feels like a real cost because it's a number on a payslip. The work you keep turning down feels like nothing, because it never shows up as a number at all — until you finally add it up.
The fear that was really driving it
Underneath the cash-flow worry was a less comfortable truth: taking on an employee meant becoming responsible for someone else's income, not just my own — and that felt heavier than any spreadsheet captured. There was also a quieter fear about losing control over the standard of work, since every job until then had my own hands and my own eye on it. Both fears were real. Neither of them, in hindsight, justified two years of turning away profitable work rather than finding a way to manage the risk properly.
What actually made the first hire work
The hire that finally happened worked because a few of the fears got addressed directly rather than just outrun: starting with a short trial period rather than a permanent contract from day one, so both sides could test the fit before committing fully; being explicit and specific about the standard expected on every job, rather than assuming it would be obvious; and — the part that mattered most for cash-flow nerves — running the numbers on a genuinely quiet month in advance, so there was a real answer to 'can I cover this wage if work dries up for a few weeks', instead of a vague worry left unresolved. None of that removed the risk of taking on staff. It made the risk something that had actually been planned for, rather than something being avoided by never hiring at all.
The advice for anyone in the same spot now
If you're a trades or service business owner turning down work because there's nobody else to do it, the honest exercise isn't 'can I afford to hire someone' — it's 'what is turning down this work actually costing me, and is that more or less than a wage would cost'. For most solo trades doing steady, profitable work, that answer arrives faster than the fear suggests. Getting the written contract and the basics right from day one takes the guesswork out of the part that's genuinely within your control.
The other lesson: capacity is a decision, not a fact
The bigger shift wasn't really about hiring at all — it was realising that 'I can only take on so much work' had quietly become treated as a fixed fact about the business, when it was actually a decision, made by default, to keep capacity exactly where it had always been. Nobody chose to cap the business at one pair of hands; it just never got revisited. Once that reframing clicked, the question stopped being 'should I hire' and became 'what would I need to be true for hiring to make sense', which is a much easier question to actually plan around.
What changed in the months after
The jobs that used to get turned away started getting taken on, and the business grew faster in the following year than in the two years of solo working combined — not because the work suddenly got easier to find, but because there was finally capacity to say yes to it. The wage that had felt like the biggest risk in the business turned out, once it was actually being paid, to be one of the more predictable costs on the books. The unpredictable cost, it turned out, had always been the one nobody was counting: the work walking out the door every month to someone else.
The part I'd still tell someone to take seriously
None of this is an argument to hire recklessly the moment things get busy. A single unusually hectic month isn't the same as a sustained pattern of turning down work, and taking on a wage commitment based on one good quarter is a genuinely different decision to taking one on after two years of steady, repeated evidence that demand outstripped capacity. The mistake wasn't being cautious. It was staying cautious for two years after the evidence had already answered the question, simply because the decision never got looked at properly in the first place.
