Every growing business reaches a point where something isn't getting done, and the decision is: hire someone or automate it. It is easy to get this call wrong in either direction.
Some automate things that genuinely need judgment and end up with a system that produces work nobody trusts. Some hire for things that could be automated, then hire again when that person drowns in the same repetitive work.
The questions that actually help
Does this work require accountable judgment? If the task involves a high-impact decision, an ambiguous complaint, or a situation outside the norm, automation can gather context and suggest next steps. An authorized person should still own the decision and its consequences.
Is it the same or essentially the same every time? Data entry, format conversion, moving information between systems, sending the same type of message on a defined trigger, these are automation candidates. Low variation, clear rules.
How often does it happen? For example, a task performed twice a month has a different business case from one performed 50 times a day. Frequency matters, but so do handling time, error cost, risk, and the useful life of the workflow.
How stable are the rules? Some processes don't change for years. Others shift quarterly as the business evolves. Automations built on stable processes have long useful lives. Those built on frequently changing rules require ongoing maintenance that can exceed the initial build cost.
A practical way to combine them
Most job descriptions contain both types of work. The customer service rep who handles complex inquiries also processes routine refund requests. The admin who does meaningful project coordination also copies data between spreadsheets.
A practical option is to automate the mechanical part of an existing role while keeping people focused on exceptions, relationships, and accountable decisions.
When a role is dominated by repeatable work that grows directly with volume, redesign the workflow before assuming the answer is another hire or full replacement. Compare automation cost, exception handling, service quality, risk, and the human work that remains before committing.
Build notes: put numbers on both options
A hire-or-automate choice is easier with a simple comparison. For the task in question, estimate hours per week now, the cost of an hour of the person who does it, and the rate of errors or delays. Then estimate the cost of each path: a hire's salary, benefits and ramp time, versus the build cost, monthly tool fees and the maintenance time of an automation.
Test whether the task suits automation. It should be repeatable, with clear rules and data that is already in a system. If the work depends on reading a situation, handling upset clients or making exceptions, a person is better and automation should only prepare their work.
Consider the mixed answer. Many roles are half repeatable work and half judgment. Automating the repeatable half can turn a new hire into a smaller part-time role or free an existing person for the judgment work. Whichever you choose, set a review date, such as three months, and compare results against your starting estimate. If the hire or the automation is not paying off by then, adjust early instead of waiting for the annual budget.
