What drives the cost of a UX audit?

Why quotes vary so much

Quotes for a UX audit vary enormously, from a quick checklist review to a multi-month programme. The number on its own tells you very little, so it helps to know what’s behind it. The biggest factor isn’t who does the work. It’s how much of the product is in scope and how much evidence the reviewer has to work through.

Our own UX Audit is a fixed-fee review of one workflow, one user role and one device, up to 10 screens or states, delivered in two weeks. We agree the fee in writing before anything starts, so there are no surprises later.

What pushes the price up

Four things make an audit bigger, and they multiply rather than add.

• More workflows. Onboarding and billing are two different audits, even if they live in the same product.
• More user roles. An admin and an everyday operator see different screens, permissions and errors.
• More devices. A responsive web app and a native mobile app need separate passes.
• More states. Ten screens with five permission levels and three failure modes is a lot more work than 10 screens on a happy path.

Evidence matters too. If you have analytics, support tickets and old research, someone has to read and weigh it. That’s time well spent, because it makes the findings far stronger, but it does add to the fee.

What brings it down without cutting corners

The cheapest way to get a better audit is preparation. A test account with realistic data saves hours of workaround. A short brief explaining what prompted the review stops the reviewer guessing. One person who can answer product questions quickly keeps the timeline intact.

Narrowing the scope helps too. “Review the whole platform” is expensive and usually vague. “Review how a new admin invites their team and sets permissions” is focused, cheaper and far more likely to change something.

Day rate or fixed fee?

Day-rate audits make sense when nobody can define the scope yet. The risk is that the work expands to fill the time, and you won’t know the final cost until it’s over.

A fixed fee works when the scope is agreed up front. You know what you’re paying, the reviewer knows what they’re committing to, and anything outside the boundary becomes a separate conversation rather than a surprise invoice. For a single workflow, we think fixed fees are fairer on both sides, which is why we work that way.

How to compare quotes

Two quotes for “a UX audit” can describe completely different jobs. Before comparing numbers, ask each provider:

1. Exactly which workflow, role and device are included?
2. What will I receive, and in what format?
3. How are findings prioritised, and who estimates the effort?
4. Will I get any design directions, or only a list of problems?
5. Is there a walkthrough, and what happens if we have questions afterwards?
6. What is explicitly not included, such as user testing, accessibility conformance or redesign?

The last question is the one that saves you money. A cheap audit that leaves out the prioritisation is expensive in the end, because your team still has to work out what to do.

Is it worth it?

An audit can help your team avoid spending a sprint on the wrong problem. If you’re about to commit engineering time to a redesign and nobody can say with confidence what’s broken, a short, focused review can reduce that uncertainty. Its value depends on what the review finds and how your team uses it.

It’s probably not worth it if you already know what’s wrong and have the evidence to back it up. In that case, spend the money on design instead. Complex Workflow Design picks up from there.