Launch playbook
Launch Readiness Scorecard
A launch does not need to be perfect. It does need a clear offer, deliverable promise, measurable next action, and a plan for what evidence changes the product afterward.
Demand
- ☐ The buyer and active problem are specific.
- ☐ There is recent evidence from qualified buyers.
- ☐ The product is not relying only on likes, compliments, or assumptions.
Offer
- ☐ The outcome is concrete enough to understand quickly.
- ☐ Scope and exclusions are explicit.
- ☐ Price logic and delivery economics have been pressure-tested.
Delivery
- ☐ The minimum product can actually create the promised first win.
- ☐ Support expectations are clear.
- ☐ Critical fulfillment, access, and failure paths have been tested.
Message
- ☐ The buyer can recognize the problem and outcome in their own language.
- ☐ Main objections are addressed without unsupported claims.
- ☐ The CTA is singular and obvious.
Measurement
- ☐ You know what behavior will count as a meaningful launch signal.
- ☐ Acquisition source and conversion events can be distinguished.
- ☐ Refunds, support issues, and buyer feedback have a place to be recorded.
Iteration
- ☐ You know what will not change during the initial test.
- ☐ There is a date or evidence threshold for the first review.
- ☐ The next build decision will be based on observed behavior, not launch emotion.
Release decision
Circle one: Launch / Small pilot / Fix critical gaps first / Stop and revalidate