From gtm-skills
Defines B2B SaaS product marketing strategy: ICP, positioning (April Dunford), messaging, battlecards, sales enablement, TAM/SAM/SOM, PMF, growth loops, PR/FAQ, and context docs.
How this skill is triggered — by the user, by Claude, or both
Slash command
/gtm-skills:marketing-strategyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Read bootstrap context before asking questions: `strategy/brand.md` for brand, audience, offer, channels, tools, constraints, and metrics; `about/me.md` for personal voice; `content/ideas.md` and `content/calendar.md` for content planning. Use legacy product-marketing context files only as fallback. Save generated drafts to `content/<platform>/drafts/YYYY-MM-DD_short-topic-slug.md`, and route d...
Read bootstrap context before asking questions: strategy/brand.md for brand, audience, offer, channels, tools, constraints, and metrics; about/me.md for personal voice; content/ideas.md and content/calendar.md for content planning. Use legacy product-marketing context files only as fallback. Save generated drafts to content/<platform>/drafts/YYYY-MM-DD_short-topic-slug.md, and route durable learnings back to strategy/brand.md, about/me.md, or content/ideas.md.
This skill is self-contained for its frontmatter scope: use its local instructions, references, scripts, and assets as the playbook; ask only for missing task-specific inputs; hand off to adjacent skills instead of expanding scope; and return an actionable artifact, decision, plan, draft, or diagnostic.
Strategy and positioning layer for B2B SaaS — from product-market fit through competitive intelligence, sales enablement, and growth loops. For launch execution and channel strategy, see go-to-market-strategy.
VISION — Where are we going? (3–10 years)
STRATEGY — How will we win? (1–3 years)
ROADMAP — What are we building? (Quarters)
EXECUTION — How are we building? (Sprints)
Philosophy: Start with the customer problem, not your solution. Make trade-offs explicit — strategy is choosing what NOT to do. Systems over tactics: growth loops compound; growth hacks don't.
Level 0: Problem Fit → Real problem worth solving
Level 1: Solution Fit → Your solution addresses the problem
Level 2: PMF → Customers pull the product from you
Level 3: Scale Fit → Repeatable growth engine working
Level 4: Moat Fit → Defensible competitive advantage established
PMF validation signals: 5+ ICP customers, below-median sales cycle, above-median LTV, <5% churn, NPS 9–10.
| Metric | What It Means | How to Calculate |
|---|---|---|
| TAM | Everyone who could theoretically buy | Target customers × avg contract value |
| SAM | Those you can reach and serve | TAM × geographic/product constraints |
| SOM | Realistic near-term share | SAM × 1–5% penetration |
Validate top-down with bottom-up: (realistic customers × conversion rate × ACV). Gap >3x → revisit assumptions.
ICP Firmographics (Series A sweet spot): 50–5,000 employees, SaaS/Tech/Professional Services, $5M–$500M revenue.
Buyer Personas:
ICP Scoring (HubSpot): A (perfect fit) → D (poor fit). Focus acquisition on A/B, disqualify D.
Attribute → Value → Outcome (e.g., AI automation → eliminates manual entry → save 10 hrs/week)Value proposition: [Product] helps [Target] [Achieve Goal] by [Unique Approach]
Positioning template:
For [target customer]
Who [need/problem]
[Product] is a [category]
That [key benefit]
Unlike [competitors]
Our product [unique differentiator]
Messaging hierarchy: One-liner → 3–5 key benefits → feature/outcome pairs → proof points (logos, stats, case studies)
Write an internal press release BEFORE building. If you can't write a compelling press release, you don't have a compelling product.
Press Release structure (~1 page):
FAQ (External + Internal): External = questions real customers would ask. Internal = questions your skeptical colleagues would ask (the hard ones).
Anti-patterns: Writing the PR after building, solution-first thinking, vague customer definition ("everyone could use this"), skipping the hard internal FAQ, marketing hyperbole instead of specific measurable claims.
Tiers: Direct competitors | Indirect/adjacent | Status quo (spreadsheets, DIY, do nothing)
Intel sources: Product trials, website monitoring, customer interviews, Gong/Chorus recordings, G2 reviews, competitor job postings, industry reports.
Battlecard template (one per competitor):
Competitor | Strengths | Weaknesses | Our advantages
When we win | When we lose
Talk tracks for top 3 objections
Proof points (case studies, review comparisons, win rate)
Update monthly. Distribute via Notion/Confluence to Sales, CS, Product.
Win/Loss process: Interview within 2 weeks of close. Track in HubSpot: reason, competitor, price factor, product gap. Share monthly insights report with product and sales.
Competitive moat types:
| Moat | Description | Examples |
|---|---|---|
| Network Effects | Product improves as more users join | Slack, LinkedIn |
| Switching Costs | Painful to leave | Salesforce, Workday |
| Data Advantages | Proprietary data improves product | Google, Waze |
| Scale Economies | Cost advantages at scale | AWS, Stripe |
| Brand | Trust and recognition | Apple, Notion |
| Loop | Mechanism | Key Metric |
|---|---|---|
| Viral | Users invite users | K-factor |
| Content | Users create discoverable content | Indexed pages |
| Paid | Revenue funds acquisition | CAC payback |
| SEO | Content ranks, drives traffic | Organic traffic |
| Motion | Best For | Key Lever |
|---|---|---|
| Freemium | Simple products, network effects | Free → paid conversion |
| Free Trial | Complex products | Trial conversion rate |
| Reverse Trial | High-value products | Premium feature discovery |
| Usage-Based | API/variable consumption | Usage expansion |
A good North Star measures value delivered, is a leading indicator of revenue, reflects product strategy, and is actionable by the product team. Examples: Slack → DAU sending messages; Airbnb → Nights booked
AARRR Funnel: Acquisition → Activation → Retention → Revenue → Referral. Fix activation before optimizing acquisition — don't fill a leaky bucket.
| Model | Pros | Cons |
|---|---|---|
| SaaS | Predictable, high LTV | Long sales cycle |
| Freemium | Low CAC, viral | Free → paid conversion hard |
| Usage-Based | Scales with customer | Revenue unpredictability |
| Marketplace | Network effects | High volume needed |
Unit economics:
LTV = (Monthly Revenue × Gross Margin %) ÷ Monthly Churn Rate
Target: LTV > 3x CAC, CAC payback < 18 months
Core assets: Sales deck (15 slides, visual-first) · One-pagers (product, competitive, case study, pricing) · Battlecards · Demo script (discover → show → Q&A → next step) · Email sequences · ROI calculator
Enablement cadence:
PMM handoffs: Demand Gen (2-week lead time) | Sales (48-hr SLA on competitive questions) | Product (weekly sync) | CS (1-week for launch enablement)
Create strategy/brand.md capturing:
Auto-draft approach: Study the repo (README, landing pages, marketing copy), draft V1, then ask: "What needs correcting? What's missing?"
All other marketing skills reference this file automatically.
| KPI | Target |
|---|---|
| Feature adoption (90 days) | >40% |
| Win rate (competitive deals) | >30% |
| Sales velocity | -20% YoY |
| Deal size (ACV) | +25% YoY |
| Launch ROMI | 3:1 (pipeline : spend) |
QBR slide structure: Executive summary → KPI dashboard (target vs. actual) → what worked / what didn't → next quarter priorities + budget ask
npx claudepluginhub manojbajaj95/claude-gtm-plugin --plugin gtm-skillsAnalyzes business context to deliver 3 tailored go-to-market strategies based on product stage, market clarity, and distribution channels.
Provides GTM playbooks for product launches, positioning with Dunford framework, messaging hierarchies, and strategy types like PLG/sales-led. Use for market entry or rebranding.
Generates go-to-market strategies for product launches covering marketing channels, messaging, success metrics, and phased timelines. Use for new product planning or market entry.