Back to Details

go-to-market-plan

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Go-to-Market Plan

上市（Go-to-Market）计划

Purpose

目标

Analyze the founder's business and current stage to deliver 3 specific, actionable go-to-market strategies that will drive measurable market penetration and customer acquisition.
分析创始人的业务及当前阶段，提供3个具体、可执行的上市（Go-to-Market）策略，以推动可衡量的市场渗透和客户获取。

Execution Logic

执行逻辑

Check $ARGUMENTS first to determine execution mode:
首先检查$ARGUMENTS以确定执行模式：

If $ARGUMENTS is empty or not provided:

若$ARGUMENTS为空或未提供：

Respond with: "go-to-market-plan loaded, proceed with details about your product, target market, or current launch situation"
Then wait for the user to provide their requirements in the next message.
回复： "go-to-market-plan已加载，请提供你的产品、目标市场或当前发布情况的详细信息"
然后等待用户在下一条消息中提供需求。

If $ARGUMENTS contains content:

若$ARGUMENTS包含内容：

Proceed immediately to Task Execution (skip the "loaded" message).
直接进入任务执行环节（跳过"已加载"提示）。

Task Execution

任务执行

When user requirements are available (either from initial $ARGUMENTS or follow-up message):
当用户需求可用时（来自初始$ARGUMENTS或后续消息）：

1. Read Business Context

1. 读取业务背景

Check if 
FOUNDER_CONTEXT.md
exists in the project root.
  • If it exists: Read it and extract: company name, industry, target audience, value proposition, products/services, business stage, competitors, pricing model, unique advantages.
  • If it doesn't exist: Proceed to Step 2 and gather this information through questions.
检查项目根目录下是否存在
FOUNDER_CONTEXT.md
文件。
  • 若存在： 读取文件并提取以下信息：公司名称、行业、目标受众、价值主张、产品/服务、业务阶段、竞争对手、定价模型、独特优势。
  • 若不存在： 进入步骤2，通过问题收集这些信息。

2. Diagnose GTM Readiness

2. 诊断GTM就绪度

