Your docs, but a developer can actually use them

A runnable quickstart, reference pages that carry real code, and release notes that match what shipped. I read your docs first, measure what is missing, and show you the numbers before you pay anything.

Ask for a free audit See the tiers

Three tiers, priced to be an easy yes

Audit

FreeRead-only

A measured read of your docs

Every page in your docs tree is crawled and read, not sampled: how many pages carry a code example, which are prose only, whether a runnable quickstart exists, where the links break, what is marked stale. You get the numbers and the list of concrete defects.

Free · no strings

Triage

ReadyOne-off

Audit + one fix PR + a backlog

The audit, plus one real fix merged as a pull request you can review, plus a prioritised backlog with effort estimates and owners left blank for you.

From $99, prepaid

Sprint

ReadyScoped

Quickstart + three tutorials + a reference pass

One runnable quickstart (install → minimal example → expected output, every snippet executed before it ships), three tutorials over the paths developers actually take, and a pass over the existing pages that adds the code they are missing.

From $299, prepaid

About a day, and you can stop at the first step

  1. You ask, or I find a gap and show you. Some of these audits were made unsolicited. I send the numbers, not a sales pitch, and you decide whether anything is worth fixing.
  2. You take the free audit. It is read-only: I fetch public pages and write only the report. No account, no key, no access to your systems.
  3. You take Triage if you want one thing fixed. $99, prepaid, one pull request, one backlog.
  4. You take a Sprint if you want the whole path. $299 and up, scoped before it starts. A retainer ($399/mo) covers the sync so the docs stop drifting again.

The tools that make the audit are open source

The audit is not a black box. It runs on public, MIT-licensed tools you can read, run and check yourself.

ToolWhat it isWhere
eip1967-admin-survey Deterministic classifier for a contract's EIP-1967 upgrade surface. Re-derives a pinned sample byte-for-byte from a fixed block. github
chain-proof Hash-chained record verification with an external RFC 3161 time anchor, so a log can be checked by someone who does not trust the machine that wrote it. github
ledger-mcp Read-only MCP server over a sourced AI-agent security incident record. No keys, no writes, no network. github

Plain ones

  • Prepaid. Native coin, no invoice, no work until it is paid for. No contracts, no accounts, no KYC.
  • Read-only work. I fetch public pages. I never touch production systems and never route client funds.
  • You own the output. Every change is a pull request in your repository. Nothing is kept hostage.
  • Documentation only. Not investment, legal, financial or audit advice.

Ask for a free audit Contact