gtm-strategy▌
kostja94/marketing-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
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.
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
How to use gtm-strategy on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add gtm-strategy
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches gtm-strategy from GitHub repository kostja94/marketing-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate gtm-strategy. Access the skill through slash commands (e.g., /gtm-strategy) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★58 reviews- ★★★★★Chaitanya Patil· Dec 16, 2024
gtm-strategy fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Kaira Sanchez· Dec 16, 2024
gtm-strategy fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Olivia Menon· Dec 12, 2024
We added gtm-strategy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Hana White· Dec 8, 2024
We added gtm-strategy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Kaira Li· Dec 4, 2024
Keeps context tight: gtm-strategy is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Kiara Martin· Nov 27, 2024
Keeps context tight: gtm-strategy is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Kiara Liu· Nov 23, 2024
We added gtm-strategy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Piyush G· Nov 7, 2024
gtm-strategy is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Omar Thomas· Nov 7, 2024
gtm-strategy is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Rahul Santra· Nov 3, 2024
gtm-strategy has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 58