After product launch, what to do: a day-by-day plan for the first week

Last updated: 11 November 2026

In the week after launch, reply to everyone who reached out, get each new visitor to one first action, and write down what people told you. Don't start building new features yet. Attention fades within days, so the job is to turn it into a few real conversations and a short list of changes that the evidence supports.

This article assumes you've already shipped and listed your product. If you're still planning, start with our guide to launching a startup product and the launch checklist.

What should you do in the first 24 hours after launch?

In the first 24 hours, answer every comment and message, fix anything that is broken, and record where your visitors came from. Speed matters more than polish here, because people who comment or sign up are the ones most likely to talk to you.

• Reply to every comment and email, including the critical ones. Ask a follow-up question where it's natural, such as "What were you hoping it would do?"
• Check the sign-up flow yourself, on a phone and in a fresh browser. Launch traffic finds bugs you never saw.
• Save the numbers while they're fresh. Note visits, sign-ups, and upvotes or reactions on each channel. Analytics tools often sample or reset, so take screenshots.
• Thank people publicly where you can, and mention what you're fixing. A visible "fixed this morning" is cheap credibility.
• Write down your baseline. Post-launch analysis guides such as Usermaven's suggest starting the first week by checking the success criteria and baseline metrics you set before launch. If you didn't set any, set them now, using what you just recorded.

What should you do on days 2 to 4?

On days 2 to 4, personally contact the people who showed real interest and ask them one specific question each. A small number of real conversations is worth more than a large number of anonymous visits.

Sort your contacts into three groups

Group	How to spot them	What to ask
Signed up and used it	Created an account and finished a first action	"What were you trying to get done?"
Signed up but stalled	Account exists, no first action	"Was anything confusing or missing?"
Commented or upvoted only	Showed interest, didn't sign up	"What would you need to see before trying it?"

The stalled group is usually the most useful. They wanted the product enough to register and then hit friction you can fix.

Send short, human messages

A message that works is brief, from a named person, and asks one question:

Hi [name], I'm [your name], I built [product]. Thanks for trying it this week. You signed up but I can see you didn't get to [first action]. Did something get in the way? One line is plenty, and I'll fix what I can.

Avoid attaching a sales pitch, a discount, or a survey link. If you have fewer than 20 people to contact, write each message by hand.

Define the first action

Pick the one thing that shows a user got value, such as importing data, sending a first message, or publishing a first page. Then check how many new sign-ups reached it. That ratio tells you more than raw sign-up counts. If you've been vague about who the product is for, the tagline examples can help you restate the promise so new visitors understand it quickly.

How do you turn launch feedback into decisions?

Put every piece of feedback in one list, tag it, and act only on themes that show up more than once or that block the first action. One loud opinion isn't a roadmap, but three unrelated people hitting the same wall is.

Use a single document or spreadsheet with these columns: source, exact words, what the person was trying to do, and a tag. Keep their wording, because paraphrasing hides the problem.

Type of feedback	Example	What to do this week
Bug	"The confirmation email never arrived."	Fix immediately
Confusion	"I don't get what this does."	Rewrite the page copy or add a demo
Missing feature	"Can it export to CSV?"	Log it, count repeats, don't build yet
Wrong audience	"I'm a big enterprise team."	Note it, don't chase it
Praise	"Saved me an hour."	Ask permission to quote it

Usermaven's guide recommends prioritising fixes by impact and effort. A simple version works for a solo founder: do the high-impact, low-effort items first, and put the rest on a "later" list with a count of how many people asked.

Be careful with feature requests. People often describe a solution when they have a problem. When someone asks for a feature, reply with "What would that let you do?" The answer often points to something smaller.

What should you do on days 5 to 7?

On days 5 to 7, ship the small fixes, tell people you did, and publish what you learned. Closing the loop with the people who gave feedback is what turns a launch-day visitor into a returning user.

• Ship two or three fixes, not twenty. Pick the ones tied to the first action.
• Email or message everyone who gave feedback with what changed. If you didn't act on something, say why in a sentence.
• Update your product page. Replace weak screenshots, add a short demo, and fix any wording people misread. Our article on launch page screenshots covers which images to prepare.
• Add proof. If a user agreed to be quoted, put their words on the page with their name and permission. Don't make up or embellish quotes.
• Write a short launch retrospective. Cover what you did, what you saw, and what surprised you. This is useful for your own notes and works as an honest post for your audience.
• Review your numbers against the baseline from day one, and decide what you'll measure over the next three weeks.

How do you keep the attention going after launch week?

Keep the attention by giving it somewhere to land: a page that stays live, a way to hear from you again, and a steady rhythm of small updates. A launch is a spike, and what keeps people is a reason to come back.

Make the listing last

Where a launch listing stays online, it can keep sending visitors after the spike. On Launch Orbit, a product gets a permanent page, and boards rank launches weekly and monthly by community upvotes, so a listing keeps its history. Ask people who like your product to leave support while the weekly or monthly window is open, and link to your page from your own site. You can also add the Launch Orbit badge to your site so visitors can see where you launched.

Capture people who aren't ready yet

Not everyone who visits will sign up. Offer an email list or waitlist for those who want to hear about updates. If you didn't build one before launch, the principles in our piece on building a waitlist with no audience still apply afterwards.

Post small updates, not big announcements

Post a short changelog entry or note each time you ship something people asked for. "You asked, we shipped" is believable because it's checkable. If your launch went quietly, you aren't alone, and our launch notes on launching when nobody knows you cover what to do next.

Relaunch only with something new

You can launch again when you have a real change, such as a major feature, a new use case, or a new pricing model. Repeating the same launch with the same message rarely gives people a reason to look twice.

If you want a permanent home for your product page and community feedback, you can submit your product on Launch Orbit for free.

Frequently asked questions

How long should I wait before building new features after launch?

Wait until you've talked to at least a handful of users and seen the same request more than once. A week of listening and fixing is usually enough to separate real patterns from one-off opinions. Meanwhile, fix bugs and confusing copy right away.

What metrics matter most in the week after launch?

Track how many new visitors signed up, how many reached the first valuable action, and where they came from. Those three show whether attention is becoming usage. Traffic and upvote counts are a weaker signal because they don't tell you whether anyone got value.

What if my launch got almost no traffic?

Treat it as a small, useful test rather than a verdict. Contact the few people who did engage, check that your page explains the product within seconds, and share it in places where your specific audience already gathers. Low numbers give you the chance to learn from a manageable number of conversations.

Should I offer discounts to people who signed up during launch?

Only if you can explain why, and not as a substitute for understanding why people stalled. A discount can hide a confusing product. Ask first, fix the cause, and then consider an offer if price came up in the conversations.

Is it worth launching on more than one platform?

It can be, because different communities see different audiences. Spread launches out so you can respond properly to each, and use the same tracking so you can compare where useful users came from.