✳FOR TEAMS THAT SHIP EVERY WEEK

Code got faster.
Docs didn’t.

Your team ships more than ever. Sabí writes up every change for you. You just check it and hit publish.

A smiling teammate peeking up from behind the panel
FROM CHANGE TO CLEAR DOCSYou’re in control.
  1. 01

    It spots the change.

    No chasing engineering.

  2. 02

    It writes for each reader.

    One for customers, one for your team, one for developers.

  3. 03

    You check it.

    Old words and new words, side by side. Then you hit publish.

HOW IT CONNECTS

Your code in. Clear docs out.

Works with GitHub and Notion today. Confluence coming soon.

Your codeGitHub, or a ZIP in the demo
SABͮReads what changed, understands the context and writes it up
Your docsNotion today. Confluence coming soon.

Coming next: GitLab, Jira and more help centres.

A product change becomes updated help

Illustrative example

What the code says

BeforeAlways includes names
const speaker = note.speakerName;

return {
  speaker,
  text: note.text,
};
AfterRespects the setting
const speaker = hideSpeakerNames
  ? "Speaker " + (note.speakerIndex + 1)
  : note.speakerName;

return { speaker, text: note.text };

What Sabí wrote

Share notes without speaker names

Turn on Hide speaker names before sharing your meeting notes. The shared notes use anonymous labels instead of names, so readers can follow the conversation without seeing who said what.

THE PROBLEM

Heard any of these lately?

The release went out Tuesday. The help pages still describe last month.

CUSTOMERS

“I followed every step. That button isn’t there anymore.”

YOUR TEAM

“Which page is right? I’ll just message product again.”

DEVELOPERS

“I can ship the feature. Or update six docs. Pick one.”

Stale docs cost more than time.

It always shows up somewhere:

  • Customers stuck on steps that changed
  • The same question in Slack, for the fifth time
  • Know-how that lives in one person’s head

One person leaves. How much of your product goes too?

A smiling teammate holding a tablet
WHY TEAMS PICK SABÍ

Docs that keep up, without the chasing.

Starts from the code

No briefs. No “quick call to explain the feature”. It reads the code.

One change, three versions

Customers get the how-to. Your team gets what to say. Developers get the details.

Skips the noise

A renamed file isn’t news. Sabí leaves it out, and tells you why.

You have the last word

Nothing goes live until you’ve read it. Or let the small stuff publish itself.

EVERY UPDATE HAS A RECEIPT

Every claim.
Backed up.

See the old words, the new words, and the code change behind them.

See a receipt for yourself
SabíReceipt · Share notes
Old wordsShared notes show who said what.
New wordsTurn on Hide speaker names to share notes without them.
Because ofChange #24 · Speaker privacy controlsChecked on staging
WHO IT’S FOR

For everyone who explains your product.