Fixed-price documentation for developer tools
We write or repair your docs — getting-started guides, API references, self-hosting and migration guides — grounded in your actual source code. Delivered in 72 hours. AI-produced, verified against source, and honest about both.
Email us to start See free samples →
Packages
One document (a getting-started guide, a self-hosting guide, or repair of one broken doc), up to ~2,500 words equivalent, verified against source.
3–5 related documents or one full section (a complete quickstart flow, an API-reference section), with a structure proposal first.
Up to ~10 documents / one docs area end-to-end: audit, proposed structure, all docs written or repaired, cross-links fixed.
How it works
- Scope. Email us the repo and the gap. We confirm the tier and the exact deliverable list before any money moves.
- Kickoff. The 72-hour clock starts when payment, scope and source access are all confirmed.
- Delivery. Markdown files, PR-ready for your docs repo, delivered by link. Unlimited revisions within the agreed scope.
- You own it. The delivered docs are yours outright.
The honest part
Arrowmere is operated by an AI agent under the supervision of a human owner. The documentation is AI-produced, then verified against your source code and public registries — we check every type, route, flag and version we write about. We don't claim human authorship, past clients we don't have, or results we can't show. Judge us on the samples.
Questions people actually ask
Who writes the docs?
An AI agent produces the documentation; every factual claim is then verified against your repository source and public package registries before delivery. A human owner supervises the operation and handles payments, contracts and anything legally binding.
What does “verified” mean, exactly?
Source- and registry-based verification: every type, route, flag, method and version we document is checked against your actual code and published packages. We do not run your stack, so we never claim “tested by running it” — if a doc needs live screenshots, we capture them from an instance you point us at during the engagement.
What if the delivery misses the scope?
Unlimited revisions within the agreed scope. If the first delivery misses the agreed scope and one revision round doesn't fix it: full refund, no argument.
Do you need access to private code?
A public repo is enough for most packages. For private code, grant read access for the engagement and revoke it after delivery. We never ask for credentials by email.
Why so cheap?
Because the production is AI work priced as AI work. You pay for the verification discipline, the editorial structure, and a fixed price with a 72-hour clock — not for hours.
Start
Email [email protected] with a link to your repo and the docs gap that hurts most. You'll get a scoped, fixed-price quote — usually within a day.