Structure before writing
We agree the map first: which pages exist, who each one is for and where a reader lands. A page in the wrong place is wasted work, however well it is written.
About Paperkraft
Docs that keep up with the product
Paperkraft is an AI technical writer for SaaS and API teams. Our agents keep your docs in step with every release, on the stack you already use. When you need docs built from scratch, our writers build them.
Our story
Why we started Paperkraft
Every software team we worked with had the same problem, and it was never a shortage of writers.
Docs were everyone's job, so nobody's
We spent years inside software teams. Documentation got written in a rush before a launch, then quietly went out of date while support answered the same questions by hand.
The hard part is keeping it true
Writing is not what makes docs hard. Reading the code, sitting with the support queue, deciding what a reader needs, and keeping all of it true after the next release is.
So we built agents for that
Paperkraft reads every merge and writes the docs change. It runs build, link and style checks, has a separate review agent score the risk, and opens a pull request.
And writers for the docs you are missing
Where a team needs docs written from scratch, our writers build them first. Then the agents keep them current, release after release.
Now in private beta
We are opening Paperkraft to teams in small batches, starting with the ones whose docs fall behind the most.
Principles
Four things we hold to
What every page and every pull request is held to, before it reaches your docs.
Nothing merges unchecked
Every change is built, link checked and style checked, and a separate review agent scores its risk. Code samples run against a live API. If one fails, the page does not go out.
Written for the reader you have
Plain language for customers, precision for developers. We never write to sound clever, and never assume knowledge the reader has not been given.
You stay in control
Every workspace starts in Co-pilot, where nothing merges until your team approves it. You decide how much can merge on its own, and you can change it any time.
Talk to us directly
A call with us. We look at your product and the docs you have today, then tell you what is worth fixing first.