How to prepare for a workflow audit (and what to bring to the call)
You need about ten minutes of preparation, and none of it is technical. Here is what actually helps, what happens in the 30 minutes, and what you should walk away with.
If you have booked a workflow audit, or you are thinking about booking one, you probably have two quiet worries. The first is that you will spend 30 minutes being sold at. The second is that you are somehow not ready, that you should have your processes written up or know which tools you want before anyone will take you seriously.
The second worry is easy to put down: ten minutes of jotting covers everything, and this article walks through exactly what to note. The first worry is fair, and there is a test for it near the end.
One thing worth knowing: almost everything written about these calls is written for the agency. How to run the call, how to qualify you, how to steer you to the close. I could not find a single guide written for the owner sitting on the other side, so this is that guide. I run these calls every week, and this is what genuinely makes them better.
What a workflow audit actually is
A workflow audit is a structured look at how your week actually runs: where work comes in, who touches it, where it sits waiting, and which repeated job is quietly costing you the most time. It ends with a decision about the first thing worth fixing and a rough number for what fixing it would be worth. You will also see the same exercise sold as an "AI readiness assessment" or an "AI workflow audit"; the label changes, what you should leave with does not.
It is a conversation, and nothing more than that. Nobody opens your systems, nobody installs anything, and nothing changes in your business because you took a call.
The short version: bring one bad week
If you do nothing else, do this. Think of the most recent week that annoyed you, and be ready to describe it honestly. The Tuesday the quotes went out late, the leads that sat unanswered over the weekend, the invoice you chased three times. A specific bad week gives the call more to work with than any process document, because it shows where the friction actually is rather than where it is supposed to be.
Everything below just sharpens that picture.
Five things to jot down before the call
Ten minutes with a notes app covers all five. Rough answers are fine for every one of them.
- The task you would delete if you could. Not the flashiest one or the most technical one. The one you complain about at dinner.
- Rough volumes. How many enquiries come in a week, how many quotes go out, how long a lead usually waits for a reply. "About thirty, more in spring" is a perfectly good answer.
- Where the work lives. Just the names: Gmail, a spreadsheet, Xero, whichever CRM you half-use. Nobody needs logins, only the map.
- Who does it today. You, your office manager, or whoever picks it up when it is nobody's job. That last case is worth mentioning, because work that belongs to nobody is usually where the most time leaks.
- What you have already tried. The Zapier weekend, the agency that did not stick, the team member who had a go. There is no judgement in this question. Knowing what did not fit, and why, saves us from proposing it again.
What you do not need to bring
- Passwords or system access. Nobody should touch your systems on a first call, and anyone who asks for logins is moving far too fast.
- Process documentation. If your processes were all written down, you would probably need this call less. In most small businesses the process lives in someone's head, and that is normal.
- A decision about tools. Which platform to use is a question for after the problem is mapped. If you arrive committed to a tool, you have done the hard part in the wrong order.
- Technical vocabulary. Describe the work the way you would describe it to a friend at a barbecue. "The same questions keep coming in and Sarah answers them all by hand" is exactly the right register.
- A budget commitment. A first call should hand you a number to take away and think about, and you should never feel one being pulled out of you.
The fastest preparation is the scorecard
If you want to arrive properly armed, take the free two-minute scorecard before the call. It asks about one repeated task, scores how ready that task is for automation, and gives you a rough monthly figure for what handing it off could be worth. Bring the result with you. It effectively becomes the agenda for the first ten minutes, and it means the call starts from your numbers instead of from zero.
What actually happens in the 30 minutes
Every operator runs these a little differently. Here is how I run mine, which should at least tell you what a working session looks like as opposed to a pitch.
| Minutes | What happens |
|---|---|
| 0 to 10 | We map how the work runs now. You talk, I ask questions. This is where your one bad week and your five notes do their job. |
| 10 to 20 | We find the bottleneck worth fixing first. Usually it is the quiet, boring one rather than the obvious one, which is why this step is a conversation and never a template. |
| 20 to 30 | We sketch what an agent would handle, what would stay human, and what the build would roughly cost. You take the sketch and the number away with you. |
There are no slides. And sometimes the honest outcome is that AI is the wrong fix for now, because the task needs clearer steps or better information before anything should be built on top of it. If that is the case, you should hear it plainly on the call.
What you should leave with
Judge any workflow audit, mine included, by whether you walk out holding three things:
- A map of where your week is leaking the most time
- The first automation worth building, and what it would handle
- A rough number for what the build would cost
All three should be yours whether or not you ever work with the person who ran the call. If the 30 minutes ends and you are holding a follow-up meeting instead of a map, you attended a pitch.
Bring your hard questions too
A working session should survive scrutiny. If you are vetting us, or anyone, bring the ten questions from the hiring guide, especially the ones about ownership and what happens when things break. An operator worth hiring will enjoy answering them, and you will learn a lot from watching anyone who does not.
Common questions
Do I need to prepare anything technical?
No. Nobody should be asking for logins, system access, or documentation on a first call. You need a clear picture of one annoying week, rough volumes, the names of the tools involved, and what you have already tried. Ten minutes of jotting covers it.
Is a free workflow audit just a sales call?
It depends entirely on who runs it. Would you leave with something useful if you never hired them? A real audit ends with a map, a first automation worth building, and a rough number, whether or not you go ahead. If the 30 minutes was mostly about their packages, it was a pitch wearing an audit's name tag.
What if my processes are a mess?
Mess is normal. In most small businesses the processes live in people's heads and inboxes rather than in any document, and finding out where things actually flow is a large part of what the call is for. You do not need to tidy anything before you book, and nobody worth talking to will judge a spreadsheet held together by habit.
How long does it take and what does it cost?
Ours takes 30 minutes and is free. A rough cost for the first build is part of what you leave with, so you can take the number away and decide in your own time.
What is an AI readiness assessment?
A newer name for the same look at your operations, usually framed around one question: which of your repeated jobs could an AI agent take over, and is the way you work today ready for that? Our free scorecard is a three-minute, self-serve version, and the audit call is the human one.
Ready when you are
Book a free 30-minute workflow audit. Bring one bad week, the five notes, and any hard questions you like. We map where your week leaks time and what we would build first, and everything from the call is yours either way.
Book a free workflow audit Want the best prep first? Take the free two-minute scorecard →