Product Launch Debrief Template
Review a software launch’s intended audience, observed journey, attributed actions and support evidence before deciding what to repeat or change.
When to use this template
Use this after a defined observation window when the team can compare its actual offer and results with the launch plan.
Choose another approach when: You want to infer revenue from votes, combine incompatible analytics counts, or call a launch a failure because one platform did not feature it.
Gather these inputs
- The original launch offer, audience and goals.
- Observed acquisition and meaningful product-action data with definitions.
- Support, research and operational evidence from the same period.
Copy and adapt the template
Edit the text below and copy it into your own document. Edits stay in this browser field and are not submitted or saved by this page.
Worked example
Illustrative example, not a Crany customer result. Replace every example detail with facts you can verify.
A fictional launch brings many visits to a demo but few completed beta requests. Support notes show that visitors thought joining the waitlist provided immediate access, while the app still required an invitation. The debrief chooses to clarify the access offer and retest the form journey before buying more traffic. It does not claim the product lacks demand from a single launch, and it does not count platform votes as activated users. The next decision follows an identified uncertainty rather than a celebratory screenshot.
How to use it
- Preserve the original goal and define a consistent observation window.
- Reconcile traffic, actual actions and qualitative evidence without blending definitions.
- Choose one justified next decision and name the evidence still needed.
Check before using it
- The recap separates published placements from intended distribution.
- A correlation is not described as a proven causal effect.
- Unknown attribution and small samples remain visible.
What to measure
Assess whether the next experiment resolves the uncertainty identified in the debrief. A launch is a bounded observation, not a complete verdict on product-market fit or lifetime channel value.
Research and sources
Platform preparation, acquisition parameters and task research support the evidence inputs. The decision-oriented debrief is original and does not inherit success claims from platform case studies.
- Product Hunt: Launch Guide — checked 2026-10-23. Launch preparation, maker participation and platform-specific promotion boundaries; no outcome guarantee.
- Google Analytics: Collect campaign data with custom URLs — checked 2026-10-23. Campaign parameter definitions and consistent naming; no attribution or conversion guarantee.
- Yale: User Interview Example Questions — checked 2026-10-23. Interview structure, current tasks, past experience, alternative workflows and discovery paths.
About Crany
Crany is an AI marketing co-founder in development for software founders and vibe coders, designed to strategize, execute approved marketing and improve based on results. This free resource is usable independently of the product. Join the public waitlist.