Ask a room of business owners whether their automation was worth it and you'll hear the same answer: "definitely, it saves loads of time." Ask how much time, and the room goes quiet.
"It saves loads of time" is a feeling. Feelings don't survive budget meetings, and they can't tell you whether to automate the next process or fix this one. If you've invested in automation, you should be able to point at evidence. Here's how to gather it without turning your business into a spreadsheet exercise.
Every automation was bought to change something: fewer errors, faster turnaround, less chasing, more capacity without more headcount. Write that expected change down as the outcome, then capture the before. A fortnight of honest baseline (how long the task takes, how often it goes wrong, how long customers wait) is what turns your eventual answer from opinion into arithmetic. No baseline, no proof. It really is that unforgiving.
Labour time is the obvious measure and usually the least interesting. Look wider. Quality: error rates, corrections, complaints. Speed: how quickly the next action happens, especially the customer-facing ones. Visibility: can people see where work is without asking? Capacity: what did the team do with the freed hours? Risk: exceptions caught instead of buried. And morale: nobody resigns over interesting work, but plenty resign over retyping. If your best person stopped doing an hour of drudgery a day, that's value even before you price it.
One caution from experience: don't convert every saved minute into cash. Thirty seconds saved a hundred times a day isn't a hire avoided, and pretending it is undermines the genuinely strong numbers elsewhere in your case. Credible beats impressive.
The automated cases and the exception cases are two different populations, and averaging them hides the truth about both. Track the routine work's speed and the exception queue's size and age separately. A rising exception count isn't failure, it's information: the rules need tuning, or the process upstream has drifted. This is exactly the operational evidence that makes a system better over time, and it's why we build measurement into our automation work rather than bolting it on when someone asks awkward questions.
The honest ledger includes the build, the subscriptions, the maintenance and the occasional attention the workflow needs. And when you compare before and after, compare the same season and the same mix of work; measuring your quiet fortnight against last year's rush proves nothing except optimism.
Sometimes the numbers will tell you an automation wasn't worth it, or that the next candidate isn't. Believe them. Knowing when not to automate is half the skill, and it's a conclusion we're comfortable reaching out loud with clients.
If you started small, as we suggested in five low-risk automations, this is the other half of the method: pick one measurable workflow, baseline it, automate it, and let the evidence decide what happens next. That's how automation programmes compound, at businesses like Jones International and at ten-person firms alike. Evidence first, expansion second.
Want help building the measurement into your next automation, or auditing the last one? That's a conversation with numbers in it, and we like those.