Where are you right now?

Every engagement starts differently.
Find where you fit.

Your documentation should answer questions before they reach your team.

Instead, users still rely on your team for answers that should already be documented. The knowledge exists, but it is stuck inside the people who built the product.

Let's turn that knowledge into documentation your users can rely on. Start a conversation →

You have writers. You don't have a system.

Everyone is documenting, but everyone is doing it differently. There is no shared style guide, no reliable workflow, and no clear owner when things fall behind.

Let's build the system behind your documentation. Book a documentation strategy session →

You're a technical writer figuring out what's next.

Maybe you've gotten your first role, you're trying to get started with API documentation, or you're looking for your place in open source. I'll help you make sense of the path with lessons from my own journey.

Get guidance from someone who's been there. Apply for mentorship →

Services

The full documentation stack — end to end.

API Documentation

REST API references, OpenAPI spec documentation, authentication guides, migration content, and changelog management. End-to-end ownership from first draft to shipped product.

  • API reference documentation
  • Getting started guides
  • Authentication & security docs
  • Migration guides
  • Developer portal content
  • OpenAPI spec reviews
View samples →

Product Documentation

User guides, onboarding content, feature documentation, and release notes for SaaS, cloud, and developer platforms.

  • User guides & tutorials
  • Feature documentation
  • Onboarding content
  • Release notes
  • Knowledge base articles
  • Admin & configuration guides
View samples →

UX Writing

Interface copy, microcopy, error messages, onboarding flows, and naming conventions. Content design that reduces user friction and improves product clarity.

  • UI text & microcopy
  • Error messages & empty states
  • Onboarding flows
  • Naming conventions
  • Content audits
  • Style guide development
View samples →

Documentation Operations

Documentation infrastructure, CI/CD pipelines, linting automation, and docs-as-code implementation. Build systems that scale with your team.

  • Docs-as-code setup (Hugo, Docusaurus)
  • GitHub Actions CI/CD pipelines
  • Vale linting integration
  • AI-assisted authoring workflows
  • Documentation site deployment
  • Process design & knowledge transfer
View samples →

Documentation Strategy & Consulting

Strategic documentation audits, content strategy, information architecture reviews, and team enablement.

  • Documentation audits
  • Information architecture
  • Content strategy
  • Style guide creation
  • Team training & workshops
  • Documentation roadmaps
View samples →

Looking for a specific type of documentation work?

Book a Discovery Call

How I Work

I approach documentation like an engineer.

Before writing anything, I understand the system behind the product by looking through the codebase, support conversations, and product history. By the time I write the first sentence, I already know where the gaps are.

Step 01

Discovery

I look at what you have, what is missing, and where users or teams are running into problems. Before writing anything, I build a clear picture of your documentation gaps and what needs to change.

↳ Documented gap analysis
Step 02

System Design

Writing is only part of the job. I design the structure, tooling, style decisions, and workflows that make documentation easier to maintain long after the project ends.

↳ Architecture that scales
Step 03

Build & Hand Off

This is where everything comes together. I write the documentation, build the workflows that keep it accurate, and make sure your team leaves with something they can confidently own. The engagement ends. The system doesn't.

↳ Docs + the system that keeps them accurate

Why not just hire an agency?

Most people who ask this question already know the answer.

Agencies are built for volume. This engagement is built around your specific problem.

Book a discovery call

I was an engineer before I was a technical writer.

Before I documented code, I wrote it. That means I can work directly with engineers, understand the code, and ask better questions before I write.

You deal with one person. All in.

From the first conversation to the final delivery, you get direct access to an experienced technical writer who understands your product, your users, and your team. No sharing context between people. No losing details along the way.

The system outlasts the engagement.

I build CI/CD pipelines, linting rules, and AI review workflows into the documentation process. When I leave, the infrastructure remains.

I've done this at real scale.

300+ API endpoints. 20+ product areas. Sole writer at a fast-moving team. I've seen the problems that come with documentation at scale and know how to work through them.

Let's build better documentation.

Whether you're scaling a docs team, starting from scratch, or trying to make your documentation easier to maintain, I'd love to help.

Free Resource

The AI Documentation Pipeline

A practical guide to building documentation workflows with automated checks, linting, and AI-assisted review.