Should I Hire Someone or Build the System First? A Decision Framework for the First Hire

In our view, the first-hire debate is usually a diagnosis problem, not a courage problem. The owner feels flat out, and the obvious fix is a second pair of hands. But "flat out" covers two different loads that need opposite solutions. Load one is field capacity: you are on the tools for the hours you want to work and you are turning away paid work. That is a hands problem, and a person solves it. Load two is admin: quoting, chasing, invoicing, scheduling, reminders, follow-ups, BAS prep, and the small daily decisions nobody else has the context to make. That is a process problem, and a person does not solve it. A person adds to it, because now you also carry payroll, supervision, insurance and someone else's mistakes. An owner on r/ausbusiness described the second load: "I'm decent at the actual work but the business side of it? Admin, cash flow, deciding if I hire someone and try to grow it, when to invest vs when to tighten up, keeping on top of BAS and even just my invoices, figuring out if my pricing is right... it feels like I'm guessing half the time." Almost none of that list is field capacity. Hiring a tradesperson does not touch a single item on it. Hiring an administrator touches some of them, but only if the process they are meant to run already exists.

Three numbers separate the two loads. Track them for two ordinary weeks, not your worst week and not your quietest. First, billable hours as a share of your working week. Count the hours you were actually on a paid job and divide by the hours you worked. High share and still refusing work means a hands problem. Low share and still exhausted means the missing hours went to admin, and a second tradesperson makes admin worse. Second, enquiries answered within one business day. Every unanswered enquiry is revenue you already paid to generate. A poor number here is a response problem, not a capacity problem. Third, manual touches per job. Follow one job from enquiry to paid invoice and count every time a human retypes or re-enters something: quote typed from a text message, job details re-entered into the scheduling app, invoice details copied into accounting, follow-up remembered from memory. If a routine job needs the same details retyped several times over, the admin load is self-inflicted, and it scales with every job a new hire brings in.

A hire is a recurring, on-costed, legally binding way to buy capacity. In Australia that means a wage plus superannuation, workers compensation, leave entitlements and your supervision time. It is the correct purchase when you need hands. It is a poor purchase when what you needed was a rule that runs itself at 7pm. There is a second cost owners forget: a hire is not productive on day one. As one commenter on r/Plumbing put it: "A new hire is going to run every job slower than you for the first couple months even with perfect SOPs, because half of what makes you fast is stuff you've internalized and can't write down." That cuts both ways. It argues against hiring as a quick fix, and it argues that the process is not optional, because documented steps are what shorten the unproductive period. You need the system either way. The only question is whether you build it before the wage starts or after. Building it first has a practical benefit owners underrate: the documented, partly automated process is the training material. The new person follows a defined path instead of absorbing your habits, and you can see exactly where they fall off it.

They are partly right, and the part worth taking seriously is not the cynicism. It is the observation that people are not components. From r/Plumbing: "Managing people is a whole different world and ballgame. They won’t be pieces you can control or fit into your systems. They’re wild cards that take management, thought, constant changing upkeep and feelings are involved ..." That is a fair warning and it should change what you expect from a system. No process removes the management load of employing a person. Rosters, feelings, motivation and judgement calls stay with you. The warning still supports building the system first, for a reason usually skipped. Managing a person against a defined process is a different job to managing a person against your unwritten preferences. If the standard exists outside your head, a performance conversation is about the standard rather than about you. If it does not exist, every correction is personal, and that is where much of the friction the veterans describe comes from. Concede the counter-argument properly: some owners do better staying solo and running service calls at a good margin. That is a legitimate business, not a failure.

Start with the path a job already takes, not with software. A solo plumber on r/Plumbing framed the goal well: "I’m a solo plumber (strata + residential, no big commercial buildings) and I’m trying to systemize my business properly before hiring so I don’t create chaos later." The order that works is straightforward. Map one job type from first enquiry to final payment: enquiry, quote, booking, job, invoice, payment, follow-up, with every step and who does it. Mark the steps that are pure data movement, because retyping and re-entering are candidates for a rule. Mark the steps that need judgement, such as pricing calls, scope changes and difficult customers, because those stay human and become your training notes for the hire. Fix intake first, since a fast consistent first reply protects revenue you have already paid for. Then connect the tools you already have. Australian trade businesses commonly run a job management tool such as ServiceM8, Tradify, simPRO or AroFlo alongside accounting software such as Xero or MYOB. The gaps between those tools are where the manual touches hide. Only after that does the hiring question have a clean answer, because you now know how many hours a week the process actually needs from a human.

When the three numbers say capacity. High billable share, healthy reply rate, low manual touches, and you are still declining profitable work. Systems are not the constraint then. Hands are. Hire, and use the mapped process as the onboarding document. The other clean case is a part-time administrator when the admin load is large but genuinely judgement-heavy and irregular. A rule cannot make a discretionary decision. If most of your admin hours are decisions rather than data entry, a person is the right answer, and the process map tells you exactly which decisions you are delegating and on what basis.

This is where small-business process work quietly dies. The build gets outsourced, the person who built it leaves, nothing is documented, and before long the business is back to WhatsApp and memory. The failure is rarely the tooling. It is that nobody inside the business could open the workflow, understand it and change it. That is the thinking behind buildAutomation. It trains two or three of your own people to map the process, build the workflow and debug it when a supplier changes an email format. No retainer, and no dependency on an outside agency for a small change. The transferable skill is diagnosis and process-mapping. The software is the easy part. If the person you want to train is yourself, and you would rather build the tools than buy them, buildAcademy teaches non-technical people to build and debug real software.

Should I hire before work is consistent or wait until I am overloaded? Neither extreme works. Hire when the numbers show capacity is the constraint and revenue is predictable enough to carry a wage through a slow month. If you are overloaded but your billable share is low, the overload is admin and a hire will make it worse. Is process work over-engineering for a two-person business? Not if you keep it to one job type. Mapping a single workflow and removing duplicate data entry pays back at any size. Over-engineering looks like buying five tools before you have written down how a job moves through your business. What is the cheapest first system to build? A reliable enquiry response. Every enquiry that goes unanswered for a day is money you already spent on marketing. Fixing intake needs no new headcount and usually uses tools you already pay for, such as your job management app and your accounting software. Will a system reduce the management load of employees? Partly. It removes ambiguity about how work should be done and gives you an objective standard to manage against. It does not remove rostering, motivation, judgement calls or the human side of employing people. Expect it to shorten training, not to replace management. Do I need to replace ServiceM8 or Xero to do this? Usually not. Most manual touches happen in the gaps between the tools rather than inside them. Connecting what you already run is cheaper and less upheaval than migrating, and it keeps the data your accountant relies on where it is. Who should build and own the automations? Someone who stays in the business. Automations fail when the only person who understood them was external. Train an internal owner who can read the workflow, change it and fix it. Capability inside the business beats a retainer outside it.

Quotes are reproduced from the linked threads with the original wording and emphasis preserved, trimmed only where marked with an ellipsis, and attributed to the subreddit only, never to an individual. r/ausbusiness thread on winging the business side of a small Australian business: https://www.reddit.com/r/ausbusiness/comments/1s31uh7/anyone_else_feel_like_theyre_winging_it_with/ . r/Plumbing thread on a solo plumber trying to systemise before hiring: https://www.reddit.com/r/Plumbing/comments/1qdgh2t/solo_plumber_doing_200kyr_trying_to_systemize/ . No statistics are cited in this article because none were available from a source we could verify.