Get started Book a demo

Works with the tools your team already uses

  • Slack
  • GitHub
  • Zendesk
  • Intercom
  • Notion
  • Confluence
  • GitBook
  • Linear
  • Jira
  • Help Scout
The problem

Your product changes every week.Your docs don't keep up.Your help centre doesn't keep up.Your knowledge base doesn't keep up.

Keeping help articles and guides current is nobody's full-time job. So they slowly go out of date, and everyone pays for it.

Updated 8 months agoExporting reportsReports can only be downloaded as PDF.

Customers find wrong answers

Outdated articles send people down the wrong path, and they stop trusting your help centre.

"How do I export to CSV?"#8812
"Can I get reports in CSV?"#8830
Same question14 this week

Support answers the same thing again

When the answer isn't written down, customers open tickets and your team types it out by hand.

SCan someone update the docs for the new release?
DI'll get to it after this sprint...

Engineers get pulled off real work

Docs land on whoever built the feature. It gets pushed back, and the gap keeps growing.

What Paperkraft does

Tell it once. Every page gets updated.

Mention Paperkraft in Slack, a pull request or a ticket. It finds every page the change touches in your docs, help centre and knowledge base, rewrites it in your voice and waits for your approval.

Connect your tools

Link GitHub, Slack, Zendesk, Intercom, Notion and more. Paperkraft reads what you already have.

@paperkraft the Export button moved to Settings. Update the help centre.
@paperkraft write the docs for this new endpoint
@paperkraft turn this answer into a help article

Ask from anywhere

Mention Paperkraft in a thread, pull request or ticket. It updates the right page and replies with a link.

Ready to publish Webhook retries. Approve?

ApproveEdit

Approve where you work

Review a change in Slack or in your docs tool with one click.

Generic

In order to export your reports, you will need to navigate to the Settings page and select the Export option.

Your style

Go to Settings, then Export.

Writes in your voice

Learns from your existing pages, your style guide and how your team edits.

Agents

Docs that change when your product does

Each agent owns one job. It opens a pull request, and the review agent checks it before anything merges.

auth/tokens.mdx
expiry 1h to 24hMerged
quickstart.mdx
same change, step 3In 24h
errors.mdx
new 401 messageReview

Docs sync

A merge changes behaviour. Every page that mentions it gets edited.

ENG-412Done
Export reports as CSV
MK@paperkraft add docs for this ticket
Drafted the page and opened a pull request.PR #483: export-csv.md

From a ticket

Mention @paperkraft on a Jira, Linear or Zendesk ticket. It writes the docs change and opens a pull request.

# product-apiThread
P
Priya10:42 AM
token expiry is 24h now, @paperkraft can you update?
1 reply
PaperkraftAPP10:43 AM
On it. Docs PR #418 opened, 3 pages.
Docs: token expiry is 24 hours
auth/tokens.mdx, quickstart.mdx, errors.mdx

Slack agent

Mention it in a thread. It opens the change.

ReportsOverviewSchedulingExport as CSV, newSharing
Export a report as CSV

Go to Settings, then Export, and choose CSV. Or ask the API for the same file.

curl https://api.acme.dev/v2/reports/42/export?format=csv

Docs writer

A new endpoint or feature gets a first-draft page in your house style, with a working example and its place in the sidebar.

Build passesLinks workHouse styleReview agent

Review agent

Checks every change before anything merges.

How it works

Follow one change from start to finish

One change: CSV export is added. Watch it reach every page.

Watching your releases and team chat

Engineering, GitHubCSV export added
Merged
Product, LinearTicket closed
Shipped
Support, Slack@paperkraft update the help centre for CSV

Built for docs teams, developers, support, engineering and product

Safety

You decide what goes live on its own

Every change is checked and scored for risk. Small fixes can publish themselves. Anything that matters waits for a person.

Auto-mergedLinks, typos, redirects, sidebar order
Merges in 24hSmall edits under 30 lines, renamed settings
Needs reviewNew pages, pricing, security, API behaviour

Autopilot by risk, not all or nothing

Start with everything waiting for review. Turn on more as you trust it.

Updated by PaperkraftToday
Edited by MayaSep 28
Created by DevAug 2

Undo anything

Every change is versioned and can be rolled back in one click.

Automations

Keeps everything current in the background

Scheduled checks compare your content to the product every week, fix what drifted and send your team a short summary.

Automations4 active
Weekly drift scanMondays 09:00. Finds pages that no longer match the product
Broken link checkDaily. Fixes links and adds redirects
Release notesFridays. Drafts notes from merged work
Repeat question digestWednesdays. Turns common tickets into articles
Screenshot checkMonthly. Flags outdated screenshots
This weekThis week
SunMonTueWedThuFriSat
Monday drift scan

Summary sent to #docs at 09:04

142Pages checked
6Updated
1Needs review
Rate limits and quotasReview

Every team gets time back

When docs keep up on their own, engineers stop writing them, support stops answering the same question and launches ship complete.

Engineering6h

saved per engineer each month

Before
With Paperkraft
Support32%

fewer repeat tickets

Before
With Paperkraft
Product100%

of launches ship with docs on day one

Before
With Paperkraft
Docs team4x

more pages kept current per writer

Before
With Paperkraft

Your team's senior technical writer

Join the beta, connect your docs repository and let the next merge update them for you.