SaaS documentation · complete user docs set
SaaS docs your users actually read.
Fifty pages that cover the whole customer journey of your product, from sign-up to power-user features and admin settings, organised the way your users look for answers, with documentation organisation methods such as Diátaxis, and published from your repo. Written by senior writers with our AI agents accelerating the mapping and first drafts.
25-day delivery · 2 free revisions
What changes for your team
- Fewer onboarding questions: getting-started and feature guides answer them before support does.
- One structure users can predict: tutorials, how-to guides, concepts and reference, each in its place.
- Docs that ship with releases: Markdown in Git, reviewed like code, published automatically.
- A style guide and templates your team can keep writing with after hand-over.
Deliverables
- Customer-journey map with the page plan (validated before writing)
- 50 pages: getting started, feature guides, concepts, admin, reference
- Structure that fits the product (Diátaxis or another method), navigation and search configured
- Docs-as-code publishing from your repository
- Style guide, page templates and contributor guide
Standards, tools and formats
- Diátaxis
- Customer-journey mapping
- Markdown · MDX
- GitBook · MkDocs · Docusaurus · Mintlify
- Docs-as-code · Git · CI
- Screenshots & annotated UI
- Vale · style linting
- AI-assisted drafting
- English · French
How the engagement runs
- Map the customer journey From your product, Jira and a few interviews we map what users do at each stage, sign-up, first value, daily use, admin, and the pages each stage needs. Our elicitation agents draft the map; you validate it.
- Draft the 50 pages Getting started, feature guides, concept pages, admin and reference, drafted against the map, accelerated by our AI writing agents, rewritten and checked by senior writers against the live product.
- Organise & publish The set is organised the way your users look for answers, with search and navigation in place: by task, by product area, by audience, using documentation organisation methods such as Diátaxis, and published docs-as-code, GitBook, MkDocs, Docusaurus or your platform, from your repo.
- Hand over Style guide, page templates and a contributor guide, so your team adds the next feature's pages the same way, or we keep them current under a monthly plan.
Add-ons
- Second set of 50 pages
Questions
What if we need more than 50 pages?
Additional blocks of 50 pages are priced at the same rate. Most SaaS products land between 50 and 150 pages; the map tells us the number before we start.
Do you need access to the product?
Yes, a test account with the roles your users have, and a short interview per product area. Our elicitation agents do the rest of the extraction from your Jira and existing material.
Which platform will the docs be on?
Yours: GitBook, MkDocs, Docusaurus, Mintlify or another docs-as-code platform. If you have none yet, the docs-as-code setup service adds one.
Can the set be bilingual?
Yes, we write natively in English and French. A second language is quoted as a block of pages at the same rate.