Skip to the content
LaunchedHere
Sign in Launchyours

When and How to Relaunch a Product

Strategy · 8 min read ·

A relaunch can give a quiet product a second chance. When it is worth doing, what must be genuinely new, and how to plan one without annoying people.

Illustration: Bold sticker of a rocket landing on its tail and getting ready for a second take-off, flat bright colours

Not every product has its moment the first time. Some launch quietly and then grow into something much better. Some change direction. Some take an honest look at the first attempt and realise the page was wrong, the audience was wrong or the product was not ready. When that happens, founders wonder whether they can launch again.

Sometimes they can, and it can be a very good idea. Done badly, though, a relaunch looks like a stunt. This guide helps you decide whether to do one and how to do it with integrity.

Why relaunch at all?

A relaunch makes sense when the situation has genuinely changed. Typical reasons:

The product is much better. The first launch happened when the product was rough. You have since fixed, rebuilt or extended it in ways a visitor would notice.

The audience has changed. You found that your real customers are different from the people you targeted. A new message for a new audience is, in effect, a new introduction.

There is a big new capability. A feature that changes what the product is for, such as a mobile app, a team version or an integration, can justify fresh attention.

The market has moved. Something has changed in your category that makes your product more relevant than before.

The first launch was missed. You may have launched into a crowded week, or with a poor page, and want a fair second try.

If your reason is only "the first launch did not get enough votes", pause. A relaunch driven by disappointment alone rarely gives a different result.

What platforms say

Rules on repeated launches vary, so read the policy of the platform you plan to use. The Show HN guidelines are a useful example of the principle. They say that minor version updates, such as "Foo 1.3.1", do not qualify, and that the work should be something people can try. In other words, the community expects something substantial.

Product Hunt's launch guidance describes launching as an event where makers share a product with a global audience, and emphasises being ready. Whether a second launch is permitted for the same product depends on its current rules, so check them directly before you plan anything.

Is it significant enough? A test

Ask yourself five questions.

  1. Could a stranger tell the difference? If you showed someone the old page and the new one, would they see a different product?
  2. Is there a new reason to try it? Something a person who ignored it last time might now care about?
  3. Would an existing user notice? Would they say "that is much better" rather than "I think something changed"?
  4. Can you say what is new in one sentence? If not, it is probably not new enough.
  5. Would you be comfortable explaining it to the first batch of people who followed you? If you would feel awkward, the story is not honest yet.

If the answer to most is yes, proceed. If not, publish an update, a changelog entry or a blog post instead. Those are the right tools for smaller changes.

How to frame a relaunch honestly

The worst thing a relaunch can do is pretend the earlier version never existed. Instead, tell the true story.

  • Say what has changed. "Since our first launch, we rebuilt the editor, added team accounts and cut the sign-up from five steps to two."
  • Say what you learned. "Our first audience was freelancers. Most of our growth came from small agencies, so we rebuilt around them."
  • Credit the people who helped. Early users whose feedback shaped the product deserve thanks.
  • Do not claim to be new. "Version 2" or "Relaunched" is an honest label. "Brand new" is not.

People generally respond well to honest evolution. Indie Hackers, for example, describes itself as a community of people working together to build profitable online businesses, with discussions and case studies from founders sharing their journeys, and a candid "here is what we changed and why" story fits that tradition.

Plan it like a first launch, only better

A relaunch gives you an advantage the first one lacked: experience. Use it.

Review your old launch. Read the comments again. Which questions were asked most? Which confusions came up? Fix them in the new page.

Update the assets. New thumbnail, tagline and gallery that reflect the current product. Our guide on designing a first impression covers it.

Use your real results. If you now have customers, you may be able to show a real example, with permission.

Mobilise your existing community. People who followed your first launch will be interested in what has changed. Tell them, and ask for honest feedback, not votes.

Plan the first hour. Our playbook applies as much the second time as the first.

Choose your moment carefully. Avoid weeks you know will be crowded, and make sure you are rested and available.

What not to do

  • Do not relaunch to farm votes. If the sole aim is a better ranking, it will show.
  • Do not relaunch too soon. A few weeks after the first is rarely enough change.
  • Do not hide the history. People will find the earlier page and wonder why you did not mention it.
  • Do not make exaggerated claims such as "completely reinvented" for a modest update.
  • Do not ignore rules. If a platform limits repeat launches, follow its policy.
  • Do not neglect existing customers. They should hear from you before strangers do.

Relaunch alternatives

Sometimes another route serves you better.

  • A changelog or release note for steady improvements.
  • A founder update post telling the story of what changed.
  • A new directory listing if you have changed category or audience, which is something many platforms allow you to edit.
  • A feature-specific announcement when only one part is new.
  • A case study featuring a real customer.

Use whichever matches the size of the change.

A relaunch checklist

  1. Write one sentence describing what is new.
  2. Confirm the platform's policy on repeat launches.
  3. List the three biggest changes since the first launch.
  4. Rebuild the page: tagline, thumbnail, gallery, description.
  5. Tell existing customers first.
  6. Prepare helpers, asking for visits and comments only.
  7. Plan the first hour and the day after.
  8. Write the honest story of what changed and why.

How long to wait

There is no fixed rule, but a sensible measure is whether your product has changed enough that the story would be different. For many founders that means at least several months of real development and real customers. A relaunch after a year, with a rebuilt core and a clearer audience, is more convincing than three relaunches in a season.

On this site

On our site, you can relaunch a listing into a later week from your account, where the relaunch price is quoted; whether the product has changed enough is your call, and the acceptable use page sets out what is allowed. The launch calendar shows the schedule. A launch entry is currently $5, and the leaderboard page shows the standings. The about-founders page names the two people who built the site.

Two short case sketches

The product that found its audience. A small team built a note-taking app for students. The first launch was polite but quiet. Over the next year they noticed that most paying users were researchers writing literature reviews. They rebuilt the editor around citations, rewrote the page for that audience and relaunched. The story they told was simple and true: "We thought this was for students; it turned out to be for people with a hundred sources to track." The relaunch drew an audience that had barely noticed the first.

The product that was not ready. A founder launched a booking tool with a half-finished payment flow. The comments were full of the same complaint. Six months later, with payments working and a clear onboarding, she relaunched with a page that began: "Last time, the payment step let you down. We rebuilt it." People who had been put off came back to look. Her honesty about the earlier problem did more than any slogan.

What the sketches share is a specific, checkable change and a truthful story. Neither relied on novelty alone.

Talking to people who saw the first launch

Before you announce publicly, write to the people who engaged the first time: those who commented, signed up or gave feedback. Tell them what you changed in response to what they said and invite them to look. Keep the message short, name the specific thing they raised and avoid asking for anything beyond a look and an honest opinion. These are the people most likely to notice progress and most likely to say so in public, which is far more convincing than anything you write about yourself.

The takeaway

A relaunch is a second chance, not a second trick. Do it when the product is clearly better or aimed at a clearly different audience, tell the true story and plan with everything the first launch taught you. Then the second time can be the one that counts.

Questions and answers

Can I launch the same product twice?
Rules vary by platform. Many allow a new launch when there is a significant update. Check the platform's policy, and make sure there is something genuinely new to show.
What counts as significant enough for a relaunch?
A major new capability, a different audience, a rebuilt product or a new version that changes what customers can do. Small fixes are better shared as updates.
How long should I wait before relaunching?
Long enough for the product to change in ways a stranger would notice. For many products that is several months.
Will a relaunch upset people who saw the first one?
Not if you are honest about what has changed and do not pretend it is new from scratch.

Sources

Related guides

Support