marketing-strategy-pmm
Product marketing skill for positioning, GTM strategy, competitive intelligence, and product launches. Use when the user asks about product positioning, go-to-market planning, competitive analysis, target audience definition, ICP definition, market research, launch plans, or sales enablement. Covers April Dunford positioning, ICP definition, competitive battlecards, launch playbooks, and international market entry. Produces deliverables including positioning statements, battlecard documents, launch plans, and go-to-market strategies.
- License 许可
- MIT
- 最近更新
- 2026-09-22
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- marketing-strategy-pmm
- triggers
- [ "product marketing", "PMM", "positioning", "GTM strategy", "go-to-market", "competitive analysis", "battlecard", "product launch", "market entry", "sales enablement", "win loss analysis" ]
- description
- Product marketing skill for positioning, GTM strategy, competitive intelligence, and product launches. Use when the user asks about product positioning, go-to-market planning, competitive analysis, target audience definition, ICP definition, market research, launch plans, or sales enablement. Covers April Dunford positioning, ICP definition, competitive battlecards, launch playbooks, and international market entry. Produces deliverables including positioning statements, battlecard documents, launch plans, and go-to-market strategies.
02 资源文件 4
- 参考文档references/international-gtm.md10.3 KB
- 参考文档references/launch-checklists.md8.8 KB
- 参考文档references/messaging-templates.md10.5 KB
- 参考文档references/positioning-frameworks.md7.6 KB
03 SKILL.md 正文
Marketing Strategy & PMM
Product marketing patterns for positioning, GTM strategy, and competitive intelligence.
Table of Contents
- ICP Definition Workflow
- Positioning Development
- Competitive Intelligence
- Product Launch Planning
- Sales Enablement
- International Expansion
- Reference Documentation
ICP Definition Workflow
Define ideal customer profile for targeting:
- Analyze existing customers (top 20% by LTV)
- Identify common firmographics (size, industry, revenue)
- Map technographics (tools, maturity, integrations)
- Document psychographics (pain level, motivation, risk tolerance)
- Define 3-5 buyer personas (economic, technical, user)
- Validate against sales cycle and churn data
- Score prospects A/B/C/D based on ICP fit
- Validation: A-fit customers have lowest churn and fastest close
Firmographics Template
| Dimension | Target Range | Rationale |
|---|---|---|
| Employees | 50-5000 | Series A sweet spot |
| Revenue | $5M-$500M | Budget available |
| Industry | SaaS, Tech, Services | Product fit |
| Geography | US, UK, DACH | Market priority |
| Funding | Seed to Growth | Willing to adopt |
Buyer Personas
| Persona | Title | Goals | Messaging |
|---|---|---|---|
| Economic Buyer | VP, Director, Head of [Department] | ROI, team productivity, cost reduction | Business outcomes, ROI, case studies |
| Technical Buyer | Engineer, Architect, Tech Lead | Technical fit, easy integration | Architecture, security, documentation |
| User/Champion | Manager, Team Lead, Power User | Makes job easier, quick wins | UX, ease of use, time savings |
ICP Validation Checklist
- [ ] 5+ paying customers match this profile
- [ ] Fastest sales cycles (< median)
- [ ] Highest LTV (> median)
- [ ] Lowest churn (< 5% annual)
- [ ] Strong product engagement
- [ ] Willing to do case studies
Positioning Development
Develop positioning using April Dunford methodology:
- List competitive alternatives (direct, adjacent, status quo)
- Isolate unique attributes (features only you have)
- Map attributes to customer value (why it matters)
- Define best-fit customers (who cares most)
- Choose market category (head-to-head, niche, new category)
- Layer on relevant trends (timing justification)
- Test with 10+ customer interviews
- Validation: 7+ customers describe value unprompted
Positioning Statement Template
FOR [target customer]
WHO [statement of need]
THE [product] IS A [category]
THAT [key benefit]
UNLIKE [competitive alternative]
OUR PRODUCT [primary differentiation]
Value Proposition Formula
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 | Content | Example |
|---|---|---|
| Headline | 5-7 words | "Ship faster with AI automation" |
| Subhead | 1 sentence | "Automate workflows so teams focus on what matters" |
| Benefits | 3-4 bullets | Speed, quality, collaboration, cost |
| Features | Supporting evidence | AI automation → 10 hrs/week saved |
| Proof | Social proof | Customer logos, stats, case studies |
Competitive Intelligence
Build competitive knowledge base:
- Identify tier 1 (direct), tier 2 (adjacent), tier 3 (status quo)
- Sign up for competitor products (hands-on evaluation)
- Monitor competitor websites, pricing, messaging
- Analyze sales call recordings for competitor mentions
- Read G2/Capterra reviews (pros and cons)
- Track competitor job postings (roadmap signals)
- Update battlecards monthly
- Validation: Sales team uses battlecards in 80%+ competitive deals
Competitive Tier Structure
| Tier | Definition | Examples |
|---|---|---|
| 1 | Direct competitor, same category | [Competitor A, B] |
| 2 | Adjacent solution, overlapping use case | [Alt Solution C, D] |
| 3 | Status quo (what they do today) | Spreadsheets, manual, in-house |
Battlecard Template
COMPETITOR: [Name]
OVERVIEW: Founded [year], Funding [stage], Size [employees]
POSITIONING:
- They say: "[Their claim]"
- Reality: [Your assessment]
STRENGTHS:
1. [What they do well]
2. [What they do well]
WEAKNESSES:
1. [Where they fall short]
2. [Where they fall short]
OUR ADVANTAGES:
1. [Your advantage + evidence]
2. [Your advantage + evidence]
WHEN WE WIN:
- [Scenario where you win]
WHEN WE LOSE:
- [Scenario where they win]
TALK TRACK:
Objection: "[Common objection]"
Response: "[Your response]"
Win/Loss Analysis
Track monthly:
- Win rate by competitor
- Top win reasons (product fit, ease of use, price)
- Top loss reasons (missing feature, price, relationship)
- Action items for product, sales, marketing
Product Launch Planning
Plan launches by tier:
| Tier | Scope | Prep Time | Budget |
|---|---|---|---|
| 1 | New product, major feature | 6-8 weeks | $50-100k |
| 2 | Significant feature, integration | 3-4 weeks | $10-25k |
| 3 | Small improvement | 1 week | <$5k |
Tier 1 Launch Workflow
Execute major product launch:
- Kickoff meeting with Product, Marketing, Sales, CS
- Define goals (pipeline $, MQLs, press coverage)
- Develop positioning and messaging
- Create sales enablement (deck, demo, battlecard)
- Build campaign assets (landing page, emails, ads)
- Train sales and CS teams
- Execute launch day (press, email, ads, outbound)
- Monitor and optimize for 30 days
- Validation: Pipeline on track to goal by week 2
Launch Day Checklist
- [ ] Press release distributed
- [ ] Email announcement sent
- [ ] Social media posts live
- [ ] Paid ads at full budget
- [ ] Sales outbound blitz launched
- [ ] In-app notification active
- [ ] Metrics monitored every 2 hours
Launch Metrics
| Metric | Leading (Daily) | Lagging (Weekly) |
|---|---|---|
| Traffic | Landing page visitors | - |
| Engagement | Demo requests, signups | Feature adoption % |
| Pipeline | MQLs generated | SQLs, pipeline $ |
| Revenue | - | Deals closed, revenue |
Sales Enablement
Equip sales team with PMM assets:
- Create sales deck (15-20 slides, visual-first)
- Build one-pagers (product, competitive, case study)
- Develop demo script (30-45 min with discovery)
- Write email templates (outreach, follow-up, closing)
- Create ROI calculator (input costs, output savings)
- Conduct monthly enablement calls
- Deliver quarterly training (positioning, competitive)
- Validation: Sales uses assets in 80%+ of opportunities
Sales Deck Structure
| Slide | Content |
|---|---|
| 1-2 | Title, agenda |
| 3-4 | Company intro, problem statement |
| 5-7 | Solution, key benefits, demo |
| 8-10 | Differentiation, case study, pricing |
| 11-12 | Implementation, support, next steps |
Demo Flow
1. Intro (2 min): Who we are, agenda
2. Discovery (5 min): Their needs, pain points
3. Demo (20 min): Product focused on their use case
4. Q&A (10 min): Objection handling
5. Next steps (3 min): Trial, POC, proposal
Sales-Marketing Handoff
| Handoff | Frequency | Content |
|---|---|---|
| Weekly sync | 30 min | Win/loss, competitive, new assets |
| Monthly enablement | 60 min | Product updates, training |
| Quarterly review | Half-day | Results, strategy, planning |
International Expansion
Enter new markets systematically:
- Validate market demand (inbound leads, TAM analysis)
- Localize website, pricing, legal
- Establish sales coverage (hire or agency)
- Adapt messaging for cultural fit
- Build local partnerships and references
- Launch localized campaigns
- Monitor CAC and conversion by market
- Validation: 3+ paying customers from market in first 90 days
Market Priority (Series A)
| Market | Timeline | Budget % | Target ARR |
|---|---|---|---|
| US | Months 1-6 | 50% | $1M |
| UK | Months 4-9 | 20% | $500k |
| DACH | Months 7-12 | 15% | $300k |
| France | Months 10-15 | 10% | $200k |
| Canada | Months 7-12 | 5% | $100k |
Localization Checklist
- [ ] Website translation (professional, not machine)
- [ ] Currency and pricing localized
- [ ] Local phone number and address
- [ ] Legal compliance (GDPR, PIPEDA)
- [ ] Local payment methods
- [ ] Sales coverage during local hours
- [ ] Local case studies and references
Reference Documentation
Positioning Frameworks
references/positioning-frameworks.md contains:
- April Dunford 5-step positioning process
- Geoffrey Moore positioning statement template
- Positioning validation interview protocol
- Competitive positioning map construction
Launch Checklists
references/launch-checklists.md contains:
- Tier 1/2/3 launch checklists
- Week-by-week launch timeline
- Launch day runbook
- Post-launch metrics dashboard
International GTM
references/international-gtm.md contains:
- US, UK, DACH, France, Canada playbooks
- Market-specific channel mix and messaging
- Localization requirements per market
- Entry timeline and budget allocation
Messaging Templates
references/messaging-templates.md contains:
- Value proposition formulas
- Persona-specific messaging
- Competitive response scripts
- Objection handling templates
- Channel-specific copy (landing pages, emails, ads)
PMM KPIs
| Metric | Target | Measurement |
|---|---|---|
| Product adoption | >40% in 90 days | Feature usage after launch |
| Win rate | >30% competitive | Deals won vs. competitors |
| Sales velocity | -20% YoY | Days from SQL to close |
| Deal size | +25% YoY | Average contract value |
| Launch pipeline | 3:1 ROMI | Pipeline $ : marketing spend |
Quick Reference
PMM Monthly Rhythm
| Week | Focus |
|---|---|
| 1 | Review metrics, update battlecards |
| 2 | Create assets, publish content |
| 3 | Support launches, optimize campaigns |
| 4 | Monthly report, plan next month |
Proactive Triggers
- No documented positioning → Without clear positioning, all marketing is guesswork.
- Messaging differs across channels → Inconsistent story confuses buyers.
- No ICP defined → Selling to everyone means selling to no one.
- Competitor repositioning → Market shift detected. Review your positioning.
Output Artifacts
| When you ask for... | You get... |
|---|---|
| "Position my product" | Positioning framework (April Dunford method) with output |
| "GTM strategy" | Go-to-market plan with channels, messaging, and timeline |
| "Competitive positioning" | Positioning map with competitive gaps and opportunities |
Communication
All output passes quality verification:
- Self-verify: source attribution, assumption audit, confidence scoring
- Output format: Bottom Line → What (with confidence) → Why → How to Act
- Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.
Related Skills
- marketing-context: For capturing foundational positioning. PMM builds on this.
- launch-strategy: For executing product launches planned by PMM.
- competitive-intel (C-Suite): For strategic competitive intelligence.
- cmo-advisor (C-Suite): For marketing budget and growth model decisions.
04 同仓库更多 Skills
syllabus
Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Triggers whenever a user uploads a syllabus, course outline, or curriculum document and wants supplementary readings. Also triggers on: 'syllabus reading list', 'find papers for my course', 'create a reading list from this syllabus', 'recent research for my class', 'supplementary readings', 'find journal articles for these topics', 'what recent papers cover this material', 'any new research on these course topics', 'update my syllabus with recent papers'. Even casual mentions when a syllabus is attached should trigger this skill.
research
Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends/sentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Triggers — "research [topic]", "look into [topic]", "what do we know about [topic]", "investigate [topic]", "find me information on [topic]", "do some research on [topic]", "I need to understand [topic]", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.
pulse
Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X/Twitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend/sentiment/problems/opportunities/comparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Triggers: 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]', or any variation requesting multi-source recency intelligence on a topic. Also use for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.
patent
Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Triggers: 'prior art search for [invention]', 'patent search on [topic]', 'freedom to operate analysis', 'FTO for [product]', 'patent landscape for [field]', 'is [invention] novel', 'patents on [topic]', 'competitive patent analysis', 'prior art for litigation', 'patent diligence on [company]'. Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.
notebooklm
Browser automation skill for controlling Google's NotebookLM. Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio Overview, infographics, slide decks, study guides, briefing docs, mind maps, timelines, FAQs), and creating new notebooks. Triggers on any phrase involving NotebookLM — 'open NotebookLM', 'check my [name] notebook', 'pull info from NotebookLM', 'ask my notebook about X', 'add [source] to NotebookLM', 'create an infographic in NotebookLM', 'use NotebookLM Studio', 'generate a slide deck from my notebook', or any variation where the goal involves NotebookLM. Requires browser automation environment — fails gracefully when unavailable.
litreview
Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER / Decomposition / hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5/10/20 queries) controls coverage vs. speed. Output is a 'launching pad' — not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'. Do NOT trigger for single one-off paper searches where the user just wants a quick list — that's a plain Consensus search.