Product Hunt for first-time founders: a 60-day pre-launch playbook

A Product Hunt launch is one day. The work that makes the launch land is the 60 days before it. Ryan Hoover started Product Hunt in November 2013 as a daily email to a small list of Silicon Valley operators. AngelList acquired it in June 2016. Since then the site has crowned roughly 4,400 daily winners and tens of thousands of Top-5 launches. Most of them produced one good day and nothing else. A small minority produced compounding sign-ups and a real audience. The difference between the two outcomes is rarely the product. It is the pre-launch work, and the launch-day mechanics. This playbook is the 60-day plan for a first-time founder launching from zero, with kill criteria you can defend.

// 01Is Product Hunt the right channel for you?

Product Hunt is a launch surface, not a distribution channel. Treat it as a distribution channel and you will be disappointed. A bare Top-of-the-Day finish typically produces 400 to 800 sign-ups, a small bump in DR for SEO, a handful of inbound press emails, and one good week of newsletter mentions. After that the spike returns to baseline. The founders who turned Product Hunt into a real channel (Loom, Cron before the Notion acquisition, Submagic, Arc browser) used the launch as the trigger for the work, not the work itself.

Three filters for whether the channel is worth 60 days

• Your product is shippable, screenshot-friendly, and live today: Product Hunt rewards a product the visitor can try in under 60 seconds. A free tier, a public demo, or a short Loom video. A 14-day-trial gated behind a credit card kills your launch on the first hover. A B2B product that requires a sales call to see anything works far worse than an indie SaaS with a free plan.
• You have 60 days of runway to do the work before launching: A no-audience launch with no pre-launch work gets 30 to 80 upvotes and finishes outside the top 20. The same product, after 60 days of network seeding and asset preparation, gets 300 to 700 upvotes and finishes in the top 5. The number of upvotes on the day is roughly linear with the size and quality of the network you built before it.
• You can finish the launch-day shift yourself: Launch day is a 16-hour live event starting at 12:01am Pacific. Replies to comments matter as much as the upvotes themselves. The maker who lives in the comments for the first 12 hours always outperforms the maker who checks in at lunch. If you cannot block the day on the calendar, push the launch.

// 02The 60-day pre-launch plan

Run the plan as eight weekly milestones. Each one produces a concrete artifact you can count. Block the launch date on a Tuesday or Wednesday, never Friday through Sunday. Avoid major launch weeks (Apple events, Y Combinator demo days, big competitor launches), because the daily feed is more crowded.

Weeks 1 to 2: Build the 100-person hunter list

Build an email list of 100 people who have all three of these properties: 1) a Product Hunt account at least 30 days old, 2) they have upvoted at least 5 products in the past 90 days, and 3) they are plausibly your buyer or are interested in your space. The list is the asset. Without it, every other piece of the plan is wasted.

Three honest sourcing channels: 1) your existing Twitter and LinkedIn followers who tweet about your space; 2) the comment sections of recent launches in your category; 3) warm intros from founders you know who have launched on PH in the last six months. Avoid the paid “Product Hunt upvote groups” entirely. The accounts in them are flagged and their votes do not count.

Weeks 3 to 4: Land the assets and make the page non-negotiable

The Product Hunt page is the asset that does the most work. The launch image (1270x760 pixels), the gallery (3 to 5 images plus optional video), the tagline (60 characters), and the description (260 characters) are the four elements visitors read in the first 8 seconds.

• Tagline: One concrete benefit, in 60 characters or fewer. Not a category. "Run marketing experiments without the $40k tool" beats "The experimentation platform for modern teams" every time.
• Gallery: Real product screenshots, in this order: 1) the moment of value, 2) the workflow that gets you there, 3) the result. No stock images. No mockups in iPhone frames if the product is a desktop app.
• Demo video: Under 90 seconds, with captions. The video plays muted by default on mobile, so captions are mandatory. The first 5 seconds must show the product, not a logo animation.

Weeks 5 to 6: Seed the network and pre-write the launch comments

Email the 100-person hunter list with a personal message, not a blast. The message is short: a one-line reminder of who you are, the launch date, the asset you are launching, and one specific way they can help. Three asks work and one does not. The three that work: upvote in the morning of launch day, leave one honest comment, share it with one specific person you think would care. The one that does not: “Please retweet.” Generic amplification does not move the day.

