Guide
Automate, delegate, or hire? A decision guide
A practical framework for deciding whether a task belongs with software, a person on your team, or a new hire.
“Should we automate this?” is usually the wrong first question. The better sequence: what exactly is the task, how often does it happen, and what does it cost when it’s done late or badly? Then the automate/delegate/hire answer mostly falls out on its own.
The three tests
1. Is it repeatable?
Automation eats repetition, not judgment. “Send every new lead a reply within five minutes and put them in the CRM” is repeatable. “Decide whether this client relationship is worth saving” is not. If you can’t describe the task as steps a reliable temp could follow on day one, it’s not an automation candidate yet — it’s a process definition candidate. (How to scope an automation project before you buy walks through exactly that.)
2. What’s the cost of the gap?
Most small businesses don’t lose money on tasks done wrong — they lose it on tasks done late or never: the lead nobody called back, the follow-up that slipped, the invoice sent three weeks after the job. Software’s superpower isn’t intelligence; it’s that it never gets busy. If the pain is dropped balls, automation wins. If the pain is hard calls, people win.
3. Does it need a relationship?
Anything where trust is the product — sales conversations, sensitive client issues, negotiations — belongs with a human, full stop. The right role for automation there is setup and follow-through: getting the meeting booked, the notes filed, the follow-up sent, so the human shows up prepared. That’s the pattern behind Booking automation that customers don’t hate.
The honest math
A part-time admin at $22/hour runs about $23,000 a year. A well-built automation handling intake, scheduling, and follow-up typically costs a few thousand to build and very little to run — and works nights, weekends, and the week everyone has the flu. But it only handles what it was built to handle. Real businesses usually land on a hybrid: automate the repetition, so the people you have can do the judgment work you actually hired them for.
A worksheet-sized version
For each task that eats your week, ask: (1) Could a temp do it from written steps? (2) Does it hurt more when it’s late than when it’s imperfect? (3) Is trust the product? Two yeses on the first two and a no on the third = automation candidate. Everything else = people.
If you’re not sure what an automated task even looks like in practice, start with What an “AI agent” actually is (and isn’t).
Found this useful?
It is one of many — the rest of the library is free to read too. Browse around, or send a note if you want to talk something through.
Browse the libraryor get in touch