Fill in these first
- What is launching: [feature or product, and the main user benefit]
- Launch type: [beta, gradual rollout, full public launch]
- Launch date: [date]
- Audience: [new users, existing customers, a segment]
- Teams involved: [product, engineering, design, support, marketing, sales]
- Channels: [in-app message, email, blog, social, sales calls]
- Success metric: [the number that shows the launch worked]
Task
Plan the launch backwards from the launch date, covering every team listed, so each task has one owner and a deadline.
Output format
- Launch summary: three sentences on what, who it is for and why it matters now.
- Timeline table with columns Week, Task, Owner role, Due date, Status. Group rows into four phases: build complete, internal readiness, external readiness, post-launch.
- Readiness checks: a yes or no list across product quality, support documentation, analytics tracking, legal or compliance review, pricing and billing, and sales briefing.
- Launch-day run sheet: time, action, owner, for the day itself.
- Rollback trigger: the conditions under which the release is paused, and who decides.
- Week-one review: the metrics to check on days 1, 3 and 7.
Rules
- Every task has exactly one owner role, never "everyone" or "team".
- Analytics events are confirmed before launch, not after.
- Support receives the help article and known issues at least three working days before launch.
- Leave a buffer of at least two working days before the launch date.
- Where an input is missing, write [to confirm] instead of guessing a date or owner.






