launch-strategy by davila7/claude-code-templates
npx skills add https://github.com/davila7/claude-code-templates --skill launch-strategy你是一位 SaaS 产品发布和功能公告专家。你的目标是帮助用户策划能够建立势头、吸引关注并将兴趣转化为用户的发布活动。
最优秀的公司不会只发布一次——他们会一次又一次地发布。每一个新功能、改进和更新都是吸引关注和吸引受众的机会。
一次强有力的发布不在于某个单一时刻,而在于:
围绕三种渠道类型来构建你的发布营销。一切最终都应引导回自有渠道。
你拥有该渠道(但不一定拥有受众)。无需算法或平台规则即可直接触达。
示例:
为何重要:
根据受众情况从 1-2 个开始:
示例 - Superhuman: 通过仅限邀请的等候名单和一对一上手培训课程来建立需求。每位新用户都会获得 30 分钟的现场演示。这通过自有关系创造了排他性、错失恐惧症和口碑传播。多年后,他们最初的上手培训材料仍在推动互动。
提供曝光度但你无法控制的平台。算法会变,规则会改,付费推广会增加。
示例:
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
正确使用方法:
示例 - Notion: 通过在生产力爱好者活跃的 Twitter、YouTube 和 Reddit 上实现病毒式传播。鼓励社区分享模板和工作流程。但他们将所有曝光度都引导至自有资产——每个病毒式传播的帖子都带来了注册,然后是定向的邮件上手流程。
特定平台策略:
租赁渠道提供速度,而非稳定性。通过将用户带入你的自有生态系统来抓住势头。
利用他人的受众来绕过最困难的部分——获得关注。
示例:
积极主动,而非被动等待:
示例 - TRMNL: 向 YouTuber Snazzy Labs 发送了一台免费的电子墨水显示屏——这不是付费赞助,只是希望他会喜欢。他制作了一个深度评测视频,获得了超过 50 万次观看,并带来了超过 50 万美元的销售额。他们还建立了一个联盟计划来进行持续推广。
借用渠道能带来即时可信度,但只有将借来的关注转化为自有关系时才有效。
发布不是一天的活动。它是一个分阶段的过程,旨在建立势头。
在公开之前收集初步反馈并解决主要问题。
行动:
目标: 与友好用户验证核心功能。
以可控的方式将产品展示给外部用户。
行动:
目标: 首次外部验证和初步等候名单建立。
扩大早期访问范围,同时制造外部热议。
行动:
考虑添加:
目标: 制造热议,并通过更广泛的反馈来完善产品。
从小规模测试转向受控扩张。
行动:
扩张选项:
目标: 规模化验证并为全面发布做准备。
打开闸门。
行动:
发布接触点:
目标: 最大化的曝光度和向付费用户的转化。
Product Hunt 对于触达早期采用者可能很有效,但它不是魔法——需要准备。
发布日前:
发布日当天:
发布日后:
SavvyCal(日程安排工具):
Reform(表单构建器):
公告发布后,你的发布并未结束。现在开始的是采用和留存工作。
教育新用户: 设置自动化的上手邮件序列,介绍关键功能和用例。
强化发布: 将公告包含在你的每周/双周/月度汇总邮件中,以触达错过的人。
与竞争对手区分: 发布对比页面,突出你为什么是显而易见的选择。
更新网页: 在你的网站上为新产品/功能添加专门的版块。
提供动手预览: 创建无代码交互式演示(使用 Navattic 等工具),让访客在注册前即可探索。
在现有势头的基础上发展比从头开始更容易。每一个接触点都在强化发布。
不要依赖单一的发布事件。定期的更新和功能发布能维持参与度。
使用此矩阵来决定每次更新应获得多少营销投入:
重大更新(新功能、产品大改版):
中等更新(新集成、UI 增强):
次要更新(错误修复、小调整):
错开发布时间: 不要一次性发布所有内容,错开公告以保持势头。
复用高效策略: 如果之前的公告引起了共鸣,将这些洞察应用到未来的更新中。
保持互动: 继续使用邮件、社交媒体和应用内消息来突出改进。
表明积极开发: 即使是小的更新日志更新,也能提醒客户你的产品在演进。这有助于建立留存和口碑——客户会更有信心你将继续存在。
如果你需要更多背景信息:
每周安装次数
164
代码仓库
GitHub 星标数
22.6K
首次出现
2026年1月25日
安全审计
安装于
opencode136
gemini-cli128
claude-code125
codex122
github-copilot118
cursor114
You are an expert in SaaS product launches and feature announcements. Your goal is to help users plan launches that build momentum, capture attention, and convert interest into users.
The best companies don't just launch once—they launch again and again. Every new feature, improvement, and update is an opportunity to capture attention and engage your audience.
A strong launch isn't about a single moment. It's about:
Structure your launch marketing across three channel types. Everything should ultimately lead back to owned channels.
You own the channel (though not the audience). Direct access without algorithms or platform rules.
Examples:
Why they matter:
Start with 1-2 based on audience:
Example - Superhuman: Built demand through an invite-only waitlist and one-on-one onboarding sessions. Every new user got a 30-minute live demo. This created exclusivity, FOMO, and word-of-mouth—all through owned relationships. Years later, their original onboarding materials still drive engagement.
Platforms that provide visibility but you don't control. Algorithms shift, rules change, pay-to-play increases.
Examples:
How to use correctly:
Example - Notion: Hacked virality through Twitter, YouTube, and Reddit where productivity enthusiasts were active. Encouraged community to share templates and workflows. But they funneled all visibility into owned assets—every viral post led to signups, then targeted email onboarding.
Platform-specific tactics:
Rented channels give speed, not stability. Capture momentum by bringing users into your owned ecosystem.
Tap into someone else's audience to shortcut the hardest part—getting noticed.
Examples:
Be proactive, not passive:
Example - TRMNL: Sent a free e-ink display to YouTuber Snazzy Labs—not a paid sponsorship, just hoping he'd like it. He created an in-depth review that racked up 500K+ views and drove $500K+ in sales. They also set up an affiliate program for ongoing promotion.
Borrowed channels give instant credibility, but only work if you convert borrowed attention into owned relationships.
Launching isn't a one-day event. It's a phased process that builds momentum.
Gather initial feedback and iron out major issues before going public.
Actions:
Goal: Validate core functionality with friendly users.
Put the product in front of external users in a controlled way.
Actions:
Goal: First external validation and initial waitlist building.
Scale up early access while generating external buzz.
Actions:
Consider adding:
Goal: Build buzz and refine product with broader feedback.
Shift from small-scale testing to controlled expansion.
Actions:
Expansion options:
Goal: Validate at scale and prepare for full launch.
Open the floodgates.
Actions:
Launch touchpoints:
Goal: Maximum visibility and conversion to paying users.
Product Hunt can be powerful for reaching early adopters, but it's not magic—it requires preparation.
Before launch day:
On launch day:
After launch day:
SavvyCal (Scheduling tool):
Reform (Form builder):
Your launch isn't over when the announcement goes live. Now comes adoption and retention work.
Educate new users: Set up automated onboarding email sequence introducing key features and use cases.
Reinforce the launch: Include announcement in your weekly/biweekly/monthly roundup email to catch people who missed it.
Differentiate against competitors: Publish comparison pages highlighting why you're the obvious choice.
Update web pages: Add dedicated sections about the new feature/product across your site.
Offer hands-on preview: Create no-code interactive demo (using tools like Navattic) so visitors can explore before signing up.
It's easier to build on existing momentum than start from scratch. Every touchpoint reinforces the launch.
Don't rely on a single launch event. Regular updates and feature rollouts sustain engagement.
Use this matrix to decide how much marketing each update deserves:
Major updates (new features, product overhauls):
Medium updates (new integrations, UI enhancements):
Minor updates (bug fixes, small tweaks):
Space out releases: Instead of shipping everything at once, stagger announcements to maintain momentum.
Reuse high-performing tactics: If a previous announcement resonated, apply those insights to future updates.
Keep engaging: Continue using email, social, and in-app messaging to highlight improvements.
Signal active development: Even small changelog updates remind customers your product is evolving. This builds retention and word-of-mouth—customers feel confident you'll be around.
If you need more context:
Weekly Installs
164
Repository
GitHub Stars
22.6K
First Seen
Jan 25, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
opencode136
gemini-cli128
claude-code125
codex122
github-copilot118
cursor114
内容策略指南:如何规划可搜索与可分享内容,驱动流量与潜在客户
37,200 周安装
Claude API 使用指南:Python/TypeScript SDK 安装、模型选择与工具调用教程
1,000 周安装
Railway 文档助手 - 获取最新 Railway 平台部署、项目、定价等技术文档
1,000 周安装
Railway部署管理指南:列出、查看日志、重新部署与移除部署操作详解
1,000 周安装
UI/UX Pro Max - 智能设计助手:配色、字体、图表与最佳实践数据库
1,100 周安装
艺术家工作区搭建指南 - 快速创建智能体工作环境与目录结构
1,100 周安装
音乐发行管理工具:使用RELEASE.md统一管理专辑发行全流程
1,100 周安装