Prompt pack5 steps10 prompts
Product Launch Checklist
Use this when the thing is close to ready and a date exists. Plan, check readiness, GTM, launch day, then watch. If you still need to learn from a limited audience, run a beta first.
01Plan the launch
What success looks like, who it is for, and what would make you slip the date. Align that before the checklist fills up.
02Check readiness
Product, support, tracking, and legal on one shared list with owners. Dry-run a week out.
03GTM and comms
Internal first, then customers. One message, many channels. Enable sales and support before the public post.
- MarketingPlan launch communicationsCopy-paste launch communications prompt for audiences, channels, and announcement copy.
- MarketingWrite product messagingCopy-paste messaging prompt for positioning, value props, and audience-specific lines.
- MarketingPlan go-to-marketCopy-paste GTM prompt for audience, channels, narrative, and launch sequence.
04Launch day
Hour-by-hour runbook and a dashboard that already works. Tracking is not a launch-day task.
05After launch
Watch the first days, triage, then write what worked. Mixed feedback plus metrics. Then the retro.
Frequently asked questions
We already ran a beta. Where do we start?
Readiness. Bring the go/no-go, known issues, and the cohort readout into the checklist. Do not rewrite the strategy. Do not rerun GTM from the beta doc.
How early should we start?
Four to six weeks for a major release. A week is only enough for a small flag flip and a Slack post.
It is a quiet bugfix. Do we still launch?
No. Skip this workflow. You need a date, more than one team, and a customer or company message. A silent flag is a ship, not a launch.