When an automation frees up a person's time, that time goes to one of three places: it becomes margin, it becomes capacity, or it dissolves into the day. Only the first two are decisions. The third is what happens when nobody makes one, and it is the most common outcome.

Most automation proposals are built on hours saved. Eight hours a week on invoicing, five on reporting, a day on onboarding. The numbers are real. What the proposal rarely says is who gets the hours back, and the people who used to spend them are listening for the answer.

Margin

The first destination is the business's bottom line. The same work is done with fewer paid hours, so the cost of doing it falls. This is the answer a nervous team hears first, because it is the one with consequences for them, and it is sometimes the right one. A business that cannot afford its current headcount is not helped by pretending otherwise.

If this is the plan, it should be said plainly, with the timescale and what it means for roles. Silence will be read as the worst version of it. A team that suspects the hours are heading for the margin and has been told nothing will, reasonably, resist the automation.

Capacity

The second destination is more work. The same people take on what they never had time for: following up the quotes that went quiet, calling the customers who have not been in touch for a year, doing the thing the owner has been meaning to do since January. This is usually the better answer commercially, and it is the one clients prefer to give.

It only works if the work exists and somebody owns it. "More time for the important things" is not a plan. A named task, with a named person and a first date, is. Without it, capacity turns into the third destination.

Dissolve

The third destination is nowhere. The hours come back in ten-minute pieces across a week, nobody is quite sure where, and the day fills with what it always filled with. The automation worked, the saving was real, and it cannot be found afterwards because it was never attached to anything.

This is not a failure of the team. A freed hour has no shape, and work expands into whatever space there is. The only protection is deciding in advance what the hour is for.

Say it before the build

The conversation to have is short. Before the workflow goes live, the owner tells the people whose time it frees where the hours are going, in plain words, with one example of what the freed time will be used for. It takes ten minutes. Without it, the team fills the silence themselves, and what they fill it with is rarely kind.

It also changes what you learn. A team that knows its freed hours will go to something they care about will tell you which tasks to take. A team that fears the margin will hide them.

What to measure

Count the hours saved, but also count where they went. Three months after go-live, ask the person whose job changed what they do now that they did not do before. If the answer is a specific thing, the automation has created capacity. If the answer is a shrug, the hours dissolved, and the case for the automation is weaker than the spreadsheet says.

Be honest in the review about which of the three it turned out to be. A client who sees you report that a saving did not turn into anything will trust the next one you report.

The question to leave with the owner

Do not ask the owner whether the automation will save time. It will. Ask what they would do with an extra day a week, and whether they have told the people who are about to get it. The answer decides whether the work was worth doing, and it is a conversation only a person can have.