Technical writing and documentation
Docs your users actually finish reading.
We write and organise documentation for B2B software companies, so customers can set up your product on their own, developers can integrate without a call, and support answers the same question less often.
Talk about your docsQuick start
Create your first project in about ten minutes. You will need an admin account and an API key.
POST /v1/projects
{ "name": "Pilot" }Next: invite your team.
Illustrative page, not from a client project.
What we write
Documentation for each reader, from first-time users to the engineers connecting your API.
- 1
Product documentation
Setup guides, how-to articles and reference pages that follow how customers really use the product.
- 2
API and developer docs
Endpoint references, authentication guides and worked examples, checked against the live API.
- 3
Help centre content
Short, searchable answers to the questions your support team hears most often.
- 4
Internal knowledge bases
Runbooks, process notes and onboarding material your own staff can find and trust.
- 5
Information architecture
Reorganise existing docs so pages have one clear home and readers can find the next step.
- 6
Style guides and templates
A shared voice, terminology list and page templates, so engineers can write docs that fit.
How an engagement works
Four steps, with drafts reviewed by your subject experts before anything is published.
Audit
Read the current docs, support tickets and search terms to see what is missing or out of date.
Plan
Agree the readers, the structure and the first set of pages to write or rewrite.
Write
Interview your experts, test each procedure ourselves and draft pages for review.
Hand over
Publish, share the templates and agree who keeps each section up to date.
Which page do your users get stuck on?
Tell us about your product, who reads your docs and where they live today. We will reply with how we would approach it.
hello@briartide.com