Most automation disappointment starts in the same place: a task was chosen because it was annoying, not because it was expensive. Annoyance and cost are different measurements, and only one of them shows up at the end of the quarter.
Count the repetitions before you count the minutes A task that takes fifteen minutes once a month is worth three hours a year. A ninety-second copy-and-paste that happens forty times a day is worth roughly a hundred and fifty hours. Teams almost always nominate the first kind of task, because it is memorable, and overlook the second, because it has become invisible. Start any automation review by counting frequency first and duration second.
Look for work that moves data sideways The clearest wins are the steps where a person acts as a courier between two systems: reading an enquiry in an inbox and typing it into a spreadsheet, copying an order reference into an accounting tool, re-keying a form response into a CRM. Nothing is being decided in these moments. A rule can carry the same field from one place to another without judgement, and without the transcription errors that come with typing at speed.
Watch for the waiting, not just the doing Some of the largest time losses are not tasks at all. A quote sits unsent because nobody noticed the form arrived. A customer waits two days for a reply that would have taken two minutes. Automated notification and routing removes delay rather than effort, and delay is often the part the customer actually feels.
Be honest about the tasks that resist automation Work that requires a judgement call, an exception, or a conversation with a person who is upset does not automate well. It can be supported — with a draft, a summary, a suggested next step — but a rule that has to guess will create rework that costs more than the original task. Automating the routine ninety percent and routing the remaining ten percent to a person is usually the better structure.
Measure the same thing before and after Pick one number before you build: enquiries handled per day, hours spent on month-end, time from form submission to first reply. Without a baseline, every automation feels successful and none of them can be defended when someone asks what it was worth.
A short review beats a long roadmap Two hours spent listing the ten most repeated actions in a team, with rough frequencies beside them, will usually identify more genuine value than a transformation plan. Build the top one, measure it, then decide whether the second is still the right one.
Our business automation work starts with exactly that list. If you want a second pair of eyes on where your time is actually going, contact us and describe the steps your team repeats most often.
AI Studio · Published 12 Jan 2026
← All insights