Services

Documentation systems built for engineering teams

Good documentation doesn't explain what your product does. It shows users how to succeed with it.

Core

Documentation engineering

Scalable systems that grow with your product.

Best for: teams scaling docs or migrating off legacy tooling.
What's included
  • Docs-as-code implementation (Git, Markdown, static site generators)
  • Documentation architecture and information design
  • Content management system setup and migration
  • Automated publishing workflows and CI/CD integration
  • Style guide development and content standards

API & developer docs

Reference developers actually use.

Best for: SaaS platforms, integration providers, developer tools.
What's included
  • API reference documentation (REST, OpenAPI/Swagger)
  • Getting started guides and tutorials
  • Code samples and interactive examples
  • Authentication and error handling documentation
  • Developer portal content strategy

Technical writing

End-to-end docs for software and complex systems.

Best for: companies needing comprehensive product documentation.
What's included
  • User guides and product documentation
  • Administrator and installation guides
  • Release notes and changelogs
  • Knowledge base articles
  • Troubleshooting and FAQ content

Specialist

Audit & strategy

Evaluate what exists and build a roadmap.

Best for: teams unsure where to start.
What's included
  • Content inventory and gap analysis
  • Usability and findability assessment
  • Metrics setup and baseline measurement
  • Prioritized improvement recommendations
  • Implementation roadmap

Technical editing

Polish existing content for clarity and consistency.

Best for: in-house writers who need expert review.
What's included
  • Developmental editing (structure, flow, completeness)
  • Copy editing (grammar, style, consistency)
  • Technical accuracy review
  • Style guide compliance
  • Accessibility improvements

Consulting & training

Build your team's documentation capability.

Best for: organizations building a docs practice.
What's included
  • Documentation process assessment
  • Tool selection and implementation guidance
  • Team training and workshops
  • AI adoption strategy for documentation
  • Ongoing advisory support

How I work

1

Discovery

We discuss goals, audience, and pain points. I review what exists.

2

Proposal

Clear scope, timeline, and fixed-price quote. No surprises.

3

Collaboration

Regular check-ins using your tools and workflows.

4

Delivery

Production-ready documentation with source files and handoff support.

Where I work

SaaS & software Integration platforms Healthcare IT Enterprise software Scientific instrumentation

What I use

MadCap Flare Oxygen XML Markdown AsciiDoc DITA OpenAPI / Swagger Postman Git & GitHub MkDocs Jekyll Hugo Confluence Intercom Claude

Not sure which one you need?

Describe the problem. I'll tell you which approach fits and roughly what it takes.

Get in touch →