Your product has friction. Let's find it.
A UX audit that goes through your product, shows exactly where it loses people, and what to fix first.
You have a product. Something is off. You can feel it, but you can't name it.
You're past the MVP. Users are in. Now what?
People drop off at points you can't quite pinpoint.
You know something is broken, but not what to fix first.
You want a clear picture before investing more in development.
How it works
- 1
Intake call
We align on scope, context, and access. 30 minutes.
- 2
Access to your product
A test account or working environment is enough.
- 3
The audit
I do the work. Delivered within one week.
- 4
Walkthrough
We go through the findings together and lock in priorities.
First, let's find what's off.
Now you've got a list you can act on.
You don't leave with a vague feeling.
You leave knowing exactly what's broken, why it matters, and what to fix first.
End-to-end flow analysis
I go through your product as a user would. Every screen, every step. Every point where something slows down, confuses, or disappears is noted with context.
Structured document
A clear document with findings, visual annotations, and references. Not a list of complaints. A tool for making decisions.
Strategic direction
What to fix and in what order. Each finding is connected to a pattern that better-designed products already use. You see the gap and you see what closing it looks like.
Debrief
We go through the deck together. You ask questions. We end with alignment on what matters most.
You're probably wondering
What is a UX audit, exactly?
A UX audit is a structured review of your product's user experience, where I go through the real flows your users move through and find where they get stuck, confused, or drop off. Instead of guessing what to fix, you get a clear, prioritised picture of what's actually costing you conversions, retention, or trust, and why.
How is a UX audit different from user testing?
User testing watches people use your product and shows you what happens. A UX audit explains why it happens and what to do about it. Testing gives you observations, an audit gives you a diagnosis and a direction. They work well together, but if you can only do one to start, the audit gets you further faster because it turns scattered signals into a plan.
Will this be about my product, or just best-practice advice?
About your product. Best practices are the floor, not the deliverable. The work is finding where your specific flow loses people, why they hesitate, and what that costs you. If I could write the findings without looking at your product, I wouldn't be doing my job.
Is my product far enough along for this?
Sooner than most founders think. A live product is ideal, because then I'm reading real behaviour, not just intended flows. But a clickable Figma flow works too, and catching the friction before you build it is cheaper than catching it after. What I need is a flow people move through, designed or real. If it's still a loose idea without a shape yet, I'll tell you that on the intake.
What do I actually walk away with?
A prioritised set of findings, each with the problem, why it matters, and a direction to fix it. Visual annotations on your own screens, not abstract principles. Plus a debrief call where we decide together what's worth acting on first and what can wait.
Do you fix the issues too, or just point them out?
The audit ends with the deck and the debrief. From there some founders take it in-house, others bring me in to design the solutions. Both are fine. The audit stands on its own either way, you're never stuck with a list you can't act on.
How fast, and what do you need from me?
The audit lands within a week. The intake is 30 minutes to align on scope, then I work from access to your product or flow. Light on your time, which is the point.
Ready to find the friction?
Start with a 30-minute intake call. We figure out what's actually worth fixing, together.
Plan an intake