Behind the scenes: how I structure a first client audit

Every new engagement starts the same way, before any recommendation, before any tooling conversation: an audit. Here’s what that actually looks like, step by step, since “audit” is one of those words that means very different things depending on who’s saying it.

Step one: map, don’t diagnose yet

The first pass is pure observation. What tools exist, what processes run where, who owns what, on paper and in practice, which are often different. No fixing anything yet, no opinions yet, just an accurate map. Diagnosing before mapping is how businesses end up solving the wrong problem confidently.

Step two: find where the map and reality disagree

Every business has a documented version of how things work, and an actual version. The gap between them is where most of the real findings live. A process that’s “supposed to” take three steps but actually takes seven, in practice, tells you more than either version alone.

Step three: talk to the people doing the work, not just the owner

Founders describe their business as it’s meant to work. The people executing it daily describe it as it actually works. Both perspectives are true and incomplete on their own. The audit needs both, and usually surfaces at least one gap the founder didn’t know existed.

Step four: rank findings by leverage, not by loudest complaint

Not every friction point is worth fixing first. The audit ranks findings by how much downstream pain each one causes, not by how recently or loudly someone complained about it. The loudest problem and the most expensive problem are frequently not the same problem.

What comes out the other end

Not a generic report. A short, ranked list: here’s what’s actually happening, here’s what it’s costing, here’s what to fix first and why that one first. No recommendation before the map is accurate, because a confident answer to the wrong question is worse than no answer at all.