Pre-write 20 to 30 of your own comments before launch day. The maker who can paste a thoughtful 3-paragraph reply to every early comment in the first hour will outpace the maker who is composing them live. The comments matter because Product Hunt’s algorithm appears to weight comments-per-upvote ratio at least as heavily as raw upvote count.

Weeks 7 to 8: Dress rehearsal and launch

In the final week, run two full dry runs of launch morning. Open the product, walk through your demo path, and time it. Pre-stage every channel announcement (Twitter post, LinkedIn post, email to your list, Indie Hackers post, and the PH page itself) as drafts on launch day morning. Schedule nothing, because the algorithm reads same-instant social pushes as a bot pattern. On launch day, post manually within the first hour.

// 03Kill criteria and what good looks like

Product Hunt is a one-day event, so the kill threshold has to be set before the day starts, not measured 60 days out. The point is to write down what a defensible result looks like so you are not negotiating with yourself at 11pm on launch day. See the kill threshold definition for the framework.

• Launch-day upvotes: Good: 300 or more, which historically lands in the top 5 of the day for a non-AI-flagship product. Kill: under 80. Under 80 means the pre-launch network did not show up; the cause is in weeks 1 to 5, not in the assets.
• Seeded-vs-organic upvote split: Good: 40% to 60% of upvotes come from your 100-person list, and the rest from cold PH traffic. Kill: more than 90% from the seeded list. A 90%+ seeded launch means the page did not earn organic upvotes; the algorithm noticed and capped the post.
• Day-of-launch sign-ups: Good: 100 or more new sign-ups in 48 hours. Kill: 15 or fewer. Sign-ups, not upvotes, are the metric that maps to revenue. A top-5 launch with no sign-ups means the product page won and the landing page lost.

// 04What to do when it works, and when it does not

When the playbook works

A working launch is the start, not the finish. The day after, you have somewhere between 300 and 800 sign-ups, 5 to 10 inbound press emails, 2 to 4 podcast invitations, and a backlink from productHunt.com that will help your SEO compound for years. The 30 days after the launch matter as much as the 60 before it.

Three moves in the post-launch month. First, write one honest retrospective post within 7 days: what worked, what did not, real numbers, no humblebrag. The retrospective itself is usually the highest-traffic post you will ever write. Second, send a personal thank-you email to each of the 100 hunter-list members. Many of them become customers, design partners, or quiet champions if you treat the launch as the start of a relationship rather than a transaction. Third, archive the launch assets (the gallery, the tagline, the demo video) into your landing-page library. They have already been tested against a live audience.

When it does not work

If you missed all three kill thresholds, the diagnostic question is not “why did PH not work”; it is “what does the data tell us about the product, not the channel.” Three patterns are common.

• Top-5 finish, zero sign-ups: The PH page worked, the landing page did not. Run a controlled test in the 30 days after launch on the landing page’s first 200 words. Replace the category positioning with the exact tagline from your PH page.
• Under 80 upvotes, strong engagement on the comments: The product resonated with the few who saw it, but the seed network was too thin. The fix is not a re-launch on Product Hunt; it is 90 days of audience-building on Twitter, LinkedIn, or Reddit, then a relaunch of a new feature once a 200-person list exists.
• Under 80 upvotes, low engagement: The pre-launch network did not show up and the cold audience did not click in. The honest read is that PH is the wrong channel today. Re-pick using the GTM engine playbook before scheduling another launch.

For founders in the third bucket especially, the GTM engine playbook is the right next read. A failed PH launch is often a signal that distribution work needs to start two or three channels upstream of PH, not be replaced by another launch on the same surface.

// 05Five things to carry forward

• 01: Product Hunt is a launch, not a channel. The 60 days before the launch decide the outcome; the 30 days after decide whether the spike compounds or fades.
• 02: The 100-person hunter list is the asset. Without it, the algorithm and the cold visitor will judge a no-audience product the same way they always have.
• 03: Comments are weighted at least as heavily as upvotes. The maker who lives in the comments for 12 hours outperforms the maker who checks in three times a day.
• 04: Sign-ups are the only metric that matters at day +2. A top-5 launch with 12 sign-ups is a landing-page problem, not a launch problem.
• 05: A failed launch is rarely a channel verdict. It is a signal about audience size, product readiness, or landing-page conversion. The diagnostic comes first, the relaunch comes much later.