Reading time:
7 min read
Last updated:
What a UX Audit Actually Finds and What It Costs
A real UX audit produces ranked findings with evidence and fixes, not adjectives. What you should receive, what it costs, and when it is worth buying.
A UX audit is a structured review of a product you already have that ends in a prioritized list of specific problems, each with evidence and a recommended fix. It is not a redesign, and it is not a general opinion about whether the product looks good. The deliverable is a document you can hand to an engineer on Monday.
It is one of the easiest things for an agency to sell badly, so here is what a real one produces, what it costs, and when it is worth buying.
What you should actually receive
A useful audit has four parts. A list of findings, each tied to a specific screen or flow. Evidence for each finding, whether that is analytics, session recordings, support tickets, or an established usability principle. A severity ranking, so you know what to fix first. And a recommended fix for each item, concrete enough to estimate.
What you should not receive is a slide deck of adjectives. If a finding reads that the interface feels cluttered, it is an opinion. If it reads that the settings page shows nineteen options with no grouping and support logged forty tickets about one of them last quarter, that is a finding.
What auditors actually look at
Most audits cover the same ground. The first run through the product as a new user with an empty account. The main flow that makes you money, step by step, counting where people drop. Error and empty states. Mobile behaviour. And accessibility basics such as contrast, focus order, and whether the thing works from a keyboard.
The first-run experience is usually where the biggest wins hide. Teams see their product full of data every day and stop noticing that a new account is a blank screen with no obvious next move.
What it costs and how long it takes
Audits are one of the few design services with reasonably public pricing, because the scope is contained. Where studios publish, a focused audit of one product area commonly runs one to two weeks and lands in the low four to five figures depending on depth and on whether user testing is included.
Watch for the difference between a heuristic review, where an experienced designer works through the product against known principles, and a research-backed audit that includes sessions with real users. The second costs more and takes longer, and it is worth it when you disagree internally about what the problem is.
When an audit is worth buying
Three situations make it a good purchase. You have traffic but weak conversion, and you cannot tell where people are giving up. You are about to spend a lot on a redesign and want to know what is actually broken before you rebuild it. Or you have an internal disagreement about priorities and need an outside read to settle it.
The redesign case is the strongest. An audit is a cheap way to find out whether you need a redesign at all, and teams often discover that four specific fixes would recover most of the value they were about to spend three months chasing.
When it is not worth it
Skip the audit if you already know what is wrong and are simply not shipping the fix. Paying someone to confirm your list does not get it built. Skip it if the product has almost no users, because there is no behaviour to review and you are really looking for product direction, which is a different service.
Also skip it if the audit is offered free. A free audit is a sales document, and it will find problems that happen to match what that agency sells.
How to tell a real audit from a sales pitch
Ask what the deliverable looks like before you buy, and ask for a sample with the client details removed. A real audit is specific, ranked, and occasionally boring. A sales document is broad, flattering about its own recommendations, and ends with a proposal for a full rebuild.
Ask one more question. Which findings would you expect us to fix without hiring you? An honest studio has an answer. How to tell if a design agency actually ships covers the rest of the checks worth making first.
Where to start
If you want a shortlist rather than more reading, we keep one for UX audit agencies working on AI products, compared on team shape, what they publish about price, and how they evidence their findings.
Studio Maydit ends every fixed-scope project with a written read on what is leaking in the product, and works with AI founders across the US, UK, and Europe. If you want to talk through whether an audit or a build is the right next step, book a free 30-minute call.
Frequently Asked Questions
Continue Reading

ChatGPT Is Introducing Ads. Here’s the UX Risk Nobody Is Talking About
As ChatGPT prepares to introduce ads, most conversations focus on revenue and scale. But the bigger question is how monetization reshapes user trust, cognitive flow, and product intent. This Studio Notes piece explores the hidden UX risks product teams should pay close attention to.

Siddarth Ponangi

Why designing for power users too early breaks SaaS products
Many SaaS products become difficult to use not because they lack features, but because they introduce complexity before users are ready for it. Designing for power users too early often feels like progress, but it quietly undermines adoption for everyone else.

Siddarth Ponangi

Why second-use experience matters more than first impressions in SaaS
Many SaaS products spend enormous effort optimizing first impressions. What often gets overlooked is what happens when users come back for the second time, which is usually where real adoption either starts or quietly falls apart.

Siddarth Ponangi

