Datasets:
License:
Repair complete skill packages and improve task discovery
Browse files- LICENSE +21 -0
- README.md +37 -10
- SKILL.md +97 -0
- _meta.json +6 -0
- references/en/README.md +51 -0
- references/ja/README.md +51 -0
- references/ko/README.md +51 -0
LICENSE
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
MIT License
|
| 2 |
+
|
| 3 |
+
Copyright (c) 2026 Iris / Gingiris
|
| 4 |
+
|
| 5 |
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
| 6 |
+
of this software and associated documentation files (the "Software"), to deal
|
| 7 |
+
in the Software without restriction, including without limitation the rights
|
| 8 |
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
| 9 |
+
copies of the Software, and to permit persons to whom the Software is
|
| 10 |
+
furnished to do so, subject to the following conditions:
|
| 11 |
+
|
| 12 |
+
The above copyright notice and this permission notice shall be included in all
|
| 13 |
+
copies or substantial portions of the Software.
|
| 14 |
+
|
| 15 |
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
| 16 |
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
| 17 |
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
| 18 |
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
| 19 |
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
| 20 |
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
| 21 |
+
SOFTWARE.
|
README.md
CHANGED
|
@@ -1,15 +1,42 @@
|
|
| 1 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 2 |
|
| 3 |
-
|
| 4 |
-
## 加入出海社群与购买资料包 · Community & Resources
|
| 5 |
|
| 6 |
-
|
| 7 |
-
- **购买资料包:** 微信添加 **staywildgrow**,咨询购买 Gingiris 出海资料包,价格 **599 元人民币**。
|
| 8 |
|
| 9 |
-
|
| 10 |
-
- **Get the resource pack:** Add **staywildgrow** on WeChat to purchase the Gingiris global growth resource pack for **CNY 599**.
|
| 11 |
|
| 12 |
-
|
|
|
|
| 13 |
|
| 14 |
-
|
| 15 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
---
|
| 2 |
+
license: mit
|
| 3 |
+
language:
|
| 4 |
+
- en
|
| 5 |
+
- zh
|
| 6 |
+
tags:
|
| 7 |
+
- agent-skills
|
| 8 |
+
- gingiris
|
| 9 |
+
- workflow
|
| 10 |
+
- launch
|
| 11 |
+
pretty_name: Startup Launch
|
| 12 |
+
---
|
| 13 |
+
# startup-launch
|
| 14 |
|
| 15 |
+
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.
|
|
|
|
| 16 |
|
| 17 |
+
## Use this workflow / 使用场景
|
|
|
|
| 18 |
|
| 19 |
+
Category: **Launch**. Version: **see source**. Distribution checked: **2026-11-08**.
|
|
|
|
| 20 |
|
| 21 |
+
This repository distributes an agent instruction package, not a training dataset. Read the task scope and prerequisites in [SKILL.md](SKILL.md) before running it.
|
| 22 |
+
这是 Agent 操作指南包,不是训练数据集。输入、产出、前置条件与完整步骤以 SKILL.md 为准。
|
| 23 |
|
| 24 |
+
## Install from the maintained source / 安装
|
| 25 |
+
|
| 26 |
+
```bash
|
| 27 |
+
npx skills add Gingiris-1031/gingiris-skills --skill startup-launch
|
| 28 |
+
```
|
| 29 |
+
|
| 30 |
+
For an offline copy, download the complete folder including references and scripts; downloading only this README is insufficient. OpenClaw users should follow the [source installation guide](https://github.com/Gingiris-1031/gingiris-skills/blob/main/OPENCLAW.md); runtime compatibility is separate from file availability.
|
| 31 |
+
|
| 32 |
+
## Start with a concrete task / 开始使用
|
| 33 |
+
|
| 34 |
+
Provide your product or source material, target audience/market, current constraint and desired deliverable. Ask the agent to apply `startup-launch`, separate observations from hypotheses, and identify missing evidence before external actions. Examples in a guide are not proof of your own results.
|
| 35 |
+
|
| 36 |
+
请提供产品或原始材料、目标用户/市场、当前约束和期望交付物。要求 Agent 使用 `startup-launch`,区分事实、假设和待验证项;涉及对外操作时遵循你的授权范围。
|
| 37 |
+
|
| 38 |
+
## Source and updates
|
| 39 |
+
|
| 40 |
+
[Maintained source](https://github.com/Gingiris-1031/gingiris-skills/tree/main/skills/startup-launch) · [Report an issue](https://github.com/Gingiris-1031/gingiris-skills/issues) · [Browse workflows](https://tools.gingiris.com/skills/)
|
| 41 |
+
|
| 42 |
+
MIT licensed. No guaranteed ranking, revenue or audience growth. Platform listing and download counts do not establish successful execution.
|
SKILL.md
ADDED
|
@@ -0,0 +1,97 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
---
|
| 2 |
+
name: startup-launch
|
| 3 |
+
description: |
|
| 4 |
+
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.
|
| 5 |
+
source: https://github.com/Gingiris-1031/gingiris-skills/tree/main/skills/startup-launch
|
| 6 |
+
tags:
|
| 7 |
+
- startup-launch
|
| 8 |
+
- launch-strategy
|
| 9 |
+
- go-to-market
|
| 10 |
+
- gtm
|
| 11 |
+
- product-launch
|
| 12 |
+
- mvp
|
| 13 |
+
- traction
|
| 14 |
+
- first-users
|
| 15 |
+
- early-stage
|
| 16 |
+
- distribution
|
| 17 |
+
- claude-code
|
| 18 |
+
- ai-agent-skill
|
| 19 |
+
- agent-skill
|
| 20 |
+
- latest
|
| 21 |
+
---
|
| 22 |
+
|
| 23 |
+
## ⚠️ 区分 B2B 与 2C
|
| 24 |
+
|
| 25 |
+
本 skill 默认偏 dev / 开源 / B2B SaaS。若产品是 **2C 消费品 / 教育 / 应用 / 游戏**:核心指标换成 D1/D7/D30 留存、激活率、病毒系数 K(非 MRR/CAC/LTV);冷启动渠道换成垂类社区 / 短视频 / 垂直 KOL(非 PH/HN/LinkedIn)。完整 2C 适配指南 + 各国渠道公开数据见 → `gingiris-seo-geo/references/2c-adaptation.md`。
|
| 26 |
+
|
| 27 |
+
---
|
| 28 |
+
|
| 29 |
+
# Startup Launch Day Playbook — Hour-by-Hour Checklist
|
| 30 |
+
|
| 31 |
+
> 🌍 **Language / 语言**: [中文](#中文版) | [English](references/en/README.md) | [日本語](references/ja/README.md) | [한국어](references/ko/README.md)
|
| 32 |
+
|
| 33 |
+
## 📦 Install
|
| 34 |
+
|
| 35 |
+
```bash
|
| 36 |
+
clawhub install startup-launch
|
| 37 |
+
```
|
| 38 |
+
|
| 39 |
+
**What you get after installing:**
|
| 40 |
+
- Hour-by-hour execution plan from T-12h to 72h post-launch
|
| 41 |
+
- Coordinated multi-channel activation sequence
|
| 42 |
+
- Crisis management playbook (site down, negative feedback, competitor attacks)
|
| 43 |
+
|
| 44 |
+
---
|
| 45 |
+
|
| 46 |
+
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.
|
| 47 |
+
|
| 48 |
+
## What You'll Learn
|
| 49 |
+
- T-12h: Final checks (servers, links, payment, copy)
|
| 50 |
+
- Hour 0: Coordinated channel activation sequence
|
| 51 |
+
- Hours 1-6: Real-time monitoring and engagement tactics
|
| 52 |
+
- Hours 6-24: Second-wave amplification
|
| 53 |
+
- 72-hour post-launch momentum playbook
|
| 54 |
+
- Crisis management (site down, negative feedback, competitor attacks)
|
| 55 |
+
|
| 56 |
+
## Who This Is For
|
| 57 |
+
- Founders with a launch date already set
|
| 58 |
+
- Teams who have the product ready but need execution confidence
|
| 59 |
+
- Anyone who's been burned by a disorganized launch before
|
| 60 |
+
|
| 61 |
+
## Traffic Engineering for Launch Day (2026 field addendum)
|
| 62 |
+
|
| 63 |
+
### Plan the day as arithmetic, not vibes
|
| 64 |
+
|
| 65 |
+
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.
|
| 66 |
+
|
| 67 |
+
### Sequencing patterns worth stealing
|
| 68 |
+
|
| 69 |
+
- **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.
|
| 70 |
+
- **Burst window**: get 50–100 creators publishing inside the same 24–48h. Algorithms reward density, not totals.
|
| 71 |
+
- **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.
|
| 72 |
+
|
| 73 |
+
### Hacker News: the 30-minute verdict
|
| 74 |
+
|
| 75 |
+
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.
|
| 76 |
+
|
| 77 |
+
### Readiness gate
|
| 78 |
+
|
| 79 |
+
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.
|
| 80 |
+
|
| 81 |
+
---
|
| 82 |
+
|
| 83 |
+
Built by Gingiris — orchestrated 30+ launches with combined 100k+ first-day visitors.
|
| 84 |
+
|
| 85 |
+
<!-- gingiris-community-cta:start -->
|
| 86 |
+
## 加入出海社群与购买资料包 · Community & Resources
|
| 87 |
+
|
| 88 |
+
- **加入出海社群:** 微信添加 **staywildgrow**,留言「**加入社群**」即可。
|
| 89 |
+
- **购买资料包:** 微信添加 **staywildgrow**,咨询购买 Gingiris 出海资料包,价格 **599 元人民币**。
|
| 90 |
+
|
| 91 |
+
- **Join the global growth community:** Add **staywildgrow** on WeChat and send **“加入社群”** (join the community).
|
| 92 |
+
- **Get the resource pack:** Add **staywildgrow** on WeChat to purchase the Gingiris global growth resource pack for **CNY 599**.
|
| 93 |
+
|
| 94 |
+
社群与资料包为可选入口,不影响本开源 Skill 的安装和使用。
|
| 95 |
+
|
| 96 |
+
The community and paid resource pack are optional; neither is required to install or use this open-source skill.
|
| 97 |
+
<!-- gingiris-community-cta:end -->
|
_meta.json
ADDED
|
@@ -0,0 +1,6 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
{
|
| 2 |
+
"ownerId": "kn71ssmn8xj5cgbj8dgnbr4dvs87rhh8",
|
| 3 |
+
"slug": "startup-launch",
|
| 4 |
+
"version": "1.1.1",
|
| 5 |
+
"publishedAt": 1780425810556
|
| 6 |
+
}
|
references/en/README.md
ADDED
|
@@ -0,0 +1,51 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# Startup Launch Day Playbook — Hour-by-Hour Checklist
|
| 2 |
+
|
| 3 |
+
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.
|
| 4 |
+
|
| 5 |
+
## The Timeline
|
| 6 |
+
|
| 7 |
+
### T-12h: Final Checks
|
| 8 |
+
- [ ] All servers load-tested and stable
|
| 9 |
+
- [ ] Payment processing verified (test transactions)
|
| 10 |
+
- [ ] All links working (landing page, docs, social)
|
| 11 |
+
- [ ] Copy proofread by 2+ people
|
| 12 |
+
- [ ] Analytics/tracking confirmed firing
|
| 13 |
+
- [ ] Team roles assigned with backup contacts
|
| 14 |
+
|
| 15 |
+
### Hour 0: Coordinated Channel Activation
|
| 16 |
+
| Channel | Action | Owner |
|
| 17 |
+
|---------|--------|-------|
|
| 18 |
+
| Product Hunt | Go live at 12:01 AM PST | Founder |
|
| 19 |
+
| Twitter/X | Launch thread (10+ tweets) | Marketing |
|
| 20 |
+
| Email list | Launch announcement | Growth |
|
| 21 |
+
| Discord/Slack | Community ping | Community |
|
| 22 |
+
| Hacker News | Show HN post | CTO |
|
| 23 |
+
|
| 24 |
+
### Hours 1-6: Real-Time Monitoring
|
| 25 |
+
- Monitor PH ranking every 30 minutes
|
| 26 |
+
- Respond to every comment within 15 minutes
|
| 27 |
+
- Watch for server load spikes
|
| 28 |
+
- Track sign-up velocity
|
| 29 |
+
- Engage in Twitter conversations
|
| 30 |
+
|
| 31 |
+
### Hours 6-24: Second-Wave Amplification
|
| 32 |
+
- Activate KOL/influencer posts (staggered)
|
| 33 |
+
- Cross-post to LinkedIn, Reddit
|
| 34 |
+
- Send "we're live" to press contacts
|
| 35 |
+
- Share early metrics/milestones publicly
|
| 36 |
+
|
| 37 |
+
### 72-Hour Post-Launch Sprint
|
| 38 |
+
- Day 2: Share user testimonials and early wins
|
| 39 |
+
- Day 3: Publish "behind the launch" content
|
| 40 |
+
- Follow up with every sign-up who hasn't activated
|
| 41 |
+
- Continue community engagement
|
| 42 |
+
|
| 43 |
+
## Crisis Management
|
| 44 |
+
| Scenario | Response | Timeframe |
|
| 45 |
+
|----------|----------|-----------|
|
| 46 |
+
| Site goes down | Switch to status page, communicate on social | < 5 min |
|
| 47 |
+
| Negative HN comments | Engage thoughtfully, don't be defensive | < 15 min |
|
| 48 |
+
| Competitor attack | Ignore unless factually wrong, then correct once | As needed |
|
| 49 |
+
| Payment issues | Fix immediately, offer manual onboarding | < 30 min |
|
| 50 |
+
|
| 51 |
+
Built by Gingiris — orchestrated 30+ launches with combined 100k+ first-day visitors.
|
references/ja/README.md
ADDED
|
@@ -0,0 +1,51 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# スタートアップ ローンチ当日 プレイブック — 時間単位チェックリスト
|
| 2 |
+
|
| 3 |
+
ローンチ当日は一発勝負です。このプレイブックは、何も漏れがないように時間単位の実行計画を提供します。T-12時間の準備から72時間のポストローンチスプリントまで。
|
| 4 |
+
|
| 5 |
+
## タイムライン
|
| 6 |
+
|
| 7 |
+
### T-12h: 最終チェック
|
| 8 |
+
- [ ] 全サーバーの負荷テスト完了・安定稼働
|
| 9 |
+
- [ ] 決済処理の検証(テストトランザクション)
|
| 10 |
+
- [ ] 全リンクの動作確認(LP、ドキュメント、ソーシャル)
|
| 11 |
+
- [ ] コピーを2名以上で校正済み
|
| 12 |
+
- [ ] アナリティクス/トラッキングの発火確認
|
| 13 |
+
- [ ] チーム役割の割当 + バックアップ連絡先
|
| 14 |
+
|
| 15 |
+
### Hour 0: チャネル同時アクティベーション
|
| 16 |
+
| チャネル | アクション | 担当 |
|
| 17 |
+
|---------|-----------|------|
|
| 18 |
+
| Product Hunt | PST 12:01 AM に公開 | 創業者 |
|
| 19 |
+
| Twitter/X | ローンチスレッド(10ツイート以上) | マーケティング |
|
| 20 |
+
| メールリスト | ローンチ告知 | グロース |
|
| 21 |
+
| Discord/Slack | コミュニティ通知 | コミュニティ |
|
| 22 |
+
| Hacker News | Show HN 投稿 | CTO |
|
| 23 |
+
|
| 24 |
+
### Hours 1-6: リアルタイムモニタリング
|
| 25 |
+
- PH ランキングを30分ごとに確認
|
| 26 |
+
- 全コメントに15分以内で返信
|
| 27 |
+
- サーバー負荷スパイクを監視
|
| 28 |
+
- サインアップ速度をトラッキング
|
| 29 |
+
- Twitter の会話にエンゲージ
|
| 30 |
+
|
| 31 |
+
### Hours 6-24: セカンドウェーブ増幅
|
| 32 |
+
- KOL/インフルエンサー投稿をずらして有効化
|
| 33 |
+
- LinkedIn、Reddit にクロスポスト
|
| 34 |
+
- プレス連絡先に「公開しました」を送信
|
| 35 |
+
- 初期指標/マイルストーンを公開共有
|
| 36 |
+
|
| 37 |
+
### 72時間ポストローンチスプリント
|
| 38 |
+
- Day 2: ユーザー証言と初期の成果を共有
|
| 39 |
+
- Day 3:「ローンチの裏側」コンテンツを公開
|
| 40 |
+
- アクティベートしていないサインアップ全員にフォローアップ
|
| 41 |
+
- コミュニティエンゲージメントを継続
|
| 42 |
+
|
| 43 |
+
## 危機管理
|
| 44 |
+
| シナリオ | 対応 | 制限時間 |
|
| 45 |
+
|---------|------|---------|
|
| 46 |
+
| サイトダウン | ステータスページに切替、SNS で通知 | 5分以内 |
|
| 47 |
+
| HN でネガティブコメント | 思慮深く対話、防御的にならない | 15分以内 |
|
| 48 |
+
| 競合からの攻撃 | 事実誤認でない限り無視、誤りは一度だけ訂正 | 必要に応じて |
|
| 49 |
+
| 決済トラブル | 即時修正、手動オンボーディングを提案 | 30分以内 |
|
| 50 |
+
|
| 51 |
+
Gingiris 制作 — 合計10万以上の初日訪問者を記録した30以上のローンチを統括。
|
references/ko/README.md
ADDED
|
@@ -0,0 +1,51 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# 스타트업 런칭 당일 플레이북 — 시간별 체크리스트
|
| 2 |
+
|
| 3 |
+
런칭 당일은 단 한 번의 기회입니다. 이 플레이북은 빠짐없이 실행할 수 있도록 시간 단위 실행 계획을 제공합니다. T-12시간 준비부터 72시간 포스트 런칭 스프린트까지.
|
| 4 |
+
|
| 5 |
+
## 타임라인
|
| 6 |
+
|
| 7 |
+
### T-12h: 최종 점검
|
| 8 |
+
- [ ] 모든 서버 부하 테스트 완료 및 안정 확인
|
| 9 |
+
- [ ] 결제 처리 검증 (테스트 트랜잭션)
|
| 10 |
+
- [ ] 모든 링크 동작 확인 (랜딩 페이지, 문서, 소셜)
|
| 11 |
+
- [ ] 카피 2명 이상 교정 완료
|
| 12 |
+
- [ ] 애널리틱스/트래킹 발화 확인
|
| 13 |
+
- [ ] 팀 역할 배정 + 백업 연락처
|
| 14 |
+
|
| 15 |
+
### Hour 0: 채널 동시 활성화
|
| 16 |
+
| 채널 | 액션 | 담당 |
|
| 17 |
+
|------|------|------|
|
| 18 |
+
| Product Hunt | PST 12:01 AM에 공개 | 창업자 |
|
| 19 |
+
| Twitter/X | 런칭 스레드 (10개 이상 트윗) | 마케팅 |
|
| 20 |
+
| 이메일 리스트 | 런칭 공지 | 그로스 |
|
| 21 |
+
| Discord/Slack | 커뮤니티 알림 | 커뮤니티 |
|
| 22 |
+
| Hacker News | Show HN 포스트 | CTO |
|
| 23 |
+
|
| 24 |
+
### Hours 1-6: 실시간 모니터링
|
| 25 |
+
- PH 랭킹 30분마다 확인
|
| 26 |
+
- 모든 댓글에 15분 이내 응답
|
| 27 |
+
- 서버 부하 스파이크 감시
|
| 28 |
+
- 가입 속도 추적
|
| 29 |
+
- Twitter 대화에 참여
|
| 30 |
+
|
| 31 |
+
### Hours 6-24: 세컨드 웨이브 증폭
|
| 32 |
+
- KOL/인플루언서 포스트를 시차를 두고 활성화
|
| 33 |
+
- LinkedIn, Reddit에 크로스포스트
|
| 34 |
+
- 언론 연락처에 "출시했습니다" 전송
|
| 35 |
+
- 초기 지표/마일스톤을 공개 공유
|
| 36 |
+
|
| 37 |
+
### 72시간 포스트 런칭 스프린트
|
| 38 |
+
- Day 2: 사용자 후기와 초기 성과 공유
|
| 39 |
+
- Day 3: "런칭 비하인드" 콘텐츠 발행
|
| 40 |
+
- 활성화하지 않은 모든 가입자에게 후속 연락
|
| 41 |
+
- 커뮤니티 참여 지속
|
| 42 |
+
|
| 43 |
+
## 위기 관리
|
| 44 |
+
| 시나리오 | 대응 | 제한 시간 |
|
| 45 |
+
|---------|------|----------|
|
| 46 |
+
| 사이트 다운 | 상태 페이지로 전환, 소셜에서 공지 | 5분 이내 |
|
| 47 |
+
| HN 부정적 댓글 | 사려 깊게 대화, 방어적 태도 금지 | 15분 이내 |
|
| 48 |
+
| 경쟁사 공격 | 사실 오류가 아니면 무시, 오류는 한 번만 바로잡기 | 필요시 |
|
| 49 |
+
| 결제 문제 | 즉시 수정, 수동 온보딩 제안 | 30분 이내 |
|
| 50 |
+
|
| 51 |
+
Gingiris 제작 — 합산 10만 이상의 첫날 방문자를 기록한 30회 이상의 런칭을 운영.
|