marketing-strategy-pmm

49
7
Source

Product marketing, positioning, GTM strategy, and competitive intelligence. Includes ICP definition, April Dunford positioning methodology, launch playbooks, competitive battlecards, and international market entry guides. Use when developing positioning, planning product launches, creating messaging, analyzing competitors, entering new markets, enabling sales, or when user mentions product marketing, positioning, GTM, go-to-market, competitive analysis, market entry, or sales enablement.

Install

mkdir -p .claude/skills/marketing-strategy-pmm && curl -L -o skill.zip "https://mcp.directory/api/skills/download/671" && unzip -o skill.zip -d .claude/skills/marketing-strategy-pmm && rm skill.zip

Installs to .claude/skills/marketing-strategy-pmm

About this skill

Marketing Strategy & Product Marketing

Expert Product Marketing playbook for Series A+ startups expanding internationally with hybrid PLG/Sales-Led motion.

Keywords

product marketing, positioning, GTM, go-to-market strategy, competitive analysis, competitive intelligence, battlecards, ICP, ideal customer profile, messaging, value proposition, product launch, market entry, international expansion, sales enablement, win loss analysis, PMM, product marketing manager, market positioning, competitive landscape, sales training

Role Coverage

This skill serves:

  • Product Marketing Manager (PMM) - Positioning, messaging, competitive intel, launches
  • Head of Marketing - Strategy, budget, org design, pipeline targets
  • Head of Growth - Experimentation, activation, retention, growth loops
  • CMO/VP Marketing - Executive strategy, board reporting, team leadership

Core KPIs by Role

PMM: Product adoption rate, win rate vs. competitors, sales velocity, launch impact metrics, competitive win rate, deal size growth

Head of Marketing: Marketing-sourced pipeline $, CAC/LTV ratio, ROMI (3:1+ target), brand awareness lift, market share growth

Head of Growth: Activation rate, WAU/MAU, conversion rates across funnel, payback period, viral coefficient (PLG)

CMO: Revenue growth %, pipeline coverage (3-4x), team productivity, budget efficiency, NPS/brand health

Tech Stack Integration

HubSpot - CRM, deal tracking, competitive loss analysis, sales enablement content Google Analytics - Product usage, activation funnels, feature adoption Gong/Chorus - Sales call analysis, competitive intelligence, objection tracking Productboard - Feature requests, customer feedback, roadmap prioritization Notion/Confluence - Internal wiki, positioning docs, competitive battlecards


1. Strategic Foundation

1.1 Company Strategy Framework (Series A Context)

Current State Analysis:

Stage: Series A
Funding: $5-15M raised
Team Size: 20-50 people
Revenue: $1-5M ARR
Market Position: Challenger/Niche leader
Growth Rate Target: 3-5x YoY

Key Challenges:
- Prove product-market fit at scale
- Expand from early adopters → mainstream
- Enter new markets (EU/US/Canada)
- Compete against incumbents
- Build repeatable sales motion

Strategic Priorities (in order):

  1. Nail positioning - Clear, differentiated value prop
  2. Scale acquisition - Repeatable, efficient channels
  3. Prove retention - Product stickiness, expansion revenue
  4. Expand markets - Geographic + vertical expansion
  5. Build brand - Awareness, trust, category leadership

1.2 ICP (Ideal Customer Profile) Definition

B2B SaaS ICP Framework:

Firmographics:

  • Company size: 50-5000 employees (Series A sweet spot)
  • Industry: SaaS, Tech, Professional Services
  • Geography: US, Canada, UK, Germany, France (prioritize by TAM)
  • Revenue: $5M-$500M annual
  • Funding stage: Seed to Growth (avoid pre-product)

Technographics:

  • Tech stack: Modern (cloud-first, API-driven)
  • Maturity: Growing fast, willing to adopt new tools
  • Existing tools: [List competitors + complementary products]
  • Integration needs: Must integrate with [Salesforce, Slack, etc.]

Psychographics:

  • Pain level: 7-10/10 (acute pain, not nice-to-have)
  • Buyer motivation: Efficiency, cost savings, revenue growth
  • Decision process: 2-6 month sales cycle
  • Risk tolerance: Early majority (not bleeding edge)

