Docs-as-code engagement
I work with docs-as-code principles and treat documentation as an essential product surface. Typical work includes:- Reviewing and improving existing documentation through pull requests
- Fixing broken or outdated flows and adding practical examples
- Rebuilding high-value sections (Getting Started, core concepts, key integrations)
- Improving structure and clarity for both human readers and LLMs
- Aligning documentation with the actual code and product behavior
- Ongoing ownership so docs stay accurate as the product evolves
Packages
All prices are in USD, and full pricing terms are on Pricing.Paid Discovery
$350 · ~1 week
- Short engagement to understand the current state
- Optional small goodwill fixes
- Clear written recommendation of the highest-value next step
- Fee credited if you proceed with a Docs Health Check or Focused Section Rebuild within 30 days
Docs Health Check + Quick Wins
$925 · ~2 weeks
- Broad review of the full documentation surface
- Priority given to critical paths
- Implementation of the highest-leverage fixes via PRs
- Examples, clarity, broken steps, small structural improvements, LLM-friendliness
- Short summary + prioritized backlog of deeper work
Focused Section Rebuild
$2,150 · ~3 to 4 weeks
- Deep work on 1 to 3 high-value sections
- Thorough research and testing of those sections
- Possible restructuring + major rewrite
- Complete examples, edge cases, and strong structure
- Delivered via well-described pull requests
Docs Partnership
$3,500 / month · Ongoing (60h / month cap)
- Ongoing part-time ownership of a defined documentation surface
- Continuous updates aligned with product changes
- Prioritized backlog management
- Regular progress check-ins
Need something outside these packages? Just say what you need. Custom scopes are normal and expected.
How the engagements differ
Paid Discovery
A short, fixed engagement that produces a clear recommendation of the highest-value next step (usually a Health Check or a Focused Section Rebuild). The fee is credited if we proceed within 30 days.Docs Health Check + Quick Wins
Breadth plus prioritized implementation. I review the entire documentation surface, focus on the most important journeys, and implement the highest-leverage fixes via pull requests. This is not a full rewrite of major sections.Focused Section Rebuild
Depth on a defined surface. We deliberately choose 1 to 3 high-value sections, and I go deep: research, real testing, possible restructuring, and major rewrite.Docs Partnership
Part-time, continuous responsibility for keeping a defined area of the documentation accurate and useful as the product moves. I work in focused blocks, typically reserving 15 hours per week per client.How I work
1
Briefing / Discovery
We clarify goals, current state, target audience, and constraints. For larger or unclear scopes I recommend starting with Paid Discovery.
2
Access & Research
I get temporary access to the docs repository (and related code when needed) and study the current state.
3
Implementation
I work directly in the repository and open pull requests with clear descriptions.
4
Feedback & Iteration
One structured revision round is included. Additional rounds or significant scope changes may carry a revision fee.
5
Delivery & Next Steps
Work is merged (or ready to merge). I provide a short summary and, when relevant, a clear recommendation for the next highest-value engagement.
Selected Work (Portfolio)
Full case cards, including context, what shipped, and what was not done, live on Work.- This website was built as a documentation page with Mintlify, using docs-as-code principles. Github Repo: @vinibarbosabr/thecoding-docs
- 0xramp.app documentation built with Mintlify. Self-serve / co-built work: I fully engineered and edited the documentation; the lead developer owns the app. Github Repo: @0xramp-labs/0xramp-docs | Site: docs.0xramp.app
- Minor contributions to @near/docs, @multiversx/mx-docs, @near-daos/sputnik-dao-contract.
Ready to start?
Send a brief
Tell me the product, the surface that hurts, and your timing. Five lines are enough.

