Typical turnaround
5–10 days
Depends on product surface area and access to staging
UX audit · Product design · Heuristic review
User experience audits that turn friction into revenue
I review your product like a senior engineer and UX partner would: flows, information architecture, accessibility, and the moments where users hesitate, abandon, or misunderstand what to do next.
Overview
Most UX problems are not missing features. They are unclear hierarchy, overloaded screens, broken mental models, and flows that assume knowledge your newest customer does not have yet.
I run structured UX audits for SaaS products, marketplaces, and B2B tools — combining heuristic evaluation, task-based review, and engineering realism about what is expensive to fix versus what is a quick win.
You get a written report, annotated screenshots, severity-ranked issues, and recommendations tied to business outcomes: activation, retention, support load, and conversion — not abstract design opinions.
At a glance
Deliverable depth
40–80 issues
Ranked by severity, effort, and revenue impact
Best for
SaaS · B2B
Teams with live users and measurable funnels
What you get
Heuristic and task-flow review
Core journeys audited against established UX principles, your analytics signals, and what your ICP actually needs to accomplish in the first session.
Information architecture map
How navigation, labeling, and screen hierarchy help or hurt discoverability — especially for power features buried three clicks deep.
Accessibility snapshot
Keyboard, contrast, focus order, and form error patterns. Not a full WCAG certification, but the issues that block real users and create legal exposure.
Prioritized remediation roadmap
Quick wins vs structural fixes, with engineering effort estimates so your team can plan sprints instead of debating opinions.
Where UX audits usually find the highest-impact fixes
Based on aggregated findings across SaaS onboarding, settings, and checkout-style flows.
How it works
Day 1Kickoff — Goals, personas, analytics, and the flows that matter most to revenue.
Days 2–4Deep review — Desktop and mobile pass, edge cases, empty states, onboarding, and settings.
Days 5–7Synthesis — Severity matrix, annotated captures, and recommendation write-up.
Day 8+Walkthrough — Live session with your product and engineering leads — optional implementation support.
Outcomes teams care about
- Clear backlog your designers and engineers can execute without another workshop
- Shared language between product, engineering, and leadership on what “good” looks like
- Fewer support tickets caused by confusing UI and dead-end flows
- Higher activation when first-run experience matches user intent
Frequently asked questions
Do you need access to our codebase?
No. A UX audit is product-facing. Staging or production access plus analytics context is enough. I can optionally review component libraries if you want design-system alignment.
How is this different from hiring a design agency?
Agencies often deliver visual exploration. I deliver an engineering-aware audit: what to fix, in what order, and what it will cost to ship — from someone who has led frontend teams and shipped SaaS at scale.
Can you stay on to implement fixes?
Yes. Many teams use the audit as phase one and bring me in for targeted implementation, design system work, or staff-level frontend leadership.
What products are a good fit?
B2B SaaS, marketplaces, fintech dashboards, and internal tools with real users. Early prototypes can be reviewed too, but the highest ROI is usually after you have usage data.
Ready for an honest UX audit?
Tell me what product you are building, your main conversion or activation metric, and timeline. I will reply with scope, price, and availability.