Launch toolkit
Toolkit
Everything around a launch. The checklist and the directories keep their pages and your saved progress.
Launch checklist
Go through it the week before your day. Your ticks stay in this browser only.
One week before
Two days before
Launch day
During the week
What works
Tagline
Good Release notes your customers actually read, written from merged pull requests.
Weak THE BEST AI TOOL FOR EVERYONE 🚀🚀
Say who it is for and what it does. No capitals, no links, no superlatives.
What is new
Good Now writes notes in five languages and posts them to Slack.
Weak Big update, check it out!
One concrete change. For a first launch: the problem you solve.
Description
Three short paragraphs work best: the problem in one sentence, how the product solves it, and who uses it today. End with what feedback you want.
Screenshots
Real screens, not mock-ups. Order them like a demo: main screen, the key action, the result. Avoid text too small to read.
Before the day
- One sentence for who it is for and what changed. That sentence is your "What's new".
- Check the demo path: a visitor should reach the product in one click from the launch page.
- Pricing and availability on the profile must match the site.
- Prepare the posts for your own channels; schedule them for 00:00 Pacific Time or your morning.
During the week
- Be present: answer comments the same day. Maker replies are labelled.
- Ask people to try the product and give feedback. Do not ask for votes in exchange for anything.
- Fix problems people report; add a dated update instead of rewriting the page.
After
- Read the result page and the discussion once more a week later.
- Write down what you learned; a relaunch with a real update is possible after 90 days.