Initial commit with translated description
This commit is contained in:
398
SKILL.md
Normal file
398
SKILL.md
Normal file
@@ -0,0 +1,398 @@
|
|||||||
|
---
|
||||||
|
name: "marketing-strategy-pmm"
|
||||||
|
description: "产品营销技能，涵盖定位、GTM策略、竞争情报和产品发布。在用户询问产品定位、上市计划、竞争分析、目标受众定义、ICP定义、市场调研、发布计划或销售赋能时使用。涵盖April Dunford定位、ICP定义、竞争战卡、发布手册和国际市场进入。产出包括定位声明、战卡文档、发布计划和上市策略等交付物。"
|
||||||
|
triggers:
|
||||||
|
- product marketing
|
||||||
|
- PMM
|
||||||
|
- positioning
|
||||||
|
- GTM strategy
|
||||||
|
- go-to-market
|
||||||
|
- competitive analysis
|
||||||
|
- battlecard
|
||||||
|
- product launch
|
||||||
|
- market entry
|
||||||
|
- sales enablement
|
||||||
|
- win loss analysis
|
||||||
|
---
|
||||||
|
|
||||||
|
# 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
|
||||||
|
|
||||||
|
| 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:
|
||||||
|
|
||||||
|
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 localized campaigns
|
||||||
|
7. Monitor CAC and conversion by market
|
||||||
|
8. **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.
|
||||||
6
_meta.json
Normal file
6
_meta.json
Normal file
@@ -0,0 +1,6 @@
|
|||||||
|
{
|
||||||
|
"ownerId": "kn7f2gr00xy51fj1nx2y64ckjs800mhn",
|
||||||
|
"slug": "marketing-strategy-pmm",
|
||||||
|
"version": "2.1.1",
|
||||||
|
"publishedAt": 1773070262187
|
||||||
|
}
|
||||||
401
references/international-gtm.md
Normal file
401
references/international-gtm.md
Normal file
@@ -0,0 +1,401 @@
|
|||||||
|
# International GTM Playbooks
|
||||||
|
|
||||||
|
Market-by-market expansion guides for US, UK, DACH, France, and Canada.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Table of Contents
|
||||||
|
|
||||||
|
- [Market Prioritization](#market-prioritization)
|
||||||
|
- [US Market Entry](#us-market-entry)
|
||||||
|
- [UK Market Entry](#uk-market-entry)
|
||||||
|
- [DACH Market Entry](#dach-market-entry)
|
||||||
|
- [France Market Entry](#france-market-entry)
|
||||||
|
- [Canada Market Entry](#canada-market-entry)
|
||||||
|
- [Localization Checklist](#localization-checklist)
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Market Prioritization
|
||||||
|
|
||||||
|
### Expansion Sequence (Series A)
|
||||||
|
|
||||||
|
| Phase | Market | Timeline | Budget % | Target ARR |
|
||||||
|
|-------|--------|----------|----------|------------|
|
||||||
|
| 1 | US | Months 1-6 | 50% | $1M |
|
||||||
|
| 2 | UK | Months 4-9 | 20% | $500k |
|
||||||
|
| 3 | DACH | Months 7-12 | 15% | $300k |
|
||||||
|
| 4 | France | Months 10-15 | 10% | $200k |
|
||||||
|
| 5 | Canada | Months 7-12 | 5% | $100k |
|
||||||
|
|
||||||
|
### Market Readiness Checklist
|
||||||
|
|
||||||
|
Enter market when ALL true:
|
||||||
|
|
||||||
|
- [ ] Product ready for market (localization if needed)
|
||||||
|
- [ ] Legal/compliance requirements met
|
||||||
|
- [ ] Pricing localized (currency, taxes)
|
||||||
|
- [ ] Sales capacity available (hire or agency)
|
||||||
|
- [ ] Marketing budget allocated
|
||||||
|
- [ ] Support coverage during local hours
|
||||||
|
- [ ] **Validation:** 3+ inbound leads from market in last 90 days
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## US Market Entry
|
||||||
|
|
||||||
|
### Market Characteristics
|
||||||
|
|
||||||
|
| Factor | US Approach |
|
||||||
|
|--------|-------------|
|
||||||
|
| Buying cycle | Fast (30-60 days average) |
|
||||||
|
| Decision process | Individual empowerment, less consensus |
|
||||||
|
| Pricing sensitivity | Value-focused, willing to pay premium |
|
||||||
|
| Communication | Direct, results-oriented |
|
||||||
|
| Relationship | Transaction > relationship (initially) |
|
||||||
|
|
||||||
|
### Entry Strategy
|
||||||
|
|
||||||
|
**Months 1-2: Foundation**
|
||||||
|
|
||||||
|
1. Establish US presence:
|
||||||
|
- US phone number (toll-free)
|
||||||
|
- US address (virtual office acceptable)
|
||||||
|
- USD pricing on website
|
||||||
|
- US case studies (even if from beta users)
|
||||||
|
|
||||||
|
2. Hire US sales:
|
||||||
|
- Option A: US-based SDR/AE (expensive but effective)
|
||||||
|
- Option B: US sales agency (lower risk, shared commission)
|
||||||
|
- Option C: Remote sales trained on US hours
|
||||||
|
|
||||||
|
3. Launch paid campaigns:
|
||||||
|
- Google Ads (high-intent keywords)
|
||||||
|
- LinkedIn (B2B targeting)
|
||||||
|
- Budget: 50% of marketing spend
|
||||||
|
|
||||||
|
**Months 3-6: Scale**
|
||||||
|
|
||||||
|
1. Optimize channels based on CAC data
|
||||||
|
2. Build US partner ecosystem:
|
||||||
|
- Integration partners (Salesforce, HubSpot)
|
||||||
|
- Resellers/VARs (for Enterprise)
|
||||||
|
- Industry associations
|
||||||
|
3. Attend US conferences (SaaStr, industry events)
|
||||||
|
4. **Validation:** $1M pipeline from US sources
|
||||||
|
|
||||||
|
### US Channel Mix
|
||||||
|
|
||||||
|
| Channel | Budget % | Expected CPL | Notes |
|
||||||
|
|---------|----------|--------------|-------|
|
||||||
|
| Google Ads | 35% | $100-200 | High intent, competitive |
|
||||||
|
| LinkedIn | 30% | $150-250 | B2B targeting |
|
||||||
|
| SEO/Content | 20% | $50 (long-term) | Invest early |
|
||||||
|
| Partnerships | 15% | Variable | Co-marketing |
|
||||||
|
|
||||||
|
### US Messaging
|
||||||
|
|
||||||
|
- Lead with ROI and business outcomes
|
||||||
|
- Use $ impact metrics prominently
|
||||||
|
- Reference US customers (logos matter)
|
||||||
|
- Emphasize speed and efficiency
|
||||||
|
- Include G2/Capterra ratings
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## UK Market Entry
|
||||||
|
|
||||||
|
### Market Characteristics
|
||||||
|
|
||||||
|
| Factor | UK Approach |
|
||||||
|
|--------|-------------|
|
||||||
|
| Buying cycle | Medium (45-90 days) |
|
||||||
|
| Decision process | Committee involvement |
|
||||||
|
| Pricing sensitivity | Value-conscious, compare options |
|
||||||
|
| Communication | Professional, less aggressive than US |
|
||||||
|
| Relationship | Balance transaction and relationship |
|
||||||
|
|
||||||
|
### Entry Strategy
|
||||||
|
|
||||||
|
**Months 4-6: Setup**
|
||||||
|
|
||||||
|
1. Localization:
|
||||||
|
- GBP pricing
|
||||||
|
- UK spellings (colour, organisation)
|
||||||
|
- UK phone number
|
||||||
|
- GDPR compliance (essential)
|
||||||
|
|
||||||
|
2. Sales coverage:
|
||||||
|
- Hire UK-based rep OR
|
||||||
|
- Partner with UK sales agency
|
||||||
|
- Ensure coverage during GMT hours
|
||||||
|
|
||||||
|
3. Content localization:
|
||||||
|
- UK case studies
|
||||||
|
- UK-relevant industry references
|
||||||
|
- Local competitor positioning
|
||||||
|
|
||||||
|
**Months 7-9: Growth**
|
||||||
|
|
||||||
|
1. Build UK partnerships:
|
||||||
|
- UK tech community (TechNation, etc.)
|
||||||
|
- London-based VCs and accelerators
|
||||||
|
- UK industry associations
|
||||||
|
|
||||||
|
2. Attend UK events:
|
||||||
|
- London Tech Week
|
||||||
|
- Industry-specific conferences
|
||||||
|
|
||||||
|
3. **Validation:** $500k pipeline from UK sources
|
||||||
|
|
||||||
|
### UK Channel Mix
|
||||||
|
|
||||||
|
| Channel | Budget % | Expected CPL | Notes |
|
||||||
|
|---------|----------|--------------|-------|
|
||||||
|
| LinkedIn | 35% | $120-200 | Strong B2B presence |
|
||||||
|
| Google UK | 30% | $80-150 | Less competitive than US |
|
||||||
|
| SEO/Content | 20% | $40 | UK-targeted keywords |
|
||||||
|
| Partnerships | 15% | Variable | Local credibility |
|
||||||
|
|
||||||
|
### UK Messaging
|
||||||
|
|
||||||
|
- More formal than US (avoid hyperbole)
|
||||||
|
- Emphasize data security and GDPR
|
||||||
|
- Reference UK/EU customers
|
||||||
|
- Understated claims (prove with data)
|
||||||
|
- Acknowledge local presence/support
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## DACH Market Entry
|
||||||
|
|
||||||
|
### Market Characteristics
|
||||||
|
|
||||||
|
| Factor | DACH Approach |
|
||||||
|
|--------|---------------|
|
||||||
|
| Buying cycle | Long (90-180 days) |
|
||||||
|
| Decision process | Consensus-driven, thorough evaluation |
|
||||||
|
| Pricing sensitivity | Quality over price, long-term view |
|
||||||
|
| Communication | Formal, detailed, precise |
|
||||||
|
| Relationship | Trust built over time, essential |
|
||||||
|
|
||||||
|
### Entry Strategy
|
||||||
|
|
||||||
|
**Months 7-9: Foundation**
|
||||||
|
|
||||||
|
1. Full localization:
|
||||||
|
- German translation (website, product UI)
|
||||||
|
- EUR pricing with German VAT handling
|
||||||
|
- German phone number and address
|
||||||
|
- GDPR compliance (strict enforcement)
|
||||||
|
- Data residency option (EU data centers)
|
||||||
|
|
||||||
|
2. German-speaking sales:
|
||||||
|
- Hire German-speaking sales rep
|
||||||
|
- Native speaker critical (not just fluent)
|
||||||
|
- Based in Germany preferred
|
||||||
|
|
||||||
|
3. Content in German:
|
||||||
|
- Translate key pages and materials
|
||||||
|
- Create German case studies
|
||||||
|
- German blog content
|
||||||
|
|
||||||
|
**Months 10-12: Growth**
|
||||||
|
|
||||||
|
1. Build local credibility:
|
||||||
|
- German customer testimonials
|
||||||
|
- German partner ecosystem
|
||||||
|
- Industry certifications (ISO, etc.)
|
||||||
|
|
||||||
|
2. Attend German events:
|
||||||
|
- CeBIT/Hannover Messe
|
||||||
|
- Industry conferences
|
||||||
|
|
||||||
|
3. **Validation:** $300k pipeline from DACH sources
|
||||||
|
|
||||||
|
### DACH Channel Mix
|
||||||
|
|
||||||
|
| Channel | Budget % | Expected CPL | Notes |
|
||||||
|
|---------|----------|--------------|-------|
|
||||||
|
| LinkedIn | 40% | $150-250 | Strong professional network |
|
||||||
|
| Google DE | 25% | $100-180 | German keywords |
|
||||||
|
| SEO (German) | 20% | $60 | Long-term investment |
|
||||||
|
| Partnerships | 15% | Variable | Critical for trust |
|
||||||
|
|
||||||
|
### DACH Messaging
|
||||||
|
|
||||||
|
- Formal tone (Sie, not du)
|
||||||
|
- Emphasize security, compliance, privacy
|
||||||
|
- Detailed specifications and documentation
|
||||||
|
- Reference German/EU customers
|
||||||
|
- Include certifications (ISO, SOC 2)
|
||||||
|
- Show long-term commitment to market
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## France Market Entry
|
||||||
|
|
||||||
|
### Market Characteristics
|
||||||
|
|
||||||
|
| Factor | France Approach |
|
||||||
|
|--------|-----------------|
|
||||||
|
| Buying cycle | Long (90-180 days) |
|
||||||
|
| Decision process | Hierarchical, formal process |
|
||||||
|
| Pricing sensitivity | Value-focused, negotiation expected |
|
||||||
|
| Communication | Formal, relationship-focused |
|
||||||
|
| Relationship | Critical, business built on trust |
|
||||||
|
|
||||||
|
### Entry Strategy
|
||||||
|
|
||||||
|
**Months 10-12: Foundation**
|
||||||
|
|
||||||
|
1. Full French localization:
|
||||||
|
- French translation (professional, not machine)
|
||||||
|
- EUR pricing with French VAT
|
||||||
|
- French phone number
|
||||||
|
- GDPR + French regulations
|
||||||
|
|
||||||
|
2. French-speaking team:
|
||||||
|
- Native French speaker for sales
|
||||||
|
- French support coverage
|
||||||
|
- Paris presence (even virtual)
|
||||||
|
|
||||||
|
**Months 13-15: Growth**
|
||||||
|
|
||||||
|
1. Build local ecosystem:
|
||||||
|
- French tech community (La French Tech)
|
||||||
|
- French partners and integrators
|
||||||
|
- Industry associations
|
||||||
|
|
||||||
|
2. Attend French events:
|
||||||
|
- VivaTech (Paris)
|
||||||
|
- Industry conferences
|
||||||
|
|
||||||
|
3. **Validation:** $200k pipeline from France
|
||||||
|
|
||||||
|
### France Channel Mix
|
||||||
|
|
||||||
|
| Channel | Budget % | Expected CPL | Notes |
|
||||||
|
|---------|----------|--------------|-------|
|
||||||
|
| LinkedIn | 35% | $130-220 | Professional network |
|
||||||
|
| Google FR | 30% | $90-160 | French keywords |
|
||||||
|
| SEO (French) | 20% | $50 | French content strategy |
|
||||||
|
| Partnerships | 15% | Variable | Local partners essential |
|
||||||
|
|
||||||
|
### France Messaging
|
||||||
|
|
||||||
|
- Formal and professional
|
||||||
|
- French language throughout (no English fallback)
|
||||||
|
- Reference French/EU customers
|
||||||
|
- Emphasize local support and presence
|
||||||
|
- Highlight innovation and modernity
|
||||||
|
- Respect cultural nuances
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Canada Market Entry
|
||||||
|
|
||||||
|
### Market Characteristics
|
||||||
|
|
||||||
|
| Factor | Canada Approach |
|
||||||
|
|--------|-----------------|
|
||||||
|
| Buying cycle | Medium (45-75 days) |
|
||||||
|
| Decision process | Similar to US, slightly more conservative |
|
||||||
|
| Pricing sensitivity | Value-conscious, compare to US prices |
|
||||||
|
| Communication | Professional, friendly, less aggressive |
|
||||||
|
| Language | English (except Quebec - French required) |
|
||||||
|
|
||||||
|
### Entry Strategy
|
||||||
|
|
||||||
|
**Months 7-9: Foundation**
|
||||||
|
|
||||||
|
1. Minimal localization:
|
||||||
|
- CAD pricing
|
||||||
|
- Canadian phone number (optional)
|
||||||
|
- PIPEDA compliance
|
||||||
|
|
||||||
|
2. Sales coverage:
|
||||||
|
- Leverage US sales team (similar hours)
|
||||||
|
- Consider Toronto-based rep for growth
|
||||||
|
|
||||||
|
3. Quebec consideration:
|
||||||
|
- French required for Quebec market
|
||||||
|
- Can delay or skip initially
|
||||||
|
|
||||||
|
**Months 10-12: Growth**
|
||||||
|
|
||||||
|
1. Canadian partnerships:
|
||||||
|
- Canadian tech community
|
||||||
|
- Toronto/Vancouver startup ecosystem
|
||||||
|
- Industry associations
|
||||||
|
|
||||||
|
2. **Validation:** $100k pipeline from Canada
|
||||||
|
|
||||||
|
### Canada Channel Mix
|
||||||
|
|
||||||
|
| Channel | Budget % | Expected CPL | Notes |
|
||||||
|
|---------|----------|--------------|-------|
|
||||||
|
| Google CA | 35% | $80-150 | Canadian targeting |
|
||||||
|
| LinkedIn | 30% | $100-180 | B2B focus |
|
||||||
|
| SEO | 20% | $40 | Canadian content |
|
||||||
|
| Partnerships | 15% | Variable | Local credibility |
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Localization Checklist
|
||||||
|
|
||||||
|
### Per-Market Checklist
|
||||||
|
|
||||||
|
**Website**
|
||||||
|
|
||||||
|
- [ ] Language translation (professional, not machine)
|
||||||
|
- [ ] Currency localization (display + checkout)
|
||||||
|
- [ ] Phone number (local format)
|
||||||
|
- [ ] Address (local presence)
|
||||||
|
- [ ] Legal pages (privacy, terms in local language)
|
||||||
|
- [ ] hreflang tags configured correctly
|
||||||
|
|
||||||
|
**Product**
|
||||||
|
|
||||||
|
- [ ] UI translation (if required for market)
|
||||||
|
- [ ] Date/time format (DD/MM/YYYY vs MM/DD/YYYY)
|
||||||
|
- [ ] Number format (1,000 vs 1.000)
|
||||||
|
- [ ] Currency in product
|
||||||
|
|
||||||
|
**Payment**
|
||||||
|
|
||||||
|
- [ ] Local currency accepted
|
||||||
|
- [ ] VAT/tax handling
|
||||||
|
- [ ] Local payment methods (SEPA, iDEAL, etc.)
|
||||||
|
- [ ] Invoicing in local format
|
||||||
|
|
||||||
|
**Legal**
|
||||||
|
|
||||||
|
- [ ] GDPR compliance (EU markets)
|
||||||
|
- [ ] PIPEDA compliance (Canada)
|
||||||
|
- [ ] Local data protection laws
|
||||||
|
- [ ] Terms of service localized
|
||||||
|
- [ ] Privacy policy localized
|
||||||
|
|
||||||
|
**Sales**
|
||||||
|
|
||||||
|
- [ ] Local sales coverage (rep or agency)
|
||||||
|
- [ ] Localized sales materials
|
||||||
|
- [ ] Local pricing and quoting
|
||||||
|
- [ ] Local references and case studies
|
||||||
|
|
||||||
|
**Support**
|
||||||
|
|
||||||
|
- [ ] Coverage during local business hours
|
||||||
|
- [ ] Language support (phone, chat, email)
|
||||||
|
- [ ] Localized documentation
|
||||||
|
- [ ] Local SLA commitments
|
||||||
|
|
||||||
|
**Marketing**
|
||||||
|
|
||||||
|
- [ ] Localized campaigns
|
||||||
|
- [ ] Local content (blog, guides)
|
||||||
|
- [ ] Local social media presence
|
||||||
|
- [ ] Local event participation
|
||||||
|
|
||||||
|
**Validation:** Native speaker review of ALL localized content before launch
|
||||||
333
references/launch-checklists.md
Normal file
333
references/launch-checklists.md
Normal file
@@ -0,0 +1,333 @@
|
|||||||
|
# Launch Checklists
|
||||||
|
|
||||||
|
GTM launch playbooks for Tier 1, 2, and 3 product releases.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Table of Contents
|
||||||
|
|
||||||
|
- [Launch Tier Definitions](#launch-tier-definitions)
|
||||||
|
- [Tier 1 Major Launch](#tier-1-major-launch)
|
||||||
|
- [Tier 2 Standard Launch](#tier-2-standard-launch)
|
||||||
|
- [Tier 3 Minor Launch](#tier-3-minor-launch)
|
||||||
|
- [Launch Metrics Dashboard](#launch-metrics-dashboard)
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Launch Tier Definitions
|
||||||
|
|
||||||
|
| Tier | Scope | Prep Time | Budget | Audience |
|
||||||
|
|------|-------|-----------|--------|----------|
|
||||||
|
| 1 | New product, major feature | 6-8 weeks | $50-100k | All prospects + press |
|
||||||
|
| 2 | Significant feature, integration | 3-4 weeks | $10-25k | Customers + select prospects |
|
||||||
|
| 3 | Small feature, improvement | 1 week | <$5k | Existing customers |
|
||||||
|
|
||||||
|
**Tier Selection Criteria:**
|
||||||
|
|
||||||
|
```
|
||||||
|
Tier 1 if ANY true:
|
||||||
|
- [ ] Net-new product line
|
||||||
|
- [ ] Revenue impact > $500k pipeline
|
||||||
|
- [ ] Press coverage expected
|
||||||
|
- [ ] Competitive response anticipated
|
||||||
|
|
||||||
|
Tier 2 if ANY true:
|
||||||
|
- [ ] Major feature request (top 10 customer ask)
|
||||||
|
- [ ] New integration with strategic partner
|
||||||
|
- [ ] Pricing or packaging change
|
||||||
|
|
||||||
|
Tier 3 otherwise:
|
||||||
|
- [ ] Bug fixes
|
||||||
|
- [ ] UI improvements
|
||||||
|
- [ ] Minor enhancements
|
||||||
|
```
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Tier 1 Major Launch
|
||||||
|
|
||||||
|
### Phase 1: Foundation (Weeks -8 to -5)
|
||||||
|
|
||||||
|
**Week -8: Kickoff**
|
||||||
|
|
||||||
|
- [ ] Schedule kickoff meeting (Product, Marketing, Sales, CS)
|
||||||
|
- [ ] Define launch goals:
|
||||||
|
- Pipeline target: $______
|
||||||
|
- MQL target: ______
|
||||||
|
- Press hits target: ______
|
||||||
|
- Adoption target: ______% in 90 days
|
||||||
|
- [ ] Assign roles (RACI matrix):
|
||||||
|
- PMM: Launch lead, positioning, messaging
|
||||||
|
- Product: Feature readiness, demo environment
|
||||||
|
- Demand Gen: Campaigns, paid ads, email
|
||||||
|
- Content: Blog posts, case studies, videos
|
||||||
|
- Sales: Enablement, outbound campaign
|
||||||
|
- [ ] Create project timeline in Asana/Monday/Notion
|
||||||
|
- [ ] **Validation:** All stakeholders confirm goals and timeline
|
||||||
|
|
||||||
|
**Week -7: Strategy**
|
||||||
|
|
||||||
|
- [ ] Develop positioning and messaging (see positioning-frameworks.md)
|
||||||
|
- [ ] Create GTM channel plan:
|
||||||
|
- Owned: Email, blog, social, webinar
|
||||||
|
- Paid: LinkedIn ads, Google ads
|
||||||
|
- Earned: Press, influencers, partners
|
||||||
|
- [ ] Define target segments (ICP, personas)
|
||||||
|
- [ ] Allocate budget by channel
|
||||||
|
- [ ] Draft press release (embargo date set)
|
||||||
|
|
||||||
|
**Week -6: Content**
|
||||||
|
|
||||||
|
- [ ] Build landing page (product page, demo request form)
|
||||||
|
- [ ] Write blog post announcement
|
||||||
|
- [ ] Create sales deck updates (5-10 new slides)
|
||||||
|
- [ ] Design social media graphics (5+ variants)
|
||||||
|
- [ ] Produce demo video (3-5 minutes)
|
||||||
|
- [ ] Draft email sequences (announcement, nurture)
|
||||||
|
|
||||||
|
**Week -5: Enablement**
|
||||||
|
|
||||||
|
- [ ] Create sales battlecard (competitive positioning)
|
||||||
|
- [ ] Write demo script (new feature walkthrough)
|
||||||
|
- [ ] Build FAQ document (top 20 questions)
|
||||||
|
- [ ] Develop objection handling guide
|
||||||
|
- [ ] Schedule sales training session
|
||||||
|
- [ ] Recruit beta customers for testimonials
|
||||||
|
- [ ] **Validation:** Sales team can demo feature confidently
|
||||||
|
|
||||||
|
### Phase 2: Preparation (Weeks -4 to -1)
|
||||||
|
|
||||||
|
**Week -4: Launch Prep**
|
||||||
|
|
||||||
|
- [ ] Set up HubSpot campaign (UTMs, attribution)
|
||||||
|
- [ ] Launch teaser campaign (social, email hints)
|
||||||
|
- [ ] Pitch press and analysts (NDA briefings)
|
||||||
|
- [ ] Create webinar registration page
|
||||||
|
- [ ] Finalize partner co-marketing plans
|
||||||
|
- [ ] QA all landing pages and forms
|
||||||
|
|
||||||
|
**Week -3: Ramp Up**
|
||||||
|
|
||||||
|
- [ ] Activate paid ads (LinkedIn, Google) at 50% budget
|
||||||
|
- [ ] A/B test landing page headlines
|
||||||
|
- [ ] Send pre-launch email to VIP customers
|
||||||
|
- [ ] Conduct sales training (2-hour session)
|
||||||
|
- [ ] Confirm webinar speakers and content
|
||||||
|
- [ ] Prepare launch day runbook
|
||||||
|
|
||||||
|
**Week -2: Final Prep**
|
||||||
|
|
||||||
|
- [ ] Increase paid ad spend to 75%
|
||||||
|
- [ ] Send webinar reminder emails
|
||||||
|
- [ ] Finalize press embargo lift time
|
||||||
|
- [ ] Complete dry run (website, forms, CRM workflow)
|
||||||
|
- [ ] Create launch day social posts (scheduled)
|
||||||
|
- [ ] Brief customer success team
|
||||||
|
|
||||||
|
**Week -1: Pre-Launch**
|
||||||
|
|
||||||
|
- [ ] Final approval on all assets
|
||||||
|
- [ ] Send VIP preview to top 10 customers
|
||||||
|
- [ ] Confirm press embargo release
|
||||||
|
- [ ] Sales team ready (trained, quotas set)
|
||||||
|
- [ ] CS team ready (docs updated, chat staffed)
|
||||||
|
- [ ] Test all systems one final time
|
||||||
|
- [ ] **Validation:** All checklist items green
|
||||||
|
|
||||||
|
### Phase 3: Launch (Weeks 1-4)
|
||||||
|
|
||||||
|
**Launch Day**
|
||||||
|
|
||||||
|
- [ ] Press release distribution (wire + direct pitch)
|
||||||
|
- [ ] Email blast to full database
|
||||||
|
- [ ] Social media posts (LinkedIn, Twitter, Facebook)
|
||||||
|
- [ ] Paid ads at 100% budget
|
||||||
|
- [ ] Sales outbound blitz (top 100 accounts)
|
||||||
|
- [ ] In-app announcement to existing users
|
||||||
|
- [ ] Monitor metrics every 2 hours:
|
||||||
|
- Traffic, signups, demo requests
|
||||||
|
- Press pickup, social engagement
|
||||||
|
- Sales pipeline created
|
||||||
|
|
||||||
|
**Days 2-7**
|
||||||
|
|
||||||
|
- [ ] Daily metrics review (conversion rates, funnel)
|
||||||
|
- [ ] A/B test optimizations based on data
|
||||||
|
- [ ] Sales follow-up (<4 hour SLA on leads)
|
||||||
|
- [ ] Respond to press and analyst inquiries
|
||||||
|
- [ ] Host webinar (Day 3 or 4)
|
||||||
|
- [ ] Post customer testimonials
|
||||||
|
- [ ] Adjust paid ads (pause underperformers)
|
||||||
|
|
||||||
|
**Week 2-4**
|
||||||
|
|
||||||
|
- [ ] Publish post-launch blog content
|
||||||
|
- [ ] Create customer case study from early adopters
|
||||||
|
- [ ] Conduct win/loss interviews (5+ deals)
|
||||||
|
- [ ] Optimize converting channels (+20% budget)
|
||||||
|
- [ ] Pause non-converting channels
|
||||||
|
- [ ] Weekly launch status report to executives
|
||||||
|
- [ ] **Validation:** Pipeline on track to goal
|
||||||
|
|
||||||
|
### Phase 4: Post-Launch (Weeks 5-12)
|
||||||
|
|
||||||
|
**Month 2**
|
||||||
|
|
||||||
|
- [ ] Launch retrospective meeting
|
||||||
|
- [ ] Document learnings (what worked, what didn't)
|
||||||
|
- [ ] Scale winning channels
|
||||||
|
- [ ] Expand to new segments if successful
|
||||||
|
- [ ] Update positioning based on customer feedback
|
||||||
|
- [ ] Plan sustaining campaigns
|
||||||
|
|
||||||
|
**Month 3**
|
||||||
|
|
||||||
|
- [ ] Final launch report (vs. goals)
|
||||||
|
- [ ] Calculate ROI (pipeline / spend)
|
||||||
|
- [ ] Publish additional case studies
|
||||||
|
- [ ] Integrate learnings into next launch plan
|
||||||
|
- [ ] Archive launch assets for reuse
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Tier 2 Standard Launch
|
||||||
|
|
||||||
|
### Timeline: 4 Weeks
|
||||||
|
|
||||||
|
**Week -4 to -3: Preparation**
|
||||||
|
|
||||||
|
- [ ] Define feature and target audience
|
||||||
|
- [ ] Create positioning and key messages
|
||||||
|
- [ ] Build landing page or product page update
|
||||||
|
- [ ] Write blog post announcement
|
||||||
|
- [ ] Update sales deck (2-3 slides)
|
||||||
|
- [ ] Create email announcement
|
||||||
|
- [ ] Brief sales team (30-min call)
|
||||||
|
|
||||||
|
**Week -2 to -1: Setup**
|
||||||
|
|
||||||
|
- [ ] Set up HubSpot campaign tracking
|
||||||
|
- [ ] Schedule social posts
|
||||||
|
- [ ] Set up paid ads (limited budget)
|
||||||
|
- [ ] QA landing pages and forms
|
||||||
|
- [ ] Notify customer success team
|
||||||
|
|
||||||
|
**Launch Week**
|
||||||
|
|
||||||
|
- [ ] Send email announcement
|
||||||
|
- [ ] Publish blog post
|
||||||
|
- [ ] Post on social media
|
||||||
|
- [ ] In-app notification to users
|
||||||
|
- [ ] Sales mention in active deals
|
||||||
|
- [ ] Monitor initial metrics
|
||||||
|
|
||||||
|
**Week +1 to +2: Follow-up**
|
||||||
|
|
||||||
|
- [ ] Analyze launch metrics
|
||||||
|
- [ ] Optimize based on data
|
||||||
|
- [ ] Collect customer feedback
|
||||||
|
- [ ] Document learnings
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Tier 3 Minor Launch
|
||||||
|
|
||||||
|
### Timeline: 1 Week
|
||||||
|
|
||||||
|
**Day -5 to -3: Prep**
|
||||||
|
|
||||||
|
- [ ] Write changelog entry
|
||||||
|
- [ ] Update support documentation
|
||||||
|
- [ ] Create in-app notification copy
|
||||||
|
- [ ] Brief CS team
|
||||||
|
|
||||||
|
**Day -2 to -1: Review**
|
||||||
|
|
||||||
|
- [ ] QA feature in staging
|
||||||
|
- [ ] Approve changelog copy
|
||||||
|
- [ ] Schedule in-app notification
|
||||||
|
|
||||||
|
**Launch Day**
|
||||||
|
|
||||||
|
- [ ] Deploy feature
|
||||||
|
- [ ] Trigger in-app notification
|
||||||
|
- [ ] Publish changelog
|
||||||
|
- [ ] Update support docs (if needed)
|
||||||
|
|
||||||
|
**Day +1 to +3: Monitor**
|
||||||
|
|
||||||
|
- [ ] Check for support tickets
|
||||||
|
- [ ] Monitor feature adoption
|
||||||
|
- [ ] Address any issues
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Launch Metrics Dashboard
|
||||||
|
|
||||||
|
### Leading Indicators (Track Daily)
|
||||||
|
|
||||||
|
| Metric | Target | Day 1 | Day 3 | Day 7 |
|
||||||
|
|--------|--------|-------|-------|-------|
|
||||||
|
| Landing page visitors | 5,000 | | | |
|
||||||
|
| Demo requests | 100 | | | |
|
||||||
|
| Free trial signups | 200 | | | |
|
||||||
|
| MQLs generated | 150 | | | |
|
||||||
|
| Pipeline created ($) | $500k | | | |
|
||||||
|
|
||||||
|
### Lagging Indicators (Track Weekly)
|
||||||
|
|
||||||
|
| Metric | Target | Week 1 | Week 2 | Week 4 |
|
||||||
|
|--------|--------|--------|--------|--------|
|
||||||
|
| SQLs generated | 30 | | | |
|
||||||
|
| Demos completed | 50 | | | |
|
||||||
|
| Deals closed (#) | 5 | | | |
|
||||||
|
| Revenue ($) | $100k | | | |
|
||||||
|
| Feature adoption (%) | 40% | | | |
|
||||||
|
|
||||||
|
### Channel Performance
|
||||||
|
|
||||||
|
| Channel | Spend | MQLs | CPL | Pipeline | ROI |
|
||||||
|
|---------|-------|------|-----|----------|-----|
|
||||||
|
| LinkedIn Ads | $10k | | | | |
|
||||||
|
| Google Ads | $5k | | | | |
|
||||||
|
| Email | $0 | | | | |
|
||||||
|
| Organic | $0 | | | | |
|
||||||
|
| Webinar | $2k | | | | |
|
||||||
|
| **Total** | **$17k** | | | | |
|
||||||
|
|
||||||
|
### Post-Launch Report Template
|
||||||
|
|
||||||
|
```
|
||||||
|
LAUNCH: [Product/Feature Name]
|
||||||
|
DATE: [Launch Date]
|
||||||
|
OWNER: [PMM Name]
|
||||||
|
|
||||||
|
EXECUTIVE SUMMARY:
|
||||||
|
- Goal: $500k pipeline in 30 days
|
||||||
|
- Actual: $[X] pipeline (X% of goal)
|
||||||
|
- Status: ✅ On Track / ⚠️ Behind / ❌ Missed
|
||||||
|
|
||||||
|
KEY RESULTS:
|
||||||
|
| Metric | Goal | Actual | % of Goal |
|
||||||
|
|--------------|---------|---------|-----------|
|
||||||
|
| MQLs | 150 | | |
|
||||||
|
| SQLs | 30 | | |
|
||||||
|
| Pipeline | $500k | | |
|
||||||
|
| Feature Adoption | 40% | | |
|
||||||
|
|
||||||
|
TOP PERFORMING:
|
||||||
|
1. [Channel/Tactic] - [Result]
|
||||||
|
2. [Channel/Tactic] - [Result]
|
||||||
|
|
||||||
|
UNDERPERFORMING:
|
||||||
|
1. [Channel/Tactic] - [Result] - [Action taken]
|
||||||
|
|
||||||
|
LEARNINGS:
|
||||||
|
1. [What worked and why]
|
||||||
|
2. [What didn't work and why]
|
||||||
|
3. [What we'd do differently]
|
||||||
|
|
||||||
|
NEXT STEPS:
|
||||||
|
1. [Action item] - Owner - Due date
|
||||||
|
2. [Action item] - Owner - Due date
|
||||||
|
```
|
||||||
446
references/messaging-templates.md
Normal file
446
references/messaging-templates.md
Normal file
@@ -0,0 +1,446 @@
|
|||||||
|
# Messaging Templates
|
||||||
|
|
||||||
|
Ready-to-use messaging frameworks for different personas and contexts.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Table of Contents
|
||||||
|
|
||||||
|
- [Value Proposition Templates](#value-proposition-templates)
|
||||||
|
- [Persona-Specific Messaging](#persona-specific-messaging)
|
||||||
|
- [Competitive Messaging](#competitive-messaging)
|
||||||
|
- [Channel-Specific Copy](#channel-specific-copy)
|
||||||
|
- [Objection Handling Scripts](#objection-handling-scripts)
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Value Proposition Templates
|
||||||
|
|
||||||
|
### One-Liner Formula
|
||||||
|
|
||||||
|
Template: `[Product] helps [Target Customer] [Achieve Goal] by [Unique Approach]`
|
||||||
|
|
||||||
|
**Examples:**
|
||||||
|
|
||||||
|
```
|
||||||
|
B2B SaaS:
|
||||||
|
"Acme helps mid-market SaaS teams ship 2x faster by automating
|
||||||
|
project workflows with AI."
|
||||||
|
|
||||||
|
Enterprise:
|
||||||
|
"Acme helps Fortune 500 companies reduce operational costs by 40%
|
||||||
|
through intelligent process automation."
|
||||||
|
|
||||||
|
SMB:
|
||||||
|
"Acme helps small businesses save 10 hours per week by automating
|
||||||
|
their daily tasks."
|
||||||
|
```
|
||||||
|
|
||||||
|
### Elevator Pitch (30 Seconds)
|
||||||
|
|
||||||
|
Template:
|
||||||
|
```
|
||||||
|
You know how [target customer] struggles with [pain point]?
|
||||||
|
|
||||||
|
[Product] is a [category] that [key differentiator].
|
||||||
|
|
||||||
|
Unlike [alternatives], we [unique value].
|
||||||
|
|
||||||
|
Our customers see [specific outcome] within [timeframe].
|
||||||
|
```
|
||||||
|
|
||||||
|
**Example:**
|
||||||
|
|
||||||
|
```
|
||||||
|
You know how engineering teams struggle with slow code reviews
|
||||||
|
that delay releases?
|
||||||
|
|
||||||
|
Acme is an AI code review platform that catches bugs before
|
||||||
|
they reach production.
|
||||||
|
|
||||||
|
Unlike manual reviews, we analyze every PR in under 2 minutes
|
||||||
|
with 95% accuracy.
|
||||||
|
|
||||||
|
Our customers ship 40% faster within their first month.
|
||||||
|
```
|
||||||
|
|
||||||
|
### Messaging Hierarchy
|
||||||
|
|
||||||
|
```
|
||||||
|
LEVEL 1: HEADLINE (5-7 words)
|
||||||
|
"Ship faster with AI-powered automation"
|
||||||
|
|
||||||
|
LEVEL 2: SUBHEAD (1 sentence)
|
||||||
|
"Acme automates your workflows so your team can focus on what matters."
|
||||||
|
|
||||||
|
LEVEL 3: KEY BENEFITS (3-4 bullets)
|
||||||
|
• Save 10+ hours per week on manual tasks
|
||||||
|
• Reduce errors by 80% with AI validation
|
||||||
|
• Deploy changes 3x faster with automated testing
|
||||||
|
• Scale operations without adding headcount
|
||||||
|
|
||||||
|
LEVEL 4: FEATURES → VALUE
|
||||||
|
• AI Automation → Eliminates repetitive work → Save $50k/year
|
||||||
|
• Real-time Sync → No version conflicts → 50% fewer errors
|
||||||
|
• Integrations → Connect existing tools → 2-hour setup
|
||||||
|
```
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Persona-Specific Messaging
|
||||||
|
|
||||||
|
### Economic Buyer (VP/Director/C-Level)
|
||||||
|
|
||||||
|
**Primary concerns:** ROI, business outcomes, risk mitigation
|
||||||
|
|
||||||
|
**Messaging principles:**
|
||||||
|
- Lead with business impact ($, %, time)
|
||||||
|
- Show ROI within 6-12 months
|
||||||
|
- Reference similar companies
|
||||||
|
- Address risk (security, implementation)
|
||||||
|
|
||||||
|
**Template:**
|
||||||
|
|
||||||
|
```
|
||||||
|
HEADLINE: [Business outcome] in [timeframe]
|
||||||
|
|
||||||
|
OPENING:
|
||||||
|
"[Role at similar company] was spending [hours/dollars] on [problem].
|
||||||
|
After implementing [Product], they achieved [specific result]."
|
||||||
|
|
||||||
|
KEY POINTS:
|
||||||
|
• [Metric] improvement in [area] (e.g., "40% reduction in manual work")
|
||||||
|
• ROI: [X]x return within [timeframe]
|
||||||
|
• Implementation: [timeframe] with [level] of effort
|
||||||
|
• Risk: [How you mitigate concerns]
|
||||||
|
|
||||||
|
CTA: "See how [similar company] achieved [result] →"
|
||||||
|
```
|
||||||
|
|
||||||
|
**Example email:**
|
||||||
|
|
||||||
|
```
|
||||||
|
Subject: How Stripe reduced deployment time by 60%
|
||||||
|
|
||||||
|
Hi [Name],
|
||||||
|
|
||||||
|
The VP of Engineering at a company similar to yours was spending
|
||||||
|
40 hours per week on code review bottlenecks.
|
||||||
|
|
||||||
|
After implementing Acme, they:
|
||||||
|
• Reduced review time by 60%
|
||||||
|
• Caught 3x more bugs before production
|
||||||
|
• Shipped new features 2 weeks faster
|
||||||
|
|
||||||
|
Would a 15-minute call to explore if similar results are possible
|
||||||
|
for [Company] make sense?
|
||||||
|
```
|
||||||
|
|
||||||
|
### Technical Buyer (Engineer/Architect)
|
||||||
|
|
||||||
|
**Primary concerns:** Technical fit, security, integration, vendor lock-in
|
||||||
|
|
||||||
|
**Messaging principles:**
|
||||||
|
- Lead with technical capabilities
|
||||||
|
- Show architecture and security details
|
||||||
|
- Demonstrate easy integration
|
||||||
|
- Provide technical documentation
|
||||||
|
|
||||||
|
**Template:**
|
||||||
|
|
||||||
|
```
|
||||||
|
HEADLINE: [Technical capability] for [their stack]
|
||||||
|
|
||||||
|
OPENING:
|
||||||
|
"Built for [their technology environment] with [key technical feature]."
|
||||||
|
|
||||||
|
KEY POINTS:
|
||||||
|
• Architecture: [how it works technically]
|
||||||
|
• Security: [certifications, compliance, encryption]
|
||||||
|
• Integration: [specific integrations with their tools]
|
||||||
|
• Performance: [benchmarks, latency, uptime]
|
||||||
|
|
||||||
|
CTA: "Read the technical whitepaper →" or "See the API docs →"
|
||||||
|
```
|
||||||
|
|
||||||
|
**Example:**
|
||||||
|
|
||||||
|
```
|
||||||
|
Subject: SOC 2 Type II compliant with 99.99% uptime
|
||||||
|
|
||||||
|
Hi [Name],
|
||||||
|
|
||||||
|
I noticed [Company] uses Kubernetes for container orchestration.
|
||||||
|
|
||||||
|
Acme integrates natively with K8s with:
|
||||||
|
• Single-line Helm chart deployment
|
||||||
|
• mTLS encryption for all traffic
|
||||||
|
• SOC 2 Type II + GDPR compliant
|
||||||
|
• 99.99% uptime SLA with $10k credit guarantee
|
||||||
|
|
||||||
|
Here's our architecture diagram: [link]
|
||||||
|
|
||||||
|
Worth a quick technical review?
|
||||||
|
```
|
||||||
|
|
||||||
|
### End User (Manager/Individual Contributor)
|
||||||
|
|
||||||
|
**Primary concerns:** Ease of use, daily workflow, learning curve
|
||||||
|
|
||||||
|
**Messaging principles:**
|
||||||
|
- Lead with time savings
|
||||||
|
- Show product in action (demo, screenshots)
|
||||||
|
- Emphasize simplicity
|
||||||
|
- Include peer testimonials
|
||||||
|
|
||||||
|
**Template:**
|
||||||
|
|
||||||
|
```
|
||||||
|
HEADLINE: [Daily benefit] in [time to value]
|
||||||
|
|
||||||
|
OPENING:
|
||||||
|
"Imagine [desired outcome] without [pain point]."
|
||||||
|
|
||||||
|
KEY POINTS:
|
||||||
|
• Get started in [timeframe] (no training required)
|
||||||
|
• Save [hours] every [timeframe]
|
||||||
|
• [Feature] makes [task] effortless
|
||||||
|
• Loved by [peer companies/roles]
|
||||||
|
|
||||||
|
CTA: "Try free for 14 days →"
|
||||||
|
```
|
||||||
|
|
||||||
|
**Example:**
|
||||||
|
|
||||||
|
```
|
||||||
|
Subject: Spend less time in meetings, more time building
|
||||||
|
|
||||||
|
Hi [Name],
|
||||||
|
|
||||||
|
What if your weekly status meetings could run themselves?
|
||||||
|
|
||||||
|
Acme automatically:
|
||||||
|
• Collects updates from your team (no nagging)
|
||||||
|
• Creates visual progress reports (no spreadsheets)
|
||||||
|
• Flags blockers before they become problems
|
||||||
|
|
||||||
|
Teams like [Company A] and [Company B] love it.
|
||||||
|
|
||||||
|
Start your free trial: [link]
|
||||||
|
```
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Competitive Messaging
|
||||||
|
|
||||||
|
### "Why Us vs. Competitor A" Framework
|
||||||
|
|
||||||
|
```
|
||||||
|
OPENING (acknowledge competition):
|
||||||
|
"Both [Product] and [Competitor A] help teams with [general category].
|
||||||
|
Here's what sets us apart:"
|
||||||
|
|
||||||
|
DIFFERENTIATORS (3-4 key points):
|
||||||
|
|
||||||
|
1. [Your advantage] vs. [Their limitation]
|
||||||
|
"Our AI catches 95% of bugs vs. their rule-based 60% coverage"
|
||||||
|
|
||||||
|
2. [Your advantage] vs. [Their limitation]
|
||||||
|
"Get started in 2 hours vs. their 2-week implementation"
|
||||||
|
|
||||||
|
3. [Your advantage] vs. [Their limitation]
|
||||||
|
"$50/user vs. their $150/user at scale"
|
||||||
|
|
||||||
|
PROOF POINT:
|
||||||
|
"[Customer] switched from [Competitor A] to us and saw [result]"
|
||||||
|
|
||||||
|
CTA:
|
||||||
|
"See a side-by-side comparison →"
|
||||||
|
```
|
||||||
|
|
||||||
|
### Competitive Positioning Statements
|
||||||
|
|
||||||
|
**When they're the market leader:**
|
||||||
|
|
||||||
|
```
|
||||||
|
"[Competitor] built the category, but it was designed for [old paradigm].
|
||||||
|
[Product] is purpose-built for [new reality] with [key differentiators]."
|
||||||
|
```
|
||||||
|
|
||||||
|
**When they're cheaper:**
|
||||||
|
|
||||||
|
```
|
||||||
|
"[Competitor] costs less upfront, but teams spend [X hours] working
|
||||||
|
around limitations. [Product] pays for itself in [timeframe] through
|
||||||
|
[specific efficiency gains]."
|
||||||
|
```
|
||||||
|
|
||||||
|
**When they have more features:**
|
||||||
|
|
||||||
|
```
|
||||||
|
"[Competitor] tries to do everything. [Product] focuses on doing
|
||||||
|
[core use case] exceptionally well. Our customers tell us they only
|
||||||
|
use 20% of [Competitor's] features anyway."
|
||||||
|
```
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Channel-Specific Copy
|
||||||
|
|
||||||
|
### Landing Page
|
||||||
|
|
||||||
|
**Above the fold:**
|
||||||
|
```
|
||||||
|
[HEADLINE - 5-7 words, benefit-focused]
|
||||||
|
Ship faster with AI-powered automation
|
||||||
|
|
||||||
|
[SUBHEAD - 1 sentence expanding on value]
|
||||||
|
Acme automates your workflows so your team can focus on what matters.
|
||||||
|
|
||||||
|
[CTA - Action-oriented]
|
||||||
|
Start Free Trial | Book Demo
|
||||||
|
```
|
||||||
|
|
||||||
|
**Social proof bar:**
|
||||||
|
```
|
||||||
|
Trusted by 5,000+ teams including [Logo] [Logo] [Logo] [Logo]
|
||||||
|
```
|
||||||
|
|
||||||
|
### Email Subject Lines
|
||||||
|
|
||||||
|
**High performers:**
|
||||||
|
- "How [Similar Company] achieved [result]"
|
||||||
|
- "[Name], quick question about [their challenge]"
|
||||||
|
- "Re: [topic they care about]" (for follow-ups)
|
||||||
|
- "[Specific number]% improvement in [metric]"
|
||||||
|
|
||||||
|
**Avoid:**
|
||||||
|
- "Quick sync?"
|
||||||
|
- "Following up..."
|
||||||
|
- "Just checking in"
|
||||||
|
- ALL CAPS or excessive punctuation!!!
|
||||||
|
|
||||||
|
### LinkedIn Ads
|
||||||
|
|
||||||
|
**Format: Single image or carousel**
|
||||||
|
|
||||||
|
```
|
||||||
|
HEADLINE (70 chars max):
|
||||||
|
"Cut code review time by 60%"
|
||||||
|
|
||||||
|
BODY (150 chars recommended):
|
||||||
|
"AI-powered code reviews that catch bugs before production.
|
||||||
|
Trusted by engineering teams at Stripe and Shopify.
|
||||||
|
Try free →"
|
||||||
|
|
||||||
|
CTA: Learn More / Try Free / Get Demo
|
||||||
|
```
|
||||||
|
|
||||||
|
### Google Ads
|
||||||
|
|
||||||
|
**Search ad format:**
|
||||||
|
|
||||||
|
```
|
||||||
|
Headline 1 (30 chars): AI Code Review Platform
|
||||||
|
Headline 2 (30 chars): Ship 40% Faster
|
||||||
|
Headline 3 (30 chars): Free 14-Day Trial
|
||||||
|
|
||||||
|
Description (90 chars):
|
||||||
|
Catch bugs before production. Trusted by 5,000+ teams.
|
||||||
|
Start your free trial today.
|
||||||
|
```
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Objection Handling Scripts
|
||||||
|
|
||||||
|
### Price Objection
|
||||||
|
|
||||||
|
**"It's too expensive"**
|
||||||
|
|
||||||
|
```
|
||||||
|
ACKNOWLEDGE: "I understand budget is a concern."
|
||||||
|
|
||||||
|
REFRAME: "Let me share how our customers think about it...
|
||||||
|
[Customer] was spending [X hours/dollars] on [problem] every month.
|
||||||
|
After implementing [Product], they saved [Y hours/dollars], paying
|
||||||
|
for the solution in [timeframe]."
|
||||||
|
|
||||||
|
QUESTION: "What would it be worth to your team to [achieve outcome]?"
|
||||||
|
|
||||||
|
ALTERNATIVE: "We also offer [smaller plan/annual discount] that might
|
||||||
|
work for your current budget. Would that help?"
|
||||||
|
```
|
||||||
|
|
||||||
|
### Competitor Objection
|
||||||
|
|
||||||
|
**"We're looking at [Competitor A] too"**
|
||||||
|
|
||||||
|
```
|
||||||
|
ACKNOWLEDGE: "That's smart to evaluate options. [Competitor A] is
|
||||||
|
a solid product."
|
||||||
|
|
||||||
|
DIFFERENTIATE: "The main differences customers tell us about:
|
||||||
|
1. [Your advantage] - [Competitor] doesn't offer this
|
||||||
|
2. [Your advantage] - Their approach is [different/older]
|
||||||
|
3. [Price/support/speed] - We're typically [X] better here"
|
||||||
|
|
||||||
|
PROOF: "[Customer] evaluated both and chose us because [reason]."
|
||||||
|
|
||||||
|
QUESTION: "What are the 2-3 things that matter most to you in
|
||||||
|
this decision?"
|
||||||
|
```
|
||||||
|
|
||||||
|
### Timing Objection
|
||||||
|
|
||||||
|
**"Not the right time"**
|
||||||
|
|
||||||
|
```
|
||||||
|
ACKNOWLEDGE: "I completely understand. Timing is everything."
|
||||||
|
|
||||||
|
EXPLORE: "Out of curiosity, what would need to change for this
|
||||||
|
to become a priority?"
|
||||||
|
|
||||||
|
FUTURE: "Would it make sense to schedule a brief call in [timeframe]
|
||||||
|
to revisit? I can share relevant updates without any pressure."
|
||||||
|
|
||||||
|
VALUE ADD: "In the meantime, I'll send over [relevant content] that
|
||||||
|
might be useful for when you're ready."
|
||||||
|
```
|
||||||
|
|
||||||
|
### Authority Objection
|
||||||
|
|
||||||
|
**"I need to check with my team/boss"**
|
||||||
|
|
||||||
|
```
|
||||||
|
ACKNOWLEDGE: "Of course, that makes sense."
|
||||||
|
|
||||||
|
SUPPORT: "What information would be most helpful for that conversation?
|
||||||
|
I can put together a one-pager with key points."
|
||||||
|
|
||||||
|
OFFER: "Would it help if I joined a brief call with [stakeholder]
|
||||||
|
to answer any technical/business questions directly?"
|
||||||
|
|
||||||
|
TIMELINE: "When do you think you'll have that conversation?
|
||||||
|
I can follow up with any additional materials beforehand."
|
||||||
|
```
|
||||||
|
|
||||||
|
### Technical Objection
|
||||||
|
|
||||||
|
**"Will this integrate with our stack?"**
|
||||||
|
|
||||||
|
```
|
||||||
|
ACKNOWLEDGE: "Great question - integration is critical."
|
||||||
|
|
||||||
|
CONFIRM: "What are the main tools you need to connect with?
|
||||||
|
[Listen and take notes]"
|
||||||
|
|
||||||
|
ANSWER: "We have native integrations with [tools]. For [tool],
|
||||||
|
we use [API/webhook/Zapier]. Here's our integration docs: [link]"
|
||||||
|
|
||||||
|
PROOF: "[Similar company] uses a similar stack and got integrated
|
||||||
|
in [timeframe]."
|
||||||
|
|
||||||
|
DEMO: "Want me to show you exactly how the integration works
|
||||||
|
in a quick demo?"
|
||||||
|
```
|
||||||
279
references/positioning-frameworks.md
Normal file
279
references/positioning-frameworks.md
Normal file
@@ -0,0 +1,279 @@
|
|||||||
|
# Positioning Frameworks
|
||||||
|
|
||||||
|
Strategic positioning methodologies for B2B SaaS products.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Table of Contents
|
||||||
|
|
||||||
|
- [April Dunford Positioning](#april-dunford-positioning)
|
||||||
|
- [Geoffrey Moore Positioning](#geoffrey-moore-positioning)
|
||||||
|
- [Positioning Validation](#positioning-validation)
|
||||||
|
- [Competitive Positioning Map](#competitive-positioning-map)
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## April Dunford Positioning
|
||||||
|
|
||||||
|
### The 5-Step Process
|
||||||
|
|
||||||
|
Execute positioning using April Dunford's "Obviously Awesome" methodology:
|
||||||
|
|
||||||
|
1. List competitive alternatives (what customers would use instead)
|
||||||
|
2. Isolate unique attributes (features only you have)
|
||||||
|
3. Map attributes to value (why each attribute matters)
|
||||||
|
4. Define best-fit customers (who cares most about this value)
|
||||||
|
5. Choose market category (where you compete)
|
||||||
|
6. **Validation:** Best-fit customers articulate your value unprompted
|
||||||
|
|
||||||
|
### Step 1: Competitive Alternatives
|
||||||
|
|
||||||
|
Document what customers do without your product:
|
||||||
|
|
||||||
|
| Alternative Type | Examples | How They Solve It |
|
||||||
|
|------------------|----------|-------------------|
|
||||||
|
| Direct competitor | Competitor A, B | Same category, different approach |
|
||||||
|
| Adjacent solution | Spreadsheets, email | Manual workaround |
|
||||||
|
| Build in-house | Custom development | Internal solution |
|
||||||
|
| Do nothing | Ignore problem | Accept status quo |
|
||||||
|
|
||||||
|
**Interview Questions:**
|
||||||
|
- "Before using us, how did you handle this?"
|
||||||
|
- "What alternatives did you evaluate?"
|
||||||
|
- "What would you switch to if we disappeared?"
|
||||||
|
|
||||||
|
### Step 2: Unique Attributes
|
||||||
|
|
||||||
|
Identify capabilities competitors lack:
|
||||||
|
|
||||||
|
```
|
||||||
|
Attribute Audit:
|
||||||
|
1. Feature: [Real-time collaboration]
|
||||||
|
- Competitor A: No (async only)
|
||||||
|
- Competitor B: Partial (limited to 5 users)
|
||||||
|
- You: Yes (unlimited users, 50ms sync)
|
||||||
|
→ Unique: Yes
|
||||||
|
|
||||||
|
2. Feature: [AI automation]
|
||||||
|
- Competitor A: No
|
||||||
|
- Competitor B: No
|
||||||
|
- You: Yes (3 AI models)
|
||||||
|
→ Unique: Yes
|
||||||
|
|
||||||
|
3. Feature: [Integrations]
|
||||||
|
- Competitor A: 500+
|
||||||
|
- Competitor B: 200+
|
||||||
|
- You: 100
|
||||||
|
→ Unique: No (table stakes)
|
||||||
|
```
|
||||||
|
|
||||||
|
### Step 3: Attribute-Value Mapping
|
||||||
|
|
||||||
|
Connect features to business outcomes:
|
||||||
|
|
||||||
|
| Attribute | Value Enabled | Customer Outcome |
|
||||||
|
|-----------|--------------|------------------|
|
||||||
|
| Real-time sync | No version conflicts | 50% fewer errors |
|
||||||
|
| AI automation | Eliminates manual work | Save 10 hrs/week |
|
||||||
|
| One-click deploy | Faster releases | Ship 2x faster |
|
||||||
|
|
||||||
|
**Value Statement Formula:**
|
||||||
|
`[Feature] enables [Value] so customers achieve [Outcome]`
|
||||||
|
|
||||||
|
### Step 4: Best-Fit Customers
|
||||||
|
|
||||||
|
Define who values your unique attributes most:
|
||||||
|
|
||||||
|
```
|
||||||
|
Best-Fit Profile:
|
||||||
|
- Company size: 200-2000 employees
|
||||||
|
- Industry: SaaS, Professional Services
|
||||||
|
- Pain: Distributed teams, collaboration bottlenecks
|
||||||
|
- Evidence:
|
||||||
|
- Fastest sales cycles (45 days vs. 75 avg)
|
||||||
|
- Lowest churn (3% vs. 8% avg)
|
||||||
|
- Highest NPS (65 vs. 45 avg)
|
||||||
|
```
|
||||||
|
|
||||||
|
### Step 5: Market Category
|
||||||
|
|
||||||
|
Choose competitive frame:
|
||||||
|
|
||||||
|
| Strategy | When to Use | Risk Level |
|
||||||
|
|----------|-------------|------------|
|
||||||
|
| Head-to-head | Strong product, big budget | Medium |
|
||||||
|
| Niche domination | Unique for segment | Low |
|
||||||
|
| Category creation | True innovation, deep pockets | High |
|
||||||
|
|
||||||
|
**Decision Framework:**
|
||||||
|
- Can you win head-to-head? → Head-to-head
|
||||||
|
- Can you dominate a niche? → Niche
|
||||||
|
- Is the market undefined? → Category creation
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Geoffrey Moore Positioning
|
||||||
|
|
||||||
|
### Crossing the Chasm Framework
|
||||||
|
|
||||||
|
Position for technology adoption lifecycle:
|
||||||
|
|
||||||
|
```
|
||||||
|
Technology Adoption Curve:
|
||||||
|
Innovators (2.5%) → Early Adopters (13.5%) → Early Majority (34%)
|
||||||
|
↑
|
||||||
|
THE CHASM
|
||||||
|
```
|
||||||
|
|
||||||
|
### Positioning Statement Template
|
||||||
|
|
||||||
|
```
|
||||||
|
FOR [target customer]
|
||||||
|
WHO [statement of need or opportunity]
|
||||||
|
THE [product name] IS A [product category]
|
||||||
|
THAT [key benefit/reason to buy]
|
||||||
|
UNLIKE [primary competitive alternative]
|
||||||
|
OUR PRODUCT [primary differentiation]
|
||||||
|
```
|
||||||
|
|
||||||
|
**Example:**
|
||||||
|
```
|
||||||
|
FOR mid-market SaaS companies with distributed engineering teams
|
||||||
|
WHO struggle with coordination across time zones
|
||||||
|
THE Acme Platform IS A real-time collaboration workspace
|
||||||
|
THAT eliminates version conflicts and communication delays
|
||||||
|
UNLIKE Slack and email which create information silos
|
||||||
|
OUR PRODUCT provides unified project context with AI-powered summaries
|
||||||
|
```
|
||||||
|
|
||||||
|
### Whole Product Concept
|
||||||
|
|
||||||
|
Define complete solution for target segment:
|
||||||
|
|
||||||
|
| Layer | Components | Your Coverage |
|
||||||
|
|-------|------------|---------------|
|
||||||
|
| Generic | Core product | 100% |
|
||||||
|
| Expected | Basic integrations, support | 90% |
|
||||||
|
| Augmented | Training, consulting, custom work | 60% |
|
||||||
|
| Potential | Future roadmap, ecosystem | 30% |
|
||||||
|
|
||||||
|
**Gap Analysis:**
|
||||||
|
- What's missing for complete solution?
|
||||||
|
- Which partners can fill gaps?
|
||||||
|
- What must you build vs. buy vs. partner?
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Positioning Validation
|
||||||
|
|
||||||
|
### Customer Interview Protocol
|
||||||
|
|
||||||
|
Validate positioning with target customers:
|
||||||
|
|
||||||
|
1. Schedule 15-20 minute calls with 10+ target customers
|
||||||
|
2. Ask open-ended questions (no leading)
|
||||||
|
3. Document exact language used
|
||||||
|
4. Look for patterns across interviews
|
||||||
|
5. **Validation:** 7+ of 10 describe value similarly
|
||||||
|
|
||||||
|
**Interview Script:**
|
||||||
|
|
||||||
|
```
|
||||||
|
Opening (2 min):
|
||||||
|
"Thanks for your time. I want to understand how you think about
|
||||||
|
[product category] and your experience with our product."
|
||||||
|
|
||||||
|
Questions (10 min):
|
||||||
|
1. "How would you describe [Product] to a colleague?"
|
||||||
|
2. "What problem does [Product] solve for you?"
|
||||||
|
3. "What alternatives did you consider?"
|
||||||
|
4. "Why did you choose us over [alternative]?"
|
||||||
|
5. "What would make you stop using us?"
|
||||||
|
|
||||||
|
Closing (3 min):
|
||||||
|
"Is there anything else you'd like to share?"
|
||||||
|
```
|
||||||
|
|
||||||
|
### Quantitative Validation
|
||||||
|
|
||||||
|
Test messaging through A/B experiments:
|
||||||
|
|
||||||
|
| Test | Control | Variant | Winner Criteria |
|
||||||
|
|------|---------|---------|-----------------|
|
||||||
|
| Landing page headline | Old positioning | New positioning | +20% conversion |
|
||||||
|
| Ad copy | Feature-focused | Value-focused | +15% CTR |
|
||||||
|
| Email subject | Generic | Personalized | +25% open rate |
|
||||||
|
|
||||||
|
**Sample Size Calculator:**
|
||||||
|
- Baseline conversion: 3%
|
||||||
|
- Minimum detectable effect: 20% relative lift
|
||||||
|
- Statistical power: 80%
|
||||||
|
- Required sample: ~2,500 per variant
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Competitive Positioning Map
|
||||||
|
|
||||||
|
### 2x2 Matrix Construction
|
||||||
|
|
||||||
|
Create visual positioning map:
|
||||||
|
|
||||||
|
```
|
||||||
|
HIGH PRICE
|
||||||
|
│
|
||||||
|
Enterprise │ Premium
|
||||||
|
(Salesforce) │ (You?)
|
||||||
|
│
|
||||||
|
────────────────────┼──────────────────
|
||||||
|
LOW │ HIGH
|
||||||
|
EASE OF USE │ EASE OF USE
|
||||||
|
│
|
||||||
|
Legacy │ Self-Serve
|
||||||
|
(Oracle) │ (Notion)
|
||||||
|
│
|
||||||
|
LOW PRICE
|
||||||
|
```
|
||||||
|
|
||||||
|
### Axis Selection
|
||||||
|
|
||||||
|
Choose dimensions that highlight your advantage:
|
||||||
|
|
||||||
|
| Good Axes | Why |
|
||||||
|
|-----------|-----|
|
||||||
|
| Ease of use vs. Power | If you're easiest to use |
|
||||||
|
| Speed vs. Accuracy | If you're fastest |
|
||||||
|
| Price vs. Features | If you're best value |
|
||||||
|
| Specialization vs. Breadth | If you own a niche |
|
||||||
|
|
||||||
|
| Bad Axes | Why |
|
||||||
|
|----------|-----|
|
||||||
|
| Quality vs. Price | Everyone claims quality |
|
||||||
|
| Innovation vs. Stability | Subjective, hard to prove |
|
||||||
|
| Customer vs. Product focus | Not differentiating |
|
||||||
|
|
||||||
|
### Positioning Map Template
|
||||||
|
|
||||||
|
```
|
||||||
|
Market Category: [Your Category]
|
||||||
|
Date: [Month Year]
|
||||||
|
|
||||||
|
Axes:
|
||||||
|
- X-axis: [Dimension 1] (Low → High)
|
||||||
|
- Y-axis: [Dimension 2] (Low → High)
|
||||||
|
|
||||||
|
Quadrants:
|
||||||
|
- Top-left: [Quadrant description]
|
||||||
|
- Top-right: [Quadrant description] ← Your target
|
||||||
|
- Bottom-left: [Quadrant description]
|
||||||
|
- Bottom-right: [Quadrant description]
|
||||||
|
|
||||||
|
Competitors:
|
||||||
|
1. [Competitor A]: Position (X, Y), Why
|
||||||
|
2. [Competitor B]: Position (X, Y), Why
|
||||||
|
3. [You]: Position (X, Y), Why you win
|
||||||
|
|
||||||
|
Strategic Implications:
|
||||||
|
- Attack: [How to position against Competitor A]
|
||||||
|
- Defend: [How to protect against Competitor B]
|
||||||
|
- Differentiate: [Your unique positioning claim]
|
||||||
|
```
|
||||||
Reference in New Issue
Block a user