Recap
Structured meeting notes with decisions and owners
Thesis
Meeting notes are inconsistent or missing. Differentiate on structure: decisions, owners, deadlines extracted automatically.
The Problem
Meeting notes are broken: 90% of meetings have no notes or terrible notes. Action items get lost in paragraph summaries. There's no accountability ("who said they'd do that?"). Same discussions repeat because decisions aren't recorded. Existing tools transcribe but don't structure. Transcripts are just more text to read.
Implementation Approaches
Zoom/Meet/Teams Integration (Recommended)
Native integrations that join meetings and generate structured recaps
Implementation
- →Bot joins scheduled meetings automatically
- →Real-time transcription via existing APIs
- →Claude extracts: decisions, action items, owners, deadlines
- →Pushes recap to Slack/email/Notion within minutes
- →Follow-up reminders for action items
Pros
- +Validated market, people already pay for meeting tools
- +Clear differentiation: structure beats raw transcription
- +High retention potential with team workflows
- +Obvious upgrade path: analytics, search, etc.
Cons
- −Competitive market (Otter, Fireflies, tl;dv)
- −Platform integrations are complex
- −Privacy concerns with recording
- −Higher infrastructure costs
Upload + Process
Upload existing transcripts or recordings for structured processing
Implementation
- →Upload audio/video or paste transcript
- →AI processes and extracts structured data
- →Output: decisions, actions, owners in clean format
- →Export to Notion, email, Slack, etc.
- →No bot needed, works with any source
Pros
- +Fastest to build, no integrations needed
- +Works with any meeting platform
- +Lower privacy concerns since user controls upload
- +Can process historical meetings
Cons
- −Extra step for users, must upload/paste
- −Not automatic, requires action
- −Harder to build habit/retention
Slack-First
Slack app that creates structured recaps from meeting discussions
Implementation
- →Slack command: /recap #meeting-channel
- →AI reads channel history and extracts structure
- →Also works with huddle transcripts
- →Posts recap directly to channel
- →Integrates with Slack's native meeting features
Pros
- +Many teams already discuss in Slack
- +Slack App Directory distribution
- +Low friction, no new tool to adopt
- +Can expand to async decisions too
Cons
- −Limited to Slack-first teams
- −Quality depends on how complete the Slack discussion is
- −Slack's meeting features are limited
Validation Plan
Hypothesis to Test
Teams will pay $12/user/mo for structured meeting recaps vs raw transcription
Validation Phases
Differentiation Test
1 week- •Get 5 meeting transcripts from target users
- •Generate structured recaps manually
- •Show users: raw transcript vs structured recap
- •Ask: 'Which would you pay for? How much more?'
Upload MVP
1 week- •Build simple upload, process, output flow
- •Launch to Product Hunt / Twitter
- •Offer 10 free recaps, then $10/mo
- •Track: uploads, conversions, feedback
Integration Beta
2 weeks- •Build Zoom or Slack integration (pick one)
- •Partner with 5 teams for beta
- •Measure: meetings processed, feature requests
- •Validate team pricing at $12/user/mo
Kill Criteria
Stop and move on if any of these become true:
- ✕Users don't see value over raw transcription
- ✕Structure extraction quality is inconsistent
- ✕Existing players already do this well
- ✕Price sensitivity below $8/user/mo