Buyer Personas (3-5 personas max):

Primary: Economic Buyer (signs contract)

  • Title: VP, Director, Head of [Department]
  • Goals: ROI, team productivity, cost reduction
  • Fears: Implementation failure, team resistance, budget waste
  • Messaging: Business outcomes, ROI, case studies

Secondary: Technical Buyer (evaluates product)

  • Title: Senior Engineer, Architect, Tech Lead
  • Goals: Solves technical problem, easy integration
  • Fears: Technical debt, vendor lock-in, poor support
  • Messaging: Technical capabilities, architecture, security

User/Champion (advocates internally)

  • Title: Manager, Team Lead, Power User
  • Goals: Makes their job easier, team loves it
  • Fears: Learning curve, change management
  • Messaging: UX, ease of use, quick wins

ICP Validation Checklist:

  • 5+ paying customers match this profile
  • Fastest sales cycles (< median time to close)
  • Highest LTV (> median customer value)
  • Lowest churn (< 5% annual)
  • Strong product engagement (daily/weekly usage)
  • Referenceable (NPS 9-10, willing to do case studies)

HubSpot ICP Tracking:

  • Create "ICP Fit" property: A (perfect), B (good), C (okay), D (poor)
  • Score based on firmographics, engagement, product usage
  • Report: Win rate by ICP score, pipeline by ICP score
  • Action: Focus acquisition on ICP A/B, nurture C, disqualify D

1.3 Market Segmentation Strategy

Segmentation Dimensions:

By Company Size (recommend starting with one):

  • SMB (10-200 employees) - Self-serve PLG, low touch, $100-$2k ACV
  • Mid-Market (200-2000 employees) - Hybrid, inside sales, $2k-$50k ACV
  • Enterprise (2000+ employees) - Sales-led, field sales, $50k+ ACV

By Vertical (choose 2-3 focus verticals):

  • Horizontal: Broad appeal (e.g., project management for any industry)
  • Vertical: Industry-specific (e.g., healthcare CRM, fintech compliance)
  • Approach: Start horizontal, add verticals as you scale

By Use Case (messaging varies):

  • Use Case A: [e.g., Team collaboration]
  • Use Case B: [e.g., Client management]
  • Use Case C: [e.g., Project tracking]
  • Each use case = different landing page, messaging, case studies

By Geography (Series A focus):

  • US/Canada: Largest TAM, fastest sales cycles, highest willingness to pay
  • UK: English-speaking, gateway to EU, similar buying behavior to US
  • Germany: Largest EU economy, high data privacy standards (GDPR leader)
  • France: Second largest EU market, localization critical
  • Nordics: High tech adoption, English proficiency, smaller markets

Segmentation Priority Matrix:

Segment: US Mid-Market SaaS Companies (200-2000 employees)
Priority: 1 (Highest)
Rationale:
  - Largest TAM ($5B)
  - Fastest sales cycle (60 days avg)
  - Highest win rate (35%)
  - Strong product fit (use cases align)
  - Existing customer base (50% of customers)
Budget Allocation: 50% of marketing spend

2. Positioning & Messaging

2.1 Positioning Framework (April Dunford Method)

Step 1: List Your True Competitive Alternatives

Not just direct competitors - what would customers do if your product didn't exist?

Alternatives:
1. Competitor A (direct)
2. Competitor B (direct)
3. Spreadsheets + email (status quo)
4. Build in-house (DIY)
5. Do nothing (ignore problem)

Step 2: Isolate Your Unique Attributes

What do you have that alternatives don't?

