gingiris-launch

Product Launch — GTM Strategy & Product Hunt #1 Playbook

Case-number and citation boundaries: references/podcast-evidence.md.

🌍 Language: English | Chinese

Product type fork: choose your path first

Who are your product's main users?

Path A: Developer / maker (default)

→ Product Hunt + GitHub + HN + dev communities → Continue reading the Launch SOP below

Path B: General consumers (students/office workers/gamers, etc.)

→ App Store + vertical community seeding + content acquisition → Skip Product Hunt(audience mismatch, extremely low ROI) → Cold-start channels: Reddit verticals / Xiaohongshu / TikTok / Quora / Zhihu → Free product as the wedge (PLG): get the first 100 real users before scaling → First 100 users SOP: find people in target communities recently complaining about the same problem → DM them to invite a free trial → solidify PMF through user interviews

Path C: B2B decision-makers

→ LinkedIn targeted outreach + industry media + HARO → Continue reading the Launch SOP below, focusing on the B2B section

---

A launch is a sequence, not an event. The teams that win Product Hunt rarely have the best product that day — they have the best timing, comment cadence, and pre-seeded audience. This playbook is the 14-day operating timeline distilled from 30+ #1 daily launches.

---

English Version

The 14-day timeline

Window	What you do
T-14 — Prep	Landing page, pricing, FAQ all live. ≥100 early users + email list. Pick one hunter. 3 gallery images + one 30-second demo video ready.
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). Greet your list. Confirm hunter timezone + 00:01 PST post time.
T-1 — Final check	Lock every asset. Draft the first comment (<500 words). Prepare 10 FAQ reply templates. Ping 10–20 core supporters for tomorrow morning.
T-0 — Launch day	00:01 PST hunter posts → 00:15 you post the maker first comment → reply in batches every 30 min (never solicit upvotes) → 14:00 PST push the second wave (mailing list + community) → 23:00 PST post a thank-you.
T+1 to T+7 — Momentum	Reply to every comment, including the critical ones. Turn the "Featured" screenshot + numbers into a case study. If you hit daily #1, write a "how we won" post and set it as canonical. Import every upvoter email into your user pool.

Hunter selection matrix

