One hour UX review: what it costs and what you get

On-Off Group

October 2026

Most of a UX review cost is write-up time, not review time. An hour spent checking one customer journey against usability standards, with the people who own it watching, gives you a list of problems and a before number for the same price bracket as a long audit's first meeting.

If you have been searching "ux review cost", you are probably after a number you can put in front of a boss who is tired of vendor decks. This is for you: what a review actually involves, how long it takes, and what you need ready before anyone looks at your customer journey.

Reviewing a journey takes about an hour. Writing it up takes days, and the write-up is most of what you are being quoted for.

So the smallest useful first step is an hour on one journey, with the people who own it in the room, and a before number written down while everyone is still looking at the screen.

Why the quote is bigger than the work

Most UX audit quotes are priced by the week, not by the hour of looking. Ask what happens in those weeks and the honest answer is document production. Screenshots. Severity ratings. A findings deck with an executive summary at the front.

The looking part is fast. Someone who knows usability standards can open an onboarding flow on a phone, try to get through it, and list the things that will cost you completions. That takes about an hour.

The expensive part is turning that hour into something that survives being emailed around. And by the time it lands, the build team has shipped again and some of the screenshots are already out of date. Clients describe the same ending every time: a PDF arrives, everyone agrees it is thorough, and nothing in it gets fixed.

Drop the document, keep the hour, and you are only paying for someone to go through the journey. The method for doing that is written up here: How to review a website or app against usability standards in 60 minutes.

What one hour can honestly cover

One journey. Start to finish. Account opening, a claim submission, a loan application, a card replacement request. Not the whole app.

Inside the hour you can check the journey against the usual standards: does each screen say where you are and what happens next, are error messages usable by someone who has made a genuine mistake, can the thing be completed on a mid-range Android phone on mobile data, does it work if you cannot read small grey text.

What comes out is a list of problems in the order they would hurt a customer, with the two or three that branch staff will keep getting calls about marked as first. Nobody needs a PDF to act on that. Someone types it into the backlog before the hour is over.

What an hour cannot do is tell you what your customers actually do. A review finds broken standards. Watching five real people try the journey shows you where they give up and ring the branch instead. That is a separate piece of work.

Write down the before number in the same hour

This is the part that gets skipped, and it is the reason people cannot answer "did it work".

Most teams have no baseline for the journey they are fixing. There is no recorded turnaround time for onboarding before the change, so after the change there is nothing to compare against. So when the boss asks whether it worked, all you can do is shrug.

So before the review ends, pick one measure and write the figure down. Completion rate on the flow. Turnaround time from submission to approval. Number of calls to branch staff about that step per week. One is enough. If nobody knows the figure, that is the finding: note that it is not measured and get it measured before the fixes go live.

A large insurer we worked with ran a series of five day design sprints on customer-facing web journeys. Journeys that used to take six months or more were designed, tested with customers and live in four weeks, and completion rates on the new journeys rose 80 per cent. Their own measurement, not ours. That 80 per cent only exists because someone wrote down the completion rate before the change.

What to have ready before the hour starts

The hour goes badly when a chunk of it is spent getting a login to work.

Have a live link or a test account that works from outside your network. A real phone, not a simulator on a laptop. One named journey with an agreed start and end point. The person who owns the backlog, on the call, able to write.

Bring any number you already have, even a rough one from a report nobody trusts. A rough number people argue about is still better than nothing.

And bring the complaints. Branch staff usually know exactly which step generates calls. That list costs nothing and points the hour at the right screens.

When you should pay for more than an hour

An hour is the wrong size for some jobs.

If you need to change how a team works, not just fix a flow, that is training or a working session, and the length and preparation are set out on Custom workshop pricing, length and what you need to prepare.

If the thing you are scoping is an AI feature, a review of screens will not help you much, because the screens do not exist yet. Build a rough working version and watch someone try to use it. What that involves is here: What building an AI feature with us involves and how long it takes.

And if the question is where customers drop out, spend the money on watching real users instead. A review will not tell you that, however a vendor sells it.

What to do this week

Pick one customer journey with a clear start and end, and write its name down.
Find one number for it: completion rate, turnaround time, or calls to branch staff per week. If there isn't one, get it measured.
Get a test account that works from an ordinary phone outside your network.
Ask two branch staff which step in that journey generates the most calls.
Book one hour with the person who owns the backlog, and fix the top three items before anyone writes a report.

Questions people ask

What drives the cost of a UX review?
Mostly the reporting. Looking at a signup or onboarding flow and spotting the problems takes an hour or two; turning that into a formatted PDF with screenshots and severity ratings takes days, and those days are what you pay for.

What do I need to bring to a one hour review?
A live link or a test account, one journey with a start and an end, and whatever number you already have for it, such as completion rate or turnaround time. If you have no number, note that and record it during the hour.

Does a review replace usability testing?
No. A review tells you where a journey breaks known usability standards. Only watching real customers use it tells you where they give up and why, so the two answer different questions.

Can a one hour review give my boss something real?
Yes, if you write down a before number in the same hour. A list of fixes plus a starting figure means the same measure can be checked again after the fixes go live.

On-Off Group trains teams, tests products with real customers, finds where a transformation has stalled and builds what gets it moving, for banks, insurers and enterprises in the Philippines, since 2015. How we help with ux review.