startup-launch · diff
git:20260629.964c192 to git:20260706.63abb98
22 added, 0 removed. Audit A to A.
---
name: startup-launch
description: |
Startup Launch Day Playbook — Hour-by-hour execution checklist for your big launch day. Covers timezone timing, channel sequencing, real-time crisis management, and post-launch momentum. By @WeiYipei.
source: https://github.com/Gingiris-1031/gingiris-skills/tree/main/skills/startup-launch
tags:
- startup-launch
- launch-strategy
- go-to-market
- gtm
- product-launch
- mvp
- traction
- first-users
- early-stage
- distribution
- claude-code
- ai-agent-skill
- agent-skill
- latest
---
## ⚠️ 区分 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`。
---
# Startup Launch Day Playbook — Hour-by-Hour Checklist
> 🌍 **Language / 语言**: [中文](#中文版) | [English](references/en/README.md) | [日本語](references/ja/README.md) | [한국어](references/ko/README.md)
## 📦 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.
## 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)
## 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)
+
+ ### 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.
+
+ ### 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.
+
+ ### Hacker News: the 30-minute verdict
+
+ 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.
+
+ ### 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.