Skip to main content
The goal is to make the first step small and clear. If you have a documentation or developer-education problem, start with one of the two $350 entry points.

Choose an entry point

Paid Discovery

Documentation EngineeringUse this when your docs, getting-started flow, or technical reference need help. I review the current state and write a concrete recommendation. The $350 fee is credited if you continue with a larger docs engagement within 30 days.

Consulting / Review Sprint

Developer EducationUse this when a tutorial, article, onboarding message, or content plan needs review. I give you written recommendations and a prioritized list of fixes.

How the process works

1

Choose your starting point

Pick Paid Discovery if the problem is mainly documentation. Pick Consulting / Review Sprint if the problem is mainly content or developer education. If you are unsure, send a brief and I will recommend one.
2

Send a brief or book a briefing

Copy the brief template on the contact page and send it by email, Signal, or Telegram. Or book a 20-minute briefing.A useful brief includes:
  • Product and chain or platform
  • The surface that hurts: docs, tutorial, onboarding, or article
  • Audience: developers, integrators, validators, users, or another group
  • Budget band
  • Timing or deadline
3

Review the statement of work

You receive a short SOW with scope, price, timeline, and payment terms. Nothing starts until you approve it.
4

Work begins

I research, write, test where relevant, and deliver through pull requests, drafts, or published content depending on the engagement. One structured revision round is included.
I reply within 48 hours. If the project is not a good fit, I will say so and point you to a better option when possible.

Send a brief

Tell me the product, the surface that hurts, and your timing. Five lines are enough.
Prefer talking first? Book a 20-minute briefing.
See Pricing for the full list of packages and timelines.
Last modified on September 25, 2026