My playbook from blank page to launch (no fluff)

Blank page to launch is where teams collect rituals the way travellers collect luggage tags. Mood boards, Gantt charts, a Slack channel named launch-vibes. Useful artefacts sometimes. Rarely a substitute for a clear offer, a decision path, and a first value people can feel before the confetti emoji arrives.

My approach is deliberately boring: decide who it is for, what job it finishes, how someone chooses you, what proof earns trust, and what you will measure in the first two weeks. Strategy is not a slide. Launch is not a date. Both are sequences of decisions that refuse to hide behind aesthetics.

Fluffy launch vs disciplined launch

**Bad SaaS launch:** Product Hunt day, twenty features, a pricing page that hedges, and no owner for week-two activation. Noise without a curriculum. **Good SaaS launch:** one job, one path to value, clear CTA, and a learning loop scheduled before the announcement.

**Bad consumer launch:** brand film before anyone validated the problem. **Good consumer launch:** small proof in the wild, then a story people can retell.

The sequence I reuse

1. Write ICP, job-to-be-done, wedge, and three non-goals on one page.
2. Draft the homepage and first-run flow from that page before expanding scope.
3. Define first value in user terms and time-box the path to reach it.
4. Collect one form of proof before broad announcement (demo, pilots, waitlist quality).
5. Launch with a measurement plan: activation, retention proxy, and five interviews.
6. Kill or freeze anything that does not serve the wedge for thirty days post-launch.

First Round Review is still a strong library for operator sequencing. Related: how I decide whether a product is worth building.