go-to-market-strategy by manojbajaj95/claude-gtm-plugin
npx skills add https://github.com/manojbajaj95/claude-gtm-plugin --skill go-to-market-strategy端到端 GTM 手册:市场进入模式选择、定位、渠道策略、分阶段发布执行、发布营销和技术产品发布。
发布是一场战役,而非单一事件。 在发布前建立势头,在发布时达到顶峰,在发布后持续发力。最优秀的公司不会只发布一次——他们会一次又一次地发布。
| 模式 | 最适合 | 关键杠杆 |
|---|---|---|
| 产品驱动增长 | 中小企业、开发者、低年均合同价值 | 免费 → 付费转化 |
| 产品驱动增长 + 销售辅助 | 中型市场、年均合同价值 | 产品合格线索 → 销售合格线索路由 |
| 销售主导 | 企业、复杂产品、年均合同价值 > $25K | 关系、支持者 |
| 社区主导 | 开发者工具、开源软件 | 社区采用 |
| 合作伙伴主导 | 地域扩张、企业 | 合作伙伴激励 |
快速决策:
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
ACV < $5K 且支持自助服务? → PLG
买家是技术人员? → 开发者/社区主导
其他情况? → 销售主导
定义你的产品如何适应市场。
定位模板:
面向 [目标客户]
他们 [需求/问题]
[产品名称] 是一个 [类别]
它 [核心优势]
不同于 [竞争对手]
我们的产品 [独特差异化优势]
验证:目标客户已定义,差异化已识别,并已与 5 位以上客户测试。
信息层级:
需创建的内容: 发布博客文章 · 产品演示视频 · 落地页 · 邮件公告 · 5-10 条社交媒体帖子
自有渠道:邮件列表 · 博客/搜索引擎优化 · 品牌社区
租用渠道:Twitter/X · LinkedIn · YouTube · Reddit — 用于引流至自有渠道
借用渠道:客座文章 · 播客访谈 · 影响者合作 · 联合营销
策略:使用租用/借用渠道引流,捕获至自有渠道。
6 周发布时间线:
在发布前定义:
| 阶段 | 目标 | 关键行动 |
|---|---|---|
| 内部发布 | 验证功能 | 与友好用户测试,修复重大问题 |
| Alpha 版 | 首次外部验证 | 落地页、等候名单、单独邀请 |
| Beta 版 | 扩大早期访问范围并制造话题 | 处理等候名单,预热你解决的问题 |
| 早期访问 | 规模化验证 | 泄露细节、使用数据、产品市场契合度调查 |
| 全面发布 | 最大化可见度 | 开放注册、开始收费、所有渠道上线 |
发布日前: 与支持者建立关系,优化列表,参与社区。
发布日: 将其视为全天活动。回应每一条评论。将流量引导回网站以捕获注册。
发布后: 跟进所有参与互动的人。将 Product Hunt 流量转化为邮件注册。
案例研究 — Reform:研究成功发布案例,在发布前优化视觉效果、进行社区互动 → 获得“当日最佳产品”第一名。
对于任何重大发布,制作这 7 项交付物:
发布营销模板请参见:references/TEMPLATES.md
收集发布输入的问卷请参见:references/INTAKE.md
完整工作流程指南请参见:references/WORKFLOW.md
适用于开发者工具、API、SDK 和技术基础设施:
| 层级 | 类型 | 时间线 | 投入 |
|---|---|---|---|
| 1 — 重大 | 新产品/正式发布 | 12-16 周 | 高 |
| 2 — 标准 | 新功能/集成 | 6-8 周 | 中 |
| 3 — 次要 | 更新/补丁 | 2-4 周 | 低 |
开发者文档 · GitHub/GitLab · 开发者博客 · API 更新日志 · Dev.to · Hacker News · Reddit · Discord/Slack · YouTube 教程
层级框架详情请参见:references/launch_tiers.md
开发者指标请参见:references/metrics_frameworks.md
sales-and-revenue-operations — 销售团队、收入运营、理想客户画像pricing-strategy — 定价决策product-strategy-and-marketing — 产品愿景与定位每周安装量
103
代码仓库
GitHub 星标数
16
首次出现
14 天前
安全审计
安装于
opencode103
gemini-cli29
amp29
cline29
github-copilot29
codex29
End-to-end GTM playbook: motion selection, positioning, channel strategy, phased launch execution, launch marketing, and technical product launches.
A launch is a campaign, not an event. Build momentum before launch, peak at launch, sustain after. The best companies don't launch once — they launch again and again.
| Motion | Best For | Key Lever |
|---|---|---|
| PLG | SMB, developers, low ACV (<$5K) | Free → paid conversion |
| PLG + Sales-Assist | Mid-market, $5K-$25K ACV | PQL → SQL routing |
| Sales-Led | Enterprise, complex product, >$25K ACV | Relationship, champion |
| Community-Led | Developer tools, OSS | Community adoption |
| Partner-Led | Geographic expansion, enterprise | Partner incentives |
Quick decision:
ACV < $5K and self-serve possible? → PLG
Buyer technical? → Developer/community-led
Everything else? → Sales-led
Define how your product fits in the market.
Positioning template:
For [target customer]
Who [need/problem]
[Product] is a [category]
That [key benefit]
Unlike [competitors]
Our product [unique differentiator]
Validate: target customer defined, differentiation identified, tested with 5+ customers.
Message hierarchy:
Content to create: Launch blog post · Product demo video (2-3 min) · Landing page · Email announcement · 5-10 social posts
Owned (highest ROI — build these first): Email list · Blog/SEO · Branded community
Rented (speed, not stability): Twitter/X · LinkedIn · YouTube · Reddit — use to drive to owned
Borrowed (shortcut to audiences): Guest posts · Podcast interviews · Influencer partnerships · Co-marketing
Strategy: Use rented/borrowed to drive traffic, capture into owned.
6-Week Launch Timeline:
Define BEFORE launch:
| Phase | Goal | Key Actions |
|---|---|---|
| Internal | Validate functionality | Test with friendly users, fix major issues |
| Alpha | First external validation | Landing page, waitlist, invite individually |
| Beta | Scale early access + buzz | Work through waitlist, tease problems you solve |
| Early Access | Validate at scale | Leak details, usage data, PMF survey |
| Full Launch | Maximum visibility | Open signups, start charging, all channels live |
Before launch day: Build relationships with supporters, optimize listing (tagline, visuals, demo video), engage in communities.
On launch day: Treat as all-day event. Respond to every comment. Drive traffic back to site to capture signups.
After: Follow up with all who engaged. Convert PH traffic into email signups.
Case study — Reform: studied successful launches, polished visuals, community engagement pre-launch → #1 Product of the Day.
For any major launch, produce these 7 deliverables:
For launch marketing templates: see references/TEMPLATES.md For intake questions to gather launch inputs: see references/INTAKE.md For full workflow guidance: see references/WORKFLOW.md
For developer tools, APIs, SDKs, and technical infrastructure:
| Tier | Type | Timeline | Investment |
|---|---|---|---|
| 1 — Major | New product/GA | 12-16 weeks | High |
| 2 — Standard | New features/integrations | 6-8 weeks | Medium |
| 3 — Minor | Updates/patches | 2-4 weeks | Low |
Dev docs · GitHub/GitLab · Developer blog · API changelog · Dev.to · Hacker News · Reddit · Discord/Slack · YouTube tutorials
For tier framework details: see references/launch_tiers.md For developer metrics: see references/metrics_frameworks.md
sales-and-revenue-operations — Sales team, RevOps, ICPpricing-strategy — Pricing decisionsproduct-strategy-and-marketing — Product vision and positioningWeekly Installs
103
Repository
GitHub Stars
16
First Seen
14 days ago
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
opencode103
gemini-cli29
amp29
cline29
github-copilot29
codex29
内容策略指南:如何规划可搜索与可分享内容,驱动流量与潜在客户
39,800 周安装