UX audit for Dev tools · Free · 10 a week
UX audits for developer tools
I read your docs, onboarding, and pricing the way a developer evaluating your tool at 11pm does, and mark what stands between them and their first successful call.
What I look for in Dev tools
-
Developers bounce before the first successful call
The time between landing and "it worked" is where you win or lose a dev. If the quickstart has a missing step, an unexplained key, or a copy-paste that fails, they close the tab and try a competitor.
-
The docs are a wall, not a path
Reference docs answer questions a developer doesn't have yet. Without one obvious golden path from zero to working, even a strong tool feels harder than it is.
-
Usage-based pricing hides the real cost
“Free to start” then a pricing page built around tiers and metered add-ons leaves a developer unable to answer the one question their boss will ask: what will this actually cost us?
What lands in your inbox
- A UX score — one number, 1 to 10, so you know where you stand.
- 3 critical blockers — the issues turning users away, in priority order.
- 5 quick wins — changes you can ship this week without a redesign.
- A copy read — where the words on the page add friction.
Those four are the same on every audit — what changes is what counts as friction for Dev tools. How the audit works, end to end walks through the method, and the UX audit checklist is the list I work through, published in full.
Narrow it down by page or flow
The four lenses stay the same; what changes is what counts as friction. Point me at the surface that matters most:
Questions
Can you audit our docs and quickstart?
Yes — that's often where the biggest wins are. I follow the golden path as a first-time developer would and mark every point where I'd get stuck or give up.
Do you need a sandbox or test key?
If completing the quickstart needs an account or an API key, send me a test one and I'll walk the whole first-call flow. If it's public, just send the URL.
You're not a developer on our stack — does that matter?
I audit clarity and friction, not your internals. If a competent developer can't get to a working call quickly, that's the finding, and it's usually the point.
What surfaces can you audit?
Docs, the quickstart, the signup and onboarding flow, or the pricing page. Tell me your goal and I'll recommend the one costing you the most developers.
How is the report delivered?
As a PDF within 24–48 hours, with annotated screenshots so anyone on your team can see exactly what I mean.
Why trust this audit
Product designer · Barcelona
Uxerfy is a UX audit service run by one person: send a URL, get back a PDF within 24–48 hours with a score out of 10, three critical blockers and five quick wins. I do every audit myself and put my name on it — here's who I am and how I work.
Verify me on LinkedIn →Here's a complete sample report. No email required — download it and see exactly what lands in your inbox.
Download a sample report (PDF) ↓Send me your URL and I'll take a look.
You'll have the report within 24–48 hours — a score, 3 blockers, 5 quick wins.
Get a free audit →