Back to Details

startup-launch

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

⚠️ 区分 B2B 与 2C

⚠️ 区分 B2B 与 2C

本 skill 默认偏 dev / 开源 / B2B SaaS。若产品是 2C 消费品 / 教育 / 应用 / 游戏：核心指标换成 D1/D7/D30 留存、激活率、病毒系数 K（非 MRR/CAC/LTV）；冷启动渠道换成垂类社区 / 短视频 / 垂直 KOL（非 PH/HN/LinkedIn）。完整 2C 适配指南 + 各国渠道公开数据见 → 
gingiris-seo-geo/references/2c-adaptation.md
。
本Skill默认偏向开发者/开源/B2B SaaS领域。若产品是 2C 消费品 / 教育 / 应用 / 游戏：核心指标替换为 D1/D7/D30 留存率、激活率、病毒系数 K（而非 MRR/CAC/LTV）；冷启动渠道替换为垂类社区 / 短视频 / 垂直 KOL（而非 PH/HN/LinkedIn）。完整 2C 适配指南 + 各国渠道公开数据详见 → 
gingiris-seo-geo/references/2c-adaptation.md
。

Startup Launch Day Playbook — Hour-by-Hour Checklist

创业公司发布日行动手册 —— 逐小时执行清单

🌍 Language / 语言: 中文 | English | 日本語 | 한국어
🌍 Language / 语言: 中文 | English | 日本語 | 한국어

📦 Install

📦 安装

bash
clawhub install startup-launch
What you get after installing:
  • Hour-by-hour execution plan from T-12h to 72h post-launch
  • Coordinated multi-channel activation sequence
  • Crisis management playbook (site down, negative feedback, competitor attacks)
Your launch day is ONE shot. This playbook gives you an hour-by-hour execution plan so nothing falls through the cracks. From T-minus-12-hours prep to the 72-hour post-launch sprint.
bash
clawhub install startup-launch
安装后你将获得：
  • 从发布前12小时到发布后72小时的逐小时执行计划
  • 协同化的多渠道激活流程
  • 危机管理手册（网站宕机、负面反馈、竞品攻击等场景）
你的发布日只有一次机会。本行动手册提供逐小时执行计划，确保不会遗漏任何细节。从发布前12小时的准备工作到发布后72小时的冲刺阶段全覆盖。

What You'll Learn

你将学到的内容

  • T-12h: Final checks (servers, links, payment, copy)
  • Hour 0: Coordinated channel activation sequence
  • Hours 1-6: Real-time monitoring and engagement tactics
  • Hours 6-24: Second-wave amplification
  • 72-hour post-launch momentum playbook
  • Crisis management (site down, negative feedback, competitor attacks)
  • T-12h：最终检查（服务器、链接、支付、文案）
  • 第0小时：协同渠道激活流程
  • 第1-6小时：实时监控与互动策略
  • 第6-24小时：第二波推广放大
  • 发布后72小时势头维持手册
  • 危机管理（网站宕机、负面反馈、竞品攻击）

Who This Is For

适用人群

  • Founders with a launch date already set
  • Teams who have the product ready but need execution confidence
  • Anyone who's been burned by a disorganized launch before
  • 已确定发布日期的创始人
  • 产品已准备就绪但需要执行信心的团队
  • 曾因发布混乱而受挫的任何人

Traffic Engineering for Launch Day (2026 field addendum)

发布日流量工程（2026年领域补充内容）

Plan the day as arithmetic, not vibes

用精准规划而非感觉来安排发布日

Fix a total-visits target, then reverse-engineer per-channel quotas — each with its own UTM short link and a named owner. Anonymized reference (an AI Agent product, late 2025): a 500K-visit launch day was assembled as ~400K from 40 creator quote-tweets, plus ~20K each from Reddit threads, geo-targeted YouTube ads, and messaging-group distribution. Final tally: ~800 signups at $6.25 per registration. The lesson cuts both ways — traffic is buildable to spec; conversion is the bottleneck you can't buy.
设定总访问量目标，然后反向推导各渠道的配额 —— 每个渠道都要有专属的UTM短链接和指定负责人。匿名参考案例（一款AI Agent产品，2025年末）：发布日50万访问量由40位创作者的引用推文贡献约40万，加上Reddit帖子、地域定向YouTube广告和消息群组分发各贡献约2万。最终统计：约800个注册，每个注册成本6.25美元。经验教训是双向的 —— 流量可以按预期构建；转化率是无法通过购买解决的瓶颈。

Sequencing patterns worth stealing

值得借鉴的渠道排序模式

  • Split objectives across two days: half your amplifiers push the website on day one, the other half push the leaderboard (PH, etc.) on day two. One day, one goal — otherwise the streams dilute each other.
  • Burst window: get 50–100 creators publishing inside the same 24–48h. Algorithms reward density, not totals.
  • Platform relay (from the Manus/Devin post-mortems): days 0–3, X/Twitter builds the conversation → days 3–10, YouTube and newsletters consolidate it → day 10+, Reddit/HN carry the long tail. For a big launch, concentrate ~80% of spend on the same day.
  • 将目标拆分到两天完成：一半推广者在第一天推送网站，另一半在第二天推送排行榜（如PH等平台）。一天聚焦一个目标 —— 否则流量会分散。
  • 爆发窗口：让50–100位创作者在24–48h内同步发布内容。算法更青睐密度而非总量。
  • 平台中继（源自Manus/Devin的复盘）：第0–3天，X/Twitter构建话题讨论 → 第3–10天，YouTube和新闻通讯巩固热度 → 第10天之后，Reddit/HN维持长尾流量。对于大型发布，将约80%的预算集中在同一天。

Hacker News: the 30-minute verdict

Hacker News：30分钟定胜负

The front page is decided in the first half hour — roughly 30 points and 10 comments, posted during the US morning window. Flat at minute 40 = done. Bring 2–3 prepared angles (a "Show" post, an open-source-alternative link, a how-it-works writeup) rather than one perfect post, and translate the winner for regional dev forums — one text, two communities.
首页排名在前30分钟内就已决定 —— 大约需要30分和10条评论，且要在美国上午时段发布。如果40分钟时数据仍平淡，就没机会了。准备2–3个不同的发布角度（比如“展示”帖、开源替代方案链接、工作原理详解），而非一篇完美的帖子，然后将效果最好的版本翻译成当地开发者论坛的语言 —— 一份文案，覆盖两个社区。

Readiness gate

就绪门槛

Don't set the date until at least 10 external developers are satisfied and still actively using the product. Pre-launch time split: 60% talking to users, 40% preparing the launch — start asset prep once the product hits "60 points," copy first, visuals later.
Built by Gingiris — orchestrated 30+ launches with combined 100k+ first-day visitors.
直到 至少10位外部开发者对产品满意并仍在积极使用，再确定发布日期。发布前时间分配：60%与用户沟通，40%准备发布 —— 当产品达到“60分”时开始准备素材，先写文案，后做视觉内容。
由Gingiris打造 —— 已统筹30+次发布，首日总访问量超10万。