Docs written and tested by an engineer

Your product might be great. Your docs still have to get a new developer to their first working result.

For API, SDK, AI, infrastructure, open-source, payment, mobile and SaaS teams whose quick start, tutorials, examples or troubleshooting pages are putting people off.

Start the docs fit check See scope and pricing Read a technical sample

No mail app? Copy the fit-check questions.

Copy the questions below and send your answers to this address from any email:

hello@mikeoladapo.com

Fit-check questions

Product or repository URL:
Who the documentation is for:
The first developer outcome that matters:
Current docs URL:
Known support or onboarding problems:
Required SDK, API, framework, or language:
Target publication date:
Available budget:
Anything else I should know:

Copying this text does not send anything.

Who this is for

There's a real product I can test

An API, SDK, code repository, dashboard, command-line tool or test environment. I work from the product itself, not from the marketing copy.

One thing a developer needs to do

Install it, log in, make the first request, deal with an error, or finish one typical integration.

The docs can be checked

The examples should run, what you need beforehand should be spelled out, and the troubleshooting should cover errors people actually hit.

Start small

Three options

Docs Triage

$300

Delivered within 48 hours

A review of one setup or integration guide
The gaps that trip people up most, in order
A short rewrite and a plan for the rest

This doesn't include rewriting all your docs.

Developer Docs Rescue

From $1,500

Five business days

Your quick start or install guide rewritten and tested
One complete end-to-end tutorial with code examples
Error and troubleshooting pages, and a list of what else is missing

Best for one SDK, API, CLI, or product integration.

Technical Launch Content Sprint

From $2,500

Seven to ten business days

Two technically verified tutorials
One engineering case study or product guide
Ready to publish, with short versions for social media

For teams who need launch material developers will trust, not generic AI-written content.

How I work

Use the product first

I go through the guide like a new developer would, and note every assumption, missing step, unclear word, broken example and place where you'd get stuck.

Write around what the reader needs to get done

Each page is built around what the reader has to do, what they should see when it works, and what to do when it doesn't.

Check the final examples

Commands, requests, setup steps and code examples are all run against the agreed version of the product before I hand over.

Background

An engineer who also writes

I build products with Next.js, Laravel, React Native, Expo, SwiftUI, Python, APIs, payments, PostgreSQL and Supabase, and I write regularly about AI and getting products ready for real customers. So I can check whether your docs are actually right, not just tidy up the wording.

Read: twelve acceptance tests for an AI-built SaaS.

Not included

Making up how the product behaves, or claims about performance nobody has tested.
Writing a whole documentation site in five days.
Publishing examples I can't test against the product.
Unlimited revisions across other products, versions or audiences.

Next step

Send me your docs link and the first thing a new developer should be able to do.

I'll tell you whether to start with the $300 review, the five-day docs rescue or the bigger content sprint.

Start the docs fit check