Service
I go through your docs, APIs, SDKs and onboarding as a new developer would, and you get a prioritised list of what to fix.
You find out where developers get stuck before they give up, and what to change first. The audit has a fixed scope, so you know what you get and when.
For clients in Germany, 19% VAT is added to the invoice. For clients abroad, I invoice the net amount and you account for the tax in your own country, for example through reverse charge. Please make sure your business can do that.
Is this for you?
What I look at
We agree on the exact scope before we start. These are the areas an audit usually covers.
Every step from landing on your site to a first working result.
Whether people find the answer, and whether the answer is complete.
Naming, consistency, types and how predictable your API behaves.
Installing, configuring and using your SDKs, CLIs and templates.
Whether an error message tells developers what went wrong and how to fix it.
Whether they're complete, runnable and match what people build.
What you get
Each finding says what happened, why it matters and what to change, ordered by impact. Here's an illustrative example.
New developers almost always hit this on their first request. The response doesn't say what's missing, so they leave the docs to search for it. Name the missing field and link to where the key comes from.
HTTP 400 Bad Request
{ "error": "invalid_request" }HTTP 400 Bad Request
{
"error": "missing_api_key",
"message": "Add your API key in the Authorization header.",
"docs": "https://docs.example.com/auth"
}How it runs
We agree on scope, audience and the developer journeys that matter most.
I go through those journeys as a new developer and note every place I stumble.
I look at the docs, API and SDKs behind each stumble and work out what to change.
You get the prioritised findings, and we go through them together with your team.
Being clear about scope is part of the deal.
TypeScript and JavaScript, frontend and backend, including Node.js and Deno. Typst too. PHP and some other languages on request.
A test account or sandbox access, access to your docs and repositories (including unpublished drafts, if relevant), a short description of who your developers are, and a contact person on your team.
The audit focuses on people. Semantic docs and intuitive APIs work for language models too, so better results with AI tools follow from good developer experience.
Tell me about your product in a short call. If an audit isn't the right fit, I'll say so.
Prefer email? Write to me directly