Unique Attributes:
1. [Feature X that no one else has]
2. [Integration Y that's exclusive]
3. [Approach Z that's differentiated]
4. [Performance metric better than all]

Step 3: Map Attributes to Value

What value do these attributes provide to customers?

Attribute: [Real-time collaboration]
→ Value: Teams can work together simultaneously
→ Outcome: 50% faster project completion

Attribute: [AI-powered automation]
→ Value: Eliminates manual data entry
→ Outcome: Save 10 hours/week per user

Step 4: Define Your Best-Fit Customers

Who cares most about this value?

Best-Fit: Mid-market SaaS companies (200-1000 employees)
Why: They have distributed teams, need real-time collaboration
Evidence: Fastest sales cycles, lowest churn, highest NPS

Step 5: Nail Your Market Category

What market do you dominate?

Options:
- Head-to-head: Compete in existing category (e.g., "CRM")
- Big fish, small pond: Own a niche (e.g., "CRM for agencies")
- Create new: Define new category (risky, expensive)

Decision: [Choose based on competitive strength and budget]

Step 6: Layer on Trends

What trends make this the right time to buy?

Trends:
- Remote work explosion (2020-2025)
- AI/ML adoption in enterprise (2024-2025)
- Data privacy regulations (GDPR, CCPA)

2.2 Messaging Architecture

Value Proposition (One-Liner):

Template: [Product] helps [Target Customer] [Achieve Goal] by [Unique Approach]

Example: "Acme helps mid-market SaaS teams ship 2x faster by automating project workflows with AI"

Messaging Hierarchy:

LEVEL 1: Value Proposition (one-liner)
[Your one-liner here]

LEVEL 2: Key Benefits (3-5 bullet points)
- Benefit 1: [Speed] → Ship products 2x faster
- Benefit 2: [Quality] → Reduce bugs by 50%
- Benefit 3: [Collaboration] → Align teams in real-time
- Benefit 4: [Cost] → Save $100k/year on tools

LEVEL 3: Features (supporting evidence)
- Feature → Benefit → Outcome
- AI automation → Eliminates manual work → Save 10 hrs/week
- Real-time sync → No version conflicts → 50% fewer errors
- Integrations → Connect existing tools → 80% faster onboarding

LEVEL 4: Proof Points
- Customer logos: [Microsoft, Shopify, Stripe]
- Stats: Used by 10,000+ teams, 4.8/5 G2 rating
- Case studies: How [Customer] achieved [Outcome]

Messaging by Persona:

Economic Buyer (VP/Director):

  • Primary concern: ROI, business outcomes
  • Tone: Professional, data-driven, results-focused
  • Key message: "Increase revenue by 25% while reducing costs by $200k/year"
  • Proof: ROI calculator, case studies with $ impact

Technical Buyer (Engineer/Architect):

  • Primary concern: Technical fit, security, scalability
  • Tone: Technical, detailed, objective
  • Key message: "Enterprise-grade architecture with 99.99% uptime and SOC 2 compliance"
  • Proof: Technical docs, security whitepaper, architecture diagram

End User (Manager/Individual Contributor):

  • Primary concern: Ease of use, daily workflow
  • Tone: Friendly, empathetic, practical
  • Key message: "Spend less time on busywork, more time on what matters"
  • Proof: Product demo, free t

Content truncated.

software-architecture

davila7

Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.

469162

scroll-experience

davila7

Expert in building immersive scroll-driven experiences - parallax storytelling, scroll animations, interactive narratives, and cinematic web experiences. Like NY Times interactives, Apple product pages, and award-winning web experiences. Makes websites feel like experiences, not just pages. Use when: scroll animation, parallax, scroll storytelling, interactive story, cinematic website.

12580

planning-with-files

davila7

Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.

7966

humanizer

davila7

Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases. Credits: Original skill by @blader - https://github.com/blader/humanizer

10250

game-development

davila7

Game development orchestrator. Routes to platform-specific skills based on project needs.

14649

2d-games

davila7

2D game development principles. Sprites, tilemaps, physics, camera.

12744

You might also like

flutter-development

aj-geddes

Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.

1,5661,368

ui-ux-pro-max

nextlevelbuilder

"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."

1,1131,185

drawio-diagrams-enhanced

jgtolentino

Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.

1,4141,106

godot

bfollington

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

1,192746

nano-banana-pro

garg-aayush

Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.

1,149683

pdf-to-markdown

aliceisjustplaying

Convert entire PDF documents to clean, structured Markdown for full context loading. Use this skill when the user wants to extract ALL text from a PDF into context (not grep/search), when discussing or analyzing PDF content in full, when the user mentions "load the whole PDF", "bring the PDF into context", "read the entire PDF", or when partial extraction/grepping would miss important context. This is the preferred method for PDF text extraction over page-by-page or grep approaches.

1,306610

Stay ahead of the MCP ecosystem

Get weekly updates on new skills and servers.