🇺🇸 Product Launch & Product Hunt #1 Playbook — Multi-channel launch timing and sequencing. T-14 warm-up → T-0 launch day → T+7 momentum. Hunter selection,...
--- name: gingiris-launch description: | 🇺🇸 Product Launch & Product Hunt #1 Playbook — Multi-channel launch timing and sequencing. T-14 warm-up → T-0 launch day → T+7 momentum. Hunter selection, maker comment templates, comment cadence, anti-shadowban rules. Distilled from 30+ Product Hunt #1 daily launches across 150+ AI startups. **Supports 3 product paths: developer/maker (PH+GitHub), B2C consumer (Reddit/communities/TikTok, skip PH), B2B (LinkedIn+media).** 🇨🇳 产品发布与 Product Hunt 夺冠手册 — 多渠道发布的时序与节奏。T-14 预热 → T-0 发布日 → T+7 后续。Hunter 选择、maker comment 模板、评论节奏、防 shadowban。提炼自 30+ 次 Product Hunt 日冠、150+ AI 创业公司实战。**支持三种产品路径:开发者/maker(PH+GitHub)、2C 消费者(社区种子/TikTok,跳过 PH)、B2B(LinkedIn+媒体)。** 🇯🇵 プロダクトローンチ&Product Hunt 1位プレイブック — マルチチャネルのローンチ時系列。T-14準備→T-0当日→T+7モメンタム。ハンター選定、メーカーコメント、コメントリズム、シャドウバン回避。**3つの製品パス対応:開発者/maker(PH+GitHub)、2C消費者(コミュニティ種・TikTok、PHスキップ)、B2B(LinkedIn+メディア)。** 🇰🇷 제품 출시 & Product Hunt 1위 플레이북 — 멀티채널 출시 타이밍과 시퀀싱. T-14 워밍업 → T-0 출시일 → T+7 모멘텀. 헌터 선정, 메이커 코멘트, 댓글 리듬, 섀도밴 방지. **3가지 제품 경로 지원: 개발자/maker(PH+GitHub), 2C 소비자(커뮤니티 씨드/TikTok, PH 건너뜀), B2B(LinkedIn+미디어).** Triggers: "product launch" | "launch strategy" | "Product Hunt" | "PH launch" | "how to launch" | "go to market" | "GTM" | "launch day" | "find a hunter" | "maker comment" | "launch sequencing" | "发布策略" | "产品发布" | "发 PH" | "Product Hunt 准备" | "找 hunter" | "ローンチ" | "출시 전략" when_to_use: | Use this skill when you need to: execute a Product Hunt launch, plan multi-channel GTM sequencing (T-14 to T+7), select a hunter, write maker comments, seed launch-day community engagement, or build cold-start momentum for a new product. Trigger phrases: "product launch" | "Product Hunt" | "GTM" | "launch strategy" | "发布策略" | "产品发布" | "发PH" | "找hunter" | "출시 전략" --- # Product Launch — GTM Strategy & Product Hunt #1 Playbook > 🌍 **Language / 语言**: [English](#english-version) | [中文](#中文版) ## 产品类型分岔:先选你的路径 **你的产品主要用户是谁?** ### 路径 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 | 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. ### 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 天时间线 | 阶段 | 动作 | |:---|:---| | **T-14 准备** | 落地页、定价、FAQ 就绪。≥100 早鸟用户 + 邮箱列表。选 **1 个** hunter。3 张主 gallery 图 + 1 个 30 秒 demo。 | | **T-7 到 T-2 预热** | PH discussion 发一篇 "we're launching, AMA"。X / LinkedIn / Reddit 预告但**不贴发布页链接**(别抢自己流量)。给用户列表打招呼。确认 hunter 时区 + **PST 00:01** 发布时间。 | | **T-1 终检** | 锁定全部 asset。写好 first comment(<500 字)。备 10 条 FAQ 回复模板。提醒 10–20 个核心支持者。 | | **T-0 发布日** | **00:01 PST** hunter 发布 → **00:15** 你发 maker first comment → 每 30 分钟回一批评论(绝不刷 upvote)→ **14:00 PST** 推 second wave → **23:00 PST** 发感谢帖。 | | **T+1 到 T+7 后续** | 回完所有评论(含差评)。把 Featured 截图 + 数据做成 case study。进 daily #1 就写 "how we won" 并设 canonical。所有 upvoter 邮箱导入用户池。 | ### Hunter 选择矩阵 | 优先级 | 标准 | |:---|:---| | **P0** | 最近 30 天有成功 hunt 且产品领域相似 | | **P1** | Follower 1k+ 且每周活跃 | | **P2** | 有真实社交关系(聊过、共同朋友) | | ❌ | Follower 50k+ 但 6 个月没 hunt — 虚荣指标、触达低 | **活跃度 > 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:预算分级产出基准 | 预算 | 现实产出 | |:---|:---| | ~$1K | 小几百注册(YouTube 小额投流 + 垂直 subreddit + 主题群) | | $5K | 24h 约 1,800 票可达——但有实战案例冲上日榜第一后被 PH 事后清票收回,控速红线不是建议是保命 | | $1–2 万 | ~100 万曝光 + 小几千注册 | | <$2 万 | 过万 star 的开源发布(执行团队 ≤5 人) | **反直觉但实测成立:预算不高别卷 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**。 ### 会复利的节奏打法 - **双日结构**——发布日(一半红人导官网)+ 打榜日(另一半导 PH),两个目标互不稀释流量。 - **KOL 集中爆破窗口**——50–100 个 KOL 约定同一 24–48h 内发布,制造算法级爆点。 - **"60 分启动"**——产品 60 分就开始备发布物料;launch 就绪判据:**≥10 个开发者满意且持续在用**。 - **四大传播支柱**(Manus/Devin 复盘):产品力叙事基础 → 情绪叙事 → 影响者飞轮 → 平台接力(Day 0–3 X 造话题 → Day 3–10 YouTube/Substack 沉淀 → Day 10+ Reddit/HN 长尾)。 - **可复现性决定情绪叙事的天花板。** 真心惊喜 ≠ 人情帮转:同一个 KOL,推荐可复现产品 2.8M 浏览 vs 人情转发只有 ~20 个赞。 ### Hacker News 速查规则 - 上首页标准:**发帖 30 分钟内 30 upvote + 10 评论**;35–45 分钟还没起来就掉出首页。 - 北京时间 18:00–20:00 发(美国上午)。 - HN agency 约 $500/帖,ROI 差,不推荐。 - 一鱼两吃:英文稿直译发 V2ex / linux.do。 --- *By Iris (生姜 Iris) · ex-COO @ AFFiNE (60k★), 30× Product Hunt #1 · Install: `npx skills add Gingiris-1031/gingiris-launch`*
don't have the plugin yet? install it then click "run inline in claude" again.