← Back to Insights
Automation

Which tasks should a small business automate first?

There's a task somewhere in your week you could do with your eyes shut. Copying the details off an order confirmation, field by field, into the system where they belong. It repeats, it never changes, and it eats the same twenty minutes it always did. That kind of job, dull and predictable, is almost always where automation should start. Still, the question I get in nearly every first conversation is "where do we begin?". Fair enough: the moment you realise work can be automated, everything suddenly looks like a candidate. But not every task is worth it, and only a small handful pay you back within weeks.

Start with whatever repeats every week

The best first automation is boring. It's the task someone does every Monday morning, the exact same way, with no judgement call involved. Creating invoices once a project wraps. Retyping order details from email into your system. Building that same monthly report from scratch.

Three things make a task a good fit, and the more of them are true, the stronger the case. Tick the ones that apply to a task you have in mind:

Tick what's true for your task.

Lead follow-up is almost always top of the list

If customers reach you through enquiries, this is usually the first one I recommend. Not because it's the easiest to build, but because it touches revenue directly.

An enquiry that lands at nine in the evening and gets picked up the next morning is often already a lost one. The customer has knocked on two other doors by then. A system that confirms, qualifies and proposes a time within minutes wins those customers back. That difference shows up in the numbers.

What to leave alone for now

Not everything makes a good starting point. Tasks full of exceptions, or that need a human judgement every single time, cost more to automate than they return. Don't start there. Build the boring, predictable things first, then use the time you free up to tackle the harder ones later.

Start here
  • Invoices the moment a project closes
  • Retyping order details into your system
  • The same monthly report, built from scratch
  • Confirming and following up new enquiries
Leave for later
  • Tasks full of exceptions
  • Work that needs a real judgement call every time
  • One-offs you only do once a quarter

Boring and predictable pays back first. The judgement-heavy work can wait.

How to map it out

Track for a week where your team's time goes. Not down to the minute, just roughly. Which tasks keep coming back? Which of those follow fixed steps? List them, estimate the hours each one eats per month, and the order sorts itself out.

Pick the one task at the top of that list and time it properly next week, start to finish. That single number usually tells you whether it's worth automating. An Automation Scan goes deeper and hands you a written plan, but the timing you can start today.

New to all this? It helps to know what AI can and can't do before you pick a tool for the job.