Hire or automate admin work: start with the copy-paste
Hire or automate admin work. That’s the fork every small firm hits when the booking tool, the invoicing app and the scheduling calendar stop talking to each other. Somebody is copying a job address from one screen into another, retyping a client’s phone number, or reformatting a time so the calendar doesn’t double-book. For a ten-person family firm, that somebody is usually the owner after dinner. The question isn’t whether the work exists. It’s whether the work is a job or a gap between tools.
Small business trend coverage keeps pointing at remote operations roles as the fix. The list of in-demand remote operations jobs includes roles like operations coordinator, virtual assistant and bookkeeper. What that coverage skips is the trade-off: a salary is a recurring commitment with management overhead. An automation is a build plus standing maintenance and breakage risk. Before you commit to either, you need to know what the work actually is.
The real challenge: you’re deciding before you’ve looked
Most owners decide by feel. The admin pile feels heavy, so they post a job. Or a software demo feels smooth, so they buy the integration. Both decisions happen before anyone has watched the work for a week. That’s the mistake. Without a task audit, you don’t know whether the role is forty hours of judgment calls or eight hours of copy-paste that two automations could remove.
Copy-paste work hides. It lives in the gaps between tools that were each sold as “all-in-one” but don’t share a data model. A booking confirmation lands in your inbox. You open the scheduling tool and create the job. You open the invoicing tool and create the invoice from the same details. Then the client emails a change, and you do it again in three places. None of that shows up in a job description. It shows up when you log every handoff for five working days.
There’s a second trap: assuming a hire removes the work. A person doing copy-paste is still doing copy-paste. They’ll be faster than you at first, then the volume grows, and you’ve added a salary, payroll, training and the quiet risk that the one person who knows the process leaves. The work didn’t disappear. It got a W-2.
A genuine partial answer: the one-week task audit
Here’s the audit we run with firms before any hire-or-automate conversation. It doesn’t require special software. A shared spreadsheet or a paper notebook works. For five working days, every time you or a team member moves information between tools, log four things: what moved, where it came from, where it went, and how long it took. Include the small ones. The two-minute copy-paste is the whole point.
- Day 1: log every transfer. Don’t judge it. Just write it down.
- Day 3: you’ll start seeing patterns. The same three fields moving from booking to invoice. The same client name retyped into the calendar.
- Day 5: sort the log into two columns. Column A: transfers that follow a rule every time. Column B: transfers that require a decision, a judgment call, or a conversation with a client.
Column A is your automation candidate list. Column B is your hire candidate list. Most firms find the split is not what they expected. The work that felt like a full-time role is often a handful of repetitive transfers plus a few genuinely human tasks. Two automations can cover the repetitive transfers. The human tasks need a person, but not necessarily a full-time one.
One caveat from our own work on workflow automation for small operations: the audit only works if you log the work as it happens, not from memory at the end of the week. Memory smooths the rough edges. It forgets the three times you switched tabs and lost your place. The log is the evidence.
What the audit leaves out: maintenance and breakage
An automation isn’t a one-time purchase. It’s a small system that sits between your tools and depends on both of them staying stable. When the booking tool updates its API, the automation breaks. When the invoicing app changes a field name, the automation silently sends the wrong data. Somebody has to notice, diagnose and fix it. That’s standing maintenance, and it doesn’t go away.
For a ten-person family firm, the maintenance burden is real but usually small. The breakage risk is the bigger issue. If the automation fails on a Friday night and nobody notices until Monday, you’ve lost a weekend of bookings or sent invoices with wrong amounts. A person would have caught the error, but a person also would have cost you a salary for fifty-two weeks a year. The trade-off is specific to your volume and your tolerance for failure.
This is where the audit’s Column B matters. If the copy-paste work touches client-facing details that change often, an automation might break more than it saves. If the work is stable and rule-based, two automations can remove the bulk of it. The audit tells you which situation you’re in. Without it, you’re guessing.
How we walk you through the decision
When a firm brings us the audit, we don’t start by selling a solution. We start by reading the log with them. The conversation goes in three steps.
- First, we separate the transfers that follow a rule from the transfers that need a judgment. This is usually the moment the owner realizes the hire they were about to post was really two automations and a part-time contractor.
- Second, we map the rule-based transfers to the specific tools you already use. Sometimes the fix is a native integration you haven’t turned on. Sometimes it’s a small custom automation that moves data between two tools that don’t talk natively. We don’t recommend building anything until we’ve checked what your current stack already does.
- Third, we price the standing maintenance honestly. An automation has a build cost and an upkeep cost. A hire has a salary and management overhead. We put both numbers on the table and let the audit decide.
For firms that already lean toward hiring, we point to the same audit as the job description. The Column B tasks become the role. The Column A tasks get automated first, so the new hire isn’t buried in copy-paste from day one. That changes the hire from a full-time admin to a part-time operations person, which changes the salary, the management load and the risk.
We’ve written before about the hire developer vs buy software trade-off, and the logic here is the same shape. The decision isn’t between a person and a tool. It’s between a recurring cost and a one-time build with upkeep. The audit is what tells you which one fits your actual work.
Before you post the job
Posting a job for a remote operations role is the easiest thing in the world. The job boards are full of templates. The salary benchmarks are a search away. What’s harder is knowing whether the role is real. A week of logging the copy-paste work answers that. It turns a feeling into a list, and the list tells you whether you need a person, an automation, or a little of both.
If you’re in the middle of this decision and want a second read on the audit, get in touch. Bring the log. We’ll help you sort Column A from Column B before you commit to a salary or a build.
What’s the one transfer in your week that you’d automate first if you knew it wouldn’t break?
About this article. This is general information and our own opinion, written from how we run operations for owners and businesses in Contra Costa County. It is not legal, tax, accounting, financial or other professional advice, it is not a recommendation to take or avoid any action, and it is not a substitute for advice about your own property, tenancy or business. CAO Investment Group is not a law firm, and reading this does not create an attorney-client or any other professional relationship. Local ordinances, fee schedules, forms, thresholds and deadlines change often and differ from city to city within Contra Costa County — anything here may be out of date by the time you read it, including as of the publication date shown above. Verify anything you plan to rely on against the current rules published by your own city or county, and speak to a qualified attorney, CPA or licensed professional about your specific situation before you act. This article refers to material published at this source, which we do not control and which may have changed or been withdrawn since we wrote about it; our description of it is our own reading, not the source speaking. We make no warranty that this information is current, complete or accurate, and we accept no liability for any action taken or not taken on the basis of it.
