OverviewHistoryStatsSecurity
npx skills add ...
Documentation
SKILL.md
npx skills add ognjengt/founder-skills --skill go-to-market-plan
Analyzes the founder's business context to deliver 3 best go-to-market strategies tailored to their current stage, product, and market. Asks up to 10 diagnostic questions when needed to understand product readiness, target market clarity, competitive positioning, and distribution channels. Use when user needs go-to-market strategy, launch planning, market entry strategy, or actionable GTM roadmap.
npx skills add ognjengt/founder-skills --skill go-to-market-plan
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.
Check $ARGUMENTS first to determine execution mode:
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.
Proceed immediately to Task Execution (skip the "loaded" message).
When user requirements are available (either from initial $ARGUMENTS or follow-up message):
Check if FOUNDER_CONTEXT.md exists in the project root.
Evaluate whether you have enough information to produce high-confidence, actionable go-to-market strategies:
Required information to proceed without questions:
If you have enough context: Proceed directly to Step 4.
If critical information is missing: Proceed to Step 3.
Use the AskUserQuestion tool to gather missing information. Ask between 3-10 questions based on what's needed:
Core GTM questions:
Context-specific questions:
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.
Based on the context gathered, analyze:
Critical analysis principles:
Create exactly 3 GTM strategies, ranked by fit and impact:
Selection criteria:
For each strategy, write:
Part A — The Strategy (What & Why)
Part B — The Exact Playbook (How)
Part C — First Action (Do This Today)
Hard constraints. No interpretation.
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."
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
Before finalizing ANY strategy, ask:
Example:
Before finalizing output, verify ALL of the following:
FOUNDER_CONTEXT.md or gathered equivalent context from the userIf ANY check fails → revise before presenting.
Use these unless the user overrides or context suggests otherwise:
Document any assumptions made at the top of the output.
## 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:
---
### 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.
---
### 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.
---
### 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.
---
## 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.
---
## 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).