product-launch git:20260807.975fe85A

Immutable. This exact content never changes and is served at /api/v1/blob/63d3004061a4d0ce.

---
name: product-launch
description: Plan and implement a product launch with positioning, assets, distribution, measurement, waitlist capture, and follow-up. Use when preparing or reviewing a launch.
license: MIT
---

# Product launch

Build a launch around a specific audience, credible claim, working conversion path, and follow-up loop. Support strategy-only work and repository implementation without pretending they are the same task.

## Workflow

1. Establish the product, launch stage, audience, problem, proof, constraints, date, owner, and target action. Inspect existing product briefs, site copy, analytics, waitlist, and prior launches before asking questions.
2. Research the category, current alternatives, audience language, communities, launch calendars, and platform rules using current sources.
3. Write the positioning in plain language: who it is for, what changes, how it works, why now, and why this product is credible. Remove claims the project cannot support.
4. Choose a launch type and a small set of channels based on actual audience access. Assign each channel a format, owner, publish time, response plan, and success metric.
5. Inventory required assets: landing page, demo, screenshots, announcement, founder post, email, directory listings, press material, support docs, and tracking links. Build only what the launch needs.
6. Confirm the conversion path works end to end. If pre-launch demand capture is needed, implement the waitlist with validated email storage, duplicate handling, confirmation, consent, admin access, and optional referrals.
7. Instrument source attribution, activation, conversion, and follow-up. Define the decision each metric will support.
8. Prepare day-of operations, replies, issue triage, follow-up touches, and a 24-hour/7-day review.

## Load deeper guidance

- Read [launch strategy](references/launch-strategy.md) for research, channel planning, assets, timelines, and reporting.
- Read [waitlist implementation](references/waitlist-implementation.md) only when the project needs a real signup flow.

## Output

Return the positioning, launch brief, channel plan, asset checklist, implementation changes, measurement plan, and follow-up schedule. Distinguish verified audience evidence from assumptions.