For product leaders
A source of truth your product org can trust.
Current, checked documentation for your developers, your team and your customers, without hiring writers or asking engineers to write.
Your week, before and after
Before
Knowledge lives in a few heads.
New joiners take months to find their way.
The wiki is quietly wrong.
After
One source that keeps itself current.
New joiners answer their own questions.
EU-owned, read-only, reviewable.
One release, three readers.
Every change reaches developers, your team and your customers in words they understand.
The change: customers can pay an invoice in parts.
LED-482The payments endpoint now accepts an amount lower than the balance. New status: partially_paid.
Backed by a ticket or changeCustomers can now pay in parts. If a customer asks why their invoice is still open, check Payment history.
Backed by a ticket or changeYou can pay an invoice in more than one payment. Your invoice stays open until it's fully paid.
Checked in the productYour team reviews only the exceptions.
Sabí checks everything first. People look at what it couldn't prove.
Review · Release 8.3
1 page needs youOnboarding that doesn't depend on who's free.
Mila, in her second week, finds the answer herself instead of asking around.
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.
- Open the invoice.
- Click Record payment.
- Enter the amount you received and click Save.
- If part is still owed, the invoice stays open and shows Partly paid.
You stay in control.
Choose which areas of your org publish on their own and which route through a reviewer.
Team edits are never overwritten when Sabí regenerates a page.
Undo any change in one click, across every team and area.
Who approves what
Choose, per area of your product, what publishes on its own and what waits for a person.
Make the case to your leadership team
Documentation costs time nobody has, so it doesn't get done.
One tech lead for setup, one reviewer, about an hour a week.
Time for a new joiner to answer five product questions on their own.
Questions
What does a pilot cost and need?
Pilot pricing is agreed with each beta partner. You need a tech lead for one setup session and a reviewer for about an hour a week.
Where is data hosted?
On EU-owned infrastructure: [providers]. See Security and trust.
Who is accountable if a page is wrong?
[Your decision. Suggested: your reviewers approve what goes public; Sabí shows the evidence behind every page and holds back what it can't prove.]
See it on your own product.
Product documentation that writes itself, then checks itself.