Build a launch countdown plan with dated tasks and owners
A dated, owner-by-owner launch task list covering prep, launch day, and the two weeks after.
The prompt
Build a launch countdown plan for me. This is step 1 of a 5-step launch pack; it works on its own, and later steps (announcement copy, Product Hunt kit, launch-day run-of-show, post-launch review) can use its output.
What I'm launching: [PRODUCT or FEATURE and the one-sentence value]
Launch date: [DATE - and whether it can move]
Audience: [WHO it's for - e.g. "existing customers", "indie developers"]
Channels I have: [e.g. email list of 2,000, LinkedIn, X, community, blog, partners, paid budget]
Team and capacity: [WHO is available and roughly how many hours each]
Must-haves before launch: [e.g. pricing page, docs, demo video, support FAQ]
Launch goal: [e.g. 300 signups in week 1, 20 demo requests - or "help me set one"]
Plan it in phases: T-28 to T-15 (assets and message), T-14 to T-1 (seeding, previews, scheduling), launch day, T+1 to T+14 (follow-up and momentum).
Rules:
- Every task gets an owner, a due date, and a "done means" definition.
- Flag the critical path: tasks that delay launch if they slip.
- Cut anything my capacity can't support and tell me what you cut and why.
- Include a go/no-go check 48 hours before launch (product stable, tracking live, links tested, support ready).
- Don't assume numbers I haven't given; mark targets as [CONFIRM].
Return:
1. A table: Date | Task | Owner | Channel | Done means | Critical path (Y/N).
2. A one-line launch goal and the 3 metrics to watch daily.
3. The top 5 risks with a fallback for each.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Marketing & Brand prompts
What to fill in
- PRODUCT or FEATURE and the one-sentence value
- DATE - and whether it can move
- WHO it's for - e.g. "existing customers", "indie developers"
- WHO is available and roughly how many hours each
- e.g. pricing page, docs, demo video, support FAQ
- CONFIRM
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Review my launch results and plan the next 30 days of momentumA clear read on what worked in the launch and a 30-day plan to keep signups coming after the spike.
- Plan the first 30 days of sales for my new online storeA day-by-day launch plan to get the first orders, reviews, and repeat buyers without a big ad budget.
- Write my launch announcement for blog, email, and changelogOne core launch message adapted into a blog post, a customer email, and a short changelog entry.
- Write a launch-day run-of-show with posts and a reply planAn hour-by-hour launch-day schedule with ready-to-post social copy, monitoring duties, and escalation rules.