Six services, one method
Every service follows the same six stages: discovery, deconstruction, structuring, documentation, validation and delivery. Take one, or combine them on a retainer.
A project
A defined piece of work with a fixed scope and price.
- Documentation audit and gap analysisfrom $3,000
- Information architecture designfrom $5,000
- Documentation debt remediationfrom $8,000
- Compliance documentation packfrom $10,000
- Platform migration documentationfrom $12,000
- Full documentation buildfrom $25,000
A monthly retainer
Your documentation kept current with every release.
- Startup: one core service, monthly reviewfrom $2,500
- Growth: up to three services, fortnightly reviewfrom $6,000
- Enterprise: all services, weekly review and governancefrom $15,000
Prices are starting points. Every engagement is quoted in writing after a discovery call.
When users can find answers quickly, support costs fall and onboarding speeds up. We write documentation that helps people get value from your product without asking for help.
The problem
Documentation gets written once, then falls behind the product. Support tickets rise, onboarding stalls and users give up before they see what the product can do.
What you get
- Getting started guides that get new users to their first success
- Feature documentation written for users, not engineers
- How-to guides and tutorials for common tasks
- FAQs and troubleshooting guides
- In-app help and tooltip copy
- A help centre that is structured, searchable and maintained
Clear technical documentation turns integration into an advantage. Poor documentation turns it into a barrier that costs you users and partners.
The problem
Reference docs drift from the code, examples stop working and developers learn the API by reading support threads. Every integration takes longer than it should.
What you get
- API reference documentation for every endpoint, field and error
- Integration guides for the paths customers actually take
- SDK and library documentation
- Code samples and tutorials that run
- Architecture and system documentation
- Changelog and versioning documentation
In regulated industries, documentation is the difference between passing an audit and failing one, and between closing a deal and losing it.
The problem
Policies are out of date, procedures don't match what teams actually do and evidence is scattered. The gaps surface at the worst moment: an audit, a due diligence request or an enterprise security review.
What you get
- Regulatory framework documentation
- Audit-ready document libraries
- Policy and procedure documentation
- Data privacy and security documentation
- Compliance reporting templates
- Ongoing maintenance as rules and products change
Release notes are often the last thing written and the first thing users read. They set expectations and show that a product is moving.
The problem
Notes are rushed out on release day, inconsistent from one version to the next or missing entirely, so users discover changes by accident.
What you get
- User-facing release notes
- Technical changelogs
- Stakeholder release summaries
- In-app release announcements
- Templates and a style guide your team can keep using
When knowledge lives in people's heads, the business is fragile. Onboarding is slow, decisions are inconsistent and people leave with what they know.
The problem
Wikis grow without structure until nobody trusts them. The real answers sit in chat threads and with the two people who have been there longest.
What you get
- Knowledge base architecture and design
- Process and procedure documentation
- Onboarding documentation
- Team and department wikis
- Decision logs
- Ongoing maintenance
Documented processes give teams one source of truth. Decisions are consistent, onboarding is faster and risk goes down.
The problem
Processes are passed on by word of mouth, done differently by each team and only written down after something goes wrong.
What you get
- Standard operating procedures
- Runbooks and incident response guides
- Workflow and process maps
- Training and onboarding documentation
- Quality assurance documentation
- Process audit and gap analysis
Not sure where to start?
An audit is usually the right first step. Book a call and we'll tell you what we would fix first.