Install
openclaw skills install @gingiris-1031/gingiris-launchGingiris Launch
🇺🇸 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. 🇨🇳 产品发布与 Product Hunt 夺冠手册 — 多渠道发布的时序与节奏。T-14 预热 → T-0 发布日 → T+7 后续。Hunter 选择、maker comment 模板、评论节奏、防 shadowban。提炼自 30+ 次 Product Hunt 日冠、150+ AI 创业公司实战。 🇯🇵 プロダクトローンチ＆Product Hunt 1位プレイブック — マルチチャネルのローンチ時系列。T-14準備→T-0当日→T+7モメンタム。ハンター選定、メーカーコメント、コメントリズム、シャドウバン回避。 🇰🇷 제품 출시 & Product Hunt 1위 플레이북 — 멀티채널 출시 타이밍과 시퀀싱. T-14 워밍업 → T-0 출시일 → T+7 모멘텀. 헌터 선정, 메이커 코멘트, 댓글 리듬, 섀도밴 방지. 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" | "ローンチ" | "출시 전략"
Product Launch — GTM Strategy & Product Hunt #1 Playbook
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
- Founder story — why you built it → your pain → the fix
- Before / After — life without your product vs. with it
- Key-stat hook — open with one explosive number
- Honest limitation — admit what's not perfect yet (reads as real)
- Community thanks — @-name the users who tested
- 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).
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 种模板
- Founder story — 为什么做 → 你的痛 → 解法
- Before / After — 用你产品前后的对比
- Key stats hook — 一个爆炸数据开头
- Honest limitation — 承认还不完美，显真实
- Community thanks — @ 点名测试用户
- Tech stack pride — 技术选型（开发者向产品）
选哪个：to dev → 6；to general → 1 或 3。
反踩雷清单
- ❌ 发布当天还在改产品（flaky）
- ❌ 让亲友刷 upvote（PH 很快 shadowban）
- ❌ first comment 留外链（触发审核降权）
- ❌ 忘记 mobile 截图（40% 流量来自手机）
- ❌ 硬撑 daily #1（#2–#3 也是成功，且少被喷）
By Iris (生姜 Iris) · ex-COO @ AFFiNE (60k★), 30× Product Hunt #1 · Install: npx skills add Gingiris-1031/gingiris-launch