The First Thing I Look at When Automating a Business Workflow

Most people think that automating a business process starts with choosing a tool. Pick the right software, connect it up, and off you go.

That is the wrong place to start. I know because I made that mistake early on — built something technically correct that solved the wrong problem. It worked perfectly and nobody used it.

Now, every engagement starts the same way. Before I look at any tool, before I write a single line of anything, I do one thing. I call it a friction audit. It takes about twenty minutes and it completely changes what gets built.

What a friction audit actually is

A friction audit is a structured conversation about time. I ask a business owner to walk me through a typical week — not in summary, but in detail. What did you do on Monday morning? What took longer than it should have? What did you do three times this week that you have done three hundred times in the past year?

The goal is not to find impressive things to automate. The goal is to find the tasks that are taking time that should not be taking time — and to understand exactly why they take the time they do.

This distinction matters enormously. A task that takes two hours a week because it is genuinely complex is different from a task that takes two hours a week because the information is scattered across three different systems and someone has to manually copy it from one to another. The first might not be automatable at all. The second can often be fixed in an afternoon.

The three questions I always ask

Within the friction audit, I have three questions I always return to:

1. What do you do more than once that feels like the same thing every time? — Repetition is the clearest signal that automation is possible. If you are writing the same email twenty times a month with small variations, that is a candidate. If you are manually updating the same spreadsheet weekly, that is a candidate.
2. What falls through the cracks? — The follow-up that did not happen. The invoice that went out late. The client whose appointment confirmation was forgotten. These failures are almost always not the fault of the person — they are the fault of a system that relies on human memory. AI does not forget.
3. What do you do after hours that should be happening during business hours? — If you are answering the same client questions at 9pm that you answered at 9am, that is a sign that the process is broken. The goal is not to work more — it is to build systems that work when you are not.

What usually comes out of it

In almost every friction audit I have done, the same categories emerge. They vary in specifics but not in type:

• Quote or proposal generation — usually manual, usually slower than it needs to be
• Follow-up communications — happening inconsistently or not at all because life gets in the way
• Appointment or job scheduling — consuming time that a tool could handle automatically
• Repetitive client-facing documents — intake forms, reports, updates that are essentially templates with small variations
• Information transfer — moving data from one system to another by hand because the systems do not talk to each other

Each of these categories has well-established solutions now. The tools exist. The question is always which one fits the specific business, and what the right order of implementation is — because trying to fix everything at once is the surest way to fix nothing.

Why this matters before any tool conversation

Here is what happens when people skip the friction audit and go straight to tools: they automate the wrong things.

They see a demo of something impressive and try to implement it in their business, without first asking whether it solves a real, costly problem. They spend time and money building something that works technically but does not move the needle because it was not solving the right problem to begin with.

The friction audit forces clarity. It means that by the time we are talking about tools, we already know what problem we are solving, how much time it is currently costing, and what a good outcome looks like. The tool becomes a means to an end — not the end itself.

You can do this yourself

You do not need to hire anyone to do a friction audit. Sit down with a notebook. Walk through your last week in as much detail as you can. For every task you did, ask: did this take longer than it should have? Did I do a version of this before? Could a machine have done this if it knew the right inputs?

You will probably come up with more opportunities than you expect. The challenge is not finding things to automate — it is prioritising which ones to tackle first, and making sure the solution fits your actual business rather than a generic template.

If you want help running a friction audit on your business, or if you have done this yourself and want to talk through what you found, get in touch. That conversation is always free.