Measure automation savings honestly, not hopefully

When a business owner asks how much time an automation will save, the answer is usually: less than you think, but still worth doing.

Most teams overestimate. They imagine the entire task disappearing. In reality, automation removes the repetitive parts—and adds new work in its place. Someone has to review the results, handle exceptions, fix mistakes, and keep the system running. The real saving is the difference between the old time and the new time, not the old time and zero.

The honest math

Let's say an accounting firm in Burnaby spends 6 hours a week entering invoice data into their accounting software by hand. They type the vendor name, the amount, the date, the account code. It's rule-based work. It's repetitive. It's a candidate for automation.

If they automate it, what happens next?

The automation reads the invoice, extracts the data, and files it. But someone still needs to:

• Check 10 to 20 percent of the invoices for accuracy (vendors get misread, amounts get scrambled)
• Handle the invoices that don't fit the pattern (a one-off vendor, an unusual format, a handwritten note)
• Fix the automation when it breaks (a new vendor uses a different layout; the software updates and the connection fails)
• Review the monthly report to catch systemic errors

That overhead usually takes 1 to 2 hours a week. So the firm saves 4 to 5 hours a week, not 6. That's still real—it's a full working day—but it's not the whole task.

A 12-person software company in Gastown might automate customer onboarding emails. Right now, someone spends 3 hours a week writing and sending personalized welcome messages. After automation, those emails go out on a schedule, but someone still reads replies, answers questions that the template didn't cover, and updates the email if the process changes. Real saving: 1.5 to 2 hours a week.

A property manager in Surrey automates tenant follow-up calls—or rather, the scheduling and reminders around them. The actual phone call still happens, and still takes the same time. But the manager saves 2 to 3 hours a week on calendar juggling and reminder emails.

How to measure it yourself

Don't guess. Time the work.

Pick the task you want to automate. For two full weeks, track how long it actually takes. Write it down: Monday 45 minutes, Wednesday 1 hour 20 minutes, Friday 2 hours. Add it up.

That's your baseline.

After the automation is live and stable—usually 4 to 6 weeks in—time it again for two weeks. Count everything: the time spent on the task itself, plus the time spent managing the automation, reviewing results, and fixing errors.

The difference is your real saving.

Be strict about this. A dental clinic in Kelowna automated appointment reminders. The receptionist thought it would save 4 hours a week. When they actually timed it, they found that checking the reminder logs, handling bounced messages, and calling patients who didn't get the text took 1.5 hours a week. Real saving: 2.5 hours. Still worthwhile, but different from the original hope.

When the saving is too small

Sometimes the honest answer is: don't automate this yet.

If a task takes 2 hours a week and automation saves 1 hour, you've freed up a couple of afternoons a month. That's nice, but it might not justify the time to set up the automation or the cost of maintaining it.

A plumber in Richmond looked at automating job scheduling. The job took 4 hours a week, but it also involved talking to customers about their needs, handling cancellations, and making sure the right person was sent to the right job. Automation would have saved maybe 1 hour—mostly data entry—and would have made the scheduling less flexible. They decided to hire a part-time office person instead.

A distributor in Calgary wanted to automate purchase order entry. The process took 6 hours a week, but it also involved checking inventory levels, negotiating with suppliers, and making judgment calls about when to order. Automation would have saved 2 hours. They did it, but they kept a person in the loop for the judgment calls.

The work that's worth automating

Automation is worth doing when:

• The task is repetitive and follows a clear pattern (data entry, file sorting, sending standard messages)
• The saving is at least 3 hours a week
• The task doesn't require judgment or relationships
• You can afford 4 to 6 weeks to set it up
• Someone will check the work

When these conditions are met, you usually see 3 to 8 hours a week of real time saved. That's meaningful. It's a day a week you get back.

Where to start

• List five tasks your team does every week that feel repetitive. Time one of them for two weeks. Write down the hours.
• Ask your team: "If we freed up 3 to 5 hours a week on this task, what would you do instead?" If the answer is valuable, the automation is worth exploring.
• Talk to one other business owner in your field who has automated something similar. Ask them the real number of hours they saved, not the number they hoped to save.