STRATEGY

Product launch plan

Use when a launch date is set and you need a sequenced plan with owners and a fallback.

launch-plan-build.md

Download .md

You are a launch lead. Produce a plan that is sequenced, not a list of channels.

What is launching: {{LAUNCH_DESCRIPTION}}
Launch date: {{LAUNCH_DATE}}
Who it is for: {{AUDIENCE}}
What success looks like in numbers: {{SUCCESS_METRIC}}
Assets and channels we have: {{ASSETS_AND_CHANNELS}}
Known risks: {{RISKS}}

Produce:
1. The one sentence launch narrative: what changes for the customer. Not a feature list.
2. Three audience segments in priority order, with the message and the first channel for each.
3. A table with columns: Phase (pre launch, launch week, post launch) | Activity | Channel | Owner placeholder | Dependency | Date relative to launch day.
4. The critical path: which items, if late, move the launch date. Mark them clearly.
5. Measurement: the leading indicator visible within 48 hours, and the lagging metric, with how each is captured.
6. A rollback and a hold decision rule: the specific condition under which we delay, and who decides.
7. The three most likely ways this launch underperforms, and the cheap mitigation for each.

Constraints: do not include activities we have no asset or channel for. No em dashes. Do not predict specific traffic or revenue numbers; describe the mechanism instead.

Fill in before running

Replace each placeholder with your own detail. The more specific you are, the less the model invents.

{{LAUNCH_DESCRIPTION}}
{{LAUNCH_DATE}}
{{AUDIENCE}}
{{SUCCESS_METRIC}}
{{ASSETS_AND_CHANNELS}}
{{RISKS}}

Getting a better result

Write the narrative in step 1 before anything else and reject it if it only describes features.
The 48 hour leading indicator stops the post launch silence where nobody knows if it worked.
Set the hold rule before launch week; nobody can decide it calmly on the day.

Questions about this prompt

When should I use this rather than a channel checklist?

When the date is fixed and you need sequence and dependencies rather than a list of places to post. A checklist hides the critical path. This puts every activity in a phase with a dependency and a date relative to launch day, then marks which items move the date if they slip.

What do I need pinned down before planning the launch?

The launch date, success stated as a number, the audience, an honest list of assets and channels you actually have, and known risks. It refuses to plan activities you have no asset or channel for, so an aspirational list produces a plan nobody can staff and the phases quietly go empty.

What comes back, and which piece is most practical?

The one sentence narrative, three prioritised segments with message and first channel, a phased activity table, the marked critical path, leading and lagging measurement, a hold and rollback rule, and three ways it underperforms. The 48 hour leading indicator is the practical piece, since it ends the week where nobody knows anything.

What is the mistake that undermines the whole plan?

Accepting a narrative in step 1 that is a feature list with a verb in front of it. Everything downstream inherits that line, so reject it and rerun before you read the table. Second, do not leave the hold rule until launch week, when nobody can set a threshold calmly.