Turn launch meetings into an auto-updated PMM decision hub

Create the Notion launch hub before connecting any automation. Add databases or sections for meeting log, decision log, action items, risks, blockers, open questions, messaging changes, owner changes, customer impact, sales impact, launch date, and next review date. Use Claude to turn your launch type and stakeholder list into field names, statuses, and required review rules. QA check: the hub should make decisions, risks, and owner changes easy to find without reading meeting notes.

Design a launch decision hub for this product launch.

Launch type:
{{launch_type}}

Team members and functions:
{{team_members}}

Launch stages:
{{launch_stages}}

Known decision areas:
{{decision_areas}}

Return:
1. Notion databases or sections
2. Required fields
3. Status options
4. Decision log format
5. Risk log format
6. Action item format
7. Review workflow
8. Owner confirmation process

Optimize for PMM visibility, not generic meeting notes.

Set a naming rule for meetings that should enter the workflow, such as [Launch Sync], [PMM Launch], or a specific launch code. In Otter, make sure the meeting owner, transcript link, meeting title, summary, action items, and date are available for Zapier to pass downstream. In Zapier, add a filter so only matching launch syncs continue to the extraction and Notion update steps. QA check: test with one real launch transcript and one unrelated meeting to confirm the filter rejects the wrong meeting.