Documentation as a service
Product docs, developer docs and help centres for SaaS and API-first companies. We check yours before we say anything about it.
Asked 6 times this week
How do I rotate an API key?
docs / api / authentication
Rotating an API key
POST /v1/keys/rotate
Authorization: Bearer •••••AI assistant
Create the new key first, deploy it, then revoke the old one.
cited · docs/api/authentication
We write into the tools you already use
Start here
Your team already knows how the product works. Most of it lives in people’s heads, old Slack threads and support replies, so it gets explained again every time somebody asks.
We write it down once, properly, and keep it that way. Product docs, developer docs and help centres for SaaS and API-first companies.
You get a documentation site, not a hiring problem.
The cost, drawn out
One customer, one question, two versions of your company. The difference is not effort. It is whether the answer was written down once.
Today
Three people. Nothing written down.2 to 4 daysEvery answer is written from scratch, by someone senior, and then lost in a thread. The next person asks the same thing next week.
What you gain
The questions your team answers most become pages, and stop coming back.
Customers and developers reach their first success without a meeting.
Sales, support and engineering describe the product the same way.
Assistants answer from your words instead of inventing their own.
“Rotate the key, then redeploy.”
cited: docs/api/authenticationDocs pages rank for the specific problems buyers type into Google.
paperkraft.co › docs › webhooksWhy a webhook fires twice
Technical buyers evaluate you at their own pace, before the first call.
evalsigned
Why this matters
When something breaks, people ask an AI before they open a ticket. What it tells them comes from your docs, or from a guess.
Services
01
Endpoint references, authentication, errors, rate limits and working examples, written so a developer can integrate without asking you a single question.
02
Setup guides, feature explanations and how-tos in plain language, for the people who buy and use the product.
03
Information architecture, navigation and a docs site that holds up as your product grows.
04
reset my password
The self-serve answers that take the repeat load off your support team.
05
Pipelines that keep pages in step with your releases, so docs stop drifting out of date.
How we work
Step 1
Human-led
A 30-minute call on your product, your support queue and whatever docs exist today. You leave knowing what is worth writing first.
Step 2
Human-led
We agree on the map before a word is written: what pages exist, who each one is for, and where a reader lands first.
Step 3
Human + agent
Agents draft from your code, your tickets and your release notes; we rewrite what they get wrong and follow every instruction ourselves on a clean setup.
Step 4
Human-led
Navigation, page layout, code samples and search. So the reader gets to the paragraph that answers them, not just the right page.
Step 5
Human + agent
Published into your own setup. Agents watch your releases and flag the pages a change just made wrong, so nothing quietly goes stale between reports.
v2.2v2.3v2.4 docs shipped same day
How the work gets done
We are not typing your docs out by hand, and we are not letting a model publish straight to your domain either. Machines do the work that is mechanical and endless; the judgment stays with the people who own the outcome.
Agents
People
The basics
Read it the way you would read a docs site: pick a page on the left.
docs / basics / what-are-docs
Documentation is your product explained in writing: what it does, how to set it up, what each screen and each API call means, and what to do when something breaks.
Every company already has this knowledge. Most keep it in people’s heads, old Slack threads and support replies, so it gets explained again and again, slightly differently each time.
If a customer or a developer can ask it, there should be a page that answers it.
docs / basics / why-docs
Because the same questions arrive every week, and answering them by hand does not scale. A written answer is read hundreds of times; a support reply is read once.
Docs also decide how fast someone gets value from your product. A customer who can find the answer at 2am stays; one who waits until Monday often does not.
Support links a paragraph instead of writing one, and trials stop stalling quietly.
docs / basics / docs-and-ai
AI assistants answer questions about your product by reading whatever is public. Your documentation is the source they quote. And when there is none, they improvise.
Structured pages make that reliable: clear headings, stable anchors, real examples and version metadata give an assistant something specific to cite instead of a guess.
A wrong AI answer about your product is still your support ticket.
docs / basics / structure
No. A long unstructured page hides the answer as effectively as having no page at all, search returns the document, not the paragraph the reader needed.
Structure is what makes docs usable: one question per heading, predictable navigation, tested steps, and metadata that says when the page was last true.
Having docs is not the goal. Being able to find the answer inside them is.
docs / basics / non-technical
Yes. Documentation is just the written answer to anything a customer or a developer might ask, and that is not a technical idea.
We write for the reader you actually have. Plain-language guides for customers, precise references for developers, and nothing written to sound clever.
You will be asked to confirm facts, never to write the pages yourself.
docs / basics / working-together
A kickoff call, a few short interviews, and review passes on drafts. We do the research, the structure and the writing; your team confirms the facts.
We write into the setup you already use, or set one up if you do not have one yet, and keep pages in step with your releases after launch.
Typical review load is a couple of hours per week during a project.
See it for yourself
Drag the handle. Nothing on the left is invented. It is what most documentation actually looks like a year in.
Take a 30-minute call and we will look at your product, your support queue and whatever docs exist today, or run the free Docs Score first and get the same read on your current pages in a couple of minutes.