Gingiris commited on
Commit
f1b93cc
·
verified ·
1 Parent(s): 403d91d

Add podcast evidence to launch

Browse files
skills/gingiris-launch/.gitattributes ADDED
@@ -0,0 +1,60 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ *.7z filter=lfs diff=lfs merge=lfs -text
2
+ *.arrow filter=lfs diff=lfs merge=lfs -text
3
+ *.avro filter=lfs diff=lfs merge=lfs -text
4
+ *.bin filter=lfs diff=lfs merge=lfs -text
5
+ *.bz2 filter=lfs diff=lfs merge=lfs -text
6
+ *.ckpt filter=lfs diff=lfs merge=lfs -text
7
+ *.ftz filter=lfs diff=lfs merge=lfs -text
8
+ *.gz filter=lfs diff=lfs merge=lfs -text
9
+ *.h5 filter=lfs diff=lfs merge=lfs -text
10
+ *.joblib filter=lfs diff=lfs merge=lfs -text
11
+ *.lfs.* filter=lfs diff=lfs merge=lfs -text
12
+ *.lz4 filter=lfs diff=lfs merge=lfs -text
13
+ *.mds filter=lfs diff=lfs merge=lfs -text
14
+ *.mlmodel filter=lfs diff=lfs merge=lfs -text
15
+ *.model filter=lfs diff=lfs merge=lfs -text
16
+ *.msgpack filter=lfs diff=lfs merge=lfs -text
17
+ *.npy filter=lfs diff=lfs merge=lfs -text
18
+ *.npz filter=lfs diff=lfs merge=lfs -text
19
+ *.onnx filter=lfs diff=lfs merge=lfs -text
20
+ *.ot filter=lfs diff=lfs merge=lfs -text
21
+ *.parquet filter=lfs diff=lfs merge=lfs -text
22
+ *.pb filter=lfs diff=lfs merge=lfs -text
23
+ *.pickle filter=lfs diff=lfs merge=lfs -text
24
+ *.pkl filter=lfs diff=lfs merge=lfs -text
25
+ *.pt filter=lfs diff=lfs merge=lfs -text
26
+ *.pth filter=lfs diff=lfs merge=lfs -text
27
+ *.rar filter=lfs diff=lfs merge=lfs -text
28
+ *.safetensors filter=lfs diff=lfs merge=lfs -text
29
+ saved_model/**/* filter=lfs diff=lfs merge=lfs -text
30
+ *.tar.* filter=lfs diff=lfs merge=lfs -text
31
+ *.tar filter=lfs diff=lfs merge=lfs -text
32
+ *.tflite filter=lfs diff=lfs merge=lfs -text
33
+ *.tgz filter=lfs diff=lfs merge=lfs -text
34
+ *.wasm filter=lfs diff=lfs merge=lfs -text
35
+ *.xz filter=lfs diff=lfs merge=lfs -text
36
+ *.zip filter=lfs diff=lfs merge=lfs -text
37
+ *.zst filter=lfs diff=lfs merge=lfs -text
38
+ *tfevents* filter=lfs diff=lfs merge=lfs -text
39
+ # Audio files - uncompressed
40
+ *.pcm filter=lfs diff=lfs merge=lfs -text
41
+ *.sam filter=lfs diff=lfs merge=lfs -text
42
+ *.raw filter=lfs diff=lfs merge=lfs -text
43
+ # Audio files - compressed
44
+ *.aac filter=lfs diff=lfs merge=lfs -text
45
+ *.flac filter=lfs diff=lfs merge=lfs -text
46
+ *.mp3 filter=lfs diff=lfs merge=lfs -text
47
+ *.ogg filter=lfs diff=lfs merge=lfs -text
48
+ *.wav filter=lfs diff=lfs merge=lfs -text
49
+ # Image files - uncompressed
50
+ *.bmp filter=lfs diff=lfs merge=lfs -text
51
+ *.gif filter=lfs diff=lfs merge=lfs -text
52
+ *.png filter=lfs diff=lfs merge=lfs -text
53
+ *.tiff filter=lfs diff=lfs merge=lfs -text
54
+ # Image files - compressed
55
+ *.jpg filter=lfs diff=lfs merge=lfs -text
56
+ *.jpeg filter=lfs diff=lfs merge=lfs -text
57
+ *.webp filter=lfs diff=lfs merge=lfs -text
58
+ # Video files - compressed
59
+ *.mp4 filter=lfs diff=lfs merge=lfs -text
60
+ *.webm filter=lfs diff=lfs merge=lfs -text
skills/gingiris-launch/README.md ADDED
@@ -0,0 +1,190 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ ---
2
+ license: mit
3
+ language:
4
+ - en
5
+ - zh
6
+ - ja
7
+ - ko
8
+ pretty_name: "Gingiris AI Product Global Launch Playbook — Product Hunt, KOL & UGC Growth"
9
+ tags:
10
+ - product-launch
11
+ - product-hunt
12
+ - go-to-market
13
+ - startup-marketing
14
+ - ai-startup
15
+ - growth-hacking
16
+ - kol-outreach
17
+ - ugc-marketing
18
+ - viral-growth
19
+ - launch-strategy
20
+ - gtm
21
+ - startup
22
+ - growth
23
+ - marketing
24
+ - ai-growth
25
+ size_categories:
26
+ - n<1K
27
+ ---
28
+
29
+ # 🚀 Gingiris AI Product Global Launch Playbook
30
+
31
+ > **Battle-tested launch strategies from 30+ Product Hunt #1 wins — including Manus, Devin, and AFFiNE (60k GitHub stars).** Built by Iris (生姜iris), Forbes Asia 30 Under 30, former cofounder & COO of AFFiNE.
32
+
33
+ **[English](#english) | [中文](#中文版) | [日本語](#日本語) | [한국어](#한국어)**
34
+
35
+ ---
36
+
37
+ ## English
38
+
39
+ ### What Is This?
40
+
41
+ The **Gingiris AI Product Global Launch Playbook** is an operational guide covering the full arc of a product launch: pre-launch positioning, Product Hunt day execution, KOL/influencer outreach, Reddit and community seeding, UGC growth loops, and post-launch momentum maintenance.
42
+
43
+ Unlike generic marketing templates, this playbook is built from **real launch campaigns** — Manus (AI agent), Devin (first AI software engineer), AFFiNE (open-source Notion alternative), and 27+ other AI products that hit Product Hunt #1. Every tactic has a specific time, template, and decision point.
44
+
45
+ ### Key Results (Verified)
46
+
47
+ | Metric | Result |
48
+ |:---|:---|
49
+ | Product Hunt #1 launches coached | 30+ |
50
+ | AFFiNE GitHub stars driven | 60,000+ |
51
+ | GitHub Trending appearances | 28 times in 5 months |
52
+ | AI startups consulted on launch | 150+ |
53
+ | Typical launch-day engagement rate uplift | 3-5x engagement vs. passive launch |
54
+
55
+ ### What's Inside
56
+
57
+ - **Pre-launch checklist** — 30-day, 7-day, 48-hour countdown templates
58
+ - **Product Hunt hunter outreach** — Scripts, timing, hunter database (top 50 by category)
59
+ - **Launch-day operation playbook** — Hour-by-hour schedule, comment moderation, community engagement momentum
60
+ - **KOL outreach templates** — Cold DM scripts for Twitter/X, LinkedIn, Telegram influencers
61
+ - **Reddit & HackerNews seeding** — Community rules, timing, authentic framing (no spam)
62
+ - **UGC growth loop** — How to turn early users into content creators
63
+ - **Post-launch momentum** — 7-day, 30-day follow-up cadence to sustain traffic spike
64
+ - **Case studies** — Manus, Devin, AFFiNE with annotated timelines
65
+
66
+ ### Use Cases
67
+
68
+ - AI SaaS launching on Product Hunt for the first time
69
+ - Developer tools going global (出海) from Asia/Europe
70
+ - Open-source projects wanting a coordinated launch moment
71
+ - Mobile apps bootstrapping initial user acquisition
72
+ - Any founder who has built something great and needs the world to know
73
+
74
+ ### When Should I Use This?
75
+
76
+ Use this playbook when you have a product that is **ready to ship** (or 2-4 weeks away) and want a structured, repeatable launch process. This is not for ideation — it's for execution.
77
+
78
+ ### What Results Can I Expect?
79
+
80
+ Teams following this playbook consistently achieve:
81
+ - Top-5 Product Hunt ranking on launch day (30+ have hit #1)
82
+ - 500-2,000 genuine signups in the first 24 hours
83
+ - 10-50 pieces of organic social content from community members
84
+ - Sustained Google Search impressions from launch-related content for 90+ days
85
+
86
+ ### FAQ
87
+
88
+ **Q: Is this different from generic launch checklists I find on Google?**
89
+ A: 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. The difference is in the specificity — exact DM scripts, timing windows, community rules for each platform.
90
+
91
+ **Q: Does this work for non-AI products?**
92
+ A: The frameworks apply broadly, but the examples and templates are tuned for AI/developer tools. If you're launching a consumer app, pair with the `gingiris-aso-growth` playbook.
93
+
94
+ **Q: What if I don't have a big existing audience?**
95
+ A: That's exactly what this playbook addresses. The KOL outreach and hunter coordination sections are specifically for founders with zero existing platform.
96
+
97
+ ---
98
+
99
+ ## 中文版
100
+
101
+ ### 这是什么?
102
+
103
+ **Gingiris AI 产品全球发布行动指南**——涵盖产品发布全流程的实操手册:上线前定位、Product Hunt 当日执行、KOL/网红外联、Reddit 和社区种草、UGC 增长循环、发布后动能维持。
104
+
105
+ 区别于泛泛的营销模板,本手册来自**真实发布战役**——Manus(AI Agent)、Devin(首个 AI 软件工程师)、AFFiNE(开源 Notion 替代品)及 27+ 个拿下 Product Hunt 日冠的 AI 产品。每个策略都有具体的时间节点、模板和决策分支。
106
+
107
+ ### 核心数据
108
+
109
+ | 指标 | 成果 |
110
+ |:---|:---|
111
+ | Product Hunt 日冠辅导 | 30+ 次 |
112
+ | AFFiNE GitHub Star 增长 | 60,000+ |
113
+ | GitHub Trending 上榜 | 5 个月内 28 次 |
114
+ | AI 创业公司发布咨询 | 150+ |
115
+
116
+ ### 内容清单
117
+
118
+ - **发布前 Checklist** — 30 天、7 天、48 小时倒计时模板
119
+ - **Product Hunt Hunter 外联** — 话术、时机、Top 50 Hunter 名单
120
+ - **发布日操作剧本** — 逐小时排期、评论运营、点赞动能策略
121
+ - **KOL 外联模板** — Twitter/X、LinkedIn、Telegram 冷 DM 话术
122
+ - **Reddit 和 HN 种草** — 社区规则、时机、真实框架(反 spam)
123
+ - **UGC 增长循环** — 如何把早期用户变成内容创作者
124
+ - **发布后持续运营** — 7 天、30 天跟进节奏
125
+ - **案例解析** — Manus、Devin、AFFiNE 带注释时间线
126
+
127
+ ---
128
+
129
+ ## 日本語
130
+
131
+ ### これは何ですか?
132
+
133
+ **Gingiris AI製品グローバルローンチプレイブック** — プロダクトローンチの全行程をカバーする実践ガイド。Product Hunt 30回以上の1位獲得経験から構築。Manus、Devin、AFFiNE(60k GitHub stars)などの実際のキャンペーンに基づく。
134
+
135
+ **主な内容**: プリローンチチェックリスト、Product Hunt当日の運営、KOLアウトリーチテンプレート、Reddit/HNシーディング、UGC成長ループ、ローンチ後の維持戦略。
136
+
137
+ ---
138
+
139
+ ## 한국어
140
+
141
+ ### 이게 무엇인가요?
142
+
143
+ **Gingiris AI 제품 글로벌 런칭 플레이북** — Product Hunt 30회 이상 1위 달성 경험으로 구축된 실전 가이드. Manus, Devin, AFFiNE(60k GitHub 스타) 등 실제 캠페인 기반.
144
+
145
+ **주요 내용**: 런칭 전 체크리스트, Product Hunt 당일 운영, KOL 아웃리치 템플릿, Reddit/HN 시딩, UGC 성장 루프, 런칭 후 유지 전략.
146
+
147
+ ---
148
+
149
+ ## About the Author
150
+
151
+ **Iris (生姜iris)** — Former cofounder & COO of [AFFiNE](https://github.com/toeverything/AFFiNE) ($10M raised, 60k+ GitHub stars). Forbes Asia 30 Under 30. Coached 150+ AI startups on global go-to-market strategy. Based across Shanghai, Singapore, and remote.
152
+
153
+ - Website: [gingiris.tools](https://gingiris.tools)
154
+ - Twitter/X: [@WeiYipei](https://x.com/WeiYipei)
155
+ - Telegram: [@Iris_carrot](https://t.me/Iris_carrot)
156
+ - Blog: [gingiris.tools](https://gingiris.tools/)
157
+
158
+ ---
159
+
160
+ ## See Also — Gingiris Playbook Series
161
+
162
+ | Playbook | Focus | HuggingFace |
163
+ |:---------|:------|:------------|
164
+ | **gingiris-growth-finder** | 🧭 Meta-router: diagnoses your situation, picks the right playbook | [Gingiris/gingiris-growth-finder](https://huggingface.co/datasets/Gingiris/gingiris-growth-finder) |
165
+ | **gingiris-opensource** | ⭐ GitHub stars, HN, OSS go-to-market | [Gingiris/gingiris-opensource](https://huggingface.co/datasets/Gingiris/gingiris-opensource) |
166
+ | **gingiris-b2b-growth** | 📈 B2B SaaS PLG/SLG, PMF to $10M ARR | [Gingiris/gingiris-b2b-growth](https://huggingface.co/datasets/Gingiris/gingiris-b2b-growth) |
167
+ | **gingiris-aso-growth** | 📱 ASO, mobile cold start, UGC matrix | [Gingiris/gingiris-aso-growth](https://huggingface.co/datasets/Gingiris/gingiris-aso-growth) |
168
+ | **gingiris-seo-geo** | 🔍 SEO + GEO dual-engine, AI search citations | [Gingiris/gingiris-seo-geo](https://huggingface.co/datasets/Gingiris/gingiris-seo-geo) |
169
+ | **gingiris-user-interview** | 🎤 User interview framework (HeyGen 937 methodology) | [Gingiris/gingiris-user-interview](https://huggingface.co/datasets/Gingiris/gingiris-user-interview) |
170
+ | **gingiris-skills** | 🛠️ Full toolkit: 12 Claude Code skills bundled | [Gingiris/gingiris-skills](https://huggingface.co/datasets/Gingiris/gingiris-skills) |
171
+ | **growth-tools** | 📚 Blog & tools hub | [Gingiris/growth-tools](https://huggingface.co/datasets/Gingiris/growth-tools) |
172
+
173
+ All playbooks live at [gingiris.tools](https://gingiris.tools) and [skills.sh/Gingiris](https://skills.sh/Gingiris).
174
+
175
+ ---
176
+
177
+ ## License
178
+
179
+ MIT — Use, adapt, and build on this freely.
180
+
181
+ ## 🔗 Related Gingiris Skills
182
+
183
+ | Skill | Focus | Install |
184
+ |-------|-------|---------|
185
+ | [gingiris-kol-outreach](https://github.com/Gingiris-1031/gingiris-kol-outreach) | KOL & Influencer Marketing SOP | `clawhub install gingiris-kol-outreach` |
186
+ | [gingiris-ugc-matrix](https://github.com/Gingiris-1031/gingiris-ugc-matrix) | UGC Matrix & Multi-Platform Content | `clawhub install gingiris-ugc-matrix` |
187
+ | [gingiris-opensource](https://github.com/Gingiris-1031/gingiris-opensource) | Open Source Launch Marketing | `clawhub install gingiris-opensource` |
188
+ | [gingiris-go-global](https://github.com/Gingiris-1031/gingiris-go-global) | Go-Global Expansion Strategy | `clawhub install gingiris-go-global` |
189
+
190
+ > 📦 **Full collection:** [gingiris-skills](https://github.com/Gingiris-1031/gingiris-skills) — All playbooks in one bundle.
skills/gingiris-launch/SKILL.md ADDED
@@ -0,0 +1,314 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ ---
2
+ name: gingiris-launch
3
+ description: |
4
+ 🇺🇸 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).**
5
+
6
+ 🇨🇳 产品发布与 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+媒体)。**
7
+
8
+ 🇯🇵 プロダクトローンチ&Product Hunt 1位プレイブック — マルチチャネルのローンチ時系列。T-14準備→T-0当日→T+7モメンタム。ハンター選定、メーカーコメント、コメントリズム、シャドウバン回避。**3つの製品パス対応:開発者/maker(PH+GitHub)、2C消費者(コミュニティ種・TikTok、PHスキップ)、B2B(LinkedIn+メディア)。**
9
+
10
+ 🇰🇷 제품 출시 & Product Hunt 1위 플레이북 — 멀티채널 출시 타이밍과 시퀀싱. T-14 워밍업 → T-0 출시일 → T+7 모멘텀. 헌터 선정, 메이커 코멘트, 댓글 리듬, 섀도밴 방지. **3가지 제품 경로 지원: 개발자/maker(PH+GitHub), 2C 소비자(커뮤니티 씨드/TikTok, PH 건너뜀), B2B(LinkedIn+미디어).**
11
+
12
+ 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" | "ローンチ" | "출시 전략"
13
+ when_to_use: |
14
+ Use this skill when you need to: execute a Product Hunt launch, plan multi-channel GTM
15
+ sequencing (T-14 to T+7), select a hunter, write maker comments, seed launch-day community
16
+ engagement, or build cold-start momentum for a new product.
17
+ Trigger phrases: "product launch" | "Product Hunt" | "GTM" | "launch strategy" |
18
+ "发布策略" | "产品发布" | "发PH" | "找hunter" | "출시 전략"
19
+ ---
20
+
21
+ # Product Launch — GTM Strategy & Product Hunt #1 Playbook
22
+
23
+ > Case-number and citation boundaries: `references/podcast-evidence.md`.
24
+
25
+ > 🌍 **Language / 语言**: [English](#english-version) | [中文](#中文版)
26
+
27
+ ## 产品类型分岔:先选你的路径
28
+
29
+ **你的产品主要用户是谁?**
30
+
31
+ ### 路径 A:开发者 / maker(默认)
32
+ → Product Hunt + GitHub + HN + dev 社区
33
+ → 继续阅读下面的 Launch SOP
34
+
35
+ ### 路径 B:普通消费者(学生/上班族/游戏玩家等)
36
+ → App Store + 垂类社区种子 + 内容获客
37
+ → **跳过 Product Hunt**(受众错配,ROI 极低)
38
+ → 冷启动渠道:Reddit 垂类 / 小红书 / TikTok / Quora / 知乎
39
+ → 免费产品当钉子(PLG):先拿到前 100 个真实用户再放量
40
+ → 前 100 用户 SOP:在目标社区找近期抒怨同类问题的人 → 私信邀请免费试用 → 用户访谈固化 PMF
41
+
42
+ ### 路径 C:B2B 决策者
43
+ → LinkedIn 精准建联 + 行业媒体 + HARO
44
+ → 继续阅读下面的 Launch SOP,重点看 B2B 部分
45
+
46
+ ---
47
+
48
+ 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.
49
+
50
+ ---
51
+
52
+ ## English Version
53
+
54
+ ### The 14-day timeline
55
+
56
+ | Window | What you do |
57
+ |:---|:---|
58
+ | **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. |
59
+ | **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. |
60
+ | **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. |
61
+ | **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. |
62
+ | **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. |
63
+
64
+ ### Hunter selection matrix
65
+
66
+ | Priority | Criteria |
67
+ |:---|:---|
68
+ | **P0** | Successful hunt in the last 30 days **and** an adjacent product domain |
69
+ | **P1** | 1k+ followers **and** active (posts weekly) |
70
+ | **P2** | A real relationship (you've talked, mutual friends) |
71
+ | ❌ | 50k+ followers but no hunt in 6 months — vanity, low reach |
72
+
73
+ Find hunters: `producthunt.com/@<category>-hunters`. **Activity beats follower count.**
74
+
75
+ ### Maker comment — pick one of 6 archetypes
76
+
77
+ 1. **Founder story** — why you built it → your pain → the fix
78
+ 2. **Before / After** — life without your product vs. with it
79
+ 3. **Key-stat hook** — open with one explosive number
80
+ 4. **Honest limitation** — admit what's not perfect yet (reads as real)
81
+ 5. **Community thanks** — @-name the users who tested
82
+ 6. **Tech-stack pride** — your architecture choices (for dev-facing products)
83
+
84
+ Choose by audience: dev product → #6; general → #1 or #3.
85
+
86
+ ### Anti-pitfall checklist
87
+
88
+ - ❌ Don't still be changing the product on launch day (flaky).
89
+ - ❌ Don't have friends/family farm upvotes — PH shadowbans fast.
90
+ - ❌ Don't put external links in the first comment (triggers review demotion).
91
+ - ❌ Don't forget mobile screenshots (40% of traffic is mobile).
92
+ - ❌ Don't force daily #1 — #2–#3 are wins too (and draw less hate).
93
+
94
+ ### Go / no-go: budget-tier benchmarks
95
+
96
+ | Budget | Realistic output |
97
+ |:---|:---|
98
+ | ~$1K | A few hundred signups (YouTube micro-ads + niche subreddits + topic groups) |
99
+ | $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 |
100
+ | $10–20K | ~1M impressions + low-thousands signups |
101
+ | <$20K | 10k+ star open-source launch (execution team ≤5 people) |
102
+
103
+ **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%.
104
+
105
+ ### Vote velocity red lines (pace even your real supporters)
106
+
107
+ - **≤100 votes/hour total, ≤30/hour from any single channel.** PH sweeps suspicious votes roughly every 2 hours — a spike gets stripped.
108
+ - Ask supporters to vote from **mobile + cellular data (4G)**, not one office Wi-Fi.
109
+ - **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.
110
+
111
+ ### Launch-day traffic: plan backwards
112
+
113
+ Set the total traffic target first → split it into per-channel hard numbers → attribute with per-channel UTM short links.
114
+ 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**.
115
+
116
+ ### Sequencing patterns that compound
117
+
118
+ - **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.
119
+ - **KOL burst window** — 50–100 KOLs commit to posting within the same 24–48h to trigger an algorithmic spike.
120
+ - **"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**.
121
+ - **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).
122
+ - **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.
123
+
124
+ ### Hacker News quick rules
125
+
126
+ - Front-page bar: **30 upvotes + 10 comments within 30 minutes of posting**; if it hasn't moved by minute 35–45, it drops off.
127
+ - Post at 18:00–20:00 Beijing time (US morning).
128
+ - HN agencies at ~$500/post are poor ROI — skip them.
129
+ - One fish, two meals: translate the same English post straight into Chinese for V2ex / linux.do.
130
+
131
+ ### PH is a paid channel — the free Thu/Fri/Sat play
132
+
133
+ 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):
134
+
135
+ 1. **Decide the goal first**: branding (fight the Mon–Wed vote pool, budget it) vs. a batch of early customers (Thu–Sat is enough).
136
+ 2. Launch on **Thursday / Friday / Saturday** — lower traffic, much weaker competition.
137
+ 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.
138
+ 4. Assets fully prepared before posting: 1 video + 5 gallery images.
139
+
140
+ ### Badge-or-relaunch rule
141
+
142
+ - Daily / weekly / monthly boards each badge the **top 5 only** — if you launch, launch to take a badge.
143
+ - 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.
144
+ - 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).
145
+
146
+ ### The core formula and the 4-step launch SOP
147
+
148
+ > Marketing = **precise user-channel matching × high-quality content design.**
149
+
150
+ | Step | Action |
151
+ |:---|:---|
152
+ | 1. Fill the SOP template | Each launch type has its own template doc; the team fills in the blanks |
153
+ | 2. Channel breakdown → list | Decide in-house vs. agency per channel; make each channel concrete (Reddit: which subreddits, whose DMs, which competitor's users) |
154
+ | 3. Content pack ×3 | Confirmed one-line intro + key feature points + user cases |
155
+ | 4. 80/20 | ~80% of the method repeats across launches; 20% is customized to this product's edge |
156
+
157
+ - Minimum crew: **1 full-time + 1–2 interns** runs a decent launch; training an in-house team takes ≈1–2 months (self-reported).
158
+ - 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).
159
+
160
+ ### Launch-day combo (4 parallel actions)
161
+
162
+ The same-day action set behind a ≈6,000-star first week (open-source launch, 2022 — self-reported):
163
+
164
+ 1. Post in target communities (Reddit etc.).
165
+ 2. **DM the follower lists of your named competitors** — this alone converted a few hundred stars.
166
+ 3. Publish the launch article + a README a stranger grasps in one pass.
167
+ 4. Submit to directory / navigation sites (a competitor's zero-budget launch covered ~40 channels in one day, ~20 of them directories).
168
+
169
+ ### 48-hour timed-vote case (election ≈ leaderboard day)
170
+
171
+ A 48h student-union election — structurally the same game as a PH launch window:
172
+
173
+ - **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.
174
+ - **Fight only your base**: target the ~3,600-person core group, not the 10K+ whole campus.
175
+ - **Seed the must-pass spots**: elevators, library entrance, canteen doors; 40+ volunteers in 5 squads, tasks assigned by proximity.
176
+ - Result: **800+ votes in 48h, ≈2× the runner-up** (recalled numbers, self-reported).
177
+
178
+ ### What to do next
179
+
180
+ - Launch day + 24h → monitor "`<product> product hunt`" keyword rankings.
181
+ - Hit daily #1 → write the "how we won" post, set canonical to your domain.
182
+ - Heavy skepticism in comments → open formal user interviews.
183
+
184
+ ---
185
+
186
+ ## 中文版
187
+
188
+ ### 14 天时间线
189
+
190
+ | 阶段 | 动作 |
191
+ |:---|:---|
192
+ | **T-14 准备** | 落地页、定价、FAQ 就绪。≥100 早鸟用户 + 邮箱列表。选 **1 个** hunter。3 张主 gallery 图 + 1 个 30 秒 demo。 |
193
+ | **T-7 到 T-2 预热** | PH discussion 发一篇 "we're launching, AMA"。X / LinkedIn / Reddit 预告但**不贴发布页链接**(别抢自己流量)。给用户列表打招呼。确认 hunter 时区 + **PST 00:01** 发布时间。 |
194
+ | **T-1 终检** | 锁定全部 asset。写好 first comment(<500 字)。备 10 条 FAQ 回复模板。提醒 10–20 个核心支持者。 |
195
+ | **T-0 发布日** | **00:01 PST** hunter 发布 → **00:15** 你发 maker first comment → 每 30 分钟回一批评论(绝不刷 upvote)→ **14:00 PST** 推 second wave → **23:00 PST** 发感谢帖。 |
196
+ | **T+1 到 T+7 后续** | 回完所有评论(含差评)。把 Featured 截图 + 数据做成 case study。进 daily #1 就写 "how we won" 并设 canonical。所有 upvoter 邮箱导入用户池。 |
197
+
198
+ ### Hunter 选择矩阵
199
+
200
+ | 优先级 | 标准 |
201
+ |:---|:---|
202
+ | **P0** | 最近 30 天有成功 hunt 且产品领域相似 |
203
+ | **P1** | Follower 1k+ 且每周活跃 |
204
+ | **P2** | 有真实社交关系(聊过、共同朋友) |
205
+ | ❌ | Follower 50k+ 但 6 个月没 hunt — 虚荣指标、触达低 |
206
+
207
+ **活跃度 > follower 数。**
208
+
209
+ ### Maker comment 6 种模板
210
+
211
+ 1. **Founder story** — 为什么做 → 你的痛 → 解法
212
+ 2. **Before / After** — 用你产品前后的对比
213
+ 3. **Key stats hook** — 一个爆炸数据开头
214
+ 4. **Honest limitation** — 承认还不完美,显真实
215
+ 5. **Community thanks** — @ 点名测试用户
216
+ 6. **Tech stack pride** — 技术选型(开发者向产品)
217
+
218
+ 选哪个:to dev → 6;to general → 1 或 3。
219
+
220
+ ### 反踩雷清单
221
+
222
+ - ❌ 发布当天还在改产品(flaky)
223
+ - ❌ 让亲友刷 upvote(PH 很快 shadowban)
224
+ - ❌ first comment 留外链(触发审核降权)
225
+ - ❌ 忘记 mobile 截图(40% 流量来自手机)
226
+ - ❌ 硬撑 daily #1(#2–#3 也是成功,且少被喷)
227
+
228
+ ### Go / no-go:预算分级产出基准
229
+
230
+ | 预算 | 现实产出 |
231
+ |:---|:---|
232
+ | ~$1K | 小几百注册(YouTube 小额投流 + 垂直 subreddit + 主题群) |
233
+ | $5K | 24h 约 1,800 票可达——但有实战案例冲上日榜第一后被 PH 事后清票收回,控速红线���是建议是保命 |
234
+ | $1–2 万 | ~100 万曝光 + 小几千注册 |
235
+ | <$2 万 | 过万 star 的开源发布(执行团队 ≤5 人) |
236
+
237
+ **反直觉但实测成立:预算不高别卷 PH。** 同样预算给 ~10 个 Twitter KOL/KOC,曝光和注册都更高——PH 曝光→upvote 转化仅 ~1%,而 Reddit 开源宣发曝光→star 转化 5–8%。
238
+
239
+ ### 上票控速红线(真实支持者也要控速)
240
+
241
+ - **总量 ≤100 票/小时,单一渠道 ≤30 票/小时。** PH 约每 2 小时清一次可疑票,突刺会被剥掉。
242
+ - 请支持者用**手机 + 蜂窝数据(4G)**投票,别挤同一个办公室 Wi-Fi。
243
+ - **badge 曝光分层:周榜曝光 ≈ 日榜 7 倍,月榜 ≈ 30 倍**——先想清楚冲哪个榜,再决定花钱节奏。
244
+
245
+ ### 发布日流量倒排法
246
+
247
+ 先定总流量盘子 → 拆成每个渠道的硬数字 → 每渠道 UTM 短链归因。
248
+ 实测案例(某 AI Agent 产品,2025-12):发布日 50 万流量 = 40 万 Twitter(40 红人 quote)+ 2 万 Reddit + 2 万 YouTube 投流 + 2 万 TG/FB/LinkedIn 群 + 其余 → **约 800 注册、CAC $6.25**。
249
+
250
+ ### 会复利的节奏打法
251
+
252
+ - **双日结构**——发布日(一半红人导官网)+ 打榜日(另一半导 PH),两个目标互不稀释流量。
253
+ - **KOL 集中爆破窗口**——50–100 个 KOL 约定同一 24–48h 内发布,制造算法级爆点。
254
+ - **"60 分启动"**——产品 60 分就开始备发布物料;launch 就绪判据:**≥10 个开发者满意且持续在用**。
255
+ - **四大传播支柱**(Manus/Devin 复盘):产品力叙事基础 → 情绪叙事 → 影响者飞轮 → 平台接力(Day 0–3 X 造话题 → Day 3–10 YouTube/Substack 沉淀 → Day 10+ Reddit/HN 长尾)。
256
+ - **可复现性决定情绪叙事的天花板。** 真心惊喜 ≠ 人情帮转:同一个 KOL,推荐可复现产品 2.8M 浏览 vs 人情转发只有 ~20 个赞。
257
+
258
+ ### Hacker News 速查规则
259
+
260
+ - 上首页标准:**发帖 30 分钟内 30 upvote + 10 评论**;35–45 分钟还没起来就掉出首页。
261
+ - 北京时间 18:00–20:00 发(美国上午)。
262
+ - HN agency 约 $500/帖,ROI 差,不推荐。
263
+ - 一鱼两吃:英文稿直译发 V2ex / linux.do。
264
+
265
+ ### PH 本质是付费渠道——周四五六免费打法
266
+
267
+ 默认把 PH 当 paid marketing:周一到周三是高流量日,基本要花钱才打得动。零预算替代方案(实测拿过日榜第一,self-reported):
268
+
269
+ 1. **先定目标**:要 branding(卷周一到三的票仓,配预算)还是只要一批早期客户(周四五六够用)。
270
+ 2. 选**周四 / 周五 / 周六**发布——流量低、竞争弱得多。
271
+ 3. 人肉拉票:LinkedIn 社群(如 4 个群、每群几百到 1,000+ 人)+ 私域社群——**逐个 DM**,绝不群发。
272
+ 4. 物料发布前全部备齐:1 个视频 + 5 张图。
273
+
274
+ ### Badge 铁律:拿不到就重发
275
+
276
+ - 日 / 周 / 月榜**各只有前 5 名有 badge**——要发就冲着 badge 发。
277
+ - 发布日竞争太强进不了前五:**给 PH 官方发邮件("我们犯了个错误")申请 remove,择低竞争日重发。** 注意:此招用的人多了,官方已开始卡——只当最后手段。
278
+ - 单次发布收益预期:小几百到大几千注册 + Discord 进小几十人 + 自媒体爬榜带来的 backlinks(自述口径基准)。
279
+
280
+ ### 核心公式与发布 SOP 四步
281
+
282
+ > marketing = **用户渠道的精准匹配 × 高质量的内容设计。**
283
+
284
+ | 步骤 | 动作 |
285
+ |:---|:---|
286
+ | 1. 填 SOP 模板 | 每种发布类型有专属模板文档,团队往里填空 |
287
+ | 2. 拆渠道 → 拉清单 | 每个渠道决策自营还是外包;渠道要定向落地(Reddit:哪些 subreddit、私信谁、对标哪个竞品的用户) |
288
+ | 3. 内容包三件套 | 一句话介绍确认 + 关键功能点 + 用户案例 |
289
+ | 4. 80/20 | 方法论 ~80% 各发布通用,20% 按产品优势定制 |
290
+
291
+ - 最小配置:**1 个 full-time + 1–2 个实习生**即可完成一次相对还行的发布;带出 in-house 团队约 1–2 个月(自述口径)。
292
+ - 一场执行到位的 organic 为主发布的 ROI 基准:**≈$1–2 万美金预算 → 几十万到上百万曝光 → 几千到上万注册**(咨询实战自述口径)。
293
+
294
+ ### 发布日组合拳(4 个并行动作)
295
+
296
+ 一周 ≈6,000 star 背后的当日动作组合(开源发布,2022,自述口径):
297
+
298
+ 1. 目标社区发帖(Reddit 等)。
299
+ 2. **私信对标竞品的 follower list**——仅此一项转化了几百个 star。
300
+ 3. 发布文章 + 一遍就能看懂的 README。
301
+ 4. 提交导航站 / 目录站(某竞品零预算发布一天铺了约 40 个渠道,其中约 20 个是导航站)。
302
+
303
+ ### 48 小时限时打榜案例(竞选 ≈ 榜单日)
304
+
305
+ 一场 48 小时投票窗口的学生会竞选——和 PH 发布日结构同构:
306
+
307
+ - **先自己走一遍漏斗**:投完一票约 5 分钟(注册 → 找席位 → 找候选人 → 验证码)。高摩擦意味着泛流量无效——只动员强意愿支持者。
308
+ - **只打基本盘**:瞄准 ~3,600 人核心群体,不碰 1 万+ 全体。
309
+ - **铺必经点位**:电梯、图书馆门口、食堂门口;40+ 志愿者分 5 个小队,按就近原则分工。
310
+ - 结果:**48 小时 800+ 票,约为第二名 2 倍**(回忆数字,self-reported)。
311
+
312
+ ---
313
+
314
+ *By Iris (生姜 Iris) · ex-COO @ AFFiNE (60k★), 30× Product Hunt #1 · Install: `npx skills add Gingiris-1031/gingiris-launch`*
skills/gingiris-launch/references/podcast-evidence.md ADDED
@@ -0,0 +1,9 @@
 
 
 
 
 
 
 
 
 
 
1
+ # Podcast evidence for launch decisions
2
+
3
+ - Historical launch budgets of roughly $10K–$20K were described as producing hundreds of thousands to over one million impressions and thousands to tens of thousands of registrations across different products. Always attach product, channel mix and activation denominator.
4
+ - Repeatable formula: channel–audience match plus official narrative, creator/community-native variants and one measurable conversion destination.
5
+ - Pause amplification when activation is weak. Traffic is not PMF.
6
+ - Keep the general method roughly 80% reusable and localize 20% for market and buyer behavior.
7
+ - Product Launch and Product Hunt are separate events with separate attribution.
8
+
9
+ The 48-hour university-election story supports friction removal and base-audience sequencing only; it is not PH algorithm evidence.