You Need Half an Admin Person: The Gap Between Doing It Yourself and Hiring

Because the salary is not the cost. The loaded cost is. Add superannuation, payroll tax where applicable, workers compensation, leave loading, a laptop, a licence seat or two, and the weeks where the owner is training rather than earning. In Australia the superannuation guarantee alone is 12 per cent of ordinary time earnings (source: ato.gov.au). None of that is exotic. It is just invisible when you are mentally comparing an admin hire to your own evenings. This is a recurring complaint in owner-operator forums. One post on r/smallbusiness put the arithmetic plainly: "I run a small marketing firm and can’t keep up with scheduling, emails, invoices, etc. I looked into hiring an office manager, but salary + taxes + training = too much right now." The other half of the problem is granularity. The work is spread across the week in fragments: chasing a deposit, rescheduling a job, re-keying a form into the job management system, sending the same six emails. You cannot hire a person for ninety minutes a day across five days at the exact moments the work appears. So the owner absorbs it, and the absorbing happens at 10pm because that is the only time left. Then the workload arrives anyway, just wearing a different shirt. Another r/smallbusiness post described what happens when one person carries it: "My front desk person is juggling phones, patient intake, appointment scheduling, referral coordination, and prior authorizations for procedures. She’s great but she’s one person doing a three-person job, and things are slipping: missed prior auths that delay procedures, phone calls going to voicemail, patients waiting 15 minutes just to check in."

Price it honestly before you price the fix. Three costs matter and they behave differently. The hours are fragmented admin time, mostly after hours, and the owner absorbs them unpaid. The leakage is late quotes, unchased invoices, missed callbacks and rework from re-keyed data, and the business feels it silently. The ceiling is the jobs you decline because you cannot handle the admin tail, and growth pays for that one invisibly. The leakage is the one nobody measures. A quote sent on day four instead of day one loses to whoever sent theirs on day one. An invoice chased on day sixty rather than day thirty is a cashflow event, not an admin event. Run the count for two weeks. Tally every recurring task, how often it happens, and how long it takes. Not an estimate from memory, an actual tally. Then look at how the total is distributed. If a small number of task types account for most of the time, that clustering is the opportunity, because those are the tasks you can retire without hiring anyone.

Because the comparison is not maths against maths. It is cashflow shape against cashflow shape. A hire is a monthly outflow that starts small, ramps with output, and can be stopped with notice. A quoted build is a lump sum out of a buffer that is also holding rent, insurance, tools and the next BAS. Even when the payback period is short, the shape is wrong. A contributor on r/n8n described the buyer's side of that conversation without much sympathy for sellers: "Client's POV: this snake oil salesman wants access to my internal business information. I also can't spend $2000 even if it saves me money. I dont have the reserves for that." The same thread made the structural point better than most vendor blogs do: "A lot of businesses struggle with cashflow, they have rent, staff, insurance, licenses, expenses, tax and a huge list of other outgoings. Give them something that works for them without the fear of investing a large sum for a result they can't yet see." That last clause is the real objection. A result they cannot yet see. An owner who has never watched one of their own processes run without them has no evidence that the second one will work either. The lump sum is not just a cashflow problem, it is a confidence problem being solved with money instead of proof. Concede the counter-argument: sometimes a hire genuinely is the right answer. If the work needs judgement, relationship, phone presence or physical presence, a person beats a workflow every time. If the work is growing faster than any single fix can absorb, hire. The argument here is narrower. The specific band of work sitting between doing it yourself and justifying a salary is usually process work, and process work is the cheapest thing in the business to remove.

One task. One week. Owner-built. Then stop and look at it. A sensible first sequence for a service business runs in five steps. First, pick the highest-frequency, lowest-judgement task, usually enquiry acknowledgement, quote follow-up or invoice reminders. Second, map it on paper first: trigger, inputs, decision points, output, failure cases. If you cannot draw it, you cannot build it, and neither can a contractor. Third, build the smallest version that handles the common case only and ignore the edge cases in version one. Fourth, run it alongside the manual process for a fortnight and compare outputs. Fifth, only then turn the manual version off. Much of this may run on tools the business already pays for. Check what your existing accounting and job management software can already do before you buy anything new, because built-in reminders, templates and triggers often go unused simply because nobody has sat down for an afternoon to configure them. The part that transfers is not the tool. It is the diagnosis: knowing which task to pick, how to map it, and how to work out why it broke on the Tuesday it broke. Someone inside the business has to hold that. If nobody does, the workflow dies the first time a form field changes, and the owner goes back to 10pm.

Not the busiest person. Not the owner alone. Aim for two or three people inside the business who can build and repair the workflows themselves. One is fragile: they get sick, they leave, they get pulled onto a job. Two or three creates redundancy and, more usefully, creates arguments about how a process should actually run. Those arguments are where the process improves. This is also the answer to the retainer trap. An external builder produces a working thing and a dependency at the same time. Every change, every broken integration, every new form field routes back through someone who charges by the hour and does not know your job cycle. The capability is the asset. The workflow is just the current output of it. If your business has an operations person, a senior admin, or a technically curious tradesperson who already builds their own spreadsheets, that is your candidate. They do not need to be a developer. They need to be the person who notices that the same problem keeps happening.

Is it cheaper to automate admin work or hire a part-time admin? It depends on the work. Repetitive, rules-based tasks with clear triggers are usually cheaper to remove than to staff. Work needing judgement, phone presence or client relationships is cheaper to hire. Tally your recurring tasks for two weeks first, then split the list into those two buckets. How many hours a week justify a first admin hire? There is no fixed threshold, and the hours question is the wrong one. The better test is composition. If most of the hours are judgement work, hire. If most are repetitive process work happening on a predictable trigger, hiring buys you a person to do work that did not need doing. Why do small automation projects work better than large ones? Cashflow shape and confidence. A small fix is paid from operating cash, proves itself within weeks, and teaches the team how the next one should be built. A large project asks for a lump sum against a result the owner has never seen work in their own business. What is the true loaded cost of an employee beyond salary? Salary plus superannuation, payroll tax where thresholds apply, workers compensation, leave entitlements, equipment, software seats, and the owner's training time. The superannuation guarantee alone is 12 per cent of ordinary time earnings (source: ato.gov.au). Training time is the cost most owners forget to count. Can I build this myself without a developer? Usually yes for the first few workflows. The hard part is not building. It is process-mapping and diagnosis: choosing the right task, drawing it accurately, and working out why it failed. Those skills are learnable and they are what keeps a workflow alive after launch. What happens when the person who built it leaves? The workflow dies, unless more than one person understands it. Train two or three people, keep a one-page map of each workflow, and make sure the logins sit in a shared business account rather than an individual's inbox.

Quoted community threads: r/smallbusiness and r/n8n. Quotes are reproduced verbatim and attributed to the subreddit, not to individuals. Superannuation guarantee rate: Australian Taxation Office, https://www.ato.gov.au/businesses-and-organisations/super-for-employers/paying-super-contributions/how-much-super-to-pay. Discussion threads: https://www.reddit.com/r/smallbusiness/comments/1p4xwag/affordable_admin_help_for_small_business_owners/, https://www.reddit.com/r/smallbusiness/comments/1r1nfib/my_dermatology_practice_is_growing_but_i_cant/, https://www.reddit.com/r/n8n/comments/1qpewps/fuck_everyone_saying_selling_n8n_automations_is/. Note on evidence: the community evidence quoted here comes from general small business forums and is not specific to Australia. The superannuation figure is Australian.