For client-facing teams
Every release, Sabí writes a plain version for your team and one for customers. No developer translation needed.

Before
You hear about changes from customers.
You're not sure which page is still true.
A developer explained it twice. You still can't explain it to a client.
Every answer means another message to product.
After
A plain "what changed" for every release.
One version for your team, one for customers.
Every page shows where it came from, so you know it's current.
Answers you can find without asking.
A short summary of each release, written for people who talk to customers.
Release 8.3
A plain version of each new feature, ready for client calls and stakeholder updates.
The change: pause a subscription.
Go to Billing, click Manage plan, then Pause. Pick 1 to 3 months. Billing stops until then.
Checked in the productReply with the page and the change behind it, so you can say what shipped and when.
You check customer pages first. Team pages can go straight out, if you want.
See what changed, and what Sabí left alone.
In beta: Sabí tries the steps in a test copy of your product before you publish.
Who approves what

A typical week
Pausing a subscription ships.
Joost's team reads what changed, and what to tell customers.
A customer wants a break instead of cancelling.
Joost already knows the answer.
Every release changes the answers, and your team finds out from customers.
One setup session, and someone to approve customer pages for the first weeks.
Questions your team sends to product or engineering each week.
Only what you've approved. Team pages stay internal.
If your help centre lives in Notion, yes. Confluence and one more help centre app are coming soon.
Every page shows the code change it came from.
In beta, yes: Sabí tries the steps in a test copy of your product and attaches a screenshot of each.
