What to do after your launch: a 7-day plan

The week after a launch is when most of its value is either collected or thrown away. It is also the week you are most tired, which is why nobody plans it. The launch was the event. The week after is where the event turns into users, reviews, links and a decision about what to do next.

Almost everything written on this topic is aimed at product teams with analysts and a marketing department. This is the version for one person. If you are still in the run-up, my launch week playbook covers the days before. Everything below starts when launch day ends.

What works only in the first 48 hours?

Anything that depends on someone remembering you. A person who commented on your launch yesterday will read a personal reply today. In three weeks, the same reply looks like a cold email. Attention fades fast and nothing you do will slow it down much, so use the window for the tasks that need it.

Three jobs belong here. First, answer every comment and message yourself, even the short ones. Second, email each person who left an address with a short, plain note and one question: what were you hoping this would do for you? Third, ask your happiest few users for a review or testimonial while the good feeling is fresh. The first reviews guide has wording that works, and the testimonials guide shows how to ask for a quote people can actually use.

What should you do on days 3 to 7?

Switch from tasks that need attention to tasks that last. These are slower and less satisfying, and they are the part of a launch that keeps paying after the thread goes quiet.

• Get listed in more places. Launch day uses up your energy, so the directories you skipped are still waiting. My launch directories guide lists where to go, and each listing is a link that keeps sending visitors long after launch week is over.
• Capture an email, not just a visit. If your launch brought people to a page with no way to hear from them again, fix that first. A single signup field is enough.
• Fix the one thing everyone tripped on. Read your comments and emails for the repeated complaint. One small fix that three people mentioned beats a new feature.
• Put proof where it can be seen. Move the best quote and any review to your homepage and your listing on the apps directory.

How do you talk to people who signed up and never came back?

Ask them. It sounds too simple, and it is the highest-value conversation of the week. Most people who sign up and vanish ran into one small obstacle, and the only way to learn which is to ask.

Write a short, personal email. Say you are the person who built it, say you noticed they signed up, and ask one question: what stopped you from getting started? Do not attach a survey. You are not after a statistically valid answer. You are after the reasons, and the number of conversations you need is small. The Nielsen Norman Group has argued for years that a handful of people per round, in its case five users in a usability test, surfaces most of the problems worth fixing. Five replies from lapsed signups will show you the pattern. If you are thinking about what to ask people before you ship the next version, the beta testers guide shows where to find more of them.

What should you publish about the launch, and when?

One short, honest write-up, published around day 5. By then you have something real to say, and the launch-day crowd has moved on, so the post reaches a fresh audience instead of repeating itself.

Make it a specific account, not a victory announcement. What did you build, who showed up, what surprised you, what will you change? Google's own guidance on helpful, people-first content asks for exactly this kind of original, first-hand writing, and the same quality that makes a post useful to a reader is what makes it worth linking to. Post it on your own site first, then share it where your launch lived. Supabase's write-up of how they run their own launches is a good model for the tone: plain, specific and about the work.

How do you read the results honestly, even a flat one?

Compare what happened to the goal you wrote down before launch, not to someone else's best day. If you did not write a goal, write one now and be honest that it is a guess. The point is to separate three things that blur together: how many people saw it, how many tried it, and how many came back.

A launch can be good at one and poor at the others. Many visitors and few signups means the pitch or the page is the problem. Many signups and few returns means the first experience is the problem. Few visitors at all usually means the audience was never in the room, which is a distribution problem and says nothing about the product. Which numbers to track, and which to ignore, is covered in launch metrics to track.

Then write the result in one paragraph. Plain words, no adjectives. A flat launch written up honestly is more useful than a good one you never looked at, because it names the assumption that was wrong.

How do you set the next milestone before the energy drops?

Do it on day 7, while you still know what the launch taught you. Pick one milestone, give it a date, and make it concrete enough that you can tell whether you hit it. "Get better at marketing" is not a milestone. "Ten people who finish setup, by the end of the month" is.

Tell the people who stuck around. A short update to your email list or the founder community is enough, and it turns a one-day event into an ongoing story. If you are weighing whether to go again soon, read how to relaunch your product first. A second launch only helps if something meaningful has changed since the first.

The 7-day schedule

Here is the whole week in one table, with a time estimate for each task and a parallel track for a launch that landed flat. The total is under ten hours of focused work, which is the point: it fits in the week when you are least able to plan.

Treat the times as estimates, not targets. If one task takes twice as long, drop the lowest-value item instead of working late. The order matters more than the clock: replies first, durable work second, review and planning last.

One more option for the middle of the week: ask other founders for help while your launch is still fresh. On Favors.dev, members earn points by leaving verified reviews, honest feedback and testimonials on each other's products, so the day 3 ask does not have to come only from your own users. The launch calendar also shows who is launching next, and a good comment on their page is a favor that tends to come back.

Frequently asked questions