Evaluate whether you have enough information to produce high-confidence, actionable go-to-market strategies:
Required information to proceed without questions:
  • What problem the product solves (core value proposition)
  • Who the ideal customer is (specific ICP, not "small businesses" or "everyone")
  • Product readiness stage (MVP, beta, ready to scale, etc.)
  • Competitive landscape (who else solves this, how you're different)
  • Distribution model (direct, channel partners, marketplace, etc.)
  • Pricing strategy (freemium, paid, enterprise, etc.)
  • Current market position (pre-launch, launched but struggling, ready to scale)
  • Available resources (team, budget, runway)
If you have enough context: Proceed directly to Step 4.
If critical information is missing: Proceed to Step 3.
评估是否拥有足够信息来制定高可信度、可执行的上市策略：
无需提问即可推进的必要信息：
  • 产品解决的核心问题（核心价值主张）
  • 理想客户是谁（具体的ICP，而非"小企业"或"所有人"）
  • 产品就绪阶段（MVP、测试版、可规模化等）
  • 竞争格局（还有哪些玩家解决该问题，你的差异化之处）
  • 分销模式（直销、渠道合作伙伴、市场平台等）
  • 定价策略（免费增值、付费、企业版等）
  • 当前市场地位（预发布、已发布但增长乏力、可规模化）
  • 可用资源（团队、预算、现金流）
若信息充足： 直接进入步骤4。
若关键信息缺失： 进入步骤3。

3. Ask Diagnostic Questions (When Needed)

3. 提出诊断问题（必要时）

Use the AskUserQuestion tool to gather missing information. Ask between 3-10 questions based on what's needed:
Core GTM questions:
  • What stage is your product at right now? (Idea, MVP, beta, launched, scaling)
  • Who is your ideal first customer? (Be specific: role, company size, industry, pain point)
  • What's the core problem your product solves? How do people solve it today?
  • How do customers currently discover solutions like yours?
  • What's your biggest struggle with go-to-market right now?
  • What have you already tried for customer acquisition? What worked? What didn't?
  • What resources do you have available? (Budget, team, timeline, network)
Context-specific questions:
  • For pre-launch: "Have you validated product-market fit? How many people have you talked to?"
  • For launched but struggling: "Where are you getting customers today? What's your current CAC vs. LTV?"
  • For scaling: "What channels are working? What's your constraint to 10x growth?"
  • For competitive positioning: "Who are your top 3 competitors? Why would someone choose you over them?"
  • For pricing clarity: "Have you tested pricing? What signals indicate customers will pay this amount?"
IMPORTANT: Only ask questions for information you truly need. Don't ask for information you can infer from FOUNDER_CONTEXT.md or the user's initial message.
使用AskUserQuestion工具收集缺失信息。根据需求提出3-10个问题：
核心GTM问题：
  • 你的产品当前处于什么阶段？（创意、MVP、测试版、已发布、规模化）
  • 你的首批理想客户是谁？（请具体说明：职位、公司规模、行业、痛点）
  • 你的产品解决的核心问题是什么？人们目前如何解决这个问题？
  • 客户目前如何发现类似你的解决方案？
  • 你当前在上市过程中面临的最大挑战是什么？
  • 你已经尝试过哪些客户获取手段？哪些有效？哪些无效？
  • 你拥有哪些可用资源？（预算、团队、时间线、人脉）
特定背景问题：
  • 针对预发布阶段："你是否验证过产品市场契合度？你已经与多少人交流过？"
  • 针对已发布但增长乏力："你当前从哪些渠道获取客户？当前的CAC与LTV对比如何？"
  • 针对规模化阶段："哪些渠道有效？实现10倍增长的制约因素是什么？"
  • 针对竞争定位："你的前3大竞争对手是谁？客户为什么会选择你而非他们？"
  • 针对定价清晰度："你是否测试过定价？哪些信号表明客户愿意支付该价格？"
重要提示： 仅询问你真正需要的信息。不要询问可从FOUNDER_CONTEXT.md或用户初始消息中推断出的信息。

4. Analyze Market Entry Strategy

4. 分析市场进入策略

Based on the context gathered, analyze:
  1. Product-Market Fit Status: Do they have it? How do you know?
  2. Market Entry Point: Where is the wedge? (Specific segment, use case, or channel)
  3. Competitive Positioning: What's the unique angle that cuts through noise?
  4. Distribution Channels: Where does the ICP actually spend time and make buying decisions?
  5. Go-to-Market Motion: Product-led, sales-led, community-led, or hybrid?
  6. Market Timing: Why now? What's changed in the market or technology?
Critical analysis principles:
  • Start narrow, expand later: Best GTM starts with a tight, underserved segment
  • Channel-product fit matters more than product-market fit early on: Great product in wrong channel = no traction
  • Identify unfair advantages: Network, expertise, distribution, brand, technology
  • Find the "bowling pin" strategy: Which customer segment unlocks adjacent segments?
  • Validate before scaling: Don't build GTM for hypothetical customers
基于收集到的背景信息，分析以下内容：
  1. 产品市场契合度状态： 他们是否具备？你如何判断？
  2. 市场切入点： 突破口在哪里？（具体细分领域、用例或渠道）
  3. 竞争定位： 什么独特角度能脱颖而出？
  4. 分销渠道： ICP实际在哪里花费时间并做出购买决策？
  5. 上市模式： 产品驱动、销售驱动、社区驱动还是混合模式？
  6. 市场时机： 为什么是现在？市场或技术发生了哪些变化？
关键分析原则：
  • 先聚焦窄域，再逐步扩张： 最佳GTM策略始于一个精准、未被充分服务的细分群体
  • 早期阶段，渠道-产品契合度比产品-市场契合度更重要： 优秀的产品若选错渠道，也无法获得关注
  • 识别不公平优势： 人脉、专业知识、分销渠道、品牌、技术
  • 找到"保龄球瓶"策略： 哪个客户群体能解锁相邻群体？
  • 先验证再规模化： 不要为假设的客户制定GTM策略

5. Generate 3 Go-to-Market Strategies

5. 生成3个上市策略

Create exactly 3 GTM strategies, ranked by fit and impact:
Selection criteria:
  • Specificity: Is this concrete enough to execute this week?
  • Channel-market fit: Will the ICP actually see this in their buying journey?
  • Differentiation: Does this position you uniquely vs. competitors?
  • Scalability: Can this grow beyond the first 10 customers?
  • Resource fit: Can they execute with current team/budget/capabilities?
  • Confidence: Only recommend if you're confident it will work for THIS product and market
For each strategy, write:
Part A — The Strategy (What & Why)
  • One-line strategy name
  • 2-3 sentences explaining WHAT the GTM approach is and WHY it fits this product/market
  • Reference the specific market wedge, competitive angle, or channel advantage it leverages
Part B — The Exact Playbook (How)
  • Step-by-step execution plan with specific actions
  • Use their actual product name, ICP details, and market specifics
  • Include concrete details: which channels, which messaging, which segments, which metrics to track
  • Specify timeline and expected milestones
Part C — First Action (Do This Today)
  • One specific task they can complete in the next 30-60 minutes
  • Concrete enough that there's no ambiguity about what to do
创建恰好3个GTM策略，按契合度和影响力排序：
选择标准：
  • 具体性： 是否足够具体，可在本周内执行？
  • 渠道-市场契合度： ICP在购买旅程中是否真的会看到并参与？
  • 差异化： 是否能让你与竞争对手形成独特定位？
  • 可扩展性： 能否在首批10个客户之后持续增长？
  • 资源契合度： 他们能否利用现有团队/预算/能力执行？
  • 可信度： 仅推荐你确信对该产品和市场有效的策略
每个策略需包含：
A部分 — 策略（内容与原因）
  • 一句话策略名称
  • 2-3句话解释该GTM方法是什么，以及为什么适合该产品/市场
  • 提及所利用的具体市场突破口、竞争角度或渠道优势
B部分 — 详细执行手册（操作方法）
  • 包含具体行动的分步执行计划
  • 使用实际产品名称、ICP细节和市场特定信息
  • 包含具体细节：哪些渠道、哪些信息传递、哪些细分群体、哪些指标需要跟踪
  • 指定时间线和预期里程碑
C部分 — 立即行动（今日可做）
  • 一项可在30-60分钟内完成的具体任务
  • 足够具体，不存在歧义

6. Format and Verify

6. 格式化与验证

  • Structure output according to Output Format section
  • Complete Quality Checklist self-verification before presenting output
  • 按照输出格式部分的要求组织输出内容
  • 在呈现输出前完成质量检查表的自我验证

Writing Rules

写作规则

Hard constraints. No interpretation.
硬性约束，无需解读。

Core Rules

核心规则

  • Zero generic GTM advice. Every strategy must be specific to THIS product and market.
  • Use actual product names, ICP details, market specifics, and competitive positioning.
  • Lead with the highest-fit strategy first (not necessarily most innovative, but most likely to work).
  • Every strategy must include a concrete playbook, not just a concept.
  • Specify metrics to track for each strategy.
  • No motivational fluff. Only actionable GTM strategy.
  • Active voice only.
  • Strategies must be executable within their resource constraints.
  • 禁止通用GTM建议。每个策略必须针对该产品和市场量身定制。
  • 使用实际产品名称、ICP细节、市场特定信息和竞争定位。
  • 优先展示契合度最高的策略（不一定是最具创新性的，但最有可能见效）。
  • 每个策略必须包含具体的执行手册，而非仅概念。
  • 指定每个策略需要跟踪的指标。
  • 禁止励志类空话。仅提供可执行的GTM策略。
  • 全程使用主动语态。
  • 策略必须在其资源约束范围内可执行。

Specificity Rules

具体性规则

  • BAD: "Use content marketing"
  • GOOD: "Write 1 deep-dive case study per week showing how [Product] helped [Specific ICP] solve [Specific Problem]. Post on LinkedIn targeting [Job Titles]. Include ROI metrics. Repurpose into email sequence for outbound. Goal: 500 views/post, 20 inbound leads/month."
  • BAD: "Build a community"
  • GOOD: "Launch a private Slack community for [Specific ICP] called '[Community Name]'. Seed it with 20 hand-picked customers. Host weekly 'Office Hours' where members can ask questions about [Problem Space]. Incentivize referrals: invite 3 peers = lifetime discount. Goal: 100 members in 60 days, 30% weekly active."
  • BAD: "Partner with influencers"
  • GOOD: "Identify 10 YouTubers with 50k-200k subscribers in [Industry] who cover [Topic]. Reach out with free access to [Product] + $500 flat fee for honest review video. Track: views, click-through rate, signups from each video. Goal: 3 partnerships, 500+ signups in 90 days."
  • 错误示例： "使用内容营销"
  • 正确示例： "每周撰写1篇深度案例研究，展示[产品]如何帮助[具体ICP]解决[具体问题]。发布在LinkedIn上，针对[职位头衔]。包含ROI指标。将内容重新利用为 outbound 邮件序列。目标：每篇帖子500次浏览量，每月20个 inbound 线索。"
  • 错误示例： "打造社区"
  • 正确示例： "为[具体ICP]启动名为'[社区名称]'的私人Slack社区。邀请20名精心挑选的客户作为种子用户。每周举办'办公时间'，成员可就[问题领域]提问。激励推荐：邀请3位同行 = 终身折扣。目标：60天内达到100名成员，周活跃度30%。"
  • 错误示例： "与网红合作"
  • 正确示例： "在[行业]中找到10位拥有5万-20万订阅者的YouTuber，他们专注于[主题]。提供免费使用[产品]的权限 + 500美元固定费用，邀请他们制作诚实的评测视频。跟踪：浏览量、点击率、每个视频带来的注册量。目标：3次合作，90天内获得500+注册量。"

Context-Based Adaptation

基于背景的适配

  • Pre-product-market fit: Focus on validation tactics (customer interviews, pilot programs, design partnerships, early adopter communities)
  • Post-product-market fit, pre-scale: Focus on repeatable acquisition (content engine, outbound playbook, referral loops, strategic partnerships)
  • Scaling stage: Focus on channel diversification, market expansion, brand building, enterprise upmarket moves
  • B2B SaaS: Prioritize outbound, content, product-led growth, partnerships, vertical events
  • B2C apps: Prioritize app store optimization, influencer marketing, viral loops, paid social
  • Marketplace: Prioritize supply-side first (harder to acquire), demand follows
  • Developer tools: Prioritize open source, technical content, developer communities, product-led growth
  • Category creation: Focus on education-first content, thought leadership, category naming/framing
  • Competitive market: Focus on wedge positioning, differentiated messaging, switching incentives
  • 产品-市场契合度验证前： 聚焦验证策略（客户访谈、试点项目、设计合作伙伴、早期采用者社区）
  • 产品-市场契合度验证后、规模化前： 聚焦可重复的客户获取（内容引擎、outbound执行手册、推荐循环、战略合作伙伴）
  • 规模化阶段： 聚焦渠道多元化、市场扩张、品牌建设、企业级向上拓展
  • B2B SaaS： 优先考虑outbound、内容、产品驱动增长、合作伙伴、垂直行业活动
  • B2C应用： 优先考虑应用商店优化、网红营销、病毒式循环、付费社交
  • 平台型产品： 优先先获取供给端（更难获取），需求端自然跟进
  • 开发者工具： 优先考虑开源、技术内容、开发者社区、产品驱动增长
  • 品类创建： 聚焦教育导向内容、思想领导力、品类命名/框架
  • 竞争激烈的市场： 聚焦突破口定位、差异化信息传递、转换激励

Quality Filters

质量筛选

Before finalizing ANY strategy, ask:
  • Is this specific to THIS product and market, or could it apply to any company?
  • Would the ICP actually see/engage with this in their buying journey?
  • Does this leverage an unfair advantage or unique positioning?
  • Can they execute this with current resources?
  • Would I personally bet money that this will produce traction?
  • If the answer to any is "no" → rewrite or replace the strategy.
在最终确定任何策略前，询问自己：
  • 这是针对该产品和市场的特定策略，还是适用于任何公司的通用策略？
  • ICP在购买旅程中是否真的会看到/参与该策略？
  • 这是否利用了不公平优势或独特定位？
  • 他们能否利用现有资源执行该策略？
  • 我个人是否会押注该策略能带来客户增长？
  • 如果任何问题的答案是"否" → 重写或替换该策略。

Output Format

输出格式

markdown
undefined
markdown
undefined

Your 3 Go-to-Market Strategies

Your 3 Go-to-Market Strategies

Based on [Product Name]'s current stage and market position, here are your 3 best go-to-market strategies:
Based on [Product Name]'s current stage and market position, here are your 3 best go-to-market strategies:

Strategy 1: [Strategy Name]

Strategy 1: [Strategy Name]

The Strategy: [2-3 sentences: What the GTM approach is, why it fits this product/market, what advantage it leverages]
The Exact Playbook:
Step 1: [Specific action with details] Step 2: [Specific action with details] Step 3: [Specific action with details] Step 4: [Specific action with details]
Metrics to Track:
  • [Specific metric 1]
  • [Specific metric 2]
  • [Specific metric 3]
Expected Milestones: [Concrete outcomes with timeline, e.g., "50 qualified leads within 30 days, 10 customers by day 60"]
Do This Today: [One 30-60 minute action they can take immediately]
The Strategy: [2-3 sentences: What the GTM approach is, why it fits this product/market, what advantage it leverages]
The Exact Playbook:
Step 1: [Specific action with details] Step 2: [Specific action with details] Step 3: [Specific action with details] Step 4: [Specific action with details]
Metrics to Track:
  • [Specific metric 1]
  • [Specific metric 2]
  • [Specific metric 3]
Expected Milestones: [Concrete outcomes with timeline, e.g., "50 qualified leads within 30 days, 10 customers by day 60"]
Do This Today: [One 30-60 minute action they can take immediately]

Strategy 2: [Strategy Name]

Strategy 2: [Strategy Name]

The Strategy: [...]
The Exact Playbook: [...]
Metrics to Track: [...]
Expected Milestones: [...]
Do This Today: [...]
The Strategy: [...]
The Exact Playbook: [...]
Metrics to Track: [...]
Expected Milestones: [...]
Do This Today: [...]

Strategy 3: [Strategy Name]

Strategy 3: [Strategy Name]

The Strategy: [...]
The Exact Playbook: [...]
Metrics to Track: [...]
Expected Milestones: [...]
Do This Today: [...]
The Strategy: [...]
The Exact Playbook: [...]
Metrics to Track: [...]
Expected Milestones: [...]
Do This Today: [...]

Execution Priority

Execution Priority

Start with: Strategy [X] — [One sentence explaining why this is the highest priority right now]
Why this order: [2-3 sentences explaining the strategic sequencing — why doing these in this order maximizes market penetration and learning]
Start with: Strategy [X] — [One sentence explaining why this is the highest priority right now]
Why this order: [2-3 sentences explaining the strategic sequencing — why doing these in this order maximizes market penetration and learning]

Success Criteria

Success Criteria

You'll know these strategies are working when:
  • [Specific metric/outcome 1 with timeline]
  • [Specific metric/outcome 2 with timeline]
  • [Specific metric/outcome 3 with timeline]
If you don't see these results, revisit your execution or pivot to a different market segment.

**Example:**

```markdown
You'll know these strategies are working when:
  • [Specific metric/outcome 1 with timeline]
  • [Specific metric/outcome 2 with timeline]
  • [Specific metric/outcome 3 with timeline]
If you don't see these results, revisit your execution or pivot to a different market segment.

**Example:**

```markdown

Your 3 Go-to-Market Strategies

Your 3 Go-to-Market Strategies

Based on DevAnalytics's current stage (MVP launched, 12 beta users, targeting engineering managers at Series A-C startups), here are your 3 best go-to-market strategies:
Based on DevAnalytics's current stage (MVP launched, 12 beta users, targeting engineering managers at Series A-C startups), here are your 3 best go-to-market strategies:

Strategy 1: Design Partnership Program with 5 Target Companies

Strategy 1: Design Partnership Program with 5 Target Companies

The Strategy: Position DevAnalytics as a co-creation partner for engineering leaders at high-growth startups who are struggling with team productivity visibility. Instead of selling a finished product, offer to build custom dashboards alongside 5 carefully selected companies in exchange for case studies and testimonials. This validates product-market fit, generates social proof, and creates evangelists who will refer you to peers.
The Exact Playbook:
Step 1: Identify 5 Series A-C startups (50-150 employees) in your network or LinkedIn 2nd connections who recently raised funding and are likely hiring aggressively. Focus on companies using your tech stack (GitHub, Jira, Linear).
Step 2: Craft a personalized outreach message referencing their recent funding announcement: "Congrats on the Series B. As you scale engineering from 20 to 50, visibility into team productivity becomes critical. I'm building DevAnalytics specifically for this problem. Would you be open to a 6-week design partnership where we build custom dashboards for your team in exchange for feedback and a case study?"
Step 3: For accepted partnerships, conduct weekly 45-minute calls to understand their specific metrics needs, build dashboards collaboratively, and iterate based on feedback.
Step 4: Document each partnership as a case study showing: problem faced, metrics tracked, decisions made based on DevAnalytics data, and quantified outcomes (e.g., "Reduced deployment time by 30%").
Metrics to Track:
  • Outreach sent: 20 (to get 5 partnerships)
  • Partnership acceptance rate (goal: 25%)
  • Weekly active users per partnership (goal: >70%)
  • Case study completion rate (goal: 100%)
Expected Milestones: 5 active design partnerships within 30 days, 3 completed case studies by day 60, 2 paid conversions by day 90.
Do This Today: Open LinkedIn and identify 10 engineering leaders at Series A-C startups who you have a mutual connection with. Export their names, companies, and connection paths to a spreadsheet.
The Strategy: Position DevAnalytics as a co-creation partner for engineering leaders at high-growth startups who are struggling with team productivity visibility. Instead of selling a finished product, offer to build custom dashboards alongside 5 carefully selected companies in exchange for case studies and testimonials. This validates product-market fit, generates social proof, and creates evangelists who will refer you to peers.
The Exact Playbook:
Step 1: Identify 5 Series A-C startups (50-150 employees) in your network or LinkedIn 2nd connections who recently raised funding and are likely hiring aggressively. Focus on companies using your tech stack (GitHub, Jira, Linear).
Step 2: Craft a personalized outreach message referencing their recent funding announcement: "Congrats on the Series B. As you scale engineering from 20 to 50, visibility into team productivity becomes critical. I'm building DevAnalytics specifically for this problem. Would you be open to a 6-week design partnership where we build custom dashboards for your team in exchange for feedback and a case study?"
Step 3: For accepted partnerships, conduct weekly 45-minute calls to understand their specific metrics needs, build dashboards collaboratively, and iterate based on feedback.
Step 4: Document each partnership as a case study showing: problem faced, metrics tracked, decisions made based on DevAnalytics data, and quantified outcomes (e.g., "Reduced deployment time by 30%").
Metrics to Track:
  • Outreach sent: 20 (to get 5 partnerships)
  • Partnership acceptance rate (goal: 25%)
  • Weekly active users per partnership (goal: >70%)
  • Case study completion rate (goal: 100%)
Expected Milestones: 5 active design partnerships within 30 days, 3 completed case studies by day 60, 2 paid conversions by day 90.
Do This Today: Open LinkedIn and identify 10 engineering leaders at Series A-C startups who you have a mutual connection with. Export their names, companies, and connection paths to a spreadsheet.

Strategy 2: "Engineering Metrics Playbook" Content + Inbound Engine

Strategy 2: "Engineering Metrics Playbook" Content + Inbound Engine

The Strategy: Engineering managers at scaling startups are overwhelmed with metric choices (velocity, cycle time, DORA metrics, etc.) but don't know which to track or how to act on them. Create an authoritative "Engineering Metrics Playbook" that becomes the go-to resource for this audience. Position DevAnalytics as the tool that makes implementing these metrics effortless. This builds SEO authority, generates inbound leads, and establishes thought leadership.
The Exact Playbook:
Step 1: Write a 3,000-word "Engineering Metrics Playbook" covering: which metrics matter at each stage (pre-PMF, scaling, enterprise), how to measure them, what benchmarks to target, and common pitfalls to avoid. Use real examples from your design partnerships.
Step 2: Publish on your blog at devanalytics.com/playbook with SEO-optimized title: "Engineering Metrics That Actually Matter: A Playbook for Scaling Startups [2026]". Optimize for keywords: "engineering metrics", "DORA metrics for startups", "engineering KPIs".
Step 3: Gate a downloadable PDF version (with additional templates and spreadsheets) behind an email signup. Use ConvertKit or similar to capture leads.
Step 4: Distribute aggressively: post on Hacker News, Reddit r/engineering, LinkedIn (tag 10 engineering influencers), Engineering Manager communities (Rands Leadership Slack, LeadDev community), and email to your 12 beta users asking them to share.
Step 5: Follow up with email sequence: Day 1: Send the playbook. Day 3: Case study from design partnership. Day 7: Product demo video. Day 14: Free trial offer.
Metrics to Track:
  • Playbook page views (goal: 1,000 in first 30 days)
  • Email conversion rate (goal: 15%)
  • Email-to-trial conversion rate (goal: 10%)
Expected Milestones: 150 email signups within 30 days, 15 trial signups within 60 days, 3 paid conversions within 90 days.
Do This Today: Outline the Engineering Metrics Playbook table of contents. List 10 metrics you'll cover and identify which of your beta users can provide examples for each.
The Strategy: Engineering managers at scaling startups are overwhelmed with metric choices (velocity, cycle time, DORA metrics, etc.) but don't know which to track or how to act on them. Create an authoritative "Engineering Metrics Playbook" that becomes the go-to resource for this audience. Position DevAnalytics as the tool that makes implementing these metrics effortless. This builds SEO authority, generates inbound leads, and establishes thought leadership.
The Exact Playbook:
Step 1: Write a 3,000-word "Engineering Metrics Playbook" covering: which metrics matter at each stage (pre-PMF, scaling, enterprise), how to measure them, what benchmarks to target, and common pitfalls to avoid. Use real examples from your design partnerships.
Step 2: Publish on your blog at devanalytics.com/playbook with SEO-optimized title: "Engineering Metrics That Actually Matter: A Playbook for Scaling Startups [2026]". Optimize for keywords: "engineering metrics", "DORA metrics for startups", "engineering KPIs".
Step 3: Gate a downloadable PDF version (with additional templates and spreadsheets) behind an email signup. Use ConvertKit or similar to capture leads.
Step 4: Distribute aggressively: post on Hacker News, Reddit r/engineering, LinkedIn (tag 10 engineering influencers), Engineering Manager communities (Rands Leadership Slack, LeadDev community), and email to your 12 beta users asking them to share.
Step 5: Follow up with email sequence: Day 1: Send the playbook. Day 3: Case study from design partnership. Day 7: Product demo video. Day 14: Free trial offer.
Metrics to Track:
  • Playbook page views (goal: 1,000 in first 30 days)
  • Email conversion rate (goal: 15%)
  • Email-to-trial conversion rate (goal: 10%)
Expected Milestones: 150 email signups within 30 days, 15 trial signups within 60 days, 3 paid conversions within 90 days.
Do This Today: Outline the Engineering Metrics Playbook table of contents. List 10 metrics you'll cover and identify which of your beta users can provide examples for each.

Strategy 3: Strategic Partnership with Engineering Enablement Consultants

Strategy 3: Strategic Partnership with Engineering Enablement Consultants

The Strategy: Engineering leaders at scaling startups often hire consultants (ex-VPEs, fractional CTOs) to help them build processes and teams. These consultants need data to make recommendations but don't have analytics tools to provide to clients. Partner with 3-5 engineering enablement consultants to make DevAnalytics their default tool for client engagements. They get better insights for clients, you get distribution into their customer base.
The Exact Playbook:
Step 1: Identify 5 engineering enablement consultants who work with Series A-C startups. Search LinkedIn for "Fractional CTO", "Engineering Consultant", "Engineering Leadership Coach". Look for people with 10k+ followers and active posting about scaling teams.
Step 2: Reach out with a partnership proposition: "I noticed you work with engineering leaders at scaling startups. I built DevAnalytics to give teams visibility into productivity metrics. Would you be interested in a partnership where you get free access to offer to your clients, and in return, you promote it as your recommended analytics tool? You get better client outcomes, we get distribution."
Step 3: Create a "Consultant Partner Program" with: free DevAnalytics access for consultants + their clients, co-branded case studies, 20% revenue share on client conversions, joint webinar opportunities.
Step 4: Provide partners with enablement materials: pitch deck, demo scripts, ROI calculator, case studies, setup guides.
Step 5: Track partner activity and double down on top performers with co-marketing initiatives.
Metrics to Track:
  • Partner outreach sent: 15
  • Partnership acceptance rate (goal: 30%)
  • Client referrals per partner per month (goal: 2)
  • Partner-referred conversions (goal: 5 in 90 days)
Expected Milestones: 3 active consultant partners within 30 days, 10 partner-referred trials within 60 days, 5 paid conversions from partners within 90 days.
Do This Today: Search LinkedIn for "Fractional CTO" and "Engineering Consultant" and create a list of 10 people with 5k+ followers who actively post about scaling engineering teams. Export to spreadsheet with their names, companies, and follower counts.
The Strategy: Engineering leaders at scaling startups often hire consultants (ex-VPEs, fractional CTOs) to help them build processes and teams. These consultants need data to make recommendations but don't have analytics tools to provide to clients. Partner with 3-5 engineering enablement consultants to make DevAnalytics their default tool for client engagements. They get better insights for clients, you get distribution into their customer base.
The Exact Playbook:
Step 1: Identify 5 engineering enablement consultants who work with Series A-C startups. Search LinkedIn for "Fractional CTO", "Engineering Consultant", "Engineering Leadership Coach". Look for people with 10k+ followers and active posting about scaling teams.
Step 2: Reach out with a partnership proposition: "I noticed you work with engineering leaders at scaling startups. I built DevAnalytics to give teams visibility into productivity metrics. Would you be interested in a partnership where you get free access to offer to your clients, and in return, you promote it as your recommended analytics tool? You get better client outcomes, we get distribution."
Step 3: Create a "Consultant Partner Program" with: free DevAnalytics access for consultants + their clients, co-branded case studies, 20% revenue share on client conversions, joint webinar opportunities.
Step 4: Provide partners with enablement materials: pitch deck, demo scripts, ROI calculator, case studies, setup guides.
Step 5: Track partner activity and double down on top performers with co-marketing initiatives.
Metrics to Track:
  • Partner outreach sent: 15
  • Partnership acceptance rate (goal: 30%)
  • Client referrals per partner per month (goal: 2)
  • Partner-referred conversions (goal: 5 in 90 days)
Expected Milestones: 3 active consultant partners within 30 days, 10 partner-referred trials within 60 days, 5 paid conversions from partners within 90 days.
Do This Today: Search LinkedIn for "Fractional CTO" and "Engineering Consultant" and create a list of 10 people with 5k+ followers who actively post about scaling engineering teams. Export to spreadsheet with their names, companies, and follower counts.

Execution Priority

Execution Priority

Start with: Strategy 1 — Design Partnership Program
Why this order: Design partnerships validate product-market fit and generate case studies, which fuel Strategy 2 (content) and Strategy 3 (partner enablement). Starting with partnerships ensures you're building GTM on top of real customer stories, not hypothetical positioning. Launch Strategy 2 (content) once you have 2-3 case studies to reference (week 4-6). Launch Strategy 3 (consultant partnerships) once you have proven client outcomes to show partners (week 8-10). This sequence builds compounding momentum: partnerships → case studies → content → inbound leads + partner referrals.
Start with: Strategy 1 — Design Partnership Program
Why this order: Design partnerships validate product-market fit and generate case studies, which fuel Strategy 2 (content) and Strategy 3 (partner enablement). Starting with partnerships ensures you're building GTM on top of real customer stories, not hypothetical positioning. Launch Strategy 2 (content) once you have 2-3 case studies to reference (week 4-6). Launch Strategy 3 (consultant partnerships) once you have proven client outcomes to show partners (week 8-10). This sequence builds compounding momentum: partnerships → case studies → content → inbound leads + partner referrals.

Success Criteria

Success Criteria

You'll know these strategies are working when:
  • 5 active design partnerships + 3 case studies completed within 60 days (Strategy 1)
  • 150 email signups + 15 product trials from content within 60 days (Strategy 2)
  • 3 active consultant partners + 10 partner-referred trials within 90 days (Strategy 3)
If you don't see these results, revisit your ICP targeting or pivot to a different market segment (e.g., enterprise vs. startup, or different tech stack).

---
You'll know these strategies are working when:
  • 5 active design partnerships + 3 case studies completed within 60 days (Strategy 1)
  • 150 email signups + 15 product trials from content within 60 days (Strategy 2)
  • 3 active consultant partners + 10 partner-referred trials within 90 days (Strategy 3)
If you don't see these results, revisit your ICP targeting or pivot to a different market segment (e.g., enterprise vs. startup, or different tech stack).

---

Quality Checklist (Self-Verification)

质量检查表（自我验证）

Before finalizing output, verify ALL of the following:
在最终确定输出前，验证以下所有内容：

Pre-Execution Check

执行前检查

  • I read 
    FOUNDER_CONTEXT.md
    or gathered equivalent context from the user
  • I have enough information about: product, ICP, stage, competitive landscape, distribution model, resources available
  • If information was missing, I used AskUserQuestion to gather it (and didn't guess)
  • 我已阅读
    FOUNDER_CONTEXT.md
    或从用户处收集了等效背景信息
  • 我已获取足够的关于产品、ICP、阶段、竞争格局、分销模式、可用资源的信息
  • 若信息缺失，我已使用AskUserQuestion工具收集（而非猜测）

Analysis Check

分析检查

  • I assessed product-market fit status based on evidence, not assumptions
  • I identified the specific market wedge or entry point (not "everyone" or "small businesses")
  • I analyzed channel-product fit (where the ICP actually makes buying decisions)
  • I matched strategies to their current stage (pre-PMF, scaling, etc.)
  • I leveraged their unfair advantages (network, expertise, positioning)
  • 我已基于证据评估产品市场契合度状态，而非假设
  • 我已确定具体的市场突破口或切入点（而非"所有人"或"小企业"）
  • 我已分析渠道-产品契合度（ICP实际在哪里做出购买决策）
  • 我已根据他们的当前阶段（验证前、规模化等）匹配策略
  • 我已利用他们的不公平优势（人脉、专业知识、定位）

Strategy Selection Check

策略选择检查

  • All 3 strategies are ranked by fit and likelihood of success (highest first)
  • Each strategy attacks market entry from a different angle (no overlap)
  • Each strategy is feasible with their current resources
  • I'm personally confident each strategy will produce measurable traction
  • No generic GTM advice — every strategy is specific to this product and market
  • 所有3个策略均按契合度和成功可能性排序（最高优先级在前）
  • 每个策略从不同角度切入市场进入（无重叠）
  • 每个策略在其当前资源下可行
  • 我个人确信每个策略能带来可衡量的客户增长
  • 无通用GTM建议 — 每个策略均针对该产品和市场量身定制

Specificity Check

具体性检查

  • Every strategy uses actual product name, ICP details, and market specifics
  • Every playbook has step-by-step actions with concrete details
  • Metrics are specific and measurable
  • Expected milestones include concrete outcomes with timelines
  • "Do This Today" actions are completable in 30-60 minutes
  • 每个策略均使用实际产品名称、ICP细节和市场特定信息
  • 每个执行手册均包含带具体细节的分步行动
  • 指标具体且可衡量
  • 预期里程碑包含带时间线的具体成果
  • "立即行动"任务可在30-60分钟内完成

Writing Rules Compliance

写作规则合规性检查

  • Zero generic advice (no "build a website", "do content marketing", etc.)
  • Active voice throughout
  • No motivational fluff or filler
  • Every strategy passes the "would I bet money on this?" test
  • Strategies are adapted to business stage and type (B2B/B2C, pre-PMF/scaling, etc.)
  • 无通用建议（无"搭建网站"、"做内容营销"等）
  • 全程使用主动语态
  • 无励志空话或冗余内容
  • 每个策略均通过"我是否会押注该策略？"测试
  • 策略已根据业务阶段和类型（B2B/B2C、验证前/规模化等）适配

Output Check

输出检查

  • Output matches the Output Format exactly
  • All 3 strategies are complete with all sections filled
  • Execution Priority section explains the strategic sequencing
  • Success Criteria section has measurable outcomes with timelines
If ANY check fails → revise before presenting.
  • 输出完全符合输出格式要求
  • 所有3个策略均完整，所有部分已填充
  • 执行优先级部分解释了战略顺序
  • 成功标准部分包含带时间线的可衡量成果
若任何检查未通过 → 修订后再呈现。

Defaults & Assumptions

默认设置与假设

Use these unless the user overrides or context suggests otherwise:
  • Number of strategies: 3 (exactly)
  • Strategy focus: Start narrow, expand later (tight ICP, specific channel, clear positioning)
  • Stage: If unclear, assume post-MVP, validating product-market fit
  • Business type: If unclear, infer from FOUNDER_CONTEXT industry field
  • Budget: Assume limited unless stated otherwise (prioritize low-cost, high-leverage tactics)
  • Timeline: Assume user wants to see initial traction within 60-90 days
  • Metrics: Track both leading indicators (activities) and lagging indicators (conversions, revenue)
  • Tone: Direct, actionable, confident. No fluff.
Document any assumptions made at the top of the output.
除非用户覆盖或背景信息另有提示，否则使用以下设置：
  • 策略数量： 3个（恰好）
  • 策略重点： 先聚焦窄域，再逐步扩张（精准ICP、具体渠道、清晰定位）
  • 阶段： 若不明确，假设处于MVP后、验证产品市场契合度阶段
  • 业务类型： 若不明确，从FOUNDER_CONTEXT的行业字段推断
  • 预算： 假设预算有限，除非另有说明（优先选择低成本、高杠杆的策略）
  • 时间线： 假设用户希望在60-90天内看到初步客户增长
  • 指标： 同时跟踪领先指标（活动）和滞后指标（转化、收入）
  • 语气： 直接、可执行、自信。无空话。
在输出顶部记录所有做出的假设。