Skip to content

What to Automate First, and What to Leave Alone

The short answer

Automate the tasks that are repetitive, rule-based, and high-volume, starting with whichever costs the most in wasted time. Outsource or hire for work that needs a skill you don't have in-house. Leave alone anything that genuinely depends on judgment, or exists as a deliberate check rather than a chore. Getting this choice wrong in either direction, automating a control or leaving an obvious repetitive task manual, both carry a real cost.

27 Sept 20265 min read

What should you automate first?

Which is worth automating first: the thirty-second approval done two hundred times a month, or the hour-long report done once? Most people's gut says the report, because it hurts more each time it comes around. The maths says otherwise, and the maths is right.

Automate first whatever scores highest once you multiply how often a task happens by how long it genuinely takes, not by which one gets complained about most. Past that ranking, a few extra filters narrow it further: the task should be rule-based rather than judgment-based, and it should already sit inside a process that's been mapped and is reasonably well understood, not a process still full of unexplained steps.

Automation vs. outsourcing vs. hiring: how to choose

Automation isn't the only option for a task that's costing you time, and it isn't always the right one.

FactorAutomateOutsourceHire
Best fitRepetitive, rule-based, high-volumeNeeds a skill your team lacks, not often enough to justify a hireOngoing, judgment-heavy, core to the business
Upfront costSetup time and toolingUsually low, pay-as-you-goRecruiting, onboarding, salary
Ongoing costMaintenance as the process changesPer-project or retainer feesOngoing salary, regardless of volume
Risk if wrongLocks in a bad process, or removes a needed judgment callDependency on an external party's quality and availabilityCost persists even if the volume of work drops

Most growing businesses end up using all three, automation for the rule-based volume work, outsourcing for occasional specialist needs, hiring for judgment-heavy, ongoing responsibility. The mistake is defaulting to one option for everything.

AI shifts this comparison in one specific way. A task that used to sit in the "outsource, because the input's too messy for simple rules" column sometimes moves into "automate" once AI can handle the messy part. Re-check anything you've previously written off as unautomatable. That verdict isn't permanent.

When automation isn't worth the investment

A few honest signals that automation is the wrong call, at least for now:

  • The task is low-volume. If it happens a handful of times a year, the setup and maintenance cost rarely earns itself back.
  • The rules keep changing. A process that's redesigned or reprioritised every few weeks is expensive to keep automated, since every change means updating the automation too.
  • The judgment call is the point. If the value of the task is a person weighing up context a rule can't capture, automating it removes the thing that made it worth doing well.
  • It's a control, not a chore. A deliberate check that exists to catch a costly mistake is protecting something. Automating it away because it "feels slow" can quietly remove the protection along with the friction.

How much automation does a small business actually need?

Enough to remove the specific tasks that are genuinely costing time, money, or accuracy, and not more than that. It's tempting to treat automation as a general modernisation project once the first one or two wins land, but automation for its own sake tends to produce a pile of disconnected tools rather than a meaningfully more efficient business. A useful check: can you name the specific cost each automation is removing? If not, it's worth pausing before adding another one.

A simple decision sequence

If you want one path to walk through rather than four separate criteria, this is the order that matters:

  1. Does it happen often enough to matter? If it's a handful of times a year, stop here, leave it alone regardless of what else is true.
  2. Can the decision be written down as a rule? If not, it needs a person, whether that's someone already on your team, a new hire, or an outsourced specialist.
  3. Is it a control, not a chore? If the step exists to catch a costly mistake, keep the judgment with a person, even if the paperwork around it gets automated.
  4. Do you have the skill in-house, and is it frequent enough to justify a hire? If you have it, automate it or keep doing it manually. If you don't and it's frequent, hire. If you don't and it's occasional, outsource.

Most tasks get filtered out well before step 4, which is the point: the sequence is designed to stop you early, rather than talk you into automating everything that's left standing.

Where the usual answer falls short

A control that looks slow isn't the same as a control that's wrong

A second signature before a large payment goes out, a manual check before a shipment leaves, an approval that exists because a mistake was expensive once: these can look exactly like the repetitive, rule-based busywork worth automating. The difference is what the step is actually protecting. Automating the paperwork around a control (routing it faster, reminding people it's overdue) is usually safe. Automating away the human judgment inside the control is a different decision, and it deserves to be made on purpose, not as a side effect of a speed project.

Key takeaways

  • Rank automation candidates by frequency times time cost, not by which task gets complained about most.
  • Automate rule-based, high-volume work; outsource occasional specialist needs; hire for ongoing, judgment-heavy responsibility.
  • Low volume, frequently changing rules, and genuine judgment calls are all signs automation isn't worth it yet.
  • Before automating an approval or check, work out whether it's friction to remove or a control to keep.
  • When in doubt, work through it in order: frequency, then rule-ability, then whether it's a control, then whether you have the skill in-house.

Getting the automate/leave-alone split right

If the comparison above points to automation, the real work is still ahead: deciding exactly which parts of the task to automate and which to leave with a person, especially anywhere a step turns out to be a control rather than a chore. Get that distinction right before anything gets built, not after.

Common mistakes

Mistake

Automating the easiest integration instead of the highest-value task

Fix

A task is tempting to automate when the systems involved happen to connect easily, whether or not it's the task actually costing you the most. Let the ranking from how to identify automation opportunities decide what's first, not which connection happens to be simplest to build.

Mistake

Treating a "not worth it yet" decision as permanent

Fix

A task that doesn't justify automating at five staff or fifty transactions a month can easily justify it at twenty staff or five hundred. Revisit the decision as volume changes, rather than assuming today's verdict holds forever.

Find out which parts stay with a person, before you build anything

If your task lands in the automate column, bring it to a free discovery call with our Principal Consultant. You'll leave knowing exactly which of its steps are safe to automate and which are a control worth keeping, before any money gets spent. The decision stays yours.

Book a free discovery call

Frequently asked questions

Should a small business automate, outsource, or hire for a repetitive task?

Automate if the task is rule-based and high-volume enough to justify the setup. Outsource if it needs a skill your team doesn't have and won't need often enough to hire for. Hire if the work is ongoing, needs judgment, and is core enough to the business to want someone accountable for it directly.

When is automation not worth the investment?

When the task is low-volume, when it changes too often for a fixed rule to keep up, or when the setup and maintenance cost is close to or higher than the manual cost it's replacing. A task done a handful of times a year rarely earns back the time spent automating it.

How much automation does a small business actually need?

Enough to remove the specific repetitive tasks that are genuinely costing time or causing errors, and no more than that. Automating for its own sake tends to produce a pile of disconnected tools rather than a meaningfully more efficient business.

Can a task be too important to automate?

Yes, when the value of the task comes specifically from a person exercising judgment or from a deliberate control, not from the mechanical steps around it. Automate the paperwork around a control if that helps; leave the judgment itself with a person.