Briefings
Walk in already current.
A new account, a new team, a board seat — getting current used to mean weeks of old decks and asking around. A briefing assembles the state of the work from your live context, in the time it takes to read it.
What it does
Everything you would otherwise dig for.
Drawn from live context, not stale docs
Briefings read from your shared context as it stands today: decisions made, commitments given, risks flagged. Nothing assembled by hand, nothing already out of date by the time you open it.
Scoped to whoever is asking
A new hire, an exec joining a review, an account owner inheriting a relationship: each gets what is relevant to their role and their question, not a generic data dump.
No archaeology, no "ask Sarah"
Why a call was made, what was tried, what changed — already captured and linked. Getting up to speed stops depending on whoever happens to remember.
How it works
Ask, read, verify.
01 · Ask
Name the seat
The account you’re taking over, the review you’re joining, the team you’re inheriting. That’s the whole request.
02 · Read
The briefing assembles itself
Decisions and their reasoning, open commitments and owners, risks, dependencies, what changed since last time — pulled from the live record, not from someone’s memory.
03 · Verify
Every claim carries its source
Each line links back to the meeting or decision it came from. Trust it, or check it in one click.
What it replaces
The onboarding tax, measured.
to current, not weeks
The reading time of the briefing is the entire ramp-up. The archaeology has already been done — continuously.
things every briefing covers
Decisions and reasoning, commitments and owners, risks and dependencies, changes since last review, who to talk to, the history of the work.
re-explaining, per manager, per week
Measured in the 2026 Coordination Tax Index. That is the meeting where someone catches everyone else up — the one a briefing deletes.
Before you ask
The questions every team asks first
- Where does the content come from?
- From your shared context — the decisions, commitments, and risks Notes captures from meetings, kept current automatically. A briefing is a view of that record, scoped to a role and a question.
- How do I know it isn’t out of date?
- Because it’s generated when you ask, from the live record — and every line shows when it happened and the meeting it came from.
- Can someone see things they shouldn’t?
- No. Briefings respect workspace permissions: the reader only gets material drawn from context they are allowed to see.
- Is it priced separately?
- No — briefings are included in the paid tier, €69 per user per month, full product free for 20 days.
The next handover shouldn’t need a handover doc.
Once your meetings feed shared context, every seat change, account transfer, and exec review starts from the same current record.
- Assembled from live context
- Scoped to role and question
- Source behind every claim