Put a Number on It: A One-Week Admin Audit Before You Hire Anyone or Buy Anything

Because nobody invoices for it. The work is real, the hours are real, and the ledger has no line for them. That is why it feels constant and stays invisible. The pattern shows up over and over in owner-run businesses. As one owner put it on r/smallbusiness: "I did the math on mine once and it was genuinely depressing. Scheduling back and forth, chasing invoices, trying to reconcile expenses. None of it shows up as billable time but it eats into everything." The damage is not one big block of lost time. It is fragmentation. Another post on r/smallbusiness described it plainly: "It was all the little things that kept interrupting the day. Replying to emails, chasing people for answers, updating documents, scheduling calls. none of them felt like much on their own, but together they easily ate up a few hours." Each task is too small to justify a decision on its own. Fifteen minutes chasing a supplier does not warrant hiring anyone. Neither does re-keying a job into the accounting file. The cost only becomes a decision when you add the fifteen-minute pieces together across a week and see the total in one place. This is also why the honest question gets asked in Australian forums in exactly these terms. From r/ausbusiness: "How many unpaid hours disappear every week into paperwork, notes, updates, and general admin?" Nobody can answer that from memory. Estimates made at the end of a week tend to run low, because the tasks easiest to forget are the small ones that only add up when you total them.

The audit has to survive the week you actually have, not an idealised one. Anything requiring a timer, an app or a discipline you do not already have will collapse by Wednesday. Use a single sheet of paper or one note on your phone with six category labels, written once: scheduling and rescheduling; quoting and following up quotes; invoicing and chasing payment; data entry and re-entry between systems; supplier, materials and ordering admin; compliance, records and reporting. Rules that keep it alive for five days: tally in five-minute blocks and round up, do not try to be precise; log after the task, not during, since one stroke next to a category takes two seconds; log it even if you did it at 9pm on the couch, especially then; include the interrupted attempts, because opening the job file, being interrupted, and coming back later is two entries; and everyone who touches admin logs, not just you, because the office coordinator's hours are the ones most likely to be underestimated. At the end of Friday, add up each category. You now have six numbers and a total. That is the whole method. It is deliberately cruder than a time-tracking tool because a crude number you actually collected beats a precise number you abandoned on day two. One caveat. A single week is a sample, not a measurement. If your week was unusually quiet or unusually chaotic, note that on the sheet and run a second week a month later.

Three conversions, in this order. Cost per week: multiply each category's hours by the hourly cost of whoever did the work. For an employee, use their loaded cost, not their base wage. For yourself, use the rate you bill clients, because an hour spent reconciling is an hour not spent on billable work or on winning the next job. That second figure is uncomfortable. It is also the honest one. Cost per job: divide the weekly total by the number of jobs completed that week. This is the number that survives growth conversations. If admin costs you a fixed amount per job, doubling your job count doubles that cost. That is the difference between a nuisance and a ceiling. Cost per year: multiply the weekly figure by your working weeks. Only use this number for comparison against annual options like a hire or a subscription. Do not use it as a headline, because it makes everything look urgent and pushes you toward buying something. Track one more line that the accounting will not show you: hours logged after 6pm. That tells you how much of the admin is coming out of unpaid personal time rather than the working day. A recurring theme in Australian threads is that admin does not just cost money, it takes the weekend. From r/AusFinance, an owner weighing up a bookkeeping quote he had not yet accepted listed what it would cover: "... they manage all my receipts so I don't have to spend my Sundays doing admin ..."

