Meeting Brief

A Meeting Brief is a one-page pre-call summary. Attendees, likely topics, relevant tickets, relevant docs, open threads from Slack, action items from the last time you spoke. One page you read before you click Start, so you spend the first five minutes talking, not catching up.

If you have an integration connected, the brief pulls from it. With none connected, the brief still runs and uses your Knowledge Base plus prior meetings on the same topic.

• Jira. Tickets mentioned on the invite or recently touched by attendees.
• Confluence. Pages that reference the project or the attendees.
• Google Drive. Specific docs you attach using the Drive Picker on the meeting setup screen.
• Slack. Recent threads in the channel linked to the meeting.
• Knowledge Base. Anything you have indexed locally. See Knowledge Base.

1. Create a meeting, or let one auto-populate from your calendar.
2. On the meeting setup screen, click Generate brief.
3. Wait a few seconds while the app pulls from each connected source.
4. Review and edit the sections you care about.

You can regenerate at any time. Each regeneration preserves your hand-edits unless you reset the section.

• Participants and roles. Pulled from the calendar invite and enriched with role data you have on file.
• Likely topics. Inferred from the calendar title, past meetings, and open tickets tied to the attendees.
• Open commitments from your side. Action items you accepted previously that are not yet done.
• Open commitments from the counterparty's side. Things they said they would do. Useful for the first two minutes of a status call.
• Relevant docs. Each with a one-line summary so you can scan without opening every tab.
• Suggested rehearses. Topics worth practicing before the call. See Rehearse Mode.

Every section is editable. If the app got something wrong, reject it. If a bullet is missing, add it. Treat the brief like a page of notes you can rewrite.

• Click any bullet to edit inline. Click the x to remove it.
• Click Add note to append your own line.
• Click Reset section to drop your edits and pull a fresh version.

A saved brief becomes part of the live-coaching context during the meeting itself. The coaching engine reads it alongside the live transcript, so suggestions reference the right tickets, docs, and commitments without you prompting them in. Starting a meeting with an open brief auto-attaches it.

Integration data is pulled using OAuth 2.1 with PKCE. Tokens are scoped to the minimum access required and stored locally on your machine. We never see your Jira tickets, Confluence pages, Drive docs, or Slack threads. The brief is assembled on your device and stays on your device. See Integrations for the full breakdown.

A quick weekly 1:1 does not need a brief. Neither does a standup. Save the feature for:

• New meetings where you have never met the other side.
• New accounts where you want the right vocabulary.
• Status calls spanning multiple tickets.
• Anything you want to be sharper on than usual.

For routine conversations, skip the brief and start the meeting. The coaching engine still has your Knowledge Base.

• Integrations. Connect Jira, Confluence, Drive, and Slack.
• Rehearse Mode. Practice a topic the brief flagged before the call.
• Knowledge Base. The fallback source when no integration is connected.