go-to-market-playbooks
GTM strategies, product positioning, messaging, and launch planning. Use when planning a product launch, entering a new market, positioning a product, or developing go-to-market strategy. Trigger on: 'plan my launch', 'GTM strategy', 'how do I position this', 'market entry plan'.
What this skill does
# Go-to-Market Playbooks ## Overview Comprehensive guide to go-to-market (GTM) strategies, product positioning, launch planning, and market entry tactics. ## When to Use This Skill **Auto-loaded by agents**: - `launch-planner` - For GTM strategies, positioning, and distribution playbooks **Use when you need**: - Planning product launches - Positioning new products - Entering new markets - Rebranding or repositioning - Competitive differentiation ## GTM Strategy Types Four core GTM motions. Pick based on product complexity, price point, and distribution model. | Motion | Model | Best For | Examples | | --------------------- | ------------------------------------------------- | ---------------------------------------------------------- | ----------------------------- | | **Product-Led (PLG)** | Product drives acquisition, conversion, expansion | Low price (<$100/mo), quick time-to-value, network effects | Slack, Dropbox, Notion, Figma | | **Sales-Led** | Sales team drives revenue | High contract values ($10K+), complex sales cycles | Salesforce, SAP | | **Community-Led** | Community drives adoption | Developer tools, open-source, passion-driven users | GitHub, HashiCorp, Discord | | **Partner-Led** | Partners drive distribution | Platform complements, ecosystem plays | Shopify apps, AWS Marketplace | > **Deep dive**: See [references/gtm-strategy-types-guide.md](references/gtm-strategy-types-guide.md) for full playbooks, funnels, and step-by-step tactics for each motion. --- ## Positioning Use April Dunford's 5-component framework: 1. **Competitive Alternatives** - What customers use today 2. **Unique Attributes** - What you have that alternatives don't 3. **Value** - What those attributes enable 4. **Target Customer** - Who cares most about that value 5. **Market Category** - What context makes the value obvious **Positioning Statement Template**: ``` For [target customer] Who [need/opportunity] [Product] is a [category] That [key benefit] Unlike [alternative] We [primary differentiation] ``` > **Deep dive**: See [assets/positioning-statement-template.md](assets/positioning-statement-template.md) for the full 5-step positioning process with worked examples. --- ## Messaging Three-level messaging hierarchy: - **Level 1**: Company messaging (mission, brand, values) - **Level 2**: Product messaging (positioning, value props, differentiators) - **Level 3**: Feature messaging (benefits, use cases, proof points) Key formulas: - **Before-After-Bridge (BAB)**: Pain -> desired state -> how product bridges the gap - **PAS (Problem-Agitate-Solve)**: Identify pain -> make it worse -> your solution > **Deep dive**: See [assets/messaging-formulas-template.md](assets/messaging-formulas-template.md) for full formulas with examples. --- ## Launch Strategy ### Launch Tiers **Tier 1: Major Launch** - New product, major rebranding, strategic pivot. Full PR, events, marketing. **Tier 2: Feature Launch** - Significant new capability. Blog post, email, social, targeted outreach. **Tier 3: Improvement** - Bug fixes, small features. Release notes, changelog. ### Launch Channels | Channel Type | Examples | | ---------------- | ---------------------------------------------------------------- | | **Owned** | Website, blog, email list, in-app, social media | | **Earned** | Press (TechCrunch), Product Hunt, Hacker News, influencers | | **Paid** | Google Ads, LinkedIn/Twitter ads, retargeting, sponsored content | | **Partnerships** | Co-marketing, integration announcements, channel partners | > **Deep dive**: See [assets/launch-timeline-template.md](assets/launch-timeline-template.md) for a Tier 1 launch checklist from T-8 weeks through post-launch. --- ## Market Entry Strategy ### TAM/SAM/SOM ``` TAM (Total Addressable Market): Everyone who could use product SAM (Serviceable Available Market): Segment you can reach SOM (Serviceable Obtainable Market): Realistic target ``` ### Beachhead Strategy (Geoffrey Moore) Dominate one narrow segment before expanding. 1. **Identify Beachhead**: Narrow, winnable segment 2. **Dominate**: Become #1 in that segment 3. **Expand**: Adjacent segments Examples: Facebook (Harvard -> Ivy League -> all colleges -> everyone), Amazon (books -> electronics -> everything) ### Market Entry Checklist - [ ] Market size validation - [ ] Competitive landscape - [ ] Regulatory requirements - [ ] Localization needs (language, currency, compliance) - [ ] Distribution partners - [ ] Pricing for market --- ## Competitive Strategy ### Competitive Intel **What to Track**: Product features/roadmap, pricing, marketing messages, customer reviews, funding/news **Sources**: Competitor websites/blogs, G2/Capterra reviews, LinkedIn (hiring = roadmap hints), earnings calls, customer conversations ### Battle Cards For each competitor, document: - Overview (size, funding, target customers, strengths) - When they win vs. when we win - Feature comparison and positioning - Objection handling scripts - Proof points (customer wins, case studies) --- ## Pricing & Packaging Five core pricing models: Freemium, Free Trial, Usage-Based, Tiered, Per-Seat. Pick a value metric that scales with customer value (per user, per event, per API call, storage). > **Deep dive**: See [references/pricing-packaging-guide.md](references/pricing-packaging-guide.md) for pricing model details and 3-tier packaging strategy. --- ## GTM Playbook Summary ``` Choose GTM Motion: Low-touch, self-serve -> PLG High-touch, complex sale -> Sales-Led Developer product -> Community-Led Platform complement -> Partner-Led Then: 1. Position (find differentiation) 2. Message (communicate value) 3. Launch (create awareness) 4. Optimize (iterate and scale) Key Success Factors: - Clear positioning - Focused beachhead - Aligned team - Measured results ``` --- ## Troubleshooting **"I don't know which GTM motion to pick"**: Start with PLG if your product has quick time-to-value and low price point. Default to sales-led for complex products with high contract values. Use the decision tree in the GTM Playbook Summary above. **"My positioning feels generic"**: You likely skipped step 1 (Competitive Alternatives). Start by listing what customers actually use today, then identify what you do that those alternatives cannot. **"Launch got no traction"**: Most common causes: wrong channel for audience, launched without a waitlist/audience, or messaging didn't communicate value clearly. Review launch tier -- you may have under-invested for the launch type. --- ## Resources **Books**: - "Obviously Awesome" - April Dunford (positioning) - "Crossing the Chasm" - Geoffrey Moore (market entry) - "Product-Led Growth" - Wes Bush (PLG strategy) - "The Mom Test" - Rob Fitzpatrick (customer discovery) **Frameworks**: - April Dunford positioning canvas - Jobs-to-be-Done framework - Lean Canvas (market fit) **Tools**: - Competitors: Crayon, Klue - Launches: Product Hunt, BetaList - Analytics: Mixpanel, Segment --- ## Deep Dive Files | File | Contents | | ------------------------------------------------------------------------------------ | ----------------------------------------------------------- | | [references/gtm-strategy-types-guide.md](references/gtm-strategy-types-guide.md) | Full PLG, sales-led, community-led, partner-led playbooks | | [references/pricing-packaging-guide.md](references/pricing-packaging-guide.md) | Pricing models,
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.