Go-to-Market — Launch, Distribute, and Grow
## Overview
Best use case
Go-to-Market — Launch, Distribute, and Grow is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
## Overview
Teams using Go-to-Market — Launch, Distribute, and Grow should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/go-to-market/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Go-to-Market — Launch, Distribute, and Grow Compares
| Feature / Agent | Go-to-Market — Launch, Distribute, and Grow | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
## Overview
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Go-to-Market — Launch, Distribute, and Grow ## Overview Go-to-market strategy, helping product teams plan launches, choose distribution channels, design growth loops, define ideal customer profiles, and execute GTM motions. This skill applies frameworks for product-led growth (PLG), sales-led growth, community-led growth, and viral loops. ## Instructions ### GTM Motion Selection ```markdown ## Choose Your GTM Motion ### Product-Led Growth (PLG) Users discover, try, and buy the product without talking to sales. **Best for**: Developer tools, productivity software, SMB SaaS **Revenue model**: Freemium or free trial → self-serve upgrade **Key metrics**: Signup → Activation → Conversion rate **Examples**: Slack, Notion, Figma, Vercel, Stripe **Requirements**: - Product delivers value before payment (free tier or trial) - Low time-to-value (< 10 minutes to first "wow") - Product can self-explain (no complex configuration) - Viral or network effects (value increases with more users) ### Sales-Led Growth (SLG) Sales team drives revenue through demos, proposals, and contracts. **Best for**: Enterprise, complex products, high ACV (>$25K/year) **Revenue model**: Annual contracts, custom pricing **Key metrics**: Pipeline → Demo → Proposal → Close rate **Examples**: Salesforce, Workday, Snowflake **Requirements**: - Complex buying process (multiple stakeholders) - High contract value justifies sales cost - Product needs customization or integration ### Community-Led Growth (CLG) Community creates awareness, education, and trust before purchase. **Best for**: Developer tools, open-source, creative tools **Revenue model**: Open-core, enterprise features, support **Key metrics**: Community members → Contributors → Enterprise leads **Examples**: Supabase, Vercel, Hashicorp, dbt **Requirements**: - Target audience gathers in communities (Discord, GitHub, Reddit) - Product benefits from shared knowledge - Team can invest in content and community management ### Hybrid (Most Common at Scale) Start with one motion, add others as you scale. Typical evolution: PLG → PLG + Sales → PLG + Sales + Partners ``` ### Ideal Customer Profile (ICP) ```markdown ## Define Your Ideal Customer Profile ### ICP Framework Your ICP is the customer segment where you have the highest win rate, shortest sales cycle, lowest churn, and highest expansion. **Company characteristics**: - Industry: SaaS, fintech, e-commerce, healthcare... - Size: 10-50 employees, $1M-$10M ARR - Stage: Seed, Series A/B, growth stage - Tech stack: Uses React, AWS, Stripe... - Pain trigger: Scaling from 5 to 20 engineers **User characteristics (within the company)**: - Role: Engineering Manager, CTO, DevOps Lead - Seniority: Mid-level decision-maker, not C-suite - Daily frustration: "I spend 3 hours/week on deployment issues" - Current solution: Manual scripts, Jenkins **Behavioral signals (how to identify them)**: - Hiring for DevOps roles (LinkedIn job posts) - Growing engineering team (crunchbase, github activity) - Active in relevant communities (DevOps subreddit, KubeCon) - Using complementary tools (Kubernetes, Terraform) ### Anti-ICP (Who to Avoid) - Enterprise with 12-month procurement cycles (if you're early stage) - Companies with in-house solutions they're invested in - Price-sensitive customers who will churn at renewal ``` ### Launch Playbook ```markdown ## Plan a Product Launch ### Pre-Launch (4-2 weeks before) **Build anticipation**: - Waitlist landing page (collect emails) - Teaser content: "We're building something for [audience]" - Early access for design partners (5-10 customers who co-build with you) - Seed community channels (Discord, Slack) **Prepare assets**: - Product demo video (90 seconds, show the aha moment) - Launch blog post (problem → solution → how it works → CTA) - Social media assets (Twitter thread, LinkedIn post, short video) - Press outreach (if relevant): Product Hunt, tech media, newsletters **Technical prep**: - Load testing (can you handle 10x normal traffic?) - Monitoring and alerting (SigNoz, Sentry) - Support channels ready (Intercom, Discord) ### Launch Day **Sequence matters**: 1. **Early morning**: Product Hunt launch (if applicable) 2. **Morning**: Blog post goes live, email to waitlist 3. **Mid-morning**: Founder posts on Twitter/LinkedIn (personal > company) 4. **Afternoon**: Engage with comments, questions, feedback 5. **Evening**: Thank early users, share metrics with team **Amplification**: - Ask design partners to share their experience - Respond to every comment (builds trust and algorithm signal) - Cross-post to relevant subreddits, HN, Indie Hackers - Newsletter shoutouts (partner with complementary tools) ### Post-Launch (1-4 weeks after) **Capture momentum**: - Share launch metrics publicly (transparency builds trust) - Write "lessons learned" post (content from the launch itself) - Follow up with every waitlist signup - Collect testimonials from early users **Measure**: - Signups vs goal - Activation rate (did they actually use it?) - Source attribution (where did converting users come from?) - Feedback themes (what do people love? what's confusing?) ``` ### Growth Loops ```markdown ## Design Growth Loops A growth loop is a system where output from one cycle feeds the next. Unlike funnels (linear), loops compound. ### User-Generated Content Loop User creates content → Content indexed by Google → New user discovers content → New user creates content Example: Stack Overflow, Reddit, Pinterest ### Viral Invitation Loop User gets value → User invites teammate → Teammate gets value → Teammate invites... Example: Slack, Dropbox, Notion Key metric: Viral coefficient (invites per user × conversion rate) If >1.0: exponential growth. If 0.3-0.5: strong assist channel. ### Paid Loop (Reinvestment) Revenue from customer → Reinvest in ads → Acquire new customer → Revenue... Example: Dollar Shave Club Key: LTV > CAC with enough margin to reinvest ### Product-Led Sales Loop Free user adopts product → Usage grows → Hits limit → Sales contacts for upgrade → Revenue → Fund product improvements → More free users Example: Slack, Figma ### Community Loop Expert shares knowledge → Community grows → Attracts more experts → More knowledge shared Example: dbt, Supabase, Vercel ``` ## Examples ### Example 1: Creating a gtm motion selection for a new product **User request:** ``` We're launching a project management tool for remote design teams. Help me create a gtm motion selection. ``` The agent applies the Go To Market framework, asking clarifying questions about target audience, market positioning, and business model. It produces a structured deliverable with specific, actionable recommendations tailored to the design-tools market, including competitive positioning and key metrics to track. ### Example 2: Reviewing and improving an existing GTM strategy **User request:** ``` Here's our current go-to-market plan for our B2B analytics platform. Review it and identify gaps. ``` The agent analyzes the existing GTM plan against best practices, checks whether the ICP is specific enough, validates channel choices against the target audience, reviews the pricing-value alignment, and identifies missing elements like activation metrics or competitive positioning. It provides specific suggestions with reasoning, not generic advice. ## Guidelines 1. **ICP before channels** — Define exactly who you're targeting before choosing how to reach them; channel strategy follows ICP 2. **One GTM motion first** — Master PLG or SLG before going hybrid; splitting focus early kills both motions 3. **Launch is not a one-day event** — A launch is a 6-week campaign: 2 weeks building anticipation, launch day, 3 weeks of follow-up 4. **Growth loops > funnels** — Funnels are linear and require constant input; loops compound and create sustainable growth 5. **PLG requires low time-to-value** — If users can't get value in 10 minutes without help, PLG won't work; invest in onboarding 6. **Design partners for credibility** — Launch with 5-10 customers who helped build the product; their testimonials are your best marketing 7. **Channel-market fit** — Not every channel works for every product; find the 1-2 channels that work and double down before diversifying 8. **Measure by cohort** — Compare launch week cohort retention to organic cohorts; launch traffic often has different quality
Related Skills
tracking-token-launches
Track new token launches across DEXes with risk analysis and contract verification. Use when discovering new token launches, monitoring IDOs, or analyzing token contracts. Trigger with phrases like "track launches", "find new tokens", "new pairs on uniswap", "token risk analysis", or "monitor IDOs".
setting-up-distributed-tracing
Execute this skill automates the setup of distributed tracing for microservices. it helps developers implement end-to-end request visibility by configuring context propagation, span creation, trace collection, and analysis. use this skill when the user re... Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
scorecard-marketing
Build quiz and assessment funnels that generate qualified leads at 30-50% conversion. Use when the user mentions "lead magnet", "quiz funnel", "assessment tool", "lead generation", or "score-based segmentation". Covers question design, dynamic results by tier, and automated follow-up sequences. For landing page conversion, see cro-methodology. For full marketing plans, see one-page-marketing. Trigger with 'scorecard', 'marketing'.
scanning-market-movers
Detect significant price movements and unusual volume across crypto markets. Calculates significance scores combining price change, volume ratio, and market cap. Use when tracking market movers, finding gainers/losers, or detecting volume spikes. Trigger with phrases like "scan market movers", "top gainers", "biggest losers", "volume spikes", "what's moving", "find pumps", or "market scan".
one-page-marketing
Build a complete marketing plan covering the full customer journey from stranger to raving fan. Use when the user mentions "marketing plan", "target market", "USP", "lead nurture", "customer lifetime value", or "referral program". Covers the PVP Index, channel selection, and advocacy systems. For brand messaging, see storybrand-messaging. For conversion optimization, see cro-methodology. Trigger with 'one', 'page', 'marketing'.
marketplace-manager
Automatically manages marketplace catalog updates, syncs marketplace.json, and handles plugin distribution when user mentions marketplace update, sync catalog, or add to marketplace. Specific to claude-code-plugins two-catalog system.
distributed-training-setup
Distributed Training Setup - Auto-activating skill for ML Training. Triggers on: distributed training setup, distributed training setup Part of the ML Training skill category.
analyzing-market-sentiment
Analyze cryptocurrency market sentiment using Fear & Greed Index, news analysis, and market momentum. Use when gauging overall market mood, checking if markets are fearful or greedy, or analyzing sentiment for specific coins. Trigger with phrases like "analyze crypto sentiment", "check market mood", "is the market fearful", "sentiment for Bitcoin", or "Fear and Greed index".
gtm-product-led-growth
Build self-serve acquisition and expansion motions. Use when deciding PLG vs sales-led, optimizing activation, driving freemium conversion, building growth equations, or recognizing when product complexity demands human touch. Includes the parallel test where sales-led won 10x on revenue.
gtm-0-to-1-launch
Launch new products from idea to first customers. Use when launching products, finding early adopters, building launch week playbooks, diagnosing why adoption stalls, or learning that press coverage does not equal growth. Includes the three-layer diagnosis, the 2-week experiment cycle, and the launch that got 50K impressions and 12 signups.
Nightmarket — API Marketplace for AI Agents
Nightmarket is a marketplace where AI agents discover and pay for third-party API services. Every call settles on-chain in USDC on Base. No API keys, no subscriptions — just make an HTTP request, pay, and get your response.
analyzing-marketing-campaign
Analyze weekly marketing campaign performance data across channels. Use when analyzing multi-channel digital marketing data to calculate funnel metrics (CTR, CVR) and compare to benchmarks, compute cost and revenue efficiency metrics (ROAS, CPA, Net Profit), or get budget reallocation recommendations based on performance rules.