Docs that stay attached to the work they were written for.
Briefs, memos, canvases, sheets, and decks stay linked to the offer, campaign, test, decision, or customer they explain. When someone opens the file later, they see the context and the latest result.
Context by default
Every file stays linked to the work, customer, launch, or decision it explains.
Revision history that matters
Edits, approvals, and comments stay attached so a later teammate can understand what changed and why.
Work-ready file types
Docs, canvases, sheets, tables, boards, and pages for the work that belongs in Lyberty.
Templates that compose
A weekly readout can pull the launches, decisions, and revenue entries that happened that week.
Summaries that cite the source
Summaries point back to the file, revision, and evidence they used.
| Task | Similar tools | Lyberty |
|---|---|---|
| Wiki / docs | Notion ($10-15/seat) | included |
| Whiteboards | Figma / Miro ($8-20/seat) | included |
| Sheets | Google Sheets + ad-hoc logic | included |
| Context linking | manual @-mentions, link rot | automatic |
| Search docs and decisions | Glean ($30-50/seat) | included |
Every document stays connected to the work it explains.
Not just version history
The memo about the pricing change stays linked to the pricing change. The brief, result, approval, and follow-up stay nearby instead of becoming separate links in separate tools.
Open a doc and you see the work around it. Open a decision and you see the memo behind it.
Notion · Google Docs · Figma gives you the tool. Lyberty ties it to the rest of the business.
Under the hood
The surface is just the view.
All six surfaces share the same record. Adopt one, and the others are already reading from what you wrote — no sync, no export, no reconcile.