Playbooks · Acquisition System

Product Hunt launch playbook, and what comes after

A one-day traffic event, not an acquisition channel. It can produce hundreds of signups and a handful of customers — and the gap between those is where founders lose the plot.

A Product Hunt launch is a one-day traffic event, not an acquisition channel. It can produce a few hundred signups and a handful of customers, and the difference between those two numbers is where founders lose the plot afterwards.

The short answer
  • Prepare for two weeks, launch for one day, judge it after six
  • Have pricing live and payment tested before you post
  • Be present in the comments all day — that is where conversion happens
  • Judge it on customers active at week six, not upvotes

A launch tests your description. It does not test your product, and it is not a growth strategy.

What a launch realistically produces

Traffic for one day, a spike in signups, and a conversion rate far below your normal one. All three are expected and none of them means much on their own.

The reason conversion looks bad is that a launch audience is full of people signing up because the product is interesting, not because they have the problem. That is not a failure — it is the nature of the traffic, and it contaminates your metrics for weeks unless you segment it.

Track the launch cohort separately from everything else. Blending it into your conversion rate produces a number that describes neither group, and it will make a healthy product look broken. Conversion benchmarks covers why traffic source dominates this metric.

Two weeks before

Four things must be working. Each one is a silent leak on the day.

Then write the assets: a one-line tagline, a first comment explaining why you built it, and three or four images that show the product doing its job rather than a feature tour.

The first comment matters more than most founders expect. It is the highest-read piece of copy in the whole launch, and it should say what problem this solves for whom — not tell your origin story.

Marcus · GhostCoach's AI coach
"I recommend deciding before launch day what number would mean it worked. Founders who skip that get four hundred upvotes and two customers, and genuinely cannot tell whether that was a success — so they launch again instead of fixing conversion."

Launch day

Block the day. The single largest determinant of outcome within your control is whether you are present in the comments, replying properly, for the whole day.

Four rules. Answer every comment within the hour. Reply personally to every signup, once. Write down the exact wording of every objection. Ship one small fix if something obvious breaks, but do not rebuild anything mid-launch.

Do not ask for upvotes directly — it violates the platform's rules and it is visible. Sharing the link with your own audience is fine and expected. For a longer list of launch day tips beyond these four rules, see the dedicated guide.

Week two onwards

The spike ends and the real work starts. Three numbers matter and none of them is upvotes.

MeasureReading
Signups who reached first valueUnder 20% means onboarding is the bottleneck
Launch-cohort conversion vs organicIf far worse, the traffic was curious, not qualified
Customers still active at week sixThe actual result of the launch

If you got plenty of signups and almost no customers, that has a specific diagnosis — why signups do not convert works through the four causes in order. If almost nobody signed up at all, that is a different problem again, covered by the flopped launch page.

Set the success number before launch day. A reasonable one for a first launch: ten people who reach first value and are still active thirty days later. Upvotes and signups are easier to get and tell you far less.

What a launch is actually for

Three things, and revenue is not really one of them.

It tests whether your one-line description makes strangers act, which is the cheapest positioning test available. It produces a batch of feedback and objections in a single day. And it creates a small pool of early users you can interview.

What it does not do is build a channel. The day after, you are back to whatever acquisition you had before — which is why the channel work should already be underway. Picking one channel covers that, and the wider launch playbook covers the full sequence around the day itself.

Product Hunt launch FAQ

Is a Product Hunt launch worth it?

As a one-day traffic event and a positioning test, yes. As an acquisition channel, no — the day after you are back to whatever you had before. Judge it on customers still active at week six rather than on upvotes or signups.

How many customers should I expect from Product Hunt?

Far fewer than the signup count suggests, because launch audiences contain many people signing up out of curiosity rather than need. A reasonable success measure for a first launch is ten people who reach first value and are still active thirty days later.

What should I prepare before a Product Hunt launch?

Pricing live and final, payment tested with a real card, activation instrumented, and a self-service first-run experience. Then a one-line tagline, a first comment explaining the problem you solve, and images showing the product working.

Why is my Product Hunt conversion rate so bad?

Launch traffic is qualitatively different from organic. Track the launch cohort separately — blending it into your overall conversion rate produces a number describing neither group and will make a healthy product look broken.

Should I ask people to upvote my launch?

No. Directly soliciting upvotes violates the platform's rules and is visible to moderators and users. Sharing the link with your own audience is fine and expected.

Set your launch-day success number

Tell Marcus your product and your list size. You get a realistic target and the sequence for the two weeks before.

Try GhostCoach free →

14-day free trial · cancel anytime · 30-day money-back on Lifetime