From a recording nobody rewatches to decisions and tasks that get tracked, searched, and followed up automatically.
SYSTEM / MEETING INTELLIGENCE
ROLE / BUILD
STATUS / ● ACTIVE
01 / DIAGNOSE
A recap doc gets written once and then goes stale: decisions made in a meeting aren't searchable later, and action items only get followed up if someone remembers to check. Without an owner, a due date, and something that resurfaces overdue items on its own, follow-through depends entirely on memory.
02 / DESIGN
FINDINGS
- 01
- 02
- 03
- 04
RECOMMENDATION
Extract decisions, action items, and open questions as structured, owned records at process time, then push overdue follow-up into a channel people already check (Slack) instead of a dashboard they have to remember to open. Make every past decision searchable by keyword or meaning, not just browsable by date.
CONSIDERED AND REJECTED
- Live meeting-bot joining calls (Zoom/Meet) instead of recording upload
- Rejected for now: building a reliable live-join bot (Google Meet has no first-party bot API) is a large, fragile effort that doesn't validate the core value, extraction and accountability. Revisit once that loop is proven and immediacy becomes the actual bottleneck.
- Keep the AI output as one unstructured summary blob
- Rejected: action items only exist if someone manually re-reads the summary and copies them out. Moved to relational decisions/action-items/open-questions tied directly to an owner and a real due date instead.
03 / BUILD
01 / DASHBOARD
02 / EXTRACTION
03 / ACCOUNTABILITY
04 / SLACK DIGEST
04 / ENABLE
SYSTEM HANDBOOK
- 01How it works
- 02Supported input formats
- 03Editing action items
- 04Search
- 05Slack notifications
05 / IMPROVE
SYSTEM / MEETING INTELLIGENCE
- V1
- upload → transcript → unstructured summary
- V2
- decisions + action items + open questions, owners resolved automatically
- V3
- task list across meetings, Slack overdue digest with mark-done button
- CURRENT
- keyword + semantic search across all past meetings, multi-tenant roles
STATUS / ● ACTIVE
This system is still evolving, not yet publicly deployed.