marketing-strategy-pmm
Product marketing skill for positioning, GTM strategy, competitive intelligence, and product launches. Covers April Dunford positioning, ICP definition, competitive battlecards, launch playbooks, and international market entry.
What this skill does
# Marketing Strategy & PMM Product marketing patterns for positioning, GTM strategy, and competitive intelligence. --- ## Table of Contents - [ICP Definition Workflow](#icp-definition-workflow) - [Positioning Development](#positioning-development) - [Competitive Intelligence](#competitive-intelligence) - [Product Launch Planning](#product-launch-planning) - [Sales Enablement](#sales-enablement) - [International Expansion](#international-expansion) - [Reference Documentation](#reference-documentation) --- ## ICP Definition Workflow Define ideal customer profile for targeting: 1. Analyze existing customers (top 20% by LTV) 2. Identify common firmographics (size, industry, revenue) 3. Map technographics (tools, maturity, integrations) 4. Document psychographics (pain level, motivation, risk tolerance) 5. Define 3-5 buyer personas (economic, technical, user) 6. Validate against sales cycle and churn data 7. Score prospects A/B/C/D based on ICP fit 8. **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 **Economic Buyer** (signs contract): - Title: VP, Director, Head of [Department] - Goals: ROI, team productivity, cost reduction - Messaging: Business outcomes, ROI, case studies **Technical Buyer** (evaluates product): - Title: Engineer, Architect, Tech Lead - Goals: Technical fit, easy integration - Messaging: Architecture, security, documentation **User/Champion** (advocates internally): - Title: Manager, Team Lead, Power User - Goals: Makes job easier, quick wins - Messaging: 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: 1. List competitive alternatives (direct, adjacent, status quo) 2. Isolate unique attributes (features only you have) 3. Map attributes to customer value (why it matters) 4. Define best-fit customers (who cares most) 5. Choose market category (head-to-head, niche, new category) 6. Layer on relevant trends (timing justification) 7. Test with 10+ customer interviews 8. **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: 1. Identify tier 1 (direct), tier 2 (adjacent), tier 3 (status quo) 2. Sign up for competitor products (hands-on evaluation) 3. Monitor competitor websites, pricing, messaging 4. Analyze sales call recordings for competitor mentions 5. Read G2/Capterra reviews (pros and cons) 6. Track competitor job postings (roadmap signals) 7. Update battlecards monthly 8. **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: 1. Kickoff meeting with Product, Marketing, Sales, CS 2. Define goals (pipeline $, MQLs, press coverage) 3. Develop positioning and messaging 4. Create sales enablement (deck, demo, battlecard) 5. Build campaign assets (landing page, emails, ads) 6. Train sales and CS teams 7. Execute launch day (press, email, ads, outbound) 8. Monitor and optimize for 30 days 9. **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: 1. Create sales deck (15-20 slides, visual-first) 2. Build one-pagers (product, competitive, case study) 3. Develop demo script (30-45 min with discovery) 4. Write email templates (outreach, follow-up, closing) 5. Create ROI calculator (input costs, output savings) 6. Conduct monthly enablement calls 7. Deliver quarterly training (positioning, competitive) 8. **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: 1. Validate market demand (inbound leads, TAM analysis) 2. Localize website, pricing, legal 3. Establish sales coverage (hire or agency) 4. Adapt messaging for cultural fit 5. Build local partnerships and references 6. Launch loc
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.