Find what's costing you users. Fix it in order.
Start with a bounded review of your product, website or checkout. Get evidence for each finding, a ranked backlog and a plan your team can act on without buying a redesign.
Is an audit the right first step?
An audit is the smallest useful engagement we offer. If you already know exactly what to change, skip it and go straight to design.
Good fit if
- You have a live product or site with an unclear conversion problem
- Your team needs evidence before committing to a redesign
- You can share key flows and available analytics
Not a fit if
- You want a guarantee of a specific conversion increase
- You need production changes during the audit
- You cannot provide access to the screens being reviewed
Four files. All yours.
Every finding links to evidence: a screen, a recording, a metric or a heuristic. No opinions without a reason.
Audit report
Findings by flow, with screenshots, evidence and severity.
Annotated screens
Every issue pinned on the screen it happens on.
Prioritized backlog
Severity, effort, owner and acceptance criteria per item.
Walkthrough
We present the top issues to your team and answer questions.
This is what a finding looks like.
An excerpt from a sample ledger. Client audits are anonymized before we ever show them.
| ID | Flow | Finding | Evidence | Severity | Effort | Acceptance criteria |
|---|---|---|---|---|---|---|
| UX-04 | Signup | Workspace name asked before the user sees any value | 62% drop at step 2 (Mixpanel, 30 days) | Critical | S | Step moves after first invoice preview; drop below 30% |
| UX-11 | Onboarding | Empty dashboard gives no next action | 5 of 6 session recordings idle > 40s | Critical | M | Empty state offers sample data and one primary action |
| UX-17 | Invoices | Bulk actions hidden behind an unlabeled icon | Heuristic: recognition over recall | Major | S | Visible label; keyboard reachable; tested with 3 users |
| UX-26 | Settings | Role permissions explained only in docs | 14 support tickets / month | Minor | M | Inline role matrix; tickets halve in 60 days |
Ten days, four checkpoints.
You spend about three hours of team time in total: a kickoff, access setup and the walkthrough.
Kickoff & access
Goals, key flows, roles and the metrics that matter. Read-only access to analytics.
- 45-min call
- Scope sheet
Review & evidence
Expert review of every in-scope screen, analytics and recordings, CWV check.
- Heuristics
- Funnels
- Recordings
Prioritize
Severity, effort and acceptance criteria for each finding. Quick wins flagged.
- Backlog CSV
- Figma notes
Walkthrough
We present, you challenge. Then you choose: build with us, your team or another vendor.
- 60-min call
- Recording
Three audit sizes.
Your proposal states a fixed price before any work starts. Screens, roles and research methods change the size.
Focused flow
- Up to 8 screens
- One user role
- Expert review + analytics
- Backlog CSV + walkthrough
Product or site
- Up to 20 screens
- Up to three roles
- One round of moderated tests
- Report, Figma notes, backlog
Full product
- Whole product or store
- All roles and states
- Analytics deep-dive
- Redesign roadmap included
An audit should end with a backlog your team can ship, with us or without us.
Where an audit usually leads.
The audit is a decision tool. These are the most common next steps.
Sample UX findings ledger
Each sample finding records the affected task, evidence, severity, suggested change and a way to check the fix. The actual audit separates measured issues from hypotheses that need a user test.
Sample UX findings ledger
Each sample finding records the affected task, evidence, severity, suggested change and a way to check the fix. The actual audit separates measured issues from hypotheses that need a user test.
You keep the agreed project files and source. This sample illustrates the handoff; it is not a client result.
Audit questions.
What will we receive after the audit?
You receive a findings ledger, annotated screens, a prioritized backlog and a review call. The scope states how many screens and user journeys we inspect.
How long does a UX audit take?
Audit scopes run from five to ten business days. Access, screen count and any user research are agreed before the schedule starts.
Do you need access to analytics?
Analytics help us identify where people leave a flow. When access is unavailable, we label those limits and avoid presenting a review opinion as a measured conversion result.
Will you fix the issues during the audit?
The audit delivers the diagnosis and backlog. Design or development work follows a separate scope so you can decide what to implement and who should do it.
Can you audit a prototype before launch?
Yes. We can inspect a clickable prototype and review task clarity, interaction states and accessibility concerns. We cannot measure live conversion or field performance for an unreleased product.
How do you prioritize findings?
We consider the effect on the user task, the evidence behind the issue and the likely effort to resolve it. The backlog distinguishes urgent blockers from improvements that need further validation.
Do you promise a conversion uplift?
No specific uplift is promised. We document the baseline where data exists and recommend how your team can measure the effect after each change.
Can we keep the report without commissioning a build?
Yes. The report and backlog are yours. You can implement the recommendations internally, hire another team or ask us to scope a design and build phase.
Scope your audit.
Tell us the product, the flows that worry you and who uses them. A fixed proposal follows within five business days.