Every week a business owner tells us some version of the same thing: "We know we should be using AI. We just don't know where to start."
The instinct is to start with the tool — pick a chatbot, buy some seats, hope it sticks. It rarely does, because the tool was never the hard part. The hard part is knowing which of your processes are worth changing at all.
An AI-readiness audit answers that question before you spend a dollar on building. Here is what actually happens inside one.
Step 1 — We map the work, not the org chart
We start by shadowing how work really moves through your business: who touches a quote before it goes out, where a customer request waits, how many systems a single order passes through. Org charts describe reporting lines; we care about the flow — the copy-paste, the re-keying, the "let me just check with accounting" delays.
By the end of this step we have a list of concrete workflows, each described the way you'd describe it to a new hire: trigger, steps, hand-offs, and the moment it's considered done.
Step 2 — We score each workflow on two axes
Not everything should be automated, and the loudest pain isn't always the best place to start. So we score each workflow on two things:
- Value — how much time, error, or delay it costs you today, and what removing that is worth.
- Effort — how structured the inputs are, how many systems are involved, and how tolerant the step is of the occasional mistake.
The best first project is rarely the flashiest. It's the boring, high-volume, well-structured task that quietly eats an afternoon a week.
Plotting value against effort turns a vague wish list into a ranked one. The top-right quadrant — high value, low effort — is where we recommend you begin.
Step 3 — We check the data and the guardrails
A workflow can look perfect on paper and still be a bad first automation if the data it depends on lives in three inboxes and someone's memory. Before recommending anything, we look at:
- Where the inputs actually come from, and how clean they are.
- What "wrong" looks like, and who would notice.
- Which steps genuinely need a human to approve before anything leaves the building.
This is also where we're honest about what not to automate yet. A step where a mistake is expensive and hard to catch belongs behind a human approval — or stays manual until the rest is proven.
Step 4 — You get a written roadmap you keep
The audit ends with a document, not a sales pitch. It lists every workflow we looked at, ranked by ROI and effort, with a recommended sequence: what to do first, what it should cost, and what "working" would look like for each one.
That report is yours. There's no obligation to build any of it with us. If you take it to another team — or do it in-house — it still holds up, because it's a map of your business, not a catalogue of our services.
Why audit-first works
Starting with an audit changes the economics of the whole project. You're no longer betting a large build budget on a hunch. You're spending a small, fixed amount to replace the hunch with evidence, and then choosing — deliberately — which one or two workflows justify a build.
Almost every engagement we run starts here. Audit first. Then build. Then run.
If you'd like to see what that top-right quadrant looks like for your business, book a free audit — it starts with a 30-minute call, no slides and no pitch.