Custom automation
vs. hiring an ops person

When a human is the right answer

Hire a person when the work is judgment: reading a tense client email and knowing whether to call or wait, negotiating with a supplier, deciding which of two bad options hurts less. Hire a person when the work is relationships, because nobody wants an automated account manager. And hire a person when your operation is still unstructured chaos, because you cannot automate a process that changes shape every week. A system encodes a process; if the process doesn’t exist yet, a good ops hire is how you find it.

When a system wins, clearly

A system wins when the work is repetitive data movement: orders re-typed from emails, leads copied between tools, reports assembled from the same four sources every Monday. Humans are expensive at this and bad at it, not because they lack skill but because attention decays on work that doesn’t deserve attention. A system runs the same logic every time, runs it at 3 a.m., never resigns, and never takes the process with it.

One of my clients, a US facilities-services company, had someone re-entering platform work orders into their field-service system daily. The work-order pipeline that replaced it parses the emails, produces the exact 28-column CSV their system requires, uploads via FTPS, and logs every order. Their founder’s words: it “will save my team days by the end of the year.” That role never had to be hired.

The cost math, without hand-waving

An ops hire in the US runs $70k+ a year in salary before benefits, payroll costs, and the weeks-to-months of onboarding before they’re productive. That number repeats every year, and if they leave, you pay the ramp-up again while the process sits in limbo. A custom system is a one-time build starting at $6,900 fixed scope, with an optional operator retainer from $2,900 a month if you want it run and extended for you. Full numbers are on my pricing page, because you shouldn’t have to book a call to do this math.

The hybrid truth nobody sells you

The honest framing isn’t “system instead of human.” It’s that a system makes the team you already have bigger, by taking the copy-paste hours off their plate and giving them back to work that needs a brain. Then, when you do hire, you hire for judgment and relationships from day one instead of burning a salary on data entry. Automate the repetitive layer first; hire above it. Every client I work with who did it in that order is glad they did.