What to do after launch day: a 30-day plan to keep the momentum

The dip after launch day is normal

A launch sends you people who were browsing launches, not people looking for your product. Most of them look, some upvote, a few sign up, and almost all of them move on to the next one. So traffic falls after a day or two on every launch, good or bad.

Do not judge the launch by the spike. Judge it by what is left once the spike is gone: how many people signed up, how many of them came back, and what they told you. Those three numbers are what the next thirty days are for.

The 30 days at a glance

Block the time in your calendar before launch day. After it, the plan only happens if it is already there.

Days 1 to 3: reply, thank, fix

Start with the people who already did something. They are the warmest you will ever have, and they remember the launch for a few days at most.

• Reply to every comment. Questions, praise and criticism alike. Answer the question that was asked, thank people by name, and when someone reports a problem, say what you will do about it and when.
• Thank the people who shared it. A short personal message to anyone who posted about your launch, forwarded it or upvoted after you asked. You may want their help again.
• Fix what launch visitors ran into. A broken sign-up or a confusing first screen costs you every visitor who hits it. Fix those before anything else, even before features people asked for.
• Write down every request. One line each: who asked, what they asked for and why. You will sort them in week 2.

The rest of week 1: follow up with every sign-up

Someone who signed up during your launch was curious enough to try. Most will not come back on their own. A personal message from the founder is often the difference between one visit and a habit.

1. Write to each new user by hand. Not a sequence: two or three sentences that show a person read their sign-up. Ask what made them try it.
2. Look at what they did. Who reached the first useful result, and who stopped before it? The ones who stopped tell you where the product loses people.
3. Offer help to anyone stuck. A short call to set it up with them is slow, and it teaches you more than any dashboard.
4. Talk to a few properly. Book five short conversations with people who signed up, whether they stayed or left. Our customer interview questions give you a script.

If the launch brought only a handful of sign-ups, do the same for each of them, just more slowly. Our guide to your first 100 users covers the channels to work on next.

Week 2: ship what people asked for

By now you have a list of requests and problems. Sort it by two questions: how many people asked, and how much it gets in the way of the first useful result. Fix the few things that score high on both, and leave the rest on the list.

• Ship small and often: a few improvements this week beat one big one next month.
• Tell each person who asked for a fix that it is live. Few things turn a trial user into a fan faster.
• Keep a public changelog. It shows a moving product to everyone who finds you later, and it gives you something to share.
• Say no clearly to requests that pull the product away from its main job. Write down why, so you can explain it once and point to it after.

If you are unsure what to build first, score the list with the RICE prioritization calculator.

Week 3: launch a second wave

Now you have something the first launch did not: real feedback, quotes from users, fixes shipped and a sharper idea of who the product is for. That makes a better second launch.

• Launch on a few more sites. Pick three to five from our list of launch directories that match your audience, and space them out instead of posting everywhere on the same day. Our guide to directory submissions shows how to tell the useful ones from the rest.
• Rewrite the listing. Use the words users used to describe the product, not the words you started with. Our guide to writing a launch listing shows how.
• Turn the launch into content. What you learned, the numbers, the surprising feedback: a short honest post about the launch often travels further than the launch did.
• Tag every link. Add UTM tags to each link you share with the UTM builder, so in week 4 you know which channel brought users who stayed.

Week 4: measure what stuck

A month after launch you can see what happened. Visitors and upvotes no longer matter much. Look at the people who signed up and ask three questions:

1. How many came back? Of everyone who signed up in launch week, how many used the product again in week two, three and four? The line always falls at first. If it flattens out instead of reaching zero, some people have found a reason to stay, and that group is your product’s real market.
2. Who are they? Look at what the people who stayed have in common: their job, their company size, where they came from. Find more people like them next month.
3. Would they miss it? Once you have a few dozen active users, send the product-market fit survey. It asks how disappointed people would be without your product, and the answers show how close you are.

Then write the next month’s plan on one page: who to reach, what to fix and what to measure. A launch is not a finish line; it is the first time you learned all three at once.

Messages you can copy

Replying to a launch comment

Thanks [name]! [Answer to their question in one or two sentences.]

[If they raised a problem:] You're right about [problem]. I'm fixing it this week and will reply here when it's live.

Following up with someone who signed up

Hi [name], I'm [your name], I made [product]. Thanks for trying it during the launch.

What made you sign up? And if anything got in the way, tell me and I'll sort it out, or we can set it up together on a 15-minute call.

Telling someone their request is live

Hi [name], you asked for [feature] during the launch. It's live now: [link].

Thanks for asking, it made the product better. Anything else that would help?

Mistakes that waste a launch

• Going quiet after launch day. Comments without a reply and sign-ups without a hello tell people nobody is home.
• Chasing the next spike. Launching everywhere the week after, before fixing what the first launch showed you, spends new attention on the same problems.
• Building every request. Each person asks for their own feature. Build what many people need on the way to the first useful result, and keep the rest on a list.
• Measuring the wrong thing. Upvotes and visits feel good and say little. People who come back say a lot.

The checklist

Questions founders ask