Launch boards

Relaunch on every big release

Several boards allow a new listing after a major update. Treat each version as a fresh announcement, and check each board's rules.

Cost
Free

Free to use. No paid tier is needed to list or post.

Verdict
works

Works: each major release is a fresh reason to post on boards that allow it.

Difficulty
Easy

Mostly self-serve. Sign up and post, with light checks.

Effort
Medium

About 5 to 10 hours a month.

First result
1 day per release

A rough range for one person working on it part-time.

Payoff
Spike

a burst of traffic, then it fades.

Best for

Products that ship real updates.

Not for

Products that ship rarely, or boards that treat relaunches as spam.

Pros

  • Each release is a fresh story
  • Reuses channels you already know

Cons

  • Boards limit relaunches
  • Needs a real update each time

The full guide

Last verified 2026-10-30

Links checked 2026-10-30 · No website to check: this channel works by word of mouth or offline

01What it is and who is there

Relaunching means treating each major release as a new announcement on the launch boards and communities that allow it. Product Hunt's own launch page says you can launch again "as often as you have new significant product iterations available." The audience is the same as each board's, but a new version gives you a real reason to show up again.

02Cost and what you actually pay for

It costs nothing beyond the boards you use. Most launch boards are free, with optional paid placement. The real cost is building a release worth announcing.

03Is it right for you?

It fits products that ship meaningful updates: a new major feature, a new platform, or a new use case. It fits poorly for products that only fix small bugs, and for boards that do not allow repeat launches. Each board has its own rules, so check them before you relaunch.

04Before you start

  • A release that a new visitor would notice, such as a new feature or a redesign.
  • A changelog entry and a short demo of what changed.
  • A list of boards that allow relaunches, with their current rules.
  • An updated landing page that leads with the new version.

05Step-by-step: how to distribute here

  1. Decide whether the release is big enough. If a first-time visitor would not notice it, wait.
  2. Check each board's rules on repeat launches.
  3. Write the announcement around what is new, not the whole product.
  4. Launch on one main board first, then share in communities over the week.
  5. Email your existing users about the release on the same day.
  6. Log results per release, so you know which boards still work for you.

06What to post or submit

Title:

[Product] [version]: [the new thing, in plain words]

First comment:

Since our last launch, we [main change]. You asked for [feature], and it's here: [how it works]. Existing users get it today. New users can try it at [link].

07Common mistakes and do-nots

  • Do not relaunch without a real change. Boards and readers notice.
  • Do not break a board's rules on repeat launches.
  • Do not repost the identical page and copy from your first launch.
  • Do not forget your existing users. They are the easiest audience for a release.

08How to measure it

  • Track visits and sign-ups per relaunch with a fresh UTM tag.
  • Compare each relaunch with the first launch.
  • A realistic test: if each relaunch brings fewer users than the last, change the angle or the boards.

09Time budget

  • Before: 3 to 6 hours per release for the page, demo and posts.
  • During: 1 to 3 hours on launch day.
  • After: 1 hour to log results.

10Pair it with

11Sources

Sources