01 Sample report
not a client report
This is what €490 buys.
Below is a sample of the UI/UX audit report format, populated with the drop-off issues we most commonly see in early SaaS and vibe-coded apps, so you can judge the depth before you pay. It is a sample of the format, not a real client's report. Client reports are confidential. The real report also annotates screenshots of your actual screens; this page shows the written layer.
UX audit report: sample
- Fee
- €490
- Turnaround
- 1 week typical
- Findings shown
- 6 of a typical 10–18
- Format
- prioritized, annotated
02 The findings
Six findings, ranked by what they cost you.
Each one names where users fall out, why, the concrete fix, and the effort involved. Priority is impact on conversion against effort to fix, so engineering knows what to do Monday morning. Real reports typically run 10–18.
High · Onboarding
Signup asks for six fields including company size and phone number before showing any product. Every field before the first value moment is a toll booth; phone number alone is a known drop-off cliff for solo founders and indie users.
- Fix Cut signup to email + password (or a magic link). Move profile questions to after the first successful action, asked one at a time in context.
- Effort 2–4 h
High · Activation
After signup the user lands on an empty dashboard: no data, no pointer, one grayed-out chart. The next step exists only in the docs. Most users who leave here never come back, and analytics will call it "churn" instead of "confusion".
- Fix Replace the empty state with a three-step start checklist seeded with sample data, one primary button per step. Delete every other CTA on that screen.
- Effort 4–6 h
High · Checkout
The pricing toggle switches monthly/yearly but the displayed number changes without a visible unit, so the yearly price reads as a 10x increase. On a card error the whole form clears, and the error message ("payment failed") names neither the field nor the fix.
- Fix Label prices per seat per month in both toggle states. Preserve form state on error; show the error inline next to the failing field with what to do about it.
- Effort 3–5 h
Medium · Trust at the paywall
The card form appears with no plan summary, no cancel-anytime line, and no human contact. The user is asked to trust before the interface has earned it, at the exact screen where hesitation costs the most.
- Fix Put a one-line plan summary, "cancel anytime, from the app", and a support email within eye-line of the pay button.
- Effort 1–2 h
Medium · Mobile reality
On a phone the primary CTA sits below the fold, the nav drawer needs a scroll to reach half its items, and several tap targets are under 40px. Most first visits are mobile; the desktop-first layout is auditioning to an empty room.
- Fix Raise the primary CTA above the fold, tighten drawer density so it fits one screen, and enforce 44px minimum tap targets on interactive elements.
- Effort 2–4 h
Low · Error states
A failed data load shows an infinite spinner. No timeout, no retry, no message. To the user this is indistinguishable from a broken product, and the support ticket it generates says "your app doesn't work".
- Fix Time out after a few seconds into an error card: plain words about what failed, a retry button, and a status link.
- Effort 2–3 h
01 High · Onboarding
Signup asks for six fields including company size and phone number before showing any product. Every field before the first value moment is a toll booth; phone number alone is a known drop-off cliff for solo founders and indie users.
- Fix Cut signup to email + password (or a magic link). Move profile questions to after the first successful action, asked one at a time in context.
- Effort 2–4 h
02 High · Activation
After signup the user lands on an empty dashboard: no data, no pointer, one grayed-out chart. The next step exists only in the docs. Most users who leave here never come back, and analytics will call it "churn" instead of "confusion".
- Fix Replace the empty state with a three-step start checklist seeded with sample data, one primary button per step. Delete every other CTA on that screen.
- Effort 4–6 h
03 High · Checkout
The pricing toggle switches monthly/yearly but the displayed number changes without a visible unit, so the yearly price reads as a 10x increase. On a card error the whole form clears, and the error message ("payment failed") names neither the field nor the fix.
- Fix Label prices per seat per month in both toggle states. Preserve form state on error; show the error inline next to the failing field with what to do about it.
- Effort 3–5 h
04 Medium · Trust at the paywall
The card form appears with no plan summary, no cancel-anytime line, and no human contact. The user is asked to trust before the interface has earned it, at the exact screen where hesitation costs the most.
- Fix Put a one-line plan summary, "cancel anytime, from the app", and a support email within eye-line of the pay button.
- Effort 1–2 h
05 Medium · Mobile reality
On a phone the primary CTA sits below the fold, the nav drawer needs a scroll to reach half its items, and several tap targets are under 40px. Most first visits are mobile; the desktop-first layout is auditioning to an empty room.
- Fix Raise the primary CTA above the fold, tighten drawer density so it fits one screen, and enforce 44px minimum tap targets on interactive elements.
- Effort 2–4 h
06 Low · Error states
A failed data load shows an infinite spinner. No timeout, no retry, no message. To the user this is indistinguishable from a broken product, and the support ticket it generates says "your app doesn't work".
- Fix Time out after a few seconds into an error card: plain words about what failed, a retry button, and a status link.
- Effort 2–3 h
03 The structure
What every report contains.
From Sanya, the design desk
Re What every UX audit report contains
Annotated screens, not adjectives
Every finding is pinned to a screenshot of your actual screen with the problem marked on it. No "the design feels dated"; you see exactly which element loses people and why.
Prioritized like a backlog
Findings are ranked by impact on conversion against effort to fix, and written so engineers can act without a designer on staff. The top of the list is your Monday morning.
A "fine as-is" list
An honest list of what we walked and did not flag, so you know what you are not paying to redesign.
Six findings shown here. Real reports typically run 10–18.
04 Next step
Get the real one.
Entry: closing
The same format, filled in with where your app actually loses people.
Balance due one conversation
Now booking