gingiris-1031/gingiris-skills/gingiris-launch

Product Launch — GTM Strategy & Product Hunt #1 Playbook

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

🌍 Language / 语言: English | 中文

产品类型分岔：先选你的路径

你的产品主要用户是谁？

路径 A：开发者 / maker（默认）

→ Product Hunt + GitHub + HN + dev 社区 → 继续阅读下面的 Launch SOP

路径 B：普通消费者（学生/上班族/游戏玩家等）

→ App Store + 垂类社区种子 + 内容获客 → 跳过 Product Hunt（受众错配，ROI 极低） → 冷启动渠道：Reddit 垂类 / 小红书 / TikTok / Quora / 知乎 → 免费产品当钉子（PLG）：先拿到前 100 个真实用户再放量 → 前 100 用户 SOP：在目标社区找近期抒怨同类问题的人 → 私信邀请免费试用 → 用户访谈固化 PMF

路径 C：B2B 决策者

→ LinkedIn 精准建联 + 行业媒体 + HARO → 继续阅读下面的 Launch SOP，重点看 B2B 部分

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

Hunter selection matrix

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

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.

• 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.

中文版

14 天时间线

Hunter 选择矩阵

活跃度 > follower 数。

Maker comment 6 种模板

1. Founder story — 为什么做 → 你的痛 → 解法
2. Before / After — 用你产品前后的对比
3. Key stats hook — 一个爆炸数据开头
4. Honest limitation — 承认还不完美，显真实
5. Community thanks — @ 点名测试用户
6. Tech stack pride — 技术选型（开发者向产品）

选哪个：to dev → 6；to general → 1 或 3。

反踩雷清单

• ❌ 发布当天还在改产品（flaky）
• ❌ 让亲友刷 upvote（PH 很快 shadowban）
• ❌ first comment 留外链（触发审核降权）
• ❌ 忘记 mobile 截图（40% 流量来自手机）
• ❌ 硬撑 daily #1（#2–#3 也是成功，且少被喷）

Go / no-go：预算分级产出基准

反直觉但实测成立：预算不高别卷 PH。 同样预算给 ~10 个 Twitter KOL/KOC，曝光和注册都更高——PH 曝光→upvote 转化仅 ~1%，而 Reddit 开源宣发曝光→star 转化 5–8%。

上票控速红线（真实支持者也要控速）

• 总量 ≤100 票/小时，单一渠道 ≤30 票/小时。 PH 约每 2 小时清一次可疑票，突刺会被剥掉。
• 请支持者用手机 + 蜂窝数据（4G）投票，别挤同一个办公室 Wi-Fi。
• badge 曝光分层：周榜曝光 ≈ 日榜 7 倍，月榜 ≈ 30 倍——先想清楚冲哪个榜，再决定花钱节奏。

发布日流量倒排法

先定总流量盘子 → 拆成每个渠道的硬数字 → 每渠道 UTM 短链归因。 实测案例（某 AI Agent 产品，2025-12）：发布日 50 万流量 = 40 万 Twitter（40 红人 quote）+ 2 万 Reddit + 2 万 YouTube 投流 + 2 万 TG/FB/LinkedIn 群 + 其余 → 约 800 注册、CAC $6.25。

会复利的节奏打法