For support and success
Every release updates your help centre and your internal pages the same day, each step checked in the product.

Before
You hear about changes from customers.
You no longer trust your own articles.
You wait on engineering for answers.
After
Help centre articles update themselves.
A short "what changed" for every release.
Fewer questions to engineering.
When a feature ships, its article is rewritten and checked the same day.
When a customer pays you, record it on the invoice so your books stay up to date. You can record the full amount or part of it.
A short summary of every release, including what to tell customers.
What changed in Release 8.3
Shipped today · 4 changesCustomers can pay an invoice in parts.
What to tell customers: record each payment; the invoice stays open until it's fully paid.
2 pages updatedThe Mark as paid button is now called Record payment.
1 page updatedInvoices can show a new label: Partly paid.
Behind-the-scenes improvements to how invoices are stored. No pages affected.
If Sabí can't prove a step, it holds it back from your help centre until someone looks.
Click Send reminder for the remaining amount.
Sabí couldn't find this button. It's built, but not switched on for customers yet. This step won't be published until someone looks at it.
Help centre articles need your sign off. Internal pages can publish on their own.
Every release ends with a plain list: what's new, what changed, what needed no action.
Undo any change in one click if something publishes before it should.
Who approves what
Choose, per area of your product, what publishes on its own and what waits for a person.
What changed in Release 8.3
Shipped today · 4 changesCustomers can pay an invoice in parts.
What to tell customers: record each payment; the invoice stays open until it's fully paid.
2 pages updatedThe Mark as paid button is now called Record payment.
1 page updatedInvoices can show a new label: Partly paid.
Behind-the-scenes improvements to how invoices are stored. No pages affected.
A scenario, not a customer story
Release 8.3 ships at 3 pm. At 4 pm, Joost's team reads what changed. The next morning, a customer asks why their invoice is still open. The answer is already in the help centre.
Articles go out of date with every release, and your team finds out from customers.
One setup session, and someone to approve help centre changes for the first weeks.
[questions escalated to engineering per week, or tickets about documented features].
Yes. Help centre articles go public once they pass your approval rules. Internal pages stay internal.
Every page shows when it was last updated and checked.
Yes. Flag any page or step, and it goes to the review queue.

Product documentation that writes itself, then checks itself.