Picture someone on your team. Every morning, she opens two different systems. She copies a number from one. She pastes it into the other. It takes about twenty minutes. She has done this every single working day for three years. Nobody has ever asked why.
This is not a story about a careless employee. It's the opposite. She does the task fast. She does it well. She probably doesn't even think about it anymore. That's exactly the problem. The task has become invisible.
Small business owners rarely notice tasks like this, because a skilled employee makes them disappear into the background. But invisible doesn't mean free. Twenty minutes a day, every working day, for three years, adds up to hundreds of hours spent moving one number from one screen to another.
The good news: you don't need to hunt down every repetitive task in your business. You need a simple way to spot the handful that are actually worth fixing first.
Why Repetitive Tasks Hide in Plain Sight
Repetitive work hides for a boring reason. It's normal. Nobody schedules a meeting to question something that already works. The invoice gets entered. The follow-up email gets sent. The report gets copied into the spreadsheet. As long as the output shows up on time, nobody stops to ask how much it costs to produce.
There's also a habit trap. Once a task becomes part of someone's routine, it stops looking like "work" and starts looking like "just how we do things here." A new employee might ask why a step exists. Everyone else has stopped asking.
And then there's ownership. A task usually belongs to one person. That person rarely complains, because complaining feels like saying they can't handle their job. So the twenty-minute task stays exactly as it is, quietly, for years.
None of this is anyone's fault. It's just what happens when a business grows without anyone stepping back to look at the full list of things people do by hand every day.
The Three-Question Test
You don't need a consultant or a fancy audit to find your best automation candidates. You need three questions, asked about any repetitive task in your business.
1. How often does it happen? Something done fifty times a day matters more than something done once a month, even if the monthly task takes longer per instance. Frequency multiplies everything else.
2. How long does it take? Add up the minutes per occurrence, then multiply by how often it happens. A five-minute task done twenty times a day is more than an hour, every single day, of someone's time.
3. How error-prone is it? This is the one people skip, and it's often the most important. Ask what happens when the task goes wrong. Does a customer get the wrong invoice? Does a shipment go to the wrong address? Does a number get entered incorrectly in your accounting? The cost of a mistake matters just as much as the time it takes.
A task that scores high on all three — happens constantly, eats real time, and causes real damage when it slips — is your best candidate. A task that happens rarely, takes two minutes, and causes no harm if it's wrong is probably fine to leave alone, even if it's tedious.
Write your repetitive tasks down. Score each one, even roughly, on these three questions. You'll usually find the answer jumps out at you. One or two tasks will clearly outscore everything else.
The Usual Suspects
Certain tasks show up in almost every business I talk to, regardless of the industry. Here's what to check first:
- Data re-entry. Typing the same customer information into a second system because two tools don't talk to each other. This happens constantly, it's boring, and it's where typos live.
- Manual follow-up emails. Sending the same reminder, confirmation, or "just checking in" message by hand, over and over, to different people.
- Copying information between two systems. Moving numbers from a point-of-sale system into a spreadsheet, or from an order form into an invoicing tool. This is almost always the same twenty-minute task from the opening of this article.
- Manual scheduling or reminder calls. Chasing appointments or deadlines by phone or by memory instead of letting a system do the chasing. I've written before about automating your business bookings if this one sounds familiar.
- Report assembly. Pulling numbers from three different places every week to build the same report, by hand, every time.
If any of these sound familiar, you already have a starting point. You don't need to search for hidden inefficiency. It's usually sitting in plain sight, done by someone who's too good at their job to complain about it.
A Concrete Example
Let's walk through one. A small accounting firm has someone who receives client receipts by email, prints a summary, and manually enters each line into their bookkeeping software. It takes about fifteen minutes per client, and they handle twelve clients a week.
Frequency: happens every week, for every client. High. Time: fifteen minutes times twelve clients is three hours a week, every week. Error risk: a mistyped number in a financial record isn't a small thing. It can mean a wrong tax filing or an upset client who has to be told their books were wrong.
That's three hours a week, times roughly fifty working weeks, which is around 150 hours a year, spent on a task where a small slip has real financial consequences. That combination — real time, real frequency, real risk — is exactly what the three-question test is designed to catch. Compare that to something like updating a "team birthdays" spreadsheet once a month. It's repetitive too, but it scores low on all three questions. Leave it alone for now.
Start With Just One
Here's where I see business owners get stuck. Once they start looking, they find a dozen tasks worth fixing, and the list feels overwhelming. So nothing happens.
Don't try to fix everything at once. Pick the single task that scored highest on frequency, time, and error risk, and fix that one first. A single win does two things: it frees up real hours you can measure, and it gives your team proof that this is worth doing again.
This is the same principle I talk about in why it's worth automating processes in general — the businesses that get the most value from automation are the ones that start small, learn from the first project, and build from there. You don't need a company-wide overhaul. You need one twenty-minute task, done every day, finally fixed.
If you'd like help figuring out which task on your team's list is actually worth automating first, I'm happy to walk through it with you.