Work with me¶
I produce technical documentation for complex systems. Hardware, software, processes, architecture. Specifications that a competent stranger can follow without calling you. Build guides that hold up in the field. Reference documentation built to last.
What I bring¶
Twenty years inside complex IT projects. Five of those as the recognised documentation specialist in a large enterprise environment. I know what documentation looks like when it fails — because I spent years fixing it.
I came up as editor-in-chief of a technology monthly. I know the difference between a document that is technically accurate and one that a human can actually use.
I work with AI tooling daily, not experimentally. The libdrone documentation stack — variables file, payload SDK, hardware specification, build guides, master specification — was produced by one person with a clear architecture and the discipline to follow it. That is the standard I work to.
How an engagement works¶
I work remotely, on a project basis. A typical engagement starts with an audit — I read what exists, identify the structural problems, and propose an architecture before writing a word. Then I build: usually a documentation framework first, then content in priority order, with review cycles as we go. I do not disappear for three months and reappear with a document. You see the work in progress.
I am one person. That means no account managers, no junior writers producing content I then have to fix, no overhead. It also means I have a finite capacity and I choose projects where the subject matter is worth understanding properly.
Rates and timelines depend on the scope. The right way to start is a short email describing what you are trying to solve.
What I do not do¶
Ghost-writing for people who want credit without work. Documentation as an afterthought bolted onto a finished product. "Just make it look nice."
Good documentation is designed before it is written. If you need someone to polish existing content, I am probably not the right person. If you need someone to build the architecture and then fill it, I am.
Who it is for¶
- Open hardware and open source projects that need documentation serious enough to attract contributors and institutional interest.
- Engineering teams that ship good products with terrible documentation and know it.
- Startups that need their internal knowledge made legible before it walks out the door with the person who holds it.
- Organisations that have been burned by documentation consultants who do not understand the technical subject matter.
The portfolio¶
Read it. That is the work. If that is the standard you need, get in touch.
Get in touch¶
No intake forms. No discovery calls unless you want one. Email is fine.