Priority	Criteria
P0	Successful hunt in the last 30 days and an adjacent product domain
P1	1k+ followers and active (posts weekly)
P2	A real relationship (you've talked, mutual friends)
❌	50k+ followers but no hunt in 6 months — vanity, low reach

Find hunters: producthunt.com/@<category>-hunters. Activity beats follower count.

Maker comment — pick one of 6 archetypes

1. Founder story — why you built it → your pain → the fix
2. Before / After — life without your product vs. with it
3. Key-stat hook — open with one explosive number
4. Honest limitation — admit what's not perfect yet (reads as real)
5. Community thanks — @-name the users who tested
6. Tech-stack pride — your architecture choices (for dev-facing products)

Choose by audience: dev product → #6; general → #1 or #3.

Anti-pitfall checklist

• ❌ Don't still be changing the product on launch day (flaky).
• ❌ Don't have friends/family farm upvotes — PH shadowbans fast.
• ❌ Don't put external links in the first comment (triggers review demotion).
• ❌ Don't forget mobile screenshots (40% of traffic is mobile).
• ❌ Don't force daily #1 — #2–#3 are wins too (and draw less hate).

Go / no-go: budget-tier benchmarks

Budget	Realistic output
~$1K	A few hundred signups (YouTube micro-ads + niche subreddits + topic groups)
$5K	~1,800 votes/24h — #1 within reach, but a real campaign at this level had its daily #1 revoked post-hoc; respect the pacing red lines
$10–20K	~1M impressions + low-thousands signups
<$20K	10k+ star open-source launch (execution team ≤5 people)

Counter-intuitive but field-tested: on a small budget, skip PH. The same spend on ~10 Twitter KOL/KOCs yields more exposure and signups — PH exposure→upvote converts at ~1%, while open-source promo on Reddit converts exposure→star at 5–8%.

Vote velocity red lines (pace even your real supporters)

• ≤100 votes/hour total, ≤30/hour from any single channel. PH sweeps suspicious votes roughly every 2 hours — a spike gets stripped.
• Ask supporters to vote from mobile + cellular data (4G), not one office Wi-Fi.
• Badge exposure tiers: a weekly badge ≈ 7× the exposure of a daily badge, monthly ≈ 30× — decide which leaderboard you're actually fighting for before you spend.

Launch-day traffic: plan backwards

Set the total traffic target first → split it into per-channel hard numbers → attribute with per-channel UTM short links. Field case (an AI Agent product, 2025-12): 500K launch-day visits = 400K Twitter (40 KOL quotes) + 20K Reddit + 20K YouTube ads + 20K TG/FB/LinkedIn groups + the rest → ~800 signups, CAC $6.25.

Sequencing patterns that compound

• Two-day structure — launch day (half your KOLs → website) + leaderboard day (other half → PH), so the two goals don't dilute each other's traffic.
• KOL burst window — 50–100 KOLs commit to posting within the same 24–48h to trigger an algorithmic spike.
• "60-point start" — start prepping launch assets when the product is at 60%; the launch-ready bar is ≥10 developers satisfied and still actively using it.
• Four propagation pillars (Manus/Devin post-mortems): product strength as the narrative base → emotional narrative → influencer flywheel → platform relay (Day 0–3 X builds the topic → Day 3–10 YouTube/Substack consolidates → Day 10+ Reddit/HN long tail).
• Reproducibility sets the ceiling of the emotional narrative. Genuine wow ≠ polite repost: the same KOL drew 2.8M views recommending a reproducible product vs ~20 likes on a favor-share.

Hacker News quick rules

• Front-page bar: 30 upvotes + 10 comments within 30 minutes of posting; if it hasn't moved by minute 35–45, it drops off.
• Post at 18:00–20:00 Beijing time (US morning).
• HN agencies at ~$500/post are poor ROI — skip them.
• One fish, two meals: translate the same English post straight into Chinese for V2ex / linux.do.

PH is a paid channel — the free Thu/Fri/Sat play

Treat PH as paid marketing by default: Mon–Wed are high-traffic days you usually only win with paid pushes. The zero-spend alternative (field-tested, took a daily #1 — self-reported):

1. Decide the goal first: branding (fight the Mon–Wed vote pool, budget it) vs. a batch of early customers (Thu–Sat is enough).
2. Launch on Thursday / Friday / Saturday — lower traffic, much weaker competition.
3. Pull votes by hand: LinkedIn groups (e.g. 4 groups, a few hundred to 1,000+ members each) + private communities — DM members one by one, never bulk-blast.
4. Assets fully prepared before posting: 1 video + 5 gallery images.

Badge-or-relaunch rule

• Daily / weekly / monthly boards each badge the top 5 only — if you launch, launch to take a badge.
• If launch-day competition is too strong for top 5: email PH support ("we made a mistake"), request removal, relaunch on a quieter day. Caveat: this trick is now widely used and PH has started pushing back — last resort only.
• Per-launch yield to expect: low hundreds to high thousands of signups + a few dozen Discord joins + backlinks from media that scrape the boards (self-reported baseline).

The core formula and the 4-step launch SOP

Marketing = precise user-channel matching × high-quality content design.

Step	Action
1. Fill the SOP template	Each launch type has its own template doc; the team fills in the blanks
2. Channel breakdown → list	Decide in-house vs. agency per channel; make each channel concrete (Reddit: which subreddits, whose DMs, which competitor's users)
3. Content pack ×3	Confirmed one-line intro + key feature points + user cases
4. 80/20	~80% of the method repeats across launches; 20% is customized to this product's edge

• Minimum crew: 1 full-time + 1–2 interns runs a decent launch; training an in-house team takes ≈1–2 months (self-reported).
• ROI baseline for a well-run organic-heavy launch: ≈$10–20K budget → hundreds of thousands to ~1M impressions → thousands to 10K+ signups (self-reported consulting benchmark).

Launch-day combo (4 parallel actions)

The same-day action set behind a ≈6,000-star first week (open-source launch, 2022 — self-reported):

1. Post in target communities (Reddit etc.).
2. DM the follower lists of your named competitors — this alone converted a few hundred stars.
3. Publish the launch article + a README a stranger grasps in one pass.
4. Submit to directory / navigation sites (a competitor's zero-budget launch covered ~40 channels in one day, ~20 of them directories).

48-hour timed-vote case (election ≈ leaderboard day)

A 48h student-union election — structurally the same game as a PH launch window:

• Walk the funnel yourself first: voting took ~5 min (register → find seat → find candidate → captcha). High friction means casual traffic is worthless — mobilize strong-intent supporters only.
• Fight only your base: target the ~3,600-person core group, not the 10K+ whole campus.
• Seed the must-pass spots: elevators, library entrance, canteen doors; 40+ volunteers in 5 squads, tasks assigned by proximity.
• Result: 800+ votes in 48h, ≈2× the runner-up (recalled numbers, self-reported).

What to do next

• Launch day + 24h → monitor "<product> product hunt" keyword rankings.
• Hit daily #1 → write the "how we won" post, set canonical to your domain.
• Heavy skepticism in comments → open formal user interviews.

---

Chinese version

14-day timeline

Phase	Action
T-14 Preparation	Landing page, pricing, FAQ ready. ≥100 early-bird users + email list. Choose 1 hunter. 3 main gallery images + 1 30-second demo.
T-7 to T-2 Warm-up	Post a "we're launching, AMA" in PH discussion. Tease on X / LinkedIn / Reddit butdo not post the launch page link(don't steal your own traffic). Greet your user list. Confirm hunter time zone + PST 00:01 launch time.
T-1 Final check	Lock all assets. Write the first comment (<500 words). Prepare 10 FAQ reply templates. Remind 10–20 core supporters.
T-0 Launch day	00:01 PST hunter launches → 00:15 you post the maker first comment → reply to a batch of comments every 30 minutes (never ask for upvotes) → 14:00 PST push the second wave → 23:00 PST post a thank-you post.
T+1 to T+7 Follow-up	Reply to all comments (including negative ones). Turn the Featured screenshot + data into a case study. If you reach daily #1, write "how we won" and set the canonical. Import all upvoter emails into the user pool.

Hunter selection matrix

Priority	Criteria
P0	Has a successful hunt in the last 30 days and a similar product area
P1	Follower 1k+ and active weekly
P2	Has a real social relationship (have chatted, mutual friends)
❌	Follower 50k+ but hasn't hunted in 6 months — vanity metric, low reach

Activity > follower count.

6 maker comment templates

1. Founder story — why you built it → your pain → the solution
2. Before / After — before-and-after comparison with your product
3. Key stats hook — start with an explosive data point
4. Honest limitation — admit it's not perfect yet, show authenticity
5. Community thanks — @ mention test users
6. Tech stack pride — tech stack choices (for developer-oriented products)

Which to choose: to dev → 6; to general → 1 or 3.

Anti-pitfall checklist

• ❌ Still changing the product on launch day (flaky)
• ❌ Asking friends and family to upvote (PH shadowbans quickly)
• ❌ first comment leaves an external link (triggers review and ranking demotion)
• ❌ forgetting a mobile screenshot (40% of traffic comes from phones)
• ❌ forcing your way to daily #1 (#2–#3 is also a success, and you get less flak)

Go / no-go: budget-tier output benchmarks

Budget	Realistic output
~$1K	A few hundred signups (small YouTube ad spend + vertical subreddits + topical groups)
$5K	About 1,800 votes in 24h is achievable—but there are real cases where someone surged to #1 on the daily chart and then had their votes revoked and stripped by PH afterward; the vote-pace red line is not a suggestion, it's survival
$10–20K	~1M impressions + a few thousand signups
<$20K	An open-source launch that gets over 10K stars (execution team ≤5 people)

Counterintuitive but proven in practice: if your budget isn't high, don't fight over PH. Give the same budget to ~10 Twitter KOLs/KOCs, and both impressions and signups are higher—PH impressions→upvote conversion is only ~1%, while Reddit open-source promotion impressions→star conversion is 5–8%.

Vote-pace red line (even real supporters need pacing control)

• Total ≤100 votes/hour, single channel ≤30 votes/hour. PH clears suspicious votes about every 2 hours, and spikes get stripped.
• Ask supporters to vote with **mobile + cellular data (4G)**, and don't cram everyone onto the same office Wi-Fi.
• Badge exposure tiers: weekly chart exposure ≈ 7x daily, monthly ≈ 30x—first figure out which chart you're targeting, then decide your spending pace.

Launch-day traffic reverse-calculation method

First set the total traffic target → break it into hard numbers per channel → attribute each channel with a UTM short link. Real case (an AI Agent product, 2025-12): 500K launch-day traffic = 400K Twitter (40 influencers quoting) + 20K Reddit + 20K YouTube ad spend + 20K TG/FB/LinkedIn groups + the rest → About 800 signups, CAC $6.25。

A compounding cadence playbook

• Two-day structure—launch day (half the influencers drive to the website) + chart-climbing day (the other half drive to PH), so the two goals don't dilute each other's traffic.
• KOL concentrated blitz window—50–100 KOLs agree to post within the same 24–48h to create an algorithm-level explosion.
• "60-point launch"—start preparing launch materials when the product is at 60 points; launch-readiness criteria:≥10 developers are satisfied and keep using it。
• Four major communication pillars(Manus/Devin retrospective): product-strength narrative foundation → emotional narrative → influencer flywheel → platform relay (Day 0–3 X builds the topic → Day 3–10 YouTube/Substack consolidate → Day 10+ Reddit/HN long tail).
• Reproducibility determines the ceiling of the emotional narrative. Genuine surprise ≠ a favor repost: for the same KOL, recommending a reproducible product got 2.8M views vs. a favor repost getting only ~20 likes.

Hacker News quick reference rules

• Criteria for making the front page:30 upvotes + 10 comments within 30 minutes of posting; if it hasn't taken off by 35–45 minutes, it drops off the front page.
• Post at Beijing time 18:00–20:00 (US morning).
• HN agency is about $500/post, poor ROI, not recommended.
• Two meals from one fish: translate the English draft directly and post it to V2ex / linux.do.

PH is essentially a paid channel—the Thursday/Friday/Saturday free playbook

By default, treat PH as paid marketing: Monday to Wednesday are high-traffic days, and you basically have to spend money to get traction. Zero-budget alternatives (self-reported, having actually taken the #1 spot on the daily leaderboard):

1. Set the goal first: do you want branding (compete for the vote pool on Monday to Wednesday, with budget) or just a batch of early customers (Thursday, Friday, Saturday is enough).
2. ChooseThursday / Friday / Saturdayto launch — traffic is low and competition is much weaker.
3. Ask for votes manually: LinkedIn communities (e.g., 4 groups, each with a few hundred to 1,000+ people) + private communities —DM one by one, never mass-send.
4. Prepare all materials before launch: 1 video + 5 images.

Badge iron rule: if you don't get it, relaunch

• daily / weekly / monthly leaderboardsonly the top 5 in each get a badge— if you're going to launch, launch aiming for the badge.
• If competition on launch day is too strong to make the top five:email the PH team ("we made a mistake") to request removal, and relaunch on a lower-competition day. Note: as more people use this trick, the team has started to crack down — treat it only as a last resort.
• Expected return from a single launch: a few hundred to a few thousand signups + a couple dozen people joining Discord + backlinks from self-media climbing the leaderboard (self-reported baseline).

Core formula and the four-step launch SOP

marketing = Precise matching of user channels × high-quality content design.

Step	Action
1. Fill in the SOP template	Each launch type has a dedicated template document, and the team fills in the blanks
2. Break down channels → make a list	For each channel, decide whether to run it in-house or outsource; channels must be targeted and specific (Reddit: which subreddits, who to DM, which competitor's users to target)
3. Content package trio	One-sentence intro confirmation + key feature points + user case
4. 80/20	Methodology is ~80% common across launches, 20% customized to product strengths

• Minimum setup:1 full-time + 1–2 internsis enough to complete a relatively decent launch; building an in-house team takes about 1–2 months (self-reported).
• ROI baseline for a well-executed organic-led launch:≈$10–20k budget → hundreds of thousands to over a million impressions → a few thousand to over ten thousand signups(self-reported from consulting practice).

Launch-day combo moves (4 parallel actions)

The same-day combo behind ~6,000 stars in one week (open-source launch, 2022, self-reported):

1. Post in target communities (Reddit, etc.).
2. DM the follower list of comparable competitors— this alone converted a few hundred stars.
3. Publish an article + a README that can be understood in one pass.
4. Submit to navigation / directory sites (one competitor's zero-budget launch covered about 40 channels in a day, about 20 of which were directory sites).

48-hour time-limited leaderboard case (campaign ≈ leaderboard day)

A 48-hour voting-window student council campaign — structurally isomorphic to a PH launch day:

• Go through the funnel yourself first: Casting one vote takes about 5 minutes (register → find seat → find candidate → captcha). High friction means broad traffic is useless—only mobilize strong-willed supporters.
• Only target the base: Target the core group of ~3,600 people, and don't touch the 10,000+ overall group.
• Cover must-pass points: Elevators, library entrance, cafeteria entrance; 40+ volunteers divided into 5 squads, assigned by proximity.
• Result:800+ votes in 48 hours, about 2 times the runner-up(recalled numbers, self-reported).

---

By Iris (生姜 Iris, the author's Chinese name) · ex-COO @ AFFiNE (60k★), 30× Product Hunt #1 · Install: npx skills add Gingiris-1031/gingiris-launch

Join the global community and purchase the resource pack · Community & Resources

• Join the global community: Add on WeChat staywildgrow, leave the message "join the community" and you're in.

• Purchase the resource pack: Add on WeChat staywildgrow, inquire about purchasing the Gingiris global resource pack, price 599 RMB。

• Join the global growth community: Add staywildgrow on WeChat and send "join the community" (join the community).

• Get the resource pack: Add staywildgrow on WeChat to purchase the Gingiris global growth resource pack for CNY 599.

The community and resource pack are optional entry points and do not affect the installation and use of this open-source Skill.

The community and paid resource pack are optional; neither is required to install or use this open-source skill.