Not every uncomfortable task is an expensive one. This is an easy decision to get wrong, because the pull is to remove the task you hate most rather than the task that costs most. Sort your six categories against two axes: total hours, and how repeatable the task is. High hours, highly repeatable and rule-based, such as invoice chasing, appointment reminders or re-entering job data between two systems, is worth building or automating, because the rules barely change. High hours but judgement-heavy, such as complex quoting, dispute resolution or scoping unusual jobs, is worth a person rather than a tool. Low hours and highly repeatable, such as weekly report formatting or filing, should be left alone, because the fix costs more than the task. Low hours, unpredictable and stressful, such as one-off compliance requests, will not be helped by automation. A category qualifies as worth removing when it is high-hours, rule-based and stable. If a task changes shape every time, no tool will hold it, and the automation will quietly break within a month. Here is a clean example of the first profile, posted on r/AusFinance: "1) Friday cashflow ritual. Every Friday arvo, no exception: send all invoices for the week, follow up every client past 7 days due (bank transfer + polite email), update one simple spreadsheet: cash in, cash out, pipeline. 90 minutes. Feels like punishment. ..." Ninety minutes, every week, same steps, same order, rules that do not change. That is the profile worth building against. Compare it against a quoting process that requires a site visit and a judgement call. Same feeling of drudgery, completely different answer.

Once you have the categories and the numbers, the choice becomes narrow rather than philosophical. Hiring an employee fits high-hours, judgement-heavy, ongoing work where you have the volume to keep them busy, and fails when the work is genuinely rule-based, because you are then paying a person to be a script. A virtual assistant fits high-hours repeatable work that still needs human judgement or client contact, and fails when the task needs deep system access or changes weekly. An off-the-shelf tool fits when your process already matches how the tool works, and fails when you need it to bridge two systems that do not talk to each other, a gap that comes up repeatedly in Australian trade and service threads. Building something fits high-hours, rule-based work that is specific to how you operate, and fails when nobody in the business owns it after it is built. That last failure mode is the one that quietly ends projects. An automation built by an outside party and understood by nobody inside breaks the first time a supplier changes an email format. The fix is not a longer retainer. It is having two or three of your own people who can read the workflow, diagnose the break and change it. The audit is the input to that. If you cannot say which category costs the most and whether it is rule-based, you cannot brief a hire, a VA, a vendor or your own team. You are buying based on irritation. The audit will not tell you what to build. It will tell you what is worth the conversation.

How long should an admin audit run? Five working days is enough for a first pass. It captures a full invoicing and scheduling cycle without exhausting anyone. If the week was unusually quiet or unusually busy, note it on the sheet and repeat the exercise a month later before committing to an expensive decision. What hourly rate should I use for my own admin time? Use your billable client rate, not a notional wage. An hour spent reconciling expenses is an hour unavailable for billable work or for winning the next job. Using a lower rate understates the cost and makes doing nothing look more sensible than it is. Do I need a time-tracking app for this? No. A paper tally in five-minute blocks is more likely to survive a busy week than an app requiring start and stop actions. Precision is not the goal. The goal is a rough total per category that you actually finish collecting by Friday. What if my admin hours look small? Then you have saved yourself an expensive decision. That is a valid result. Check the cost-per-job figure before dismissing it, because a small weekly number that scales with volume becomes a ceiling on growth well before it becomes a visible expense. Which admin tasks are worth automating first? The ones that are high-hours, rule-based and stable week to week. Invoice reminders, appointment confirmations and re-entering data between two systems usually qualify. Quoting, dispute handling and anything requiring a site visit or a judgement call usually do not. Who should own an automation once it is built? Someone inside the business who understands the process and can change it. Automations fail when the only person who understands the workflow is external. Two or three trained internal people is the difference between something that lasts and something that quietly stops working.

Quotes are reproduced verbatim and attributed to the subreddit only, not to individuals. r/smallbusiness: https://www.reddit.com/r/smallbusiness/comments/1sukn23/admin_time_and_costs/ and https://www.reddit.com/r/smallbusiness/comments/1upm3ii/what_is_one_admin_task_you_have_found_a_way_to/. r/ausbusiness: https://www.reddit.com/r/ausbusiness/comments/1r3c2gd/document_administration/. r/AusFinance: https://www.reddit.com/r/AusFinance/comments/1rq9hnm/businessowners_sole_traders_what_are_you_actually/ and https://www.reddit.com/r/AusFinance/comments/1syqy88/freelancers_small_biz_owners_in_aus_5_years_which/. No statistics are cited in this article. Every figure discussed is one you calculate from your own week.