[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75F5YXTKT7FR2AQBFS07CSQ":3,"skill-same:01M75F5YXTKT7FR2AQBFS07CSQ":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":40,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":6,"updatedAt":43,"install":44,"resources":57},"01M75F5YXTKT7FR2AQBFS07CSQ","marketing-strategy-pmm",null,"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.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fmarketing-strategy-pmm\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"marketing-strategy-pmm\"\ndescription: 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.\ntriggers:\n  - product marketing\n  - PMM\n  - positioning\n  - GTM strategy\n  - go-to-market\n  - competitive analysis\n  - battlecard\n  - product launch\n  - market entry\n  - sales enablement\n  - win loss analysis\n---\n\n# Marketing Strategy & PMM\n\nProduct marketing patterns for positioning, GTM strategy, and competitive intelligence.\n\n---\n\n## Table of Contents\n\n- [ICP Definition Workflow](#icp-definition-workflow)\n- [Positioning Development](#positioning-development)\n- [Competitive Intelligence](#competitive-intelligence)\n- [Product Launch Planning](#product-launch-planning)\n- [Sales Enablement](#sales-enablement)\n- [International Expansion](#international-expansion)\n- [Reference Documentation](#reference-documentation)\n\n---\n\n## ICP Definition Workflow\n\nDefine ideal customer profile for targeting:\n\n1. Analyze existing customers (top 20% by LTV)\n2. Identify common firmographics (size, industry, revenue)\n3. Map technographics (tools, maturity, integrations)\n4. Document psychographics (pain level, motivation, risk tolerance)\n5. Define 3-5 buyer personas (economic, technical, user)\n6. Validate against sales cycle and churn data\n7. Score prospects A\u002FB\u002FC\u002FD based on ICP fit\n8. **Validation:** A-fit customers have lowest churn and fastest close\n\n### Firmographics Template\n\n| Dimension | Target Range | Rationale |\n|-----------|--------------|-----------|\n| Employees | 50-5000 | Series A sweet spot |\n| Revenue | $5M-$500M | Budget available |\n| Industry | SaaS, Tech, Services | Product fit |\n| Geography | US, UK, DACH | Market priority |\n| Funding | Seed to Growth | Willing to adopt |\n\n### Buyer Personas\n\n| Persona | Title | Goals | Messaging |\n|---------|-------|-------|-----------|\n| Economic Buyer | VP, Director, Head of [Department] | ROI, team productivity, cost reduction | Business outcomes, ROI, case studies |\n| Technical Buyer | Engineer, Architect, Tech Lead | Technical fit, easy integration | Architecture, security, documentation |\n| User\u002FChampion | Manager, Team Lead, Power User | Makes job easier, quick wins | UX, ease of use, time savings |\n\n### ICP Validation Checklist\n\n- [ ] 5+ paying customers match this profile\n- [ ] Fastest sales cycles (\u003C median)\n- [ ] Highest LTV (> median)\n- [ ] Lowest churn (\u003C 5% annual)\n- [ ] Strong product engagement\n- [ ] Willing to do case studies\n\n---\n\n## Positioning Development\n\nDevelop positioning using April Dunford methodology:\n\n1. List competitive alternatives (direct, adjacent, status quo)\n2. Isolate unique attributes (features only you have)\n3. Map attributes to customer value (why it matters)\n4. Define best-fit customers (who cares most)\n5. Choose market category (head-to-head, niche, new category)\n6. Layer on relevant trends (timing justification)\n7. Test with 10+ customer interviews\n8. **Validation:** 7+ customers describe value unprompted\n\n### Positioning Statement Template\n\n```\nFOR [target customer]\nWHO [statement of need]\nTHE [product] IS A [category]\nTHAT [key benefit]\nUNLIKE [competitive alternative]\nOUR PRODUCT [primary differentiation]\n```\n\n### Value Proposition Formula\n\nTemplate: `[Product] helps [Target Customer] [Achieve Goal] by [Unique Approach]`\n\nExample: \"Acme helps mid-market SaaS teams ship 2x faster by automating project workflows with AI\"\n\n### Messaging Hierarchy\n\n| Level | Content | Example |\n|-------|---------|---------|\n| Headline | 5-7 words | \"Ship faster with AI automation\" |\n| Subhead | 1 sentence | \"Automate workflows so teams focus on what matters\" |\n| Benefits | 3-4 bullets | Speed, quality, collaboration, cost |\n| Features | Supporting evidence | AI automation → 10 hrs\u002Fweek saved |\n| Proof | Social proof | Customer logos, stats, case studies |\n\n---\n\n## Competitive Intelligence\n\nBuild competitive knowledge base:\n\n1. Identify tier 1 (direct), tier 2 (adjacent), tier 3 (status quo)\n2. Sign up for competitor products (hands-on evaluation)\n3. Monitor competitor websites, pricing, messaging\n4. Analyze sales call recordings for competitor mentions\n5. Read G2\u002FCapterra reviews (pros and cons)\n6. Track competitor job postings (roadmap signals)\n7. Update battlecards monthly\n8. **Validation:** Sales team uses battlecards in 80%+ competitive deals\n\n### Competitive Tier Structure\n\n| Tier | Definition | Examples |\n|------|------------|----------|\n| 1 | Direct competitor, same category | [Competitor A, B] |\n| 2 | Adjacent solution, overlapping use case | [Alt Solution C, D] |\n| 3 | Status quo (what they do today) | Spreadsheets, manual, in-house |\n\n### Battlecard Template\n\n```\nCOMPETITOR: [Name]\nOVERVIEW: Founded [year], Funding [stage], Size [employees]\n\nPOSITIONING:\n- They say: \"[Their claim]\"\n- Reality: [Your assessment]\n\nSTRENGTHS:\n1. [What they do well]\n2. [What they do well]\n\nWEAKNESSES:\n1. [Where they fall short]\n2. [Where they fall short]\n\nOUR ADVANTAGES:\n1. [Your advantage + evidence]\n2. [Your advantage + evidence]\n\nWHEN WE WIN:\n- [Scenario where you win]\n\nWHEN WE LOSE:\n- [Scenario where they win]\n\nTALK TRACK:\nObjection: \"[Common objection]\"\nResponse: \"[Your response]\"\n```\n\n### Win\u002FLoss Analysis\n\nTrack monthly:\n- Win rate by competitor\n- Top win reasons (product fit, ease of use, price)\n- Top loss reasons (missing feature, price, relationship)\n- Action items for product, sales, marketing\n\n---\n\n## Product Launch Planning\n\nPlan launches by tier:\n\n| Tier | Scope | Prep Time | Budget |\n|------|-------|-----------|--------|\n| 1 | New product, major feature | 6-8 weeks | $50-100k |\n| 2 | Significant feature, integration | 3-4 weeks | $10-25k |\n| 3 | Small improvement | 1 week | \u003C$5k |\n\n### Tier 1 Launch Workflow\n\nExecute major product launch:\n\n1. Kickoff meeting with Product, Marketing, Sales, CS\n2. Define goals (pipeline $, MQLs, press coverage)\n3. Develop positioning and messaging\n4. Create sales enablement (deck, demo, battlecard)\n5. Build campaign assets (landing page, emails, ads)\n6. Train sales and CS teams\n7. Execute launch day (press, email, ads, outbound)\n8. Monitor and optimize for 30 days\n9. **Validation:** Pipeline on track to goal by week 2\n\n### Launch Day Checklist\n\n- [ ] Press release distributed\n- [ ] Email announcement sent\n- [ ] Social media posts live\n- [ ] Paid ads at full budget\n- [ ] Sales outbound blitz launched\n- [ ] In-app notification active\n- [ ] Metrics monitored every 2 hours\n\n### Launch Metrics\n\n| Metric | Leading (Daily) | Lagging (Weekly) |\n|--------|-----------------|------------------|\n| Traffic | Landing page visitors | - |\n| Engagement | Demo requests, signups | Feature adoption % |\n| Pipeline | MQLs generated | SQLs, pipeline $ |\n| Revenue | - | Deals closed, revenue |\n\n---\n\n## Sales Enablement\n\nEquip sales team with PMM assets:\n\n1. Create sales deck (15-20 slides, visual-first)\n2. Build one-pagers (product, competitive, case study)\n3. Develop demo script (30-45 min with discovery)\n4. Write email templates (outreach, follow-up, closing)\n5. Create ROI calculator (input costs, output savings)\n6. Conduct monthly enablement calls\n7. Deliver quarterly training (positioning, competitive)\n8. **Validation:** Sales uses assets in 80%+ of opportunities\n\n### Sales Deck Structure\n\n| Slide | Content |\n|-------|---------|\n| 1-2 | Title, agenda |\n| 3-4 | Company intro, problem statement |\n| 5-7 | Solution, key benefits, demo |\n| 8-10 | Differentiation, case study, pricing |\n| 11-12 | Implementation, support, next steps |\n\n### Demo Flow\n\n```\n1. Intro (2 min): Who we are, agenda\n2. Discovery (5 min): Their needs, pain points\n3. Demo (20 min): Product focused on their use case\n4. Q&A (10 min): Objection handling\n5. Next steps (3 min): Trial, POC, proposal\n```\n\n### Sales-Marketing Handoff\n\n| Handoff | Frequency | Content |\n|---------|-----------|---------|\n| Weekly sync | 30 min | Win\u002Floss, competitive, new assets |\n| Monthly enablement | 60 min | Product updates, training |\n| Quarterly review | Half-day | Results, strategy, planning |\n\n---\n\n## International Expansion\n\nEnter new markets systematically:\n\n1. Validate market demand (inbound leads, TAM analysis)\n2. Localize website, pricing, legal\n3. Establish sales coverage (hire or agency)\n4. Adapt messaging for cultural fit\n5. Build local partnerships and references\n6. Launch localized campaigns\n7. Monitor CAC and conversion by market\n8. **Validation:** 3+ paying customers from market in first 90 days\n\n### Market Priority (Series A)\n\n| Market | Timeline | Budget % | Target ARR |\n|--------|----------|----------|------------|\n| US | Months 1-6 | 50% | $1M |\n| UK | Months 4-9 | 20% | $500k |\n| DACH | Months 7-12 | 15% | $300k |\n| France | Months 10-15 | 10% | $200k |\n| Canada | Months 7-12 | 5% | $100k |\n\n### Localization Checklist\n\n- [ ] Website translation (professional, not machine)\n- [ ] Currency and pricing localized\n- [ ] Local phone number and address\n- [ ] Legal compliance (GDPR, PIPEDA)\n- [ ] Local payment methods\n- [ ] Sales coverage during local hours\n- [ ] Local case studies and references\n\n---\n\n## Reference Documentation\n\n### Positioning Frameworks\n\n`references\u002Fpositioning-frameworks.md` contains:\n\n- April Dunford 5-step positioning process\n- Geoffrey Moore positioning statement template\n- Positioning validation interview protocol\n- Competitive positioning map construction\n\n### Launch Checklists\n\n`references\u002Flaunch-checklists.md` contains:\n\n- Tier 1\u002F2\u002F3 launch checklists\n- Week-by-week launch timeline\n- Launch day runbook\n- Post-launch metrics dashboard\n\n### International GTM\n\n`references\u002Finternational-gtm.md` contains:\n\n- US, UK, DACH, France, Canada playbooks\n- Market-specific channel mix and messaging\n- Localization requirements per market\n- Entry timeline and budget allocation\n\n### Messaging Templates\n\n`references\u002Fmessaging-templates.md` contains:\n\n- Value proposition formulas\n- Persona-specific messaging\n- Competitive response scripts\n- Objection handling templates\n- Channel-specific copy (landing pages, emails, ads)\n\n---\n\n## PMM KPIs\n\n| Metric | Target | Measurement |\n|--------|--------|-------------|\n| Product adoption | >40% in 90 days | Feature usage after launch |\n| Win rate | >30% competitive | Deals won vs. competitors |\n| Sales velocity | -20% YoY | Days from SQL to close |\n| Deal size | +25% YoY | Average contract value |\n| Launch pipeline | 3:1 ROMI | Pipeline $ : marketing spend |\n\n---\n\n## Quick Reference\n\n### PMM Monthly Rhythm\n\n| Week | Focus |\n|------|-------|\n| 1 | Review metrics, update battlecards |\n| 2 | Create assets, publish content |\n| 3 | Support launches, optimize campaigns |\n| 4 | Monthly report, plan next month |\n\n## Proactive Triggers\n\n- **No documented positioning** → Without clear positioning, all marketing is guesswork.\n- **Messaging differs across channels** → Inconsistent story confuses buyers.\n- **No ICP defined** → Selling to everyone means selling to no one.\n- **Competitor repositioning** → Market shift detected. Review your positioning.\n\n## Output Artifacts\n\n| When you ask for... | You get... |\n|---------------------|------------|\n| \"Position my product\" | Positioning framework (April Dunford method) with output |\n| \"GTM strategy\" | Go-to-market plan with channels, messaging, and timeline |\n| \"Competitive positioning\" | Positioning map with competitive gaps and opportunities |\n\n## Communication\n\nAll output passes quality verification:\n- Self-verify: source attribution, assumption audit, confidence scoring\n- Output format: Bottom Line → What (with confidence) → Why → How to Act\n- Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.\n\n## Related Skills\n\n- **marketing-context**: For capturing foundational positioning. PMM builds on this.\n- **launch-strategy**: For executing product launches planned by PMM.\n- **competitive-intel** (C-Suite): For strategic competitive intelligence.\n- **cmo-advisor** (C-Suite): For marketing budget and growth model decisions.\n","# Marketing Strategy & PMM\n\nProduct marketing patterns for positioning, GTM strategy, and competitive intelligence.\n\n---\n\n## Table of Contents\n\n- [ICP Definition Workflow](#icp-definition-workflow)\n- [Positioning Development](#positioning-development)\n- [Competitive Intelligence](#competitive-intelligence)\n- [Product Launch Planning](#product-launch-planning)\n- [Sales Enablement](#sales-enablement)\n- [International Expansion](#international-expansion)\n- [Reference Documentation](#reference-documentation)\n\n---\n\n## ICP Definition Workflow\n\nDefine ideal customer profile for targeting:\n\n1. Analyze existing customers (top 20% by LTV)\n2. Identify common firmographics (size, industry, revenue)\n3. Map technographics (tools, maturity, integrations)\n4. Document psychographics (pain level, motivation, risk tolerance)\n5. Define 3-5 buyer personas (economic, technical, user)\n6. Validate against sales cycle and churn data\n7. Score prospects A\u002FB\u002FC\u002FD based on ICP fit\n8. **Validation:** A-fit customers have lowest churn and fastest close\n\n### Firmographics Template\n\n| Dimension | Target Range | Rationale |\n|-----------|--------------|-----------|\n| Employees | 50-5000 | Series A sweet spot |\n| Revenue | $5M-$500M | Budget available |\n| Industry | SaaS, Tech, Services | Product fit |\n| Geography | US, UK, DACH | Market priority |\n| Funding | Seed to Growth | Willing to adopt |\n\n### Buyer Personas\n\n| Persona | Title | Goals | Messaging |\n|---------|-------|-------|-----------|\n| Economic Buyer | VP, Director, Head of [Department] | ROI, team productivity, cost reduction | Business outcomes, ROI, case studies |\n| Technical Buyer | Engineer, Architect, Tech Lead | Technical fit, easy integration | Architecture, security, documentation |\n| User\u002FChampion | Manager, Team Lead, Power User | Makes job easier, quick wins | UX, ease of use, time savings |\n\n### ICP Validation Checklist\n\n- [ ] 5+ paying customers match this profile\n- [ ] Fastest sales cycles (\u003C median)\n- [ ] Highest LTV (> median)\n- [ ] Lowest churn (\u003C 5% annual)\n- [ ] Strong product engagement\n- [ ] Willing to do case studies\n\n---\n\n## Positioning Development\n\nDevelop positioning using April Dunford methodology:\n\n1. List competitive alternatives (direct, adjacent, status quo)\n2. Isolate unique attributes (features only you have)\n3. Map attributes to customer value (why it matters)\n4. Define best-fit customers (who cares most)\n5. Choose market category (head-to-head, niche, new category)\n6. Layer on relevant trends (timing justification)\n7. Test with 10+ customer interviews\n8. **Validation:** 7+ customers describe value unprompted\n\n### Positioning Statement Template\n\n```\nFOR [target customer]\nWHO [statement of need]\nTHE [product] IS A [category]\nTHAT [key benefit]\nUNLIKE [competitive alternative]\nOUR PRODUCT [primary differentiation]\n```\n\n### Value Proposition Formula\n\nTemplate: `[Product] helps [Target Customer] [Achieve Goal] by [Unique Approach]`\n\nExample: \"Acme helps mid-market SaaS teams ship 2x faster by automating project workflows with AI\"\n\n### Messaging Hierarchy\n\n| Level | Content | Example |\n|-------|---------|---------|\n| Headline | 5-7 words | \"Ship faster with AI automation\" |\n| Subhead | 1 sentence | \"Automate workflows so teams focus on what matters\" |\n| Benefits | 3-4 bullets | Speed, quality, collaboration, cost |\n| Features | Supporting evidence | AI automation → 10 hrs\u002Fweek saved |\n| Proof | Social proof | Customer logos, stats, case studies |\n\n---\n\n## Competitive Intelligence\n\nBuild competitive knowledge base:\n\n1. Identify tier 1 (direct), tier 2 (adjacent), tier 3 (status quo)\n2. Sign up for competitor products (hands-on evaluation)\n3. Monitor competitor websites, pricing, messaging\n4. Analyze sales call recordings for competitor mentions\n5. Read G2\u002FCapterra reviews (pros and cons)\n6. Track competitor job postings (roadmap signals)\n7. Update battlecards monthly\n8. **Validation:** Sales team uses battlecards in 80%+ competitive deals\n\n### Competitive Tier Structure\n\n| Tier | Definition | Examples |\n|------|------------|----------|\n| 1 | Direct competitor, same category | [Competitor A, B] |\n| 2 | Adjacent solution, overlapping use case | [Alt Solution C, D] |\n| 3 | Status quo (what they do today) | Spreadsheets, manual, in-house |\n\n### Battlecard Template\n\n```\nCOMPETITOR: [Name]\nOVERVIEW: Founded [year], Funding [stage], Size [employees]\n\nPOSITIONING:\n- They say: \"[Their claim]\"\n- Reality: [Your assessment]\n\nSTRENGTHS:\n1. [What they do well]\n2. [What they do well]\n\nWEAKNESSES:\n1. [Where they fall short]\n2. [Where they fall short]\n\nOUR ADVANTAGES:\n1. [Your advantage + evidence]\n2. [Your advantage + evidence]\n\nWHEN WE WIN:\n- [Scenario where you win]\n\nWHEN WE LOSE:\n- [Scenario where they win]\n\nTALK TRACK:\nObjection: \"[Common objection]\"\nResponse: \"[Your response]\"\n```\n\n### Win\u002FLoss Analysis\n\nTrack monthly:\n- Win rate by competitor\n- Top win reasons (product fit, ease of use, price)\n- Top loss reasons (missing feature, price, relationship)\n- Action items for product, sales, marketing\n\n---\n\n## Product Launch Planning\n\nPlan launches by tier:\n\n| Tier | Scope | Prep Time | Budget |\n|------|-------|-----------|--------|\n| 1 | New product, major feature | 6-8 weeks | $50-100k |\n| 2 | Significant feature, integration | 3-4 weeks | $10-25k |\n| 3 | Small improvement | 1 week | \u003C$5k |\n\n### Tier 1 Launch Workflow\n\nExecute major product launch:\n\n1. Kickoff meeting with Product, Marketing, Sales, CS\n2. Define goals (pipeline $, MQLs, press coverage)\n3. Develop positioning and messaging\n4. Create sales enablement (deck, demo, battlecard)\n5. Build campaign assets (landing page, emails, ads)\n6. Train sales and CS teams\n7. Execute launch day (press, email, ads, outbound)\n8. Monitor and optimize for 30 days\n9. **Validation:** Pipeline on track to goal by week 2\n\n### Launch Day Checklist\n\n- [ ] Press release distributed\n- [ ] Email announcement sent\n- [ ] Social media posts live\n- [ ] Paid ads at full budget\n- [ ] Sales outbound blitz launched\n- [ ] In-app notification active\n- [ ] Metrics monitored every 2 hours\n\n### Launch Metrics\n\n| Metric | Leading (Daily) | Lagging (Weekly) |\n|--------|-----------------|------------------|\n| Traffic | Landing page visitors | - |\n| Engagement | Demo requests, signups | Feature adoption % |\n| Pipeline | MQLs generated | SQLs, pipeline $ |\n| Revenue | - | Deals closed, revenue |\n\n---\n\n## Sales Enablement\n\nEquip sales team with PMM assets:\n\n1. Create sales deck (15-20 slides, visual-first)\n2. Build one-pagers (product, competitive, case study)\n3. Develop demo script (30-45 min with discovery)\n4. Write email templates (outreach, follow-up, closing)\n5. Create ROI calculator (input costs, output savings)\n6. Conduct monthly enablement calls\n7. Deliver quarterly training (positioning, competitive)\n8. **Validation:** Sales uses assets in 80%+ of opportunities\n\n### Sales Deck Structure\n\n| Slide | Content |\n|-------|---------|\n| 1-2 | Title, agenda |\n| 3-4 | Company intro, problem statement |\n| 5-7 | Solution, key benefits, demo |\n| 8-10 | Differentiation, case study, pricing |\n| 11-12 | Implementation, support, next steps |\n\n### Demo Flow\n\n```\n1. Intro (2 min): Who we are, agenda\n2. Discovery (5 min): Their needs, pain points\n3. Demo (20 min): Product focused on their use case\n4. Q&A (10 min): Objection handling\n5. Next steps (3 min): Trial, POC, proposal\n```\n\n### Sales-Marketing Handoff\n\n| Handoff | Frequency | Content |\n|---------|-----------|---------|\n| Weekly sync | 30 min | Win\u002Floss, competitive, new assets |\n| Monthly enablement | 60 min | Product updates, training |\n| Quarterly review | Half-day | Results, strategy, planning |\n\n---\n\n## International Expansion\n\nEnter new markets systematically:\n\n1. Validate market demand (inbound leads, TAM analysis)\n2. Localize website, pricing, legal\n3. Establish sales coverage (hire or agency)\n4. Adapt messaging for cultural fit\n5. Build local partnerships and references\n6. Launch localized campaigns\n7. Monitor CAC and conversion by market\n8. **Validation:** 3+ paying customers from market in first 90 days\n\n### Market Priority (Series A)\n\n| Market | Timeline | Budget % | Target ARR |\n|--------|----------|----------|------------|\n| US | Months 1-6 | 50% | $1M |\n| UK | Months 4-9 | 20% | $500k |\n| DACH | Months 7-12 | 15% | $300k |\n| France | Months 10-15 | 10% | $200k |\n| Canada | Months 7-12 | 5% | $100k |\n\n### Localization Checklist\n\n- [ ] Website translation (professional, not machine)\n- [ ] Currency and pricing localized\n- [ ] Local phone number and address\n- [ ] Legal compliance (GDPR, PIPEDA)\n- [ ] Local payment methods\n- [ ] Sales coverage during local hours\n- [ ] Local case studies and references\n\n---\n\n## Reference Documentation\n\n### Positioning Frameworks\n\n`references\u002Fpositioning-frameworks.md` contains:\n\n- April Dunford 5-step positioning process\n- Geoffrey Moore positioning statement template\n- Positioning validation interview protocol\n- Competitive positioning map construction\n\n### Launch Checklists\n\n`references\u002Flaunch-checklists.md` contains:\n\n- Tier 1\u002F2\u002F3 launch checklists\n- Week-by-week launch timeline\n- Launch day runbook\n- Post-launch metrics dashboard\n\n### International GTM\n\n`references\u002Finternational-gtm.md` contains:\n\n- US, UK, DACH, France, Canada playbooks\n- Market-specific channel mix and messaging\n- Localization requirements per market\n- Entry timeline and budget allocation\n\n### Messaging Templates\n\n`references\u002Fmessaging-templates.md` contains:\n\n- Value proposition formulas\n- Persona-specific messaging\n- Competitive response scripts\n- Objection handling templates\n- Channel-specific copy (landing pages, emails, ads)\n\n---\n\n## PMM KPIs\n\n| Metric | Target | Measurement |\n|--------|--------|-------------|\n| Product adoption | >40% in 90 days | Feature usage after launch |\n| Win rate | >30% competitive | Deals won vs. competitors |\n| Sales velocity | -20% YoY | Days from SQL to close |\n| Deal size | +25% YoY | Average contract value |\n| Launch pipeline | 3:1 ROMI | Pipeline $ : marketing spend |\n\n---\n\n## Quick Reference\n\n### PMM Monthly Rhythm\n\n| Week | Focus |\n|------|-------|\n| 1 | Review metrics, update battlecards |\n| 2 | Create assets, publish content |\n| 3 | Support launches, optimize campaigns |\n| 4 | Monthly report, plan next month |\n\n## Proactive Triggers\n\n- **No documented positioning** → Without clear positioning, all marketing is guesswork.\n- **Messaging differs across channels** → Inconsistent story confuses buyers.\n- **No ICP defined** → Selling to everyone means selling to no one.\n- **Competitor repositioning** → Market shift detected. Review your positioning.\n\n## Output Artifacts\n\n| When you ask for... | You get... |\n|---------------------|------------|\n| \"Position my product\" | Positioning framework (April Dunford method) with output |\n| \"GTM strategy\" | Go-to-market plan with channels, messaging, and timeline |\n| \"Competitive positioning\" | Positioning map with competitive gaps and opportunities |\n\n## Communication\n\nAll output passes quality verification:\n- Self-verify: source attribution, assumption audit, confidence scoring\n- Output format: Bottom Line → What (with confidence) → Why → How to Act\n- Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.\n\n## Related Skills\n\n- **marketing-context**: For capturing foundational positioning. PMM builds on this.\n- **launch-strategy**: For executing product launches planned by PMM.\n- **competitive-intel** (C-Suite): For strategic competitive intelligence.\n- **cmo-advisor** (C-Suite): For marketing budget and growth model decisions.\n",{"name":5,"triggers":23,"description":7},[24,25,26,27,28,29,30,31,32,33,34],"product marketing","PMM","positioning","GTM strategy","go-to-market","competitive analysis","battlecard","product launch","market entry","sales enablement","win loss analysis","main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fmarketing-strategy-pmm",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add agisota\u002Fold-one --skill marketing-strategy-pmm",{"tool":50,"command":51},"bunx","bunx skills add agisota\u002Fold-one --skill marketing-strategy-pmm",{"tool":53,"command":54},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill marketing-strategy-pmm","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fmarketing-strategy-pmm\u002FSKILL.md",true,[],[59,66,73,82,89,96],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":77,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]