The Clarity Audit is two weeks of structured product diagnosis. It maps where your product is losing growth and why, then delivers a prioritised brief that names each real problem, what it's costing you, and the order to solve things in. You finish knowing exactly what to do next, whether or not you keep working with me.

If you're considering a product audit, the thing you actually want to know is simple and rarely answered straight: what do I get, what does it cost me, and what do I do with it afterward? Sales pages tend to answer in adjectives. So here's the concrete version of my two-week Clarity Audit, week by week: what happens, what I ask you for, what lands at the end, and what you do with it next. The more exactly you can picture it, the easier the decision, which is the point.

What it is, in one line

The Clarity Audit is phases one and two of how I work - Diagnose and Align - delivered as a standalone, two-week engagement. You don't have to commit to a longer relationship to get it. It's a complete piece of work that ends in a clear answer, and you can take that answer anywhere, including to someone else.

That last part matters and I mean it: the audit is designed to be valuable on its own. If at the end you decide to fix everything in-house, you'll have a prioritised plan to do it. I'd rather give you something genuinely useful and earn the next step than gate the answer behind a contract.

Week one: Diagnose

The first week is about finding what's actually broken, underneath what looks broken.

The first couple of days, context and access. I start with you and your team, not the product. What is this product supposed to do, for whom, and what does success look like in numbers you care about. Where do you think it's failing. What's already been tried. Then I get access to what tells the truth: your analytics, your support queue, your funnel data, and the product itself. I ask for honest access, not a curated tour, because the curated tour is usually where the real problem is hiding.

The middle of week one, the diagnosis. This is the core of the week. I map every primary user flow in your product and rate the friction at each point - where people slow down, get confused, or leave. I cross that against your data, so a friction point I suspect in the product is confirmed by a drop-off in the funnel or a cluster in the support queue. The goal isn't a list of UI nitpicks. Anyone can produce that. The goal is to separate symptoms from causes: to find the small number of real problems that are generating the long list of visible ones, because most product problems aren't what they look like on the surface.

By the end of week one I have a diagnosis: not "here are forty things wrong" but "here are the few things actually costing you growth, and here's the evidence."

Week two: Align

A diagnosis nobody acts on is worthless. Week two turns the findings into something your business can decide with.

Early in week two, business translation. I take every product and UX problem from week one and translate it into business language. Not "the onboarding has high cognitive load" but "this single step is where you lose a large share of the signups you've already paid to acquire, and here is what that is costing you in revenue." A UX problem nobody can put a number on never gets prioritised, because it can't compete with everything else demanding attention. So I make each problem legible in the terms leadership actually uses: growth, cost, risk.

The back half of week two, prioritisation and the brief. I rank the findings into 3 to 5 initiatives, ordered by impact against effort, so you're not looking at a wall of problems but at a sequence: solve this first, because it's the highest return for the least work, then this. That ranked set is the core deliverable.

What you walk away with

At the end of the two weeks you get:

  • A Product and UX Diagnosis - every primary user flow mapped, friction points identified and rated, grounded in your real data, not opinion.
  • A Business Impact Assessment - each problem translated into what it's costing you in growth, cost, or risk, so the priorities are obvious.
  • A Prioritised Roadmap - 3 to 5 ranked initiatives, the specific things to solve, in the order that returns the most for the least effort.
  • A Stakeholder Alignment Session - a live presentation to your leadership team. I walk your decision-makers through the findings in person, so the alignment is real and shared, not a document that gets skimmed once and filed.

The throughline of all four: you finish knowing what to solve first and why. That's the whole product. Clarity you can act on Monday.

What it costs

The Clarity Audit is a fixed two-week engagement, with an investment of $3,000 to $10,000 USD depending on the size and complexity of your product. You know the cost before you commit, and you know exactly what you're getting for it.

The more useful way to think about cost, though, is the other side of the ledger: what it costs not to do it. If your product has a real problem you haven't named, you're already paying for it - in acquisition you're wasting, in growth you're not getting, in a team building against the wrong target. Two weeks of diagnosis is cheap next to a quarter spent solving the wrong problem, which is the default alternative.

Who it's for (and who it isn't)

The audit is built for a specific moment: you have a product with real potential, something isn't working, and nobody can quite name what. You suspect the problem is bigger or deeper than the symptoms suggest, and you'd rather know than keep guessing.

It's not for you if you already know exactly what's wrong and just need it built - that's an execution job, not a diagnosis, and you'd be paying for an answer you already have. And it's not for a product that's working fine and growing well. The audit earns its cost when there's a real, unnamed problem to find. If there isn't, I'll tell you in the first conversation and save us both the two weeks.

What happens next

After the audit, you have a clear, ranked plan and full ownership of it. From there you choose:

  • Solve it in-house. You have everything you need to brief your own team and start on the highest-impact problem first. No strings.
  • Keep working with me. The audit is the first two phases of how I work. If it makes sense, I carry straight on into Design, Build, and the long compounding work after - the same person, no re-briefing, no translation loss, the context already in the room.

Either way, the two weeks stand on their own. You'll know what's actually broken, what it's costing you, and what to do first. That's the deal.

If you've been guessing at what's wrong with your product, two weeks of structured diagnosis will end the guessing. You'll leave with a ranked plan and a clear answer, whichever way you take it from there.

Book a conversation and tell me about your product. I'll tell you what I see.