Technical writing and documentation
Good documentation turns working software into software people can actually use, and we write it next to the developers who build it.

Software that nobody understands is hard to adopt, hard to support and hard to hand over. Documentation closes that gap. It answers the questions users, new developers and support staff would otherwise bring to your team again and again.
Why clear documentation matters
Most teams know their docs are behind. The code changes weekly, and the pages describing it change once a year, if at all. The result is familiar:
- New developers spend their first weeks asking questions that a good page could answer.
- Support tickets repeat the same few problems.
- Integrators guess at API behaviour and guess wrong.
- Knowledge sits in one person's head, and leaves when they do.
Writing things down well is not a luxury. It is part of making a product maintainable.
What we write
User guides
Task-based instructions for the people who use your product. We start from what the reader is trying to do, not from the menu structure, and we keep steps short and in order.
API references
Endpoint descriptions, parameters, example requests and responses, error cases and authentication notes. A good reference lets an integrator succeed without sending an email. We pair it with a short getting-started page so the first call works quickly.
Release notes
Plain summaries of what changed, who it affects and whether anyone needs to act. We separate new features, fixes and breaking changes so readers can scan for what matters to them.
Onboarding docs
Setup guides, architecture overviews and conventions for developers joining a project. These are especially useful for distributed teams, where a colleague is not always available down the hall. See how this fits into our wider way of working.
How writers work with developers
Accuracy comes from proximity. Our writers sit inside the project rather than waiting for a finished build.
- Join the conversation. Writers attend planning and review sessions, so they hear about changes early.
- Read the code and run the product. Every instruction is tried by hand before it is published.
- Draft, then review with the author. The developer who built a feature checks the page for technical errors.
- Keep docs in the repository. Where it suits the team, documentation lives beside the code and changes in the same pull request.
- Update with every release. A change is not finished until its page reflects it.
Writing style
We aim for plain sentences, consistent terms and examples that can be copied and run. Jargon is explained once, then used consistently. Each page covers one purpose and says so at the top.
Where it fits
Documentation work pairs naturally with web application development, mobile apps and maintenance and support. If you are preparing a project, our guide on how to brief a development project is a good place to start, and you can see other roles on the careers page.
Have a project that needs better docs? Get in touch through the contact page.