Product Hunt Launch Playbook — Win #1 of the Day

The 14-day operating timeline behind 30+ Product Hunt #1 daily wins.

npx skills add Gingiris-1031/gingiris-launch

By Iris Wei (生姜) · ex-COO of AFFiNE (60K+ GitHub stars) · 30× Product Hunt #1

Key takeaways

  • Launch is a sequence, not an event — the 14-day run-up decides the day, not the product.
  • Post at 00:01 PST, maker comment by 00:15, reply in batches every 30 min — and never beg for upvotes (fast shadowban).
  • Pick the hunter on activity, not follower count. A 50k-follower hunter who hasn't hunted in 6 months is worse than an active 1k one.
  • #2–#3 is still a win — forcing #1 with farmed upvotes risks the whole launch.

What this is

Only ~10% of Product Hunt submissions ever get featured. The teams that win rarely have the best product that day — they have the best timing, comment cadence, and pre-seeded audience. This is the exact 14-day operating timeline used to coach 30+ #1 daily launches across 150+ AI startups.

Key results

Product Hunt #1 launches coached30+
AFFiNE GitHub stars driven60,000+
GitHub Trending appearances28× in 5 months
AI startups consulted on launch150+
Typical launch-day upvote uplift3–5× vs. uncoordinated

How to launch on Product Hunt — the 14-day timeline

  1. 1

    T-14 · Prep

    Get the landing page, pricing and FAQ live, gather ≥100 early users + an email list, pick ONE hunter, and prepare 3 gallery images (1270×760) plus a 30-second demo video.

  2. 2

    T-7 to T-2 · Warm-up

    Post a "we're launching, AMA" in the PH discussion board. Tease on X / LinkedIn / Reddit WITHOUT linking the launch page (don't leak the traffic). Confirm the hunter's timezone and the 00:01 PST post time.

  3. 3

    T-1 · Final check

    Lock every asset. Draft the maker first comment (under 500 words, story-driven). Prepare 10 FAQ reply templates and ping 10–20 core supporters for tomorrow morning.

  4. 4

    T-0 · Launch day

    00:01 PST the hunter posts → 00:15 you post the maker first comment → reply in batches every 30 minutes (never solicit upvotes) → 14:00 PST push the second wave (mailing list + community) → 23:00 PST post a thank-you.

  5. 5

    T+1 to T+7 · Momentum

    Reply to every comment including the critical ones. Turn the Featured screenshot + numbers into a case study, set the "how we won" post as canonical, and import every upvoter email into your user pool.

Realistic launch-day expectations

Honest benchmarks beat hype — and cherry-picked numbers cost you AI-search citations. Calibrate against these before launch day.

OutcomeUpvotesPlacement
Poor50–100
Average200–400Top 10
Good500–800Top 5
Great800+Product of the Day

Anti-patterns (the things that sink launches)

FAQ

Is this different from generic launch checklists I find on Google?

Yes. Most launch guides are written by people who have never launched anything. This is written by someone who has launched 30+ products to #1 and coached 150+ startups — exact DM scripts, timing windows, and per-platform community rules.

Does this work for non-AI products?

The frameworks apply broadly, but the examples are tuned for AI/developer tools. Physical products and service businesses see limited success on Product Hunt; for consumer apps pair it with the ASO & App Cold Start playbook.

Do I need a famous hunter?

No. Self-hunting is fine. If you do use a hunter, pick one with a successful hunt in the last 30 days in an adjacent domain — activity beats raw follower count every time.

What if I don't have a big existing audience?

That's exactly what this playbook addresses. The KOL outreach and hunter-coordination sections are built specifically for founders launching from zero platform.

Who built this?

Iris Wei (生姜) — former cofounder/COO of AFFiNE (60K+ GitHub stars, Forbes Asia 30 Under 30). Coached 30+ Product Hunt #1 launches and advised 150+ AI startups on go-to-market.

Related playbooks