Post-Launch Checklist: What to Do in the 48 Hours, Week One and Month One
After a launch, answer every comment, sort what visitors reported into blockers and annoyances, and write down what each channel sent. Within a week, write to the people who signed up but never finished and change something real on the page. At the end of the month, compare channels by conversations and first uses, not raw visits, and decide whether to keep, change or drop each one.
What actually happens after the post goes quiet?
A launch is a spike followed by a long, flat stretch, and the flat stretch is where a product either gets learned from or forgotten. Makers often take the quiet as a verdict. It is better read as the moment you finally have a sample: a few dozen people looked, some tried, a handful wrote to you. The jobs after launch are about turning that small sample into decisions.
This list is arranged by how fast things go stale. Comments lose value in hours, bug reports in days, and channel results in weeks. Work from the fastest-fading item to the slowest. If you did not launch yet, start with the pre-launch checklist, and if the day itself went badly, what to do after a failed launch covers that case separately.
Which jobs cannot wait past the first 48 hours?
- Reply to every comment and email that is still unanswered, because a first-time visitor who gets a reply tends to come back, and one who does not rarely does.
- Sort every complaint into two piles, blockers that stop someone finishing the main action and annoyances that merely slow them, since only the first pile justifies a code change this week.
- Thank the people who helped by name, in public where it fits and in private where it does not, which costs minutes and is remembered for years.
- Copy the numbers out of your analytics into a file before the dashboard rolls its window forward.
- Screenshot the launch page and its feed position as they looked, so the story you tell later matches what happened.
- Write down the five questions people asked most, because those are your next FAQ entries.
On this site, your launch page keeps working after the first day: it stays in the All-time feed, comments stay threaded, and the launch itself is final once published. A tagline that confused people gets fixed on your own page and in your next post, and a factual error goes to support@postyourbuildideas.com. Questions about how to word the page are in the launch description templates.
What should week one contain?
- Write to every signup who did not finish. One honest, short message asking what stopped them gets more truth than a survey. A starting wording is below.
- Fix the top three blockers and announce them. Telling the people who complained that you fixed it is how complaints become users.
- Add the repeated questions to the page. Each one you answer once on the page saves you every future reply.
- Post a second time only after something changed. A second post with the same page and the same pitch teaches nothing.
- Compare each tagged link. Note visits, first uses and conversations per channel, as laid out in launch metrics to track.
Subject: Did something get in the way? Hi [first name], You signed up for [product] on [day] but I can see you did not get as far as [the main action]. That is useful for me to know, not a criticism. Was it unclear what to do first, was something broken, or was it simply not what you needed? One line back is plenty, and I will read it myself. Thanks for trying it, [your name]
What does the first month look like?
| When | Job | Decision it feeds |
|---|---|---|
| Day 1 to 2 | Replies, triage, save numbers | What to fix before any more promotion |
| Day 3 to 7 | Follow-ups to signups, fix blockers, update the page | Whether the page explains the product |
| Week 2 | One new channel, with its own tagged link | Whether a second place reaches different people |
| Week 3 | One piece of writing that answers a question people asked | Whether search or sharing can bring visitors without you |
| Week 4 | Compare channels, write the retrospective | Keep, change or drop each channel; relaunch or move on |
At the end of the month, write a short retrospective while the details are fresh. The launch retrospective template gives you the questions. If the numbers say nobody wanted it, that is a result, and you have spent a month rather than a year learning it. If they say a few people wanted it a lot, the next job is the first hundred users, one conversation at a time.
When is it sensible to relaunch?
Relaunch when something material changed: a new capability, a new audience, a different promise on the page, or a fix for the thing that lost people. Do not relaunch because the first attempt was quiet and you hope the second will be louder. The same product with the same words will give the same result, and some places refuse the same website again within days. On this board, the same website cannot launch again within seven days.
If you do have something new, say what changed in the first line, and link the earlier discussion so nobody feels tricked. The decision rule is simple: if you can finish the sentence “this time, the difference for a visitor is…” with something a stranger would care about, relaunch. If you cannot, spend the week on the product. To bring the product to a fresh audience instead of a repeat, try one of the places that list new products and launch your product free on this board if you have not yet.
What should you skip, and which mistakes cost the most?
- Skip the redesign. A launch teaches you where people stumble; change those spots, not everything.
- Skip chasing links. A single useful conversation beats a dozen directory listings you never revisit.
- Skip comparing yourself with other launches that day. You do not know their audience, history or effort.
- Mistake: no record. If you cannot say what each channel sent, the month teaches you nothing.
- Mistake: only counting visits. Ten visitors who tried the product tell you more than two hundred who left.
- Mistake: silence after the thank-yous. Share one real update a month with the people who helped, and keep it honest.
When the month is done, a new idea is often the right next step. The ideas board holds ideas people have posted and will not build themselves.
Frequently asked questions
What should I do the day after I launch?
Reply to every unanswered comment, sort what people reported into blockers and annoyances, and save the numbers from your analytics before the window rolls forward. Thank anyone who helped. Do not post anywhere new until you have changed something real, because a second post with the same page repeats the first result.
How long should I keep watching the numbers after a launch?
Check them daily for the first week, then weekly for a month. Record visits, first uses and conversations per tagged link each time. Daily checking after that mostly produces anxiety, whereas a weekly table shows the trend. Stop when the retrospective is written and you have decided what to do next.
Is a quiet launch a failure?
Not necessarily. A quiet launch gives you a small sample, and a small sample can still answer which page text confused people and which channel reached anyone relevant. It fails only if you learn nothing from it. Write down what happened, change one real thing and try a different channel.
Should I thank people who voted or commented?
Yes, briefly and specifically. A one-line reply that names what the person said, or a short public thanks to the people who tried the product, takes minutes. Skip mass messages to everyone who clicked anything, and never reward votes with favours, since that pushes the launch toward vote trading.
Written by Post your build ideas with AI assistance and edited for this site. Where a page names another product, the facts came from that product’s own pages on the date shown above; terms change, so check them before you rely on them. About the publisher.