Hire an Ops Person or Automate the Role? How to Actually Decide

You’re drowning in the same ten tasks every week. Scheduling. Data entry. Chasing down invoices. Copy-pasting between systems that don’t talk to each other. At some point, the thought shows up: I need to hire someone.

Maybe you do. But before you post the job, it’s worth doing the math — the real math, not just “salary divided by 12.”

The real cost of a hire

Here’s a hypothetical, just to make the numbers concrete. Say you hire an ops coordinator at $45,000/year. That’s not what it costs you.

• Payroll taxes, benefits, workers’ comp: often another 15-25% on top. Call it $52,000-$56,000 in year one.
• Recruiting time: writing the posting, screening resumes, interviewing. Even a fast search eats 15-20 hours of your time.
• Ramp time: 60-90 days before they’re doing the job at full speed, and you’re still checking their work most of that time.
• Management overhead: 1-on-1s, answering questions, catching mistakes. Call it an hour a week, forever.
• Turnover risk: if they leave in a year or two, you’re back at the top of this list, paying the recruiting and ramp costs again.

None of these numbers are a quote — they’re illustrative, and your actual costs will differ by role, location, and benefits package. But the pattern holds: a $45k hire is rarely a $45k decision. It’s closer to $55k-$60k in year one once you count the soft costs, and some of that repeats every year they’re on payroll. If you want the specific version of this math for your business, there’s a free ROI calculator on this site you can plug your own numbers into.

That’s not an argument against hiring. People are often the right answer — more on that below. It’s an argument for knowing the real number before you compare it to anything else.

What automation actually does

Automation isn’t a replacement for a person. It’s a replacement for the parts of a job that don’t need a person.

Most ops-heavy roles are a mix: maybe 60% repetitive, rule-based work (pulling data, updating a spreadsheet, sending a status email, formatting a report) and 40% judgment work (handling the weird case, dealing with an unhappy client, deciding what actually matters this week).

Automation goes after the 60%. Not to eliminate the role — to make the role worth having. If you do hire someone, they spend their time on the judgment calls, not the copy-paste. If you don’t hire, you (or your existing team) get that time back.

To be specific about where this comes from: my own hands-on experience with a live, ongoing automation is a content pipeline I built and run as a volunteer for a 200+ member church. It’s been unattended since early this year and takes me about an hour a month to babysit. That’s a volunteer project, not a paid engagement, and I’m not going to pretend otherwise. What it taught me is the same principle that shows up in the automation work from my engineering career: the boring, repetitive 60% is almost always separable from the judgment-heavy 40%, and separating it is where the leverage is.

I want to be direct about one thing: I will never build something whose purpose is to fire your people. If that’s the ask, I’m not the right person for it. The automations I build are meant to take the grind off someone’s plate — either so you don’t have to hire for it, or so the person you do hire has a better job.

The honest decision rule

Here’s the rule I’d actually use:

Automate the parts of the job that are repetitive and rule-based. If you could write the steps down as a checklist and any careful person could follow it without judgment calls, that’s an automation candidate — scheduling, data entry, reminders, report generation, status updates, moving information from one system to another.

Hire for judgment, relationships, and physical presence. If the job requires reading a room, negotiating, comforting an upset customer, making a call with incomplete information, or being physically somewhere — that’s a person’s job, and it should stay one.

Often it’s both. The most common outcome for a growing business isn’t “hire” or “automate” — it’s automate the grind first, see how much of the role is left, and then decide whether what remains is worth a hire, a part-time hire, or nothing at all. Sometimes automating the 60% means the remaining 40% fits inside hours you already have. Sometimes it doesn’t, and you still need to hire — just for a smaller, better-defined role.

When automation is NOT the answer yet

I’d be doing you a disservice if I didn’t flag this: automation isn’t always the right move, and a good answer here should cost you nothing.

• Too low volume. If the task happens five times a month, the time to build and maintain an automation may not pay back. Automation earns its keep on repetition.
• The process is still changing. If you’re two months into a new workflow and still figuring out the steps, automating it now means automating something you’re about to change anyway. Let it stabilize first.
• Nobody owns the process yet. Automation works best on a process someone already understands well enough to describe. If the steps live only in someone’s head and change based on mood, that’s a documentation problem before it’s an automation problem.

If any of those describe your situation, the honest answer is: wait, or hire, or both — not automate.

How to find out which one you need

You don’t have to guess at this alone, and you don’t have to figure out the categorization yourself. There’s also a short readiness self-audit on this site you can run through before we talk, just to get your own thinking organized.

I offer a free 20-minute call to look at what’s actually eating your time and figure out which bucket it falls into — automate, hire, or wait. If I can’t find at least 5 hours a week worth automating, I’ll tell you that directly. That’s the guarantee: an honest no is on the table, not just a pitch.

You’re running the business. The business shouldn’t be running you. Book the call and let’s figure out which fix actually fits.