Automation

How many hours are you really losing? Count before you spend a euro

An owner-manager calls me, decided: he wants to "put AI everywhere" in his business. He's read things, he senses he's losing time, he wants to act. My first answer always surprises him: before spending a single euro, we're going to count. Not guess by feel, actually count. Because "I'm losing masses of time" isn't a figure you can decide anything from. "I spend 14 hours a week on tasks a machine could prepare", now that's one.

Most owner-managers know they're losing time, but couldn't say how much, or on exactly what. That's normal: these tasks are scattered through the day, a quarter of an hour here, ten minutes there, never one visible block. And until they're written down in black and white, you can neither prioritise them nor judge whether a tool is worth its price. Counting first is what turns a vague hunch into a solid decision.

The notebook week: the only method that works

What I asked him to do, and what you can do from tomorrow, fits in one sentence. For a week, keep a note on your phone, and for every repetitive task that takes more than ten minutes, write down two things: what, and how long. Typing a quote, re-entering an invoice, chasing a customer, answering the same question for the thirtieth time, copying figures from one tool to another. Just the task and the duration. Nothing else.

After seven days, the list speaks for itself. Two or three lines come up every day and carry the most weight. These are your candidates, and they're almost never the ones you'd have named from memory.

14h / week

Once counted, this owner-manager's repetitive tasks weighed fourteen hours a week. Nearly two working days, invisible until you add them up. You don't fight an impression, you fight a figure.

The slip-up the count avoided: not automating

Here's the most useful result of the exercise, and the most counter-intuitive coming from someone who installs automation. One of the tasks this owner-manager complained about most, the one that annoyed him so much it triggered his call, actually only came up once or twice a month. It was tiresome, but rare. Counting it showed that automating that particular thing would have cost more than the time it saved. We left it alone. Conversely, a small task he didn't even mention, it seemed so trivial, came up several times a day and weighed hours. That's the one we tackled first. Without the count, we'd have put the energy in exactly the wrong place.

Worth remembering. What annoys you most isn't necessarily what costs you most. Annoyance is measured by intensity, cost is measured by frequency multiplied by duration. An unbearable but monthly chore weighs less than a painless but daily micro-task. Only counting tells the difference, and that's what stops you investing in the wrong place.

What people discover by counting

When someone reports back their notebook week to me, there's almost always the same moment of surprise. It isn't the total that shocks, it's the breakdown. Tasks thought marginal weigh hours; others people dreaded actually take up little space. The classics that keep coming up: copying the same information from one piece of software to another because the two don't talk to each other, answering the same customer question in writing for the hundredth time, reformatting a document redone identically every week, hunting for an attachment or a figure you know you've seen somewhere.

There's also an effect I hadn't anticipated at first: the simple act of counting is a relief. A vague burden, the one felt by an owner-manager who senses they're running without quite knowing after what, weighs more than a clear list, even a long one. Seeing it written in black and white, "here's where my hours go", brings something concrete where there was only a feeling of being overwhelmed. Many tell me the exercise alone, even before anything's been automated, has already given them back some clarity on their own week.

What you can do alone starting this week

Start the notebook week tonight. You need no tool, no provider, just a note and a bit of discipline. At the end, you'll have your real list, costed, ranked. Just seeing it written down will show you where to start and, just as important, what isn't worth touching. It's the diagnosis I'd run with you anyway; you might as well already have the material for it.

Once you have the list, connecting the right tasks and leaving the others alone is the heart of my automation work built onto your tools. To see this method applied for real, read how this plumber went from two hours of paperwork a night to fifteen minutes a week; and if your lost hours are hiding in your figures, there's putting your figures back in order.