I help technical teams see what's broken before it becomes someone else's emergency.
Usually that starts with documentation — but it often surfaces workflow gaps, tool overlap, and knowledge that lives nowhere. I inspect, diagnose, and deliver a clear priority list. 48-hour turnaround. No meetings required.
Fixed scope. Async delivery. Written findings.
Ways to work together
Documentation Audit
$500I review your docs architecture, content, structure, and tooling. You get a prioritized findings memo showing what's working, what's broken, and what to fix first, with quick wins at the top.
Every audit starts with an automated baseline from docs-score, then I layer in a manual review.
Audit + Implementation
$1,749Everything in the audit, plus I implement your top 3-5 fixes. Broken links resolved, content restructured, navigation cleaned up, schema problems fixed.
Start with the audit and upgrade if you want the fixes done rather than handed off.
Technical Systems Assessment
CustomFor teams whose problem is bigger than documentation: tool sprawl, undocumented integrations, workflow risk, and systems nobody fully understands.
Most engagements run $2,000-$5,000 and produce a clear findings memo: what you have, what overlaps, what's undocumented, and what to do next.
Not sure which fits? Start with the $500 audit. It is the lowest-risk way to get a clear picture. If the problem turns out to be bigger than docs, I will tell you.
What I actually work on
Documentation is usually the symptom. The deeper problem is that technical systems - tools, workflows, integrations, migrations, and team knowledge - grow faster than anyone audits them.
- +Docs nobody trusts but everyone still references
- +Tools adopted one at a time, with no shared inventory
- +Workflows that live in someone's head and break when they leave
- +Integration points nobody owns and nobody wants to touch
- +Systems that made sense when they were built and now slow everyone down
Recent examples: years-old Confluence sprawl nobody owns, broken Docusaurus builds that fail quietly, Notion exports turned into MDX cleanup projects, GitBook migrations where half the links died, and integrations documented once in 2021 by someone who left.
If your technical systems are the project no engineer wants to open, that is the work I do.
Why work with me?
- » 15+ years across developer tools, regulated fintech, and technical systems. At NinjaTrader I owned documentation for 40,000 users, led a support team of 15, and spent six years turning customer workflow problems into product and process improvements.
- » Migration experience under real customer pressure. At Ookla / Speedtest.net I helped ISP enterprise users and consumers move from Flash-era workflows to HTML5, JavaScript, and HTTPS without losing the plot for the people depending on the tools.
- » Async-first. No syncs, standups, or status meetings. Everything is delivered in writing, with a Loom walkthrough when a screen explanation is clearer.
- » Fixed scope, fixed price. You know what you are getting before you pay. No billable-hour ambiguity, no scope creep.
- » If I cannot find meaningful problems worth fixing, I will say so. The point is a clear answer, not a larger invoice.
See what an audit looks like.
Preview the memo format before you spend $500. The full sample is gated on purpose so I can learn what buyers actually need to inspect first.
Good fit
- + Small engineering teams at B2B SaaS companies
- + Developer tools, API platforms, and internal tooling teams
- + Mid-market ops and IT leads dealing with tool sprawl or workflow documentation gaps
- + Teams inheriting systems they did not build and need to understand quickly
Not a fit
- - Pure marketing blogs
- - One-off proofreading
- - Teams that need daily standups and ongoing project management
Start with the $500 audit.
You get a clear picture in 48-72 hours. Then you decide if you want the fixes implemented or the work scoped further.
If I cannot find meaningful problems worth fixing, I will say so.