Skip to content
Live42 checked claims
marketinque

Product Hunt and launch days

A launch is a few weeks of preparation around one day. What the platform itself says about ranking, hunters and asking for upvotes matters more than the folklore around them.

21 steps, about 32 hours of work · 3 plays · 4 checked claims

A Product Hunt launch is won in the three weeks before it. The account needs a history, the followers need to be in place, the gallery and first comment need to be written, and a real user needs to be ready to comment. Launch day is about replies, not upvote requests, and the recap often travels further than the launch.

The concept, explained in full: Product marketing.

Do it

Every step in the free launch plan that this topic needs, in the order you need them. Each keeps its plan number.

  1. What should be ready before the three weeks start?5 steps
  2. What do you do in the three weeks before launch?11 steps
  3. What happens on launch day?5 steps
  4. How do you make the launch last longer than a day?5 steps

What should be ready before the three weeks start?

The assets every launch platform asks for, written once.

  1. 1.2.2.5Record a 60–90 second demo video

    Product Hunt listings with a video tend to get more upvotes. Sources that give a multiplier disagree, from about 2× to 4×, so treat the direction as sound and the number as unknown. Reused a dozen times later.

    2hFlowjam’s launch video cost guideevidence: weak

  2. 3.2.1.1Write a tagline under 10 words

    Outcome first. Every form has this field and most have a hard character limit.

    20m

  3. 3.2.1.2Write the 50-word short description

    What it does and for whom, in the words a directory’s own search results show. Forms with a 60-character limit take the tagline instead.

    20m

  4. 3.2.1.5Write the founder story in three sentences

    Curated directories reject listings without one. Reused verbatim on launch day.

    25m

  5. 1.6.4Put email capture on the site

    Even with nothing to send yet. The list you start today is the launch audience in Phase 2.

    45m

What do you do in the three weeks before launch?

Warm the account, build the notification list, and write everything you will post on the day.

  1. 3.5.1.1Day −21: warm up your account

    Three thoughtful comments a day for two weeks. A cold account reads as a throwaway.

    7h

  2. 3.5.1.2Day −21: follow 100+ active makers

    They are the notification surface on launch day.

    30m

  3. 3.5.1.3Day −14: create the Upcoming page

    Every subscriber is a guaranteed notification the moment you go live.

    45mProduct HuntDR 91how to do it

  4. 3.5.1.4Day −14 to −1: drive traffic to the Upcoming page

    This is the only pre-launch asset that converts directly into first-hour momentum.

    2h

  5. 3.5.1.5Day −10: line up a hunter, optional

    Product Hunt’s own FAQ says who posts a product does not affect its ranking; one practitioner sample of 30 launches puts a hunter’s share of upvotes at 15–25% with no method. If you want one, it is for their audience. Trade a feature or an intro, never cash.

    1hevidence: strong (2)

  6. 3.5.1.7Day −7: write the tagline and 260-character description

    Reuse the kit from 2.2.1 — this is why you wrote three variants.

    45m

  7. 3.5.1.8Day −7: write your own first comment

    Why you built it, what is different, what to try first. Posted the second you go live.

    45m

  8. 3.5.1.9Day −7: line up a customer to comment

    Product Hunt says position depends on comments as well as points, and that upvotes from established, active members count for more. A real user’s early comment helps on both.

    20mevidence: moderate

  9. 3.5.1.10Day −3: warm up your email list

    “We launch Tuesday, here is what to expect, reply for a heads-up.” No ask yet.

    30m

  10. 3.5.1.11Day −1: run the whole flow in incognito

    Signup, checkout, video autoplay, CTA destination. On a phone, on mobile data.

    45m

What happens on launch day?

Go live early, post the first comment at once, and answer every comment fast.

  1. 3.5.2.1Go live at 12:01 AM Pacific, Tuesday to Thursday

    Maximises the 24-hour window. Weekend launches reach fewer people; published estimates of how many fewer run from 40% to 70% and none shows its data.

    15m

  2. 3.5.2.2Post your first comment immediately

    The story you already wrote. Never let the comment section open empty.

    15m

  3. 3.5.2.3Reply to every comment within 30 minutes

    Product Hunt says position depends on points, comments, time since launch and other signals, so answer every comment quickly. The platform does not say that maker responsiveness itself is weighted.

    8hevidence: moderate

  4. 3.5.2.4Share to every channel you own

    X thread, LinkedIn long-form, your list, Indie Hackers, your communities. Not strangers’ DMs.

    2h

  5. 3.5.2.5Ask for feedback, never for upvotes

    Product Hunt’s FAQ says never to ask for upvotes, which can get an account flagged as spam: share the link and ask for feedback instead. No source gives a conversion multiplier for either.

    5mevidence: strong

How do you make the launch last longer than a day?

Echo it on the platforms that reward a launch, then publish the honest recap.

  1. 3.5.3.1Post Show HN — only with a technical angledev tool

    Architecture, a novel approach, a hard problem. “We launched a SaaS” gets flagged to death.

    45mHacker NewsDR 91 · nofollow

  2. 3.5.3.2Submit to BetaList

    Two-to-four week queue unless you pay to expedite. Submit early.

    20mBetaListDR 64how to do it

  3. 3.5.3.3Submit to the secondary launch platforms

    Fazier, Uneed, Microlaunch, DevHunt, PeerPush, OpenHunts, TinyLaunch. #1 is achievable on several.

    2h

  4. 3.5.3.4Publish the launch recap with real numbers, day 2

    Honest, including what flopped. Recaps consistently out-travel the launch itself.

    2hhow to do it

  5. 3.5.3.5Cross-post the recap to Indie Hackers and r/SaaS

    Both permit promotion in this format, and both index well.

    30m

Plays

Reusable patterns that explain how: backed by read sources first, then practitioner advice, then our own ideas.

  • Listing on the niche directories your buyers browsePractitioner · 1 source

    Submit the product to the few niche directories and launch platforms your buyers actually browse, with a keyword-aware, benefit-led description and a real screenshot. Niche directories convert better than generic ones, often rank for "[category] tools" queries themselves, and supply durable backlinks that strengthen your domain.

  • A Product Hunt launch treated like a campaignPractitioner · 1 source

    Treat Product Hunt as a campaign, not a lottery ticket: teaser page up early, a demo video and origin-story maker comment ready, genuine first-hour supporters lined up, and full-day comment presence. The rank matters less than the residue — the badge, the backlink, early adopters, and a launch-day audience you keep.

  • Give away the entire playbook you sell withOur idea

    Post your full working method as a thread — every step, template, and threshold, nothing held back. Generosity at this level is rare enough to travel, and it sorts the audience perfectly: DIY readers become your distribution, while the people with money and no time buy the thing that executes the playbook.

What the evidence says

Sources

Founder questions

What day should you launch on Product Hunt?

A weekday, Tuesday to Thursday, going live at 12:01 AM Pacific time so you get the full 24-hour window. Weekend launches get far less traffic.

Should you ask people to upvote your launch?

No. Ask for feedback instead. Asking for upvotes can trip Product Hunt’s anti-manipulation filters, and comments from real users count for more than raw votes.

Do you need a hunter to launch on Product Hunt?

No. A hunter is optional and worth a modest share of day-one momentum at most. Trade a favour or an introduction for one, and never pay cash.

Related topics

Go further

Where it sits in the plan

Keep reading

The whole library, sourced.

Topics, plays, terms and the evidence behind each launch-plan step, every claim linked to the page it came from.