gtm-strategy
When the user wants to plan go-to-market strategy, GTM framework, or market entry. Also use when the user mentions "GTM," "go-to-market," "market entry," "new market," "repositioning," "PLG," "sales-led," "product-led," "marketing-led," "ICP," "buyer persona," "GTM motion," or "market expansion." For launch checklist, use product-launch.
Best use case
gtm-strategy is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
When the user wants to plan go-to-market strategy, GTM framework, or market entry. Also use when the user mentions "GTM," "go-to-market," "market entry," "new market," "repositioning," "PLG," "sales-led," "product-led," "marketing-led," "ICP," "buyer persona," "GTM motion," or "market expansion." For launch checklist, use product-launch.
Teams using gtm-strategy 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/gtm/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How gtm-strategy Compares
| Feature / Agent | gtm-strategy | 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?
When the user wants to plan go-to-market strategy, GTM framework, or market entry. Also use when the user mentions "GTM," "go-to-market," "market entry," "new market," "repositioning," "PLG," "sales-led," "product-led," "marketing-led," "ICP," "buyer persona," "GTM motion," or "market expansion." For launch checklist, use product-launch.
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
# Strategies: Go-to-Market Guides go-to-market (GTM) strategy—the blueprint for launching or repositioning a product that aligns product, marketing, sales, and customer success around reaching and winning target customers. Organizations with documented GTM see ~10% higher success rates and 3× revenue growth; ~72% of B2B miss GTM targets in year 1, often due to execution gaps. Use this skill when planning GTM for product launch, new market entry, repositioning, or feature launch. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## GTM Scenarios | Scenario | Scope | Use | |----------|-------|-----| | **Product launch** | New product to market | Full GTM; see **product-launch** for launch execution | | **New market entry** | New geography or segment | Full GTM; different buying behaviors, competitors, regulations | | **Repositioning** | Shift who you serve, what you solve | Messaging, ICP, channel alignment; not just rebrand | | **Feature launch** | New capability in existing product | Tiered by impact; T1 (revenue) = full planning; T2/T3 = lighter | **GTM vs product launch**: GTM is the strategy; product launch is the execution phase. GTM applies to multiple scenarios—not just new products. ## GTM Modes | Mode | When to Use | ACV | Buyer | |------|-------------|-----|-------| | **Product-led (PLG)** | Value in minutes; self-evaluate; simple adoption | <$10K | Buyer = end user | | **Sales-led (SLG)** | Multi-stakeholder; complex procurement; implementation | >$25K | Enterprise; negotiation | | **Marketing-led (MLG)** | Content, SEO, paid drive awareness; market education | Varies | Demand gen focus | | **Hybrid** | PLG for acquisition; sales for expansion | Common | Self-serve → sales handoff | **Decision factors**: ACV, product complexity, buyer profile, how customers want to buy. Target LTV:CAC ≥3:1; CAC payback <12 months. ## 90-Day Execution Framework | Phase | Weeks | Focus | |-------|-------|-------| | **Market analysis** | 1–3 | Validate demand; competitive landscape; TAM; buying signals | | **Strategy design** | 4–6 | ICP, personas; positioning; pricing; GTM mode; channels | | **Execution build** | 7–9 | Messaging, content, sales playbook; tech stack | | **Launch & iterate** | 10–12 | Go live; measure; iterate | **Key**: Connect plan to real buying activity within 90 days—not disconnected strategy documents. ## ICP vs Buyer Persona | Type | Level | Defines | |------|-------|---------| | **ICP** | Company | Which organizations deliver best unit economics; firmographics (industry, size, revenue), technographics, problem intensity | | **Buyer persona** | Individual | Decision-makers within target companies; roles, goals, pain points, objections, preferred channels | **ICP impact**: Defined ICPs → ~68% higher conversion, ~50% lower CAC, ~30% shorter sales cycles. Include negative profiles (explicit disqualifiers) to protect pipeline quality. ## Market Analysis | Element | Purpose | |---------|---------| | **TAM** | Total addressable market; named account lists; primary TAM, serviceable TAM, accounts with buying signals | | **Competitive landscape** | Customer bases, strengths, weaknesses, positioning claims | | **Buying patterns** | Replace assumptions with data; customer pain points; decision criteria | ## Enterprise / High-ACV Challenges | Challenge | Mitigation | |-----------|------------| | **Customization** | Product modularity; professional services; clear scope | | **Data security / private deployment** | On-prem or private cloud; compliance; security certifications | | **Procurement cycles** | Multi-stakeholder alignment; champion building; long sales cycles | | **Buy vs SaaS** | Total cost of ownership; flexibility; ongoing value | **Use**: When GTM targets enterprise or high-ACV—expect longer cycles, procurement, and security requirements. ## New Market Entry ~70% of international market entries fail within two years—often from overestimating demand, underestimating execution, spreading resources thin. | Entry model | Trade-off | |-------------|-----------| | **Organic expansion** | High control; slower; capital-intensive | | **Strategic partnerships** | Faster access; shared risk; reduced control | | **M&A / Acquisition** | Immediate presence; high integration risk | | **Asset-light** (EOR, outsourcing) | Fastest; minimal upfront; market testing | | **Pilot testing** | Lowest commitment; validation | **Critical**: Domestic playbook won't transfer. Buying behaviors vary (self-service US vs consultation-heavy Europe vs relationship-driven APAC); competitive landscapes shift; regulatory complexity multiplies (GDPR, data localization). ## Repositioning **Repositioning** = Strategic shift in who you serve, what problem you solve, where you play. **Rebranding** = Visual/verbal expression (logo, voice). Repositioning ≠ rebrand. | When to reposition | Avoid | |--------------------|-------| | Moving upmarket (SMB → enterprise) | Quick fix for missed quarters | | New geography with different dynamics | Leadership boredom | | ICP fundamentally changed | | | Major pivot, launch, or acquisition | | **Success factors**: Research-driven (customer discovery, market analysis); cross-functional alignment (sales, marketing, product, clinical); sharp differentiation. ## Cross-Functional Alignment - **RACI**: Responsible, Accountable, Consulted, Informed—clarify roles across teams - **Shared timelines, tools, accountability** - **Consistent messaging** across all channels ## Output Format - **Scenario** (product launch, new market, repositioning, feature) - **GTM mode** (PLG/SLG/MLG/Hybrid) recommendation - **90-day** phase plan - **ICP** and **persona** (or link to project-context) - **Market analysis** checklist - **Launch** execution → see **product-launch** ## Related Skills - **product-launch**: Launch execution; channels, timeline, checklist; implements GTM for product launch - **pmf-strategy**: Validate PMF before scaling GTM - **cold-start-strategy**: First users; differs from full GTM (0→1 vs commercialization) - **rebranding-strategy**: Domain change, 301, announcement; when repositioning includes rebrand - **localization-strategy**: New market entry; i18n, multilingual - **paid-ads-strategy**: Ad channel for GTM - **website-structure**: Pages needed for GTM - **branding**: Positioning, differentiation; GTM messaging foundation
Related Skills
seo-strategy
When the user wants to plan SEO strategy, prioritize SEO work, or understand the SEO workflow. Also use when the user mentions "SEO strategy," "SEO plan," "SEO roadmap," "SEO priority," "SEO audit," "SEO workflow," "where to start SEO," "SEO approach," "organic growth strategy," "why SEO," "SEO value," or "search strategy." For technical/crawl audit execution, use seo-audit. For keyword research, use keyword-research. For AI search visibility, use generative-engine-optimization.
retention-strategy
When the user wants to reduce churn, improve customer retention, or plan lifecycle marketing. Also use when the user mentions "retention," "churn," "customer lifecycle," "churn prevention," "at-risk customers," or "loyalty program." For lifecycle, use growth-funnel.
pmf-strategy
When the user wants to validate product-market fit, measure PMF, or plan before scaling. Also use when the user mentions "PMF," "product-market fit," "product market fit," "Sean Ellis test," "very disappointed," "vitamin vs painkiller," "PMF validation," "premature scaling," or "validate before scale." For GTM after validation, use gtm-strategy.
indie-hacker-strategy
When the user wants indie hacker or bootstrapping founder strategy—growth, channels, Build in Public, or solo founder tactics. Also use when the user mentions "indie hacker," "indie developer," "bootstrapping," "bootstrapped founder," "solo founder," "Build in Public," "scratch your own itch," "Micro-SaaS," "first 100 users," or "solo company." For cold start, use cold-start-strategy.
cold-start-strategy
When the user wants to plan cold start, get first users, or launch a new product with zero traction. Also use when the user mentions "cold start," "cold start problem," "first users," "seed users," "finding users," "finding early users," "Fiverr Upwork," "comment outreach," "Twitter search users," "product launch strategy," "0 to 1 growth," "early-stage acquisition," "launch channels," "get first customers," "Product Hunt launch," "AppSumo," "LTD," "indie hacker," "bootstrapping," or "solo founder." For directory listing copy and submissions, use directory-submission. For Product Hunt day-of execution, use product-hunt-launch. For GTM motion design, use gtm-strategy.
pricing-strategy
When the user wants to plan, design, or optimize pricing strategy and structure. Also use when the user mentions "pricing strategy," "pricing model," "pricing tiers," "freemium," "value-based pricing," "anchoring," "price structure," or "monetization strategy." For pricing page, use pricing-page-generator.
discount-marketing-strategy
When the user wants to plan, implement, or optimize discount and promotional pricing strategy. Also use when the user mentions "discount strategy," "promo code," "coupon," "redeem code," "lifetime deal," "LTD," "AppSumo," "Black Friday," "Cyber Monday," "BFCM," "seasonal sale," or "promotional pricing." For pricing page, use pricing-page-generator.
paid-ads-strategy
When the user wants to plan paid ads strategy, allocate ad budget, or choose paid channels. Also use when the user mentions "paid ads," "paid media," "PPC," "SEM," "web ads," "app ads," "TV ads," "CTV," "OOH," "banner ads," "ad network," "ad alliance," "Taaft ads," "Shopify App Store ads," "Google Ads," "Meta Ads," "PMF testing," "PMF validation," "test product-market fit with ads," "ad spend," "ad budget," "ROAS," "paid acquisition," "Quality Score," or "ad-to-page alignment." For Google Ads execution, use google-ads. For Meta Ads execution, use meta-ads. For landing page alignment, use landing-page-generator.
open-source-strategy
When the user wants open source strategy, OSS commercialization, or open source growth. Also use when the user mentions "open source strategy," "OSS strategy," "open source commercialization," "open source to paid," "open core," "COSS," "commercial open source," "GitHub stars strategy," "DevHunt," "open source marketing," "open source growth," "Llama," "Dify," "Cursor," "open source business model," or "developer tools directory." For GitHub tactics, use github.
localization-strategy
When the user wants to plan or implement localization strategy for multilingual and global growth. Also use when the user mentions "localization," "multilingual," "i18n," "global expansion," "market entry," "localization strategy," "hreflang," "multi-language SEO," or "international SEO." For translation workflow, glossary, and style guide, use translation.
rebranding-strategy
When the user wants to plan or execute a rebrand—domain change, 301 redirects, migration, or announcement. Also use when the user mentions "rebranding," "rebrand," "domain change," "domain migration," "301 redirect," "change domain name," "rebrand announcement," "social media rebrand," "brand launch," or "domain redirect." For domain choice, use domain-selection.
content-strategy
When the user wants to plan content for SEO, create content calendar, or build topic clusters. Also use when the user mentions "content strategy," "content plan," "topic clusters," "pillar content," "pillar page," "cluster articles," "editorial calendar," "content hub," "content planning," "content clusters," "topic cluster strategy," "content strategy for SEO," or "content calendar." For editorial mix, use content-marketing.