Technical Writing & API Documentation

Bad documentation is expensive in a way that's hard to see on a balance sheet. It shows up as support emails, as the same question asked four times a week, as a customer who bought the thing and quietly gave up on setting it up.

Good documentation is mostly a writing problem, not a technical one. Someone who knows the product deeply is usually the worst person to explain it, because they can no longer remember what it was like not to know. That gap is the job.

What We Document

• API documentation — endpoint references, request and response examples, authentication flows, error tables.
• User manuals and guides — the walkthrough that ships with the product or lives in the help centre.
• Installation and integration guides — step-by-step setup, including the steps everyone forgets to write down.
• Knowledge base articles — the searchable answers that stop the same ticket arriving repeatedly.
• Release notes and changelogs — written so a customer can tell whether an update affects them.

Written For the Person Who Has to Follow It

The test we apply to every piece is simple: can someone who has never seen this system get to the end without guessing? That means numbered steps that match what's actually on screen, plain descriptions of what each parameter does, and worked examples rather than abstract syntax. It also means saying what happens when something fails, which is the part most documentation skips and most readers need.

You Don't Have to Hand Over a Spec

Most clients don't have a tidy source document to pass along — they have a working product, a few scattered notes, and the knowledge in their head. That's a normal starting point. We work from whatever exists: a demo, a screen recording, an existing half-finished draft, or a conversation. The drafting is ours; what we need from you is corrections on the draft, which is far less work than writing it.

Why This Costs More Than a Blog Post

Technical writing starts at $200 for 1,000 words, with two rounds of revisions included. It sits above general content writing because it takes longer — accuracy has to be verified against the actual product, not just read for tone. Ongoing documentation work is usually better handled through a monthly plan; see the pricing page for how those compare.

Who Needs This

Software companies, equipment manufacturers, and any Ontario business shipping something with a setup process. If your support inbox keeps answering the same question, or a launch is being held up because nobody wants to write the manual, that's the situation this service exists for.