# Product launch plan

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

## Fill in before running

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

## Prompt

```
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.
```

## 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.

---

From the QuQi prompt library - https://www.quqi.io/prompts/launch-plan-build