Automation

Where to start with business automation: a practical map

Czytaj po polsku: wersja polska

The most common automation mistake isn’t picking the wrong tool. It’s starting with a tool at all. Someone reads about AI, buys a subscription, and goes looking for something to automate. Six weeks later there’s a half-built workflow nobody trusts and a renewal nobody wants to pay.

Automation that sticks runs the other way round. You start from where the business actually hurts, automate the single most painful repetitive task, prove it saved real hours, and only then do the next one. Here’s the map.

Step 1 — Find the repetitive, rules-based, frequent tasks

Good automation candidates share three traits:

  • Repetitive — the same shape every time.
  • Rules-based — you could write down how you decide, even if you never have.
  • Frequent — it happens often enough that small savings compound.

A weekly invoice-to-project match qualifies. A once-a-year strategic decision does not. When in doubt, follow the groans: the task your team complains about every week is usually the one.

Step 2 — Score them honestly

For each candidate, ask two questions and nothing more:

  1. How many hours a month does it eat? (frequency × time per instance)
  2. How painful is it to change? (does it touch money, compliance, or customers directly?)

Plot them. The first thing you automate should be high hours, low risk — boring, frequent, internal. Not the customer-facing, money-moving process that feels important. Earn trust on something safe first.

The biggest wins are almost never glamorous. They’re the quiet, repetitive admin tasks that quietly eat a day a week.

Step 3 — Automate the wrapper before the judgement

Most tasks are 80% mechanical wrapper and 20% human judgement. Automate the wrapper:

  • The data entry, copying, formatting, and routing — automate fully.
  • The decision in the middle — keep a human in the loop, at least at first.

This is also how you keep quality. The system does the tedious 80%; your expert reviews the 20% that actually needs a brain. Over time, as you watch where the human always decides the same way, more of it becomes a rule.

Step 4 — Measure in hours, not vibes

Before you build, write down the current cost: “This eats roughly 6 hours a week across two people.” After two weeks live, measure again. If you can’t point to recovered hours or recovered revenue, you automated the wrong thing — kill it and move on. No sunk-cost loyalty.

Step 5 — Then, and only then, scale

Once one automation is trusted and measured, the next is easy: you’ve built the habit, the team believes it, and you know what “good” looks like. Most businesses that try to automate ten things at once finish none. The ones that compound do exactly one thing at a time.

A 30-minute exercise to do today

  1. List every task your team does at least weekly.
  2. Mark each as high/low hours and high/low risk.
  3. Circle the highest-hours, lowest-risk task.
  4. That’s your first automation. Everything else waits.

You don’t need a platform, a data team, or a transformation programme. You need one painful, boring, frequent task — and the discipline to fix only that before reaching for the next.