Something's broken, so you hire someone to handle it.
Leads aren't getting followed up, so you hire a coordinator. Nobody's asking for reviews, so it goes on the new admin's list. The reporting takes all Sunday, so you bring in a part-timer.
Sometimes that's right. Often it's the most expensive way to avoid an afternoon of thinking, and it commits you to that expense forever.
Here's how to tell the difference before you post the job.
Run the real number first
A hire does not cost the salary. Write down the whole thing.
- Salary.
- Payroll taxes and benefits.
- The recruiting time, which is your time.
- The training time, which is also your time, and there's more of it than you think.
- The management time, which is forever. A person needs a manager. That's usually you.
- The three months of reduced output while they learn.
- The risk they leave in eighteen months and you do the whole thing again.
A $45,000 hire is, realistically, closer to $60,000 in year one once you count the taxes, the tools, and the hours you spend that you weren't spending before.
Now compare it to the thing you're avoiding.
A follow-up system that never drops a lead is a fixed cost, once, plus small maintenance. It doesn't call in sick, doesn't need onboarding, doesn't quit, and it does the task the same way at 11pm on a Saturday as it does on Monday morning. It also doesn't need you to manage it, which is the cost owners systematically forget.
The comparison is not "person vs. software." It's "one-time cost with small upkeep" vs. "recurring cost, forever, that grows with wages and needs your attention every week."
The test: is the work rules or judgment?
Here's the actual dividing line, and it isn't about cost at all.
Rules work has a right answer that you could write down. Send the follow-up on day three. Route the plumbing lead to Dave. Log the call. Send the invoice when the job closes. Ask for a review three hours after completion. Pull the numbers into a report every Monday.
Anyone can do this. That's the tell. If you could teach it to a competent teenager in a week, it doesn't need a salary, it needs a system. And the person you hire to do it will be bored, will do it inconsistently within two months, and will eventually leave, taking the process with them.
Judgment work requires a person deciding something that isn't in a rulebook. Handling an unhappy customer. Reading a room in a sales call. Deciding this job is worth doing at a loss because of who referred it. Training a new tech. Noticing something is off before anyone can say what.
That's what people are for, and you should hire aggressively for it, because it's where humans are irreplaceable and where automation is actively harmful.
Now go look at the job description you were about to post. What percentage is rules work?
If it's 80% rules and 20% judgment, you're about to hire a person to be a slow, expensive, unhappy computer, and give them 20% of a real job.
The move that actually works
Build the system for the rules part. Then hire someone into the judgment part, and hire better, because now you can afford it.
Watch what happens to the job description.
Before: "Admin assistant. Answer phones, log leads, send follow-ups, chase quotes, request reviews, prepare the weekly report, handle customer questions." $40k, hard to fill, boring, high turnover.
After the systems are in: "Customer manager. You own our relationship with every customer. The routine communication runs itself. Your job is the hard conversations, the saves, the upsells, and the customers who need a human." $55k, easy to fill, someone good actually wants it, and they stay.
Same money, roughly. Wildly different outcome. And the second person is a genuine asset, while the first was a fragile, expensive patch over a process problem.
That's the real argument for automation in a small business. Not that it replaces people. It makes the people you hire worth hiring.
The three signs you're hiring to avoid a system
One: you're describing the job in verbs a computer could do. Enter. Send. Track. Remind. Compile. Copy. If the verbs are all mechanical, that's a system.
Two: the role exists because of a tool gap. "We need someone to move information from the phone system into the CRM." That is not a job. That is an integration you didn't build, and you're about to pay someone $40,000 a year to be a data cable.
Three: you can't say what "great" looks like. If the best possible version of this person just does the same tasks with fewer mistakes, there's no ceiling on the role and no reason for anyone good to take it. Great people need judgment work or they leave.
When to hire, no argument
Hire when:
- You need capacity, not consistency. More jobs need more hands. No system installs an HVAC unit.
- The work is genuinely relational. Sales, retention, the awkward conversations, the customers who need to feel known.
- The process isn't settled. If it changes every month, a person adapts and a system needs rebuilding. Get the person, let them do it manually, and let the stable version of the process emerge. Then automate what's stopped changing.
- The judgment is the value. Estimating, diagnosing, teaching, deciding.
And hire when a system genuinely can't do it, which is more often than the AI people admit and less often than owners assume.
The order that saves you money
If I had to write it as a rule:
Systematize the rules work first. Then hire for judgment, at a level you couldn't previously afford, into a role that's actually worth doing.
Doing it in the other order is how small businesses end up with five people who are all 70% busy doing things a computer should be doing, an owner who can't take a week off, and a payroll number that terrifies them.
The systems are the cheaper half of this and nobody starts there, because hiring feels like growth and building feels like a project. But payroll is the biggest number on your P&L and it's the one that never goes back down.
Before you post the job: take the job description, and put a check next to every line a system could do. If most of it's checked, you've got a build to do, and a much better hire waiting for you on the other side.
If you want help drawing that line, that's the sort of thing I get called in for. Send me the job description you were about to post and I'll tell you honestly which half is a system. Here's how to reach me.