Automation ROI: how to decide what to automate first

“It only takes ten minutes”

That is the sentence behind most wasted hours in small businesses. Ten minutes feels like nothing. Do it 25 times a week and it is more than 200 hours a year. Nobody notices, because it never arrives as one big block of time.

The fix starts with counting, not building. Most people skip that step and automate whatever annoys them most, which is not always what costs the most.

The formula

Hours a year = minutes × times per week × 52 ÷ 60. Multiply by what an hour of your time costs, and you get the yearly cost of the task.

Here is a worked example with three tasks (example numbers, and an hour valued at €30, which is your own figure to change):

The invoices feel annoying but come last. The lead copying looks small but comes first. Ranked by the number, the first task to automate is the lead copying.

How to build your list

You cannot rank what you have not written down. For one week, keep a simple note. Every time you do something that feels repetitive, write the task, how long it took and how often it comes up. Ask each person on the team to do the same, because the tasks that eat the most time are often the ones the owner never sees. At the end of the week you will have ten to twenty rows, and several will surprise you.

What makes a good first task

• It happens often. Frequency is what turns minutes into hours.
• The steps are the same every time. If you can write them as a checklist, a machine can follow them.
• The input and the result are clear. You know what goes in and what should come out.
• A mistake is cheap to fix. Start where an error costs you a minute, not a client.

A bad first task is the opposite. It is rare, it needs judgement, the steps change each time, or nobody agrees what “done” looks like. Build there and you spend weeks on something that saves little.

Automation is a ladder, not a leap

People hear “automate” and picture custom software. Most of the time the right answer is lower down. From cheapest to most expensive:

• Delete it. Some tasks exist because nobody asked whether anyone reads the result.
• Template it. A saved reply, a report layout or a checklist removes much of the thinking.
• Use a rule in a tool you already have. Most email, forms and CRM tools can move data between them with no code.
• Connect two tools. An integration that passes new leads from a form to a sheet or CRM.
• Build it. Only when the task is frequent, the steps are fixed and nothing off the shelf fits.

Start at the top of that list and stop as soon as the task stops hurting.

SOP first, automation second

Before you automate anything, write the steps down. Who does what, in which order, with what. Two things happen. You find steps you can simply delete. And you find out whether the task is the same every time, which decides whether it can be automated at all.

A real example, with a caveat: at T&V Advertising, a creative agency, project delivery became 35% faster after we wrote SOPs and standardised the project phases. That took two months and it was documents and templates, not software. The T&V Advertising case study has the detail and how we measure says what the figure counts. It does not mean you will get 35%. It does show that writing things down can pay before any code exists. The one SOP that saves small teams 10+ hours a week is a good place to start.

Measure it after

When you have automated something, count again. After a month, compare the minutes the task takes now with the figure you started from. If you saved less than you expected, find out why. Perhaps someone still does the old steps by hand, or the exceptions take more time than you thought. Also decide who owns the automation. Things that run quietly in the background break quietly too, and someone needs to notice. A short note describing what it does and what to check when it stops is enough.

Compare the yearly figure with the cost to build

Now you have a number. If the lead copying costs €6,500 a year in time and a build would cost €1,500 (example), it pays for itself in under three months. If the build costs €8,000, it takes more than a year, and a simpler fix may be better. Remember that automations need looking after too, so add something for that.

If your top task is chasing slow replies to new leads, what a slow reply costs you puts a price on it. Sometimes the answer is a tool you can already subscribe to. Sometimes it is a small custom build. When custom software beats another subscription gives a plain checklist for choosing.

Questions

What should I automate first?

The task at the top of your ranked list, which usually means the one that happens most often with the same steps every time. Count the hours first, because the task that annoys you most is not always the one that costs you most.

How do I work out the time an automation saves?

Multiply the minutes one run takes by how many times a week it happens, then by 52, then divide by 60. That gives hours a year. Multiply by your hourly cost to get the yearly figure. The hourly cost is your own estimate.

Is it worth automating a 10-minute task I do once a week?

On its own, usually not. Ten minutes once a week is under nine hours a year. It becomes worth it if mistakes are costly or if the task blocks something else.

Want us to look at your numbers?

Writing SOPs and building automations is a paid service, but the first step is free. In 30 minutes we go through your task list together and I tell you honestly what I would do first.

Book a free 30-minute call. I look at your numbers first, and within 48 hours you get a written audit, yours to keep. No card, no contract.