Where did your AI time savings go?

Statistics Canada reports 19.2% of businesses used AI to produce goods or deliver services in the year to spring 2026, triple the 2024 share. So here’s the question I’d put to any owner counting on AI time savings. Where did the saved hours actually go? If nobody named a home for them before the tool rolled out, I’d bet the week spent them for you.

The pitch was a simple trade. The tool takes the slow work, your team gets hours back and the firm comes out ahead. The slow work really did get faster, at a lot of firms at once, and most of them are left with the same question about the month.

Sit with the clearest AI win in your firm for a second. A report that took an afternoon now takes an hour. First drafts move faster too, because your clients are prompting the first draft themselves and your team starts from something instead of a blank page. The saving is real at the task. Then look at the month around the task. The same people end the same weeks as full as before, and nobody can point at what the freed time built. Picture a property manager in Cochrane, as an example, whose monthly owner reports now take a morning instead of two days. Ask where the rest of those two days went and the honest answer is usually the inbox.

Where do freed hours actually go?

They go to the three places unnamed time always goes. Some get pocketed, and I mean that without blame. The job that took an hour now takes twenty minutes, and the other forty dissolve into the day in pieces too small to notice.

Some get spread thin, two minutes here and five there across ten tasks, savings that never stand in one pile long enough to hold a new job. The rest get eaten, because work expands into open room. The hour the report used to take becomes two more meetings about the report.

Time you do not assign does not sit waiting. The week assigns it for you.

Nobody wastes the saving on purpose. Unassigned time flows downhill into whatever already had a claim on the day. The inbox had a claim. The meeting load had a claim. The work you wanted the hours for had no claim written down, so it got served last, which is to say not at all.

Why does the month still look the same?

Because a saving only shows up where it lands. Ten minutes back on a task is a fact about the task.

It becomes a fact about the firm only when the minutes stack into something with a name: the follow-up calls that used to slide, the backlog that used to grow, the client who used to wait three days and now waits one. If the stack never forms, the month reads like the month before it, and the owner ends up defending a purchase with a feeling.

An hour saved in ten places is not an hour anywhere until somebody gathers it.

The tool hands time back one small refund at a time. Turning refunds into results is a separate job, and it belongs to the owner. Firms that skip it get faster tasks and the same month, then blame the tool for a capture problem it was never going to solve.

What changes when the hours have a named home?

The saving stops dissolving, because the person who gets the time back knows it is already spoken for. The report writer who gains two hours on a Tuesday knows those hours belong to the follow-up list, so the list is where Tuesday afternoon goes.

The tool does not change at all. It was never the missing piece. The missing piece was one decision, made in writing, before the rollout, about where freed time goes when it shows up. If I could make only one rule for an AI rollout, it would be that one.

Name the home before the tool arrives, or the week will name one for you.

A named home also settles the renewal argument owners have with themselves. You stop asking if the tool feels worth it and look at the landing spot instead. The calls got made or they did not. The backlog shrank or it did not. That is a plain thing to look at, and the next buying decision gets firmer ground than a memory of the demo.

How do you pick the landing spot?

Pick work that is valuable, waiting, and easy to see. The old leads nobody called back. The proposals that went out rough because the polish hour never existed, and polish matters because clients pay for the finished job, not the fast draft.

The client check-ins that only happen when something breaks. Choose one home per workflow, and write it in one sentence the person doing the work can repeat back to you. One home I’d put high on the list is bidding the job your crew used to pass on.

One named home beats five good intentions every week of the year.

Keep the home small enough to be honest. A wish to grow the business never collects a single hour. A sentence like this one does: the two hours from the Tuesday report go to the follow-up list until it is clear. When it is clear, name the next home.

Where should your freed hours go starting Monday?

Take one workflow where the tool already gives time back. Write down where its freed hours go starting Monday, in one sentence, with the job and the owner named. Say it out loud to the person who owns that workflow, so the hours have a witness besides a note in a file.

Then put a date thirty days out and look once, with one plain question: did the hours land where we sent them?

If they landed, name the home for the next workflow before its rollout, not after. If they dissolved again, the home was too vague, so name a smaller one and run the month again.

Saved time keeps only where somebody is waiting for it.

Choosing where freed time lands, across the whole firm, is part of every AI Strategy Roadmap I write.

Common questions about AI time savings

Name one home for this week’s freed hours. If you want more checks like it, they’re in the AI Newsletter with ZAK every week.