Run a Launch Debrief

The debrief is where a launch stops being an event and starts being a compounding asset. Teams that debrief honestly ship better launches because they encode lessons instead of repeating them.

One paragraph for the team and stakeholders: what you launched, what the goal was, what actually happened against it, and the one-line takeaway.

The channels, messages, tactics, and people that paid off. Be specific — "Founder thread on X drove 40% of signups" is useful; "Social did well" is not.

What you expected to work and did not. Be specific, not blameful. The point is to understand cause, not assign fault.

The three to seven recurring patterns synthesized from signals — positioning, pricing, product, onboarding, comparison, and praise. Quote a representative signal under each theme.

Concrete follow-ups with owners and deadlines. Each action should resolve a specific underperformance or theme — not be a generic "improve onboarding".

What to repeat, what to change, and what to retire next time. This becomes the starting blueprint for the next launch.

The debrief module ships with a manual template covering all of the sections above. It is clearly labeled as a template, not as generated content — fill it in with real numbers and quotes.

When an AI provider is configured, LaunchRoom can draft an initial debrief from your blueprint, signals, timeline, and outreach data. AI generation requires configuration — until then, use the manual template. Always review and edit AI drafts before sharing.