Purpose
Produce an elite-tier go-to-market strategy document that identifies the market wedge, selects and scores beachhead segments, designs channel strategy with unit economics, sequences launch phases with gates and kill criteria, positions against competitors, and defines success metrics with explicit failure conditions — a GTM strategy a PM cannot produce unaided. The output is a GTM Strategy Document — not a launch checklist, but a structural argument for how to win the first customers and compound from there.
When to Use / When NOT to Use
Use this skill when:
- Launching a new product or feature into a market (new or existing)
- Entering a new market with an existing product
- Pivoting an existing product's GTM motion (e.g., sales-led to product-led)
- Evaluating whether a market entry is viable (go/no-go decision)
- Designing channel strategy with unit economics constraints
- Planning launch sequencing with explicit gates and kill criteria
- Assessing launch readiness before committing budget
Do NOT use this skill when:
- You need a competitive analysis without a launch plan (use Competitive Market Analysis skill)
- You need a product specification (use Specification Writing skill)
- You need to validate a problem exists before solving it (use Problem Framing skill)
- You need to run experiments to validate assumptions (use Metric Design & Experimentation skill)
- You need a marketing campaign plan (this produces strategy, not execution assets)
- The product is already at scale and you need retention/growth optimization (this is for market entry, not market defense)
Anti-inputs (what this skill does NOT handle):
- Marketing copy, email sequences, or campaign assets (downstream of GTM strategy)
- Pricing model design in isolation (pricing is one dimension of channel economics here, not the sole output)
- Organizational design for GTM teams (team structure follows strategy, not the other way around)
- International expansion playbooks (this covers market entry logic; localization is a separate discipline)
Context Gate (Step -1: Is GTM Strategy the Right Artifact?)
Before applying any framework, verify that a GTM strategy document is what the situation actually needs. The most common failure mode is producing an excellent GTM strategy for a product that shouldn't be launched yet.
Run these checks BEFORE proceeding:
| Check |
Question |
If NO → Redirect |
| Problem validated? |
Has the problem been validated with ≥5 target users? |
→ Problem Framing skill first. A GTM strategy for an unvalidated problem is a plan to efficiently deliver something nobody wants. |
| Product exists or is specced? |
Is there a product, prototype, or detailed spec to launch? |
→ Specification Writing skill first. GTM without a product is strategy theater. |
| Market is external? |
Is the target market external customers, not internal adoption? |
→ For internal rollout (enterprise feature adoption, internal tool deployment), GTM frameworks over-engineer the problem. Use a simpler adoption playbook. |
| Competitive landscape known? |
Do you know who the alternatives are (including "do nothing")? |
→ Run Competitive Market Analysis skill first, or do lightweight competitor scan. GTM positioning requires knowing what you're positioning against. |
| Decision authority exists? |
Is there someone who can act on this GTM strategy? |
→ If this is exploratory ("should we even consider this market?"), produce a market entry memo instead of a full GTM strategy. |
If all checks pass: Proceed to Framework Selection (Step 0).
If 1-2 checks fail: Note the gaps explicitly in the output header and proceed with caveats. Flag which sections are hypothetical.
If 3+ checks fail: Stop. The right artifact is not a GTM strategy. Recommend the upstream skill.
Reader Navigation
How to Read This Document
| Time Available |
What to Read |
What You'll Get |
| 5 minutes |
Executive Summary + Segment Selection table + Failure Criteria table |
Go/no-go signal, who to target first, when to stop |
| 15 minutes |
Above + Market Entry Thesis + Channel Strategy + Launch Sequence |
Full strategic logic: why this market, how to reach customers, what order |
| 30 minutes |
Full document |
Complete GTM strategy with all frameworks, unit economics, positioning, and self-critique |
| Your Role |
Start Here |
Focus On |
| VP/GM |
Executive Summary → Failure Criteria → Assumption Registry |
Decision: fund this GTM or not. Kill criteria tell you when to pull the plug. |
| PM |
Full document, sequentially |
You own execution. Every section has specific actions, timelines, and gates. |
| Marketing Lead |
Positioning section → Channel Strategy → Launch Sequence |
Positioning statement, channel selection, launch phases and messaging per phase. |
| Sales Lead |
Segment Selection → Channel Strategy (direct sales row) → Battlecards |
Who to call, what to say, how to handle objections. |
| Finance/Ops |
Channel Unit Economics → Launch Sequence (budget per phase) → Failure Criteria |
CAC, payback period, budget gates, kill thresholds. |
Notation Key
| Symbol |
Meaning |
| H / M / L |
Confidence level: H = >70% confident, M = 40-70%, L = <40% |
| (T1)-(T6) |
Evidence tier: T1 = behavioral data, T2 = primary research, T3 = expert analysis, T4 = industry reports, T5 = executive statements, T6 = inference |
| O→I→R→C→W |
Observation → Implication → Response → Confidence → Watch indicator (mandatory cascade for all recommendations) |
[POTENTIALLY STALE] |
Claim based on data >6 months old — verify before acting |
[EVIDENCE-LIMITED] |
Key conclusion rests on T4-T6 evidence only — validate with T1-T2 before committing budget |
| ████░░░░░░ |
Progress bar showing relative strength (1-10 scale) |
| ✅ / ⚠️ / ❌ |
Gate passed / gate at risk / gate failed |
Format Rules (Read First)
These rules govern every output produced by this codex. They are quality enforcement mechanisms, not style preferences.
Take positions. Never hedge with weasel words. "Likely," "may," "could," and "seems" are banned from conclusions. Flag uncertainty with explicit confidence levels: H (>70% confident), M (40-70%), L (<40%). Example: "The beachhead segment is 10-50 person design agencies hitting Figma collaboration limits (H)" not "SMBs could be a good target market."
Per-cell evidence tier annotation is mandatory in all comparison matrices. Every cell in a segment scoring table, channel economics comparison, or positioning matrix must carry an inline evidence tier tag: (T1), (T2), (T3) etc. Where evidence is absent: (T6: inferred). A matrix with untagged cells is incomplete.
The O→I→R→C→W cascade applies to ALL strategic recommendations, not just final sections. Format: Observation [evidence tier] → Implication [mechanism] → Response [specific action + owner + timeline] → Confidence [H/M/L + assumption] → Watch Indicator [observable signal + threshold].
Begin with Framework Selection (Step 0) before applying any framework. Identify the stage (new market entry, expansion, feature launch, pivot); select the 3-4 load-bearing frameworks; note which to skip.
Contradictions between frameworks are signal, not noise. When two frameworks reach different conclusions (e.g., segment scoring says enterprise but channel economics says PLG/SMB), surface the contradiction explicitly and state which to weight more heavily and why.
Flag time-sensitive claims. Any claim based on data older than 6 months must carry [POTENTIALLY STALE — verify before presenting]. Market conditions change faster than competitive positions.
Flag thin-evidence conclusions. If a key strategic conclusion rests only on Tier 4-6 evidence, prepend it with [EVIDENCE-LIMITED: validate with Tier 1-2 before acting].
First reference to any framework includes a one-line explanation. Not everyone reading a GTM strategy knows what "PLG" or "CAC" or "beachhead" means. Example: "Product-led growth (PLG) — users adopt the product through self-serve trial before any sales contact." This makes the document navigable by non-creators.
The Executive Summary uses zero framework jargon. A VP who has never heard of "beachhead strategy" or "CAC payback period" must be able to read the Executive Summary and make a decision. Framework terms appear in the body, not the summary.
Output Template (Mandatory Document Skeleton)
Every GTM Strategy Document MUST follow this exact structure. Copy this skeleton and fill it in. Do not reorder sections, skip sections, or invent new top-level sections. If a framework was skipped in Step 0, note "Skipped — not load-bearing for this stage" in that section.
# GTM Strategy: [Product — e.g., "Vanta Analytics Self-Serve Launch"]
> **Date:** [YYYY-MM-DD] | **Stage:** [new_market_entry / existing_market_expansion / feature_launch / pivot] | **Confidence band:** [Overall H/M/L] | **Staleness window:** [Date after which key claims need revalidation]
---
## How to Read This Document
[Reader Navigation table — by time available and by role. See Reader Navigation section above.]
## Notation Key
[Symbol definitions table. See Notation Key above.]
---
## Executive Summary
[≤300 words. Zero jargon. A VP reads only this and decides whether to fund the GTM. Must answer: What are we launching? For whom? Why now? What's the entry point? What does success look like in 6 months? What kills this? Final sentence = the recommended action in bold.]
---
## Step 0: Framework Selection
| Stage | Primary frameworks (apply in full) | Supporting frameworks (scan only) | Skipped (why) |
|---|---|---|---|
| [e.g., "New market entry"] | [e.g., Market Entry Thesis, Segment Selection, Channel Strategy] | [e.g., Distribution & Growth Mechanics] | [e.g., "Competitive Positioning — no direct competitors yet"] |
---
## 1. Market Entry Thesis
### Why This Market
[Market selection rationale — size, growth, structural opportunity]
### Why Now (Timing Thesis)
| Timing Signal | Evidence | Confidence |
|--------------|----------|------------|
| [e.g., "Regulatory change creating demand"] | [specific evidence] (TX) | H/M/L |
| [e.g., "Incumbent distracted by platform migration"] | [specific evidence] (TX) | H/M/L |
| [e.g., "Cost curve crossing — AI makes X viable at Y price"] | [specific evidence] (TX) | H/M/L |
### The Wedge
[What is the specific gap in the incumbent's armor? What gives you disproportionate advantage in a specific segment? This is NOT "we're better" — it's "we can win THIS slice because of THIS structural advantage."]
### Wedge Defensibility Assessment
| Dimension | Assessment | Evidence |
|-----------|-----------|----------|
| Time to replicate | [months/years] | (TX) |
| Capital to replicate | [$X] | (TX) |
| Structural barrier | [what prevents copying — counter-positioning, data moat, regulatory, network effects] | (TX) |
| **Verdict** | [Durable moat / Temporary arbitrage / Speed-dependent] | H/M/L |
### Go/Wait/Pivot Decision Table
| Signal | Market Ready | Market NOT Ready |
|--------|-------------|-----------------|
| Product readiness | → **GO**: launch beachhead | → **WAIT**: build MVP, re-assess in [X weeks] |
| Product NOT ready | → **BUILD**: market is ready, accelerate product | → **PIVOT**: wrong market or wrong product |
---
## 2. Segment Selection & Prioritization
### Beachhead Candidates
| Segment | Description | Size (est.) | Evidence |
|---------|------------|-------------|----------|
| [Segment A] | [Specific enough to find 100 prospects by name] | [$ or # users] (TX) | [How you know this segment exists] |
| [Segment B] | [Same specificity] | [$ or #] (TX) | [Evidence] |
| [Segment C] | [Same specificity] | [$ or #] (TX) | [Evidence] |
### ICP Scoring Matrix
| Criterion | Weight | Segment A | Segment B | Segment C |
|-----------|:------:|:---------:|:---------:|:---------:|
| Acute pain (validated) | 25% | [1-5] (TX) | [1-5] (TX) | [1-5] (TX) |
| Willingness to pay | 20% | [1-5] (TX) | [1-5] (TX) | [1-5] (TX) |
| Accessibility (can you reach them?) | 20% | [1-5] (TX) | [1-5] (TX) | [1-5] (TX) |
| Reference-ability (will they tell others?) | 15% | [1-5] (TX) | [1-5] (TX) | [1-5] (TX) |
| Expansion potential (leads to adjacent segments?) | 10% | [1-5] (TX) | [1-5] (TX) | [1-5] (TX) |
| Competitive vacuum (incumbents weak here?) | 10% | [1-5] (TX) | [1-5] (TX) | [1-5] (TX) |
| **Weighted Score** | | **[X.X]** | **[X.X]** | **[X.X]** |
### Expansion Path
[Beachhead → Adjacent Segment 1 → Adjacent Segment 2 → Mainstream]
[For each transition: what evidence or milestone triggers expansion? What do you carry from the previous segment (references, product features, channel)?]
---
## 3. Channel Strategy with Unit Economics
### Channel Selection Matrix
| Channel | Segment Fit | CAC (est.) | Payback (mo.) | LTV/CAC | Scalability | Evidence |
|---------|:-----------:|:----------:|:-------------:|:-------:|:-----------:|:--------:|
| [Direct sales] | [H/M/L] | [$X] (TX) | [X mo.] (TX) | [X:1] (TX) | [H/M/L] | [source] |
| [PLG / self-serve] | [H/M/L] | [$X] (TX) | [X mo.] (TX) | [X:1] (TX) | [H/M/L] | [source] |
| [Content/SEO] | [H/M/L] | [$X] (TX) | [X mo.] (TX) | [X:1] (TX) | [H/M/L] | [source] |
| [Paid acquisition] | [H/M/L] | [$X] (TX) | [X mo.] (TX) | [X:1] (TX) | [H/M/L] | [source] |
| [Partnership/channel] | [H/M/L] | [$X] (TX) | [X mo.] (TX) | [X:1] (TX) | [H/M/L] | [source] |
| [Community] | [H/M/L] | [$X] (TX) | [X mo.] (TX) | [X:1] (TX) | [H/M/L] | [source] |
### Primary Channel Deep-Dive
[For the #1 selected channel: full conversion funnel, unit economics at each stage, evidence requirements before scaling budget]
### Channel Sequencing
| Phase | Channel | Budget | Success Criteria to Add Next Channel |
|-------|---------|--------|--------------------------------------|
| Phase 1 | [ONE channel] | [$X] | [Metric ≥ threshold, e.g., "CAC < $200 on 50+ conversions"] |
| Phase 2 | [Add second] | [$X] | [Metric ≥ threshold] |
| Phase 3 | [Add third] | [$X] | [Metric ≥ threshold] |
---
## 4. Launch Sequencing & Gating
### Phase Plan
| Phase | Duration | Audience | Gate Criteria (must ALL be true to proceed) | Kill Criteria (if ANY true, stop) |
|-------|----------|----------|----------------------------------------------|-----------------------------------|
| **Alpha** (internal) | [X weeks] | [Internal team, N users] | [List specific metrics] | [List specific thresholds] |
| **Closed Beta** (design partners) | [X weeks] | [N design partners] | [List specific metrics] | [List specific thresholds] |
| **Open Beta** (waitlist) | [X weeks] | [N users from waitlist] | [List specific metrics] | [List specific thresholds] |
| **GA** (general availability) | [X weeks] | [Target segment] | [List specific metrics] | [List specific thresholds] |
| **Scale** | [Ongoing] | [Expansion segments] | [List specific metrics] | [List specific thresholds] |
### Launch Risk Register
| Risk | Phase | Severity (1-5) | Probability (H/M/L) | Mitigation | Owner |
|------|-------|:--------------:|:--------------------:|------------|-------|
| [Risk 1] | [Phase] | [X] | [H/M/L] | [Specific action] | [Role] |
| [Risk 2] | [Phase] | [X] | [H/M/L] | [Specific action] | [Role] |
---
## 5. Competitive Positioning for Launch
### Positioning Statement
> For **[target customer]** who **[need/job-to-be-done]**, **[product]** is a **[market category]** that **[key benefit]**. Unlike **[primary alternative]**, we **[key differentiator]**.
### Battlecards (per competitor)
**vs. [Competitor A]:**
| They'll Say | You Say | Evidence |
|------------|---------|----------|
| "[Objection 1]" | "[Counter + proof point]" | (TX) |
| "[Objection 2]" | "[Counter + proof point]" | (TX) |
**vs. [Competitor B]:**
[Same structure]
### Positioning Validation Checklist
- [ ] Tested with ≥5 prospects before launch
- [ ] Positioning resonates with target segment (not just internal team)
- [ ] Differentiation is verifiable (not aspirational)
- [ ] Category choice is intentional (creating new vs. entering existing)
---
## 6. Success Metrics & Failure Criteria
### Leading Indicators (weekly review)
| Metric | Target | Goodhart Countermeasure | Antidote Metric |
|--------|--------|------------------------|-----------------|
| [e.g., Activation rate] | [≥X%] | [How it could be gamed] | [What to also watch] |
| [e.g., Time-to-value] | [≤X days] | [How it could be gamed] | [What to also watch] |
### Lagging Indicators (monthly review)
| Metric | Target (6-mo) | Target (12-mo) |
|--------|:-------------:|:--------------:|
| [e.g., Revenue] | [$X] | [$X] |
| [e.g., Retention] | [≥X%] | [≥X%] |
### Failure Criteria (HARD stops — not "reassess")
| Condition | Timeframe | Action |
|-----------|-----------|--------|
| [e.g., "<50 beta signups after 4 weeks of outreach"] | [By date] | **STOP:** [Specific action — pivot, kill, or redesign] |
| [e.g., "CAC >3x target after 100 conversions"] | [By date] | **STOP:** [Specific action] |
| [e.g., "NPS <20 from design partners"] | [By date] | **STOP:** [Specific action] |
### Review Cadence
| Cadence | What's Reviewed | Decision Authority | Escalation |
|---------|----------------|-------------------|------------|
| Weekly | Leading indicators | PM | Flag to VP if 2+ metrics miss for 2+ weeks |
| Monthly | Lagging indicators + gate criteria | PM + VP | Kill/pivot decision if failure criteria met |
| Quarterly | Full GTM strategy review | VP/GM | Strategy re-architecture if market conditions shift |
---
## 7. Distribution & Growth Mechanics
### Growth Model
| Model | Applicability | Evidence | Investment Required |
|-------|:------------:|----------|:-------------------:|
| Viral (user invites user) | [H/M/L/N/A] | [Why or why not] (TX) | [$X] |
| Content (SEO/thought leadership) | [H/M/L/N/A] | [Why or why not] (TX) | [$X] |
| Sales-led | [H/M/L/N/A] | [Why or why not] (TX) | [$X] |
| Product-led (PLG) | [H/M/L/N/A] | [Why or why not] (TX) | [$X] |
| Platform/marketplace | [H/M/L/N/A] | [Why or why not] (TX) | [$X] |
### Flywheel Design
[Which actions create compounding advantages? Draw the loop: More X → More Y → Better Z → More X]
### Reference Customer Strategy
| Slot | Target Profile | Selection Criteria | Storytelling Value |
|:----:|---------------|--------------------|--------------------|
| 1 | [Specific company type] | [Why this customer matters as a reference] | [What story they tell] |
| 2 | [Specific company type] | [Why] | [Story] |
| 3-5 | [Remaining slots] | [Criteria] | [Stories] |
---
## Strategic Recommendations (O→I→R→C→W Cascade)
**Recommendation 1: [Title]**
- **Observation** [TX]: [What we see]
- **Implication**: [Why it matters — the mechanism]
- **Response**: [Specific action + owner + timeline]
- **Confidence**: [H/M/L] — assumes [key assumption]
- **Watch**: [Observable signal]; if [threshold], re-assess
**Recommendation 2: [Title]**
[Same structure]
**Recommendation 3: [Title]**
[Same structure]
---
## Cross-Framework Contradictions
| Contradiction | Framework A says | Framework B says | Resolution / Which to weight |
|---|---|---|---|
| [e.g., "Segment scoring vs. channel economics"] | [Segment A scores highest] | [Channel economics favor Segment B's motion] | [Which matters more and why] |
---
## Assumption Registry
| # | Assumption | Framework it underpins | Confidence | Evidence | What would invalidate this |
|---|---|---|---|---|---|
| 1 | | | H/M/L | (TX) | |
| 2 | | | H/M/L | (TX) | |
| 3 | | | H/M/L | (TX) | |
---
## Adversarial Self-Critique
**Weakness 1: [Title]**
[Steelmanned argument against this GTM strategy. What assumption is made? What evidence would disprove it? Scenario where this launch is catastrophically wrong.]
**Weakness 2: [Title]**
[Same depth]
**Weakness 3: [Title]**
[Same depth]
---
## Revision Triggers
| Trigger | What to re-assess | Timeline |
|---|---|---|
| [Observable event — e.g., "Competitor launches competing product"] | [Which sections break] | [When to check] |
| [e.g., "Key assumption invalidated"] | [Which sections break] | [When to check] |
---
## Sources
[All sources cited in the strategy, with evidence tier and date.]
Rules for using this template:
- Do not skip sections. If a section isn't applicable, write "Skipped — [reason]" and move on.
- Every table cell with a rating, estimate, or claim must have an evidence tier tag —
(T1) through (T6).
- Section headers are conclusions, not labels. Replace generic headers (e.g., "Channel Strategy") with insight headers (e.g., "PLG Is the Only Viable Channel — Direct Sales CAC Is 5x Too High") after completing the section.
- The Executive Summary is written last but appears first. Do not write it until all sections are complete.
- Failure Criteria must be specific and time-bound. "Revenue is too low" is not a failure criterion. "<$50K ARR after 6 months with ≥$200K GTM spend" is.
Domain Frameworks
This section IS the knowledge weapon. Each framework is encoded with its scoring rubrics, decision tables, and application methodology — not merely referenced. A PM using this skill produces a GTM strategy that requires these frameworks; without them, the output degrades to a generic launch plan.
Framework 1: Market Entry Thesis
The structural argument for why this market, why now, and what gives you a disproportionate right to win a specific slice. Without a market entry thesis, a GTM strategy is a plan to spend money without a theory of why it will work.
The Three Pillars:
| Pillar |
Question |
What "Good" Looks Like |
What "Bad" Looks Like |
| Why This Market |
Is there a structural opportunity, not just a large TAM? |
"Regulatory change X creates $Y of newly addressable demand in segment Z" |
"The market is $50B and growing" |
| Why Now |
What timing signal makes this the right moment? |
"Incumbent is mid-platform migration; 18-month window before they stabilize" |
"AI is changing everything" |
| What's the Wedge |
Where is the gap in the incumbent's armor? |
"Design agencies with 15+ Figma users hit collaboration limits the incumbent can't fix without re-architecting" |
"Our product is better" |
Timing Thesis — The Four Forces:
| Force |
Signal |
Example |
Evidence Tier Needed |
| Technology shift |
New capability makes previously impossible product viable at target price |
"LLM costs dropped 90% in 12 months — AI-native analytics now viable at $50/user/mo" |
T1-T2 (cost data, product benchmarks) |
| Regulatory change |
New rules create demand or remove barriers |
"GDPR created demand for privacy-first analytics; EU AI Act will do the same for explainable AI" |
T1 (regulatory text, enforcement timeline) |
| Behavior change |
User expectations shifted by adjacent products |
"Users now expect natural language interfaces after ChatGPT — SQL-based tools feel broken" |
T2-T3 (user research, adoption data) |
| Cost curve crossing |
Economics that didn't work now work |
"Cloud compute at $X means we can offer real-time analytics at SMB pricing" |
T1 (pricing data, unit economics model) |
Decision Table — Should We Enter?
| Market Ready? |
Product Ready? |
Decision |
| ✅ Yes |
✅ Yes |
GO — launch into beachhead segment |
| ✅ Yes |
❌ No |
BUILD — market window is open; accelerate product; set deadline |
| ❌ No |
✅ Yes |
WAIT — monitor timing signals; re-assess in [X weeks] |
| ❌ No |
❌ No |
PIVOT — wrong market or wrong product; return to Problem Framing |
Wedge Identification Method:
A wedge is not "our product is better." A wedge is a structural advantage in a specific segment that incumbents cannot easily replicate. The wedge is what gets you the first 10 customers without competing on brand, distribution, or scale — advantages you don't have yet.
| Wedge Type |
Mechanism |
Example |
Durability |
| Counter-positioning |
Incumbent can't copy you without cannibalizing their core |
Canva vs. Adobe: self-serve design threatens Adobe's enterprise sales motion |
High — structural |
| Underserved segment |
Incumbent ignores a segment because it's too small or too different |
Notion serving individual knowledge workers while Confluence focuses on enterprise IT |
Medium — until segment grows large enough to attract attention |
| Technology discontinuity |
New technology enables 10x better/cheaper solution in a niche |
AI-native code review replacing manual reviewer workflows |
Medium — until incumbents adopt the same technology |
| Distribution advantage |
You can reach the segment cheaper than incumbents |
Built-in marketplace distribution (Shopify apps, Salesforce AppExchange) |
Low-Medium — marketplace rules change |
| Regulatory arbitrage |
New regulation creates requirements incumbents aren't built to meet |
GDPR-compliant analytics when incumbents are built on data collection |
Medium — until incumbents adapt |
Anti-pattern: "Large TAM Therefore Enter"
The sentence "The market is $50B so even 1% = $500M" contains zero strategic content. It doesn't explain:
- Why you can capture any share at all
- Which segment of the TAM is accessible to you
- What your wedge is against players who already have distribution, brand, and scale
- Why now rather than 2 years ago or 2 years from now
If your market entry thesis is "big market + good product = success," you don't have a market entry thesis. You have a hope.
Framework 2: Segment Selection & Prioritization
The single most consequential GTM decision: who to target first. Get this wrong and everything downstream fails — wrong channels, wrong messaging, wrong product priorities. A beachhead segment (the first market niche you dominate completely before expanding) must be specific enough to find 100 prospects by name.
Segment Definition Rules:
| Rule |
Bad Example |
Good Example |
Why |
| Name 100 prospects |
"SMBs" |
"10-50 person design agencies using Figma who hit collaboration limits at 15+ users" |
If you can't name 100 companies that fit the definition, the segment is too vague to target |
| Observable behavior |
"Companies that need better analytics" |
"Companies posting Looker admin job postings while complaining about LookML complexity on forums" |
Behavior is targetable; need-states are not |
| Willingness to pay |
"Price-sensitive small businesses" |
"Design agencies paying $15+/user/mo for Figma who would pay $10/user/mo for a collaboration add-on" |
Willingness to pay must be specific enough to model unit economics |
| Reachable |
"Enterprise companies globally" |
"US-based mid-market SaaS companies whose Head of Data attends dbt community events" |
You need a channel to actually reach these people |
ICP Scoring Rubric:
| Criterion |
Weight |
Score 5 |
Score 3 |
Score 1 |
| Acute pain |
25% |
Validated with ≥5 interviews; customers actively seeking solutions |
Some evidence of pain from secondary sources |
Assumed pain; no direct validation |
| Willingness to pay |
20% |
Customers have budget allocated; comparable products exist at target price |
Budget exists but not allocated; price sensitivity unclear |
No evidence of willingness to pay |
| Accessibility |
20% |
Clear channel exists; can reach 80%+ of segment through 1-2 channels |
Reachable through 3+ channels, none dominant |
No clear way to reach the segment efficiently |
| Reference-ability |
15% |
Segment is vocal (conference speakers, bloggers, community participants) |
Moderately connected; will provide references if asked |
Private; won't be public references |
| Expansion potential |
10% |
Adjacent segments are 5x+ larger and share buying criteria |
Adjacent segments exist but different buying criteria |
Dead-end segment; no expansion path |
| Competitive vacuum |
10% |
No incumbent actively serving this segment |
Incumbent serves it poorly; opportunity to displace |
Strong incumbent with high switching costs |
Decision Table — Beachhead Selection:
| Weighted Score |
Decision |
| ≥4.0 |
Strong beachhead — proceed to channel strategy |
| 3.0-3.9 |
Viable but risky — validate the weakest scoring criterion before committing |
| <3.0 |
Weak beachhead — find a better segment or return to Problem Framing |
Expansion Path — Crossing the Chasm Connection:
The beachhead is not the destination. It's the first pin in the bowling alley (Geoffrey Moore's metaphor for sequential niche domination that builds to mainstream adoption). Each segment transition must be planned:
| Transition |
Trigger to Expand |
What Carries Over |
What Changes |
| Beachhead → Adjacent 1 |
[Metric threshold — e.g., "50%+ share in beachhead, ≥10 references"] |
[Product features, brand in adjacent community] |
[Messaging, channel mix, possibly pricing] |
| Adjacent 1 → Adjacent 2 |
[Next metric threshold] |
[Broader product, more references] |
[New channel, enterprise motion?] |
| Adjacent 2 → Mainstream |
[Market pull — inbound exceeds outbound] |
[Brand, product maturity, reference library] |
[Everything — this is the chasm crossing] |
Framework 3: Channel Strategy with Unit Economics
Channels are not "marketing tactics." Channels are the economic engine of your GTM. A channel that doesn't have viable unit economics is a way to lose money efficiently.
Channel Taxonomy with Fit Indicators:
| Channel |
Best For |
Worst For |
Typical CAC Range |
Time to Signal |
| Direct sales |
Enterprise ($50K+ ACV), complex products, relationship-driven |
SMB, self-serve products, price-sensitive segments |
$5K-$50K |
3-6 months |
| PLG (product-led growth) |
SMB, developer tools, prosumer products, low ACV with high volume |
Enterprise (long sales cycles), regulated industries |
$50-$500 |
1-3 months |
| Content/SEO |
Considered purchases, educational buyers, long sales cycles |
Impulse purchases, time-sensitive launches |
$100-$2K |
6-18 months |
| Paid acquisition |
Proven unit economics to scale, retargeting, brand awareness |
Unproven products (too expensive to learn via paid), low-LTV products |
$200-$5K |
1-4 weeks |
| Partnership/channel |
Established ecosystems, marketplace distribution, co-selling |
Products without clear partner value prop, early-stage products |
$500-$5K |
3-12 months |
| Community |
Developer tools, PLG products, identity-driven products |
Enterprise B2B, transactional products |
$200-$2K |
6-18 months |
| Outbound |
Mid-market, defined ICP, products with clear ROI story |
Mass-market consumer, products without clear buyer persona |
$1K-$10K |
1-3 months |
| Events/conferences |
Enterprise, relationship-driven sales, brand-building in niche |
Broad consumer, low ACV, early-stage products without demo-ready product |
$2K-$20K |
1-6 months |
Per-Channel Unit Economics Template:
For the primary channel, calculate:
Awareness → Interest → Trial/Demo → Activation → Paid Conversion → Retention → Expansion
Funnel Stage | Volume | Conversion | Cost/Stage | Cumulative CAC
─────────────────────────────────────────────────────────────────────────────
Awareness (impressions)| [X] | [X%] | $[X] | $[X]
Interest (clicks/signups)| [X] | [X%] | $[X] | $[X]
Trial/Demo | [X] | [X%] | $[X] | $[X]
Activation | [X] | [X%] | $[X] | $[X]
Paid conversion | [X] | [X%] | $[X] | $[X] ← This is your CAC
─────────────────────────────────────────────────────────────────────────────
Payback period: [X months] = CAC / (Monthly revenue per customer)
LTV/CAC: [X:1] = (ARPU × Avg. lifetime months × Gross margin) / CAC
Minimum Viable Channel Rule:
Start with ONE channel. Prove it works (positive unit economics on ≥50 conversions). Then add a second. Multi-channel from day 1 is a failure mode — you learn nothing because no channel gets enough investment to produce statistically meaningful signal.
| Channel Count |
Stage |
Criteria |
| 1 |
Launch → Product-market fit |
Primary channel producing repeatable conversions |
| 2 |
Growth |
Primary channel proven; second channel shows early positive signal |
| 3+ |
Scale |
First two channels have positive unit economics at scale |
Evidence Requirements Before Scaling:
| Evidence Level |
What It Means |
Budget Implication |
| Hypothesis (no data) |
You think this channel will work based on analogy or logic |
$0 — don't spend until you have signal |
| Signal (<50 conversions) |
Early data suggests viability but sample size is too small |
Cap at 10% of GTM budget |
| Proof (50-200 conversions) |
Unit economics are clear; conversion funnel is mapped |
Scale to 30% of GTM budget |
| Proven (200+ conversions) |
Repeatable, predictable, scalable |
Unlimited (within LTV/CAC constraints) |
Framework 4: Launch Sequencing & Gating
Every launch has phases. Every phase has gates. Every gate has kill criteria. A launch without gates is a launch without learning — you'll discover problems at GA that should have been caught in beta.
Phase Taxonomy:
| Phase |
Purpose |
Audience |
Duration |
What You Learn |
| Alpha |
Internal validation |
Internal team (10-50 users) |
2-4 weeks |
Major bugs, UX failures, performance issues |
| Closed Beta |
Design partner validation |
5-20 hand-picked customers |
4-8 weeks |
Product-market fit signal, activation flow, early retention |
| Open Beta |
Broader validation |
50-500 from waitlist |
4-8 weeks |
Channel viability, support load, pricing validation |
| GA |
Market launch |
Target segment |
Ongoing |
Growth rate, unit economics, competitive response |
| Scale |
Expansion |
Adjacent segments |
Ongoing |
Cross-segment fit, channel economics at scale |
Gate Criteria Rubric:
Each phase transition requires ALL gates to pass. If any gate fails, you stay in the current phase, fix the issue, and re-evaluate.
| Gate Category |
Alpha → Beta |
Beta → Open Beta |
Open Beta → GA |
GA → Scale |
| Usage |
≥X DAU/WAU ratio |
≥X activation rate |
≥X retention (day 30) |
≥X retention (day 90) |
| Satisfaction |
No P0 bugs open |
NPS ≥X from design partners |
NPS ≥X from open beta |
NPS ≥X from GA cohort |
| Economics |
N/A |
Design partners willing to pay |
CAC < $X on ≥50 conversions |
LTV/CAC ≥ 3:1 |
| Support |
<X tickets/user/week |
<X tickets/user/week |
Support scalable (self-serve ≥80%) |
Support cost < X% of revenue |
| Positioning |
N/A |
Positioning tested with ≥5 prospects |
Win rate ≥X% vs. primary alternative |
Win rate stable or improving |
Kill Criteria — Hard Stops:
Kill criteria are not "reassess" criteria. They are specific, time-bound conditions that mean "stop spending money on this GTM." The purpose of kill criteria is to prevent sunk cost escalation — continuing a failing launch because you've already invested.
| Kill Signal |
Threshold |
What It Means |
Action |
| Zero activation |
<5% of beta users complete core action after 30 days |
Product doesn't deliver value quickly enough, or value prop is wrong |
Kill or pivot product, not GTM |
| No willingness to pay |
<10% of beta users willing to pay any amount |
Product is useful but not valuable enough to pay for |
Re-examine pricing or pivot to different monetization |
| CAC death spiral |
CAC > LTV after 100+ conversions |
Channel economics are fundamentally broken |
Kill channel, try different channel, or reduce CAC via product improvement |
| Competitive wipeout |
Primary competitor matches your wedge within beta period |
Wedge was speed-dependent and you lost the race |
Pivot to different wedge or different segment |
Minimum Viable Launch (MVL):
The MVL is the smallest launch that produces learning, not the biggest launch you can afford. The purpose of each phase is to answer a specific question:
| Phase |
Question It Answers |
MVL Size |
| Alpha |
Does the product work? |
10-50 internal users |
| Beta |
Do target customers want this? |
5-20 design partners |
| Open Beta |
Can we acquire customers through our primary channel? |
50-200 users via primary channel |
| GA |
Do unit economics work at scale? |
200+ customers |
Framework 5: Competitive Positioning for Launch
Positioning is not messaging. Positioning is the strategic decision about what mental real estate you occupy in the buyer's mind relative to alternatives. Messaging is how you communicate that position. Get positioning wrong and no amount of brilliant messaging will fix it.
April Dunford's Positioning Framework (adapted for GTM):
| Element |
Question |
Output |
| Competitive alternatives |
What would customers use if your product didn't exist? (Include "do nothing" and "manual workaround") |
List of 3-5 real alternatives |
| Unique attributes |
What do you have that alternatives don't? (Be specific — "AI-powered" is not unique in 2026) |
2-3 genuinely differentiated capabilities |
| Value for customer |
What does your unique capability enable the customer to do? (Customer language, not product language) |
Value statement in customer's words |
| Target customer |
Who cares most about this value? (This should match your beachhead segment) |
Specific ICP definition |
| Market category |
What frame of reference helps the customer understand what you are? |
Category name — existing or new |
Positioning Statement Template:
For [target customer with specific pain] who [currently do X with Y limitations], [product] is a [market category] that [delivers specific value]. Unlike [primary competitive alternative], [product] [key differentiator that matters to this segment].
Positioning Validation:
Test positioning with ≥5 prospects from the target segment BEFORE launch. Iterate based on:
| Signal |
Interpretation |
Action |
| Prospect immediately understands what you do |
Category choice is correct |
Proceed |
| Prospect says "oh, like [competitor]?" correctly |
Positioning is clear relative to alternatives |
Proceed |
| Prospect says "oh, like [wrong category]?" |
Category choice is wrong |
Reframe the category |
| Prospect doesn't understand why they'd switch from current solution |
Value for customer is unclear or insufficient |
Sharpen the differentiation |
| Prospect says "that's interesting but not for us" |
Target customer is wrong, or you're talking to wrong person |
Check segment selection |
Battlecard Structure:
For each primary competitor, build a battlecard that sales and marketing can use:
| Section |
Content |
| Quick take |
2-sentence summary of how we win against this competitor |
| Their pitch |
What they'll say about themselves (and what's true vs. marketing) |
| Our wedge |
Where w |
…(truncated)
1---2name: go-to-market-strategy3description: Use when planning a product launch, market entry, or GTM strategy — segment selection, channel strategy, launch sequencing, pricing validation, competitive positioning, or launch readiness assessment. Encodes wedge identification, channel unit economics, launch gating, and failure criteria. Produces a GTM strategy document, not a launch checklist.4license: MIT5---67## Purpose89Produce an elite-tier go-to-market strategy document that identifies the market wedge, selects and scores beachhead segments, designs channel strategy with unit economics, sequences launch phases with gates and kill criteria, positions against competitors, and defines success metrics with explicit failure conditions — a GTM strategy a PM cannot produce unaided. The output is a GTM Strategy Document — not a launch checklist, but a structural argument for how to win the first customers and compound from there.1011## When to Use / When NOT to Use1213**Use this skill when:**14- Launching a new product or feature into a market (new or existing)15- Entering a new market with an existing product16- Pivoting an existing product's GTM motion (e.g., sales-led to product-led)17- Evaluating whether a market entry is viable (go/no-go decision)18- Designing channel strategy with unit economics constraints19- Planning launch sequencing with explicit gates and kill criteria20- Assessing launch readiness before committing budget2122**Do NOT use this skill when:**23- You need a competitive analysis without a launch plan (use Competitive Market Analysis skill)24- You need a product specification (use Specification Writing skill)25- You need to validate a problem exists before solving it (use Problem Framing skill)26- You need to run experiments to validate assumptions (use Metric Design & Experimentation skill)27- You need a marketing campaign plan (this produces strategy, not execution assets)28- The product is already at scale and you need retention/growth optimization (this is for market entry, not market defense)2930**Anti-inputs (what this skill does NOT handle):**31- Marketing copy, email sequences, or campaign assets (downstream of GTM strategy)32- Pricing model design in isolation (pricing is one dimension of channel economics here, not the sole output)33- Organizational design for GTM teams (team structure follows strategy, not the other way around)34- International expansion playbooks (this covers market entry logic; localization is a separate discipline)3536---3738## Context Gate (Step -1: Is GTM Strategy the Right Artifact?)3940Before applying any framework, verify that a GTM strategy document is what the situation actually needs. The most common failure mode is producing an excellent GTM strategy for a product that shouldn't be launched yet.4142**Run these checks BEFORE proceeding:**4344| Check | Question | If NO → Redirect |45|-------|----------|-------------------|46| **Problem validated?** | Has the problem been validated with ≥5 target users? | → Problem Framing skill first. A GTM strategy for an unvalidated problem is a plan to efficiently deliver something nobody wants. |47| **Product exists or is specced?** | Is there a product, prototype, or detailed spec to launch? | → Specification Writing skill first. GTM without a product is strategy theater. |48| **Market is external?** | Is the target market external customers, not internal adoption? | → For internal rollout (enterprise feature adoption, internal tool deployment), GTM frameworks over-engineer the problem. Use a simpler adoption playbook. |49| **Competitive landscape known?** | Do you know who the alternatives are (including "do nothing")? | → Run Competitive Market Analysis skill first, or do lightweight competitor scan. GTM positioning requires knowing what you're positioning against. |50| **Decision authority exists?** | Is there someone who can act on this GTM strategy? | → If this is exploratory ("should we even consider this market?"), produce a market entry memo instead of a full GTM strategy. |5152**If all checks pass:** Proceed to Framework Selection (Step 0).5354**If 1-2 checks fail:** Note the gaps explicitly in the output header and proceed with caveats. Flag which sections are hypothetical.5556**If 3+ checks fail:** Stop. The right artifact is not a GTM strategy. Recommend the upstream skill.5758---5960## Reader Navigation6162### How to Read This Document6364| Time Available | What to Read | What You'll Get |65|---------------|-------------|-----------------|66| **5 minutes** | Executive Summary + Segment Selection table + Failure Criteria table | Go/no-go signal, who to target first, when to stop |67| **15 minutes** | Above + Market Entry Thesis + Channel Strategy + Launch Sequence | Full strategic logic: why this market, how to reach customers, what order |68| **30 minutes** | Full document | Complete GTM strategy with all frameworks, unit economics, positioning, and self-critique |6970| Your Role | Start Here | Focus On |71|-----------|-----------|----------|72| **VP/GM** | Executive Summary → Failure Criteria → Assumption Registry | Decision: fund this GTM or not. Kill criteria tell you when to pull the plug. |73| **PM** | Full document, sequentially | You own execution. Every section has specific actions, timelines, and gates. |74| **Marketing Lead** | Positioning section → Channel Strategy → Launch Sequence | Positioning statement, channel selection, launch phases and messaging per phase. |75| **Sales Lead** | Segment Selection → Channel Strategy (direct sales row) → Battlecards | Who to call, what to say, how to handle objections. |76| **Finance/Ops** | Channel Unit Economics → Launch Sequence (budget per phase) → Failure Criteria | CAC, payback period, budget gates, kill thresholds. |7778### Notation Key7980| Symbol | Meaning |81|--------|---------|82| **H / M / L** | Confidence level: H = >70% confident, M = 40-70%, L = <40% |83| **(T1)-(T6)** | Evidence tier: T1 = behavioral data, T2 = primary research, T3 = expert analysis, T4 = industry reports, T5 = executive statements, T6 = inference |84| **O→I→R→C→W** | Observation → Implication → Response → Confidence → Watch indicator (mandatory cascade for all recommendations) |85| `[POTENTIALLY STALE]` | Claim based on data >6 months old — verify before acting |86| `[EVIDENCE-LIMITED]` | Key conclusion rests on T4-T6 evidence only — validate with T1-T2 before committing budget |87| ████░░░░░░ | Progress bar showing relative strength (1-10 scale) |88| ✅ / ⚠️ / ❌ | Gate passed / gate at risk / gate failed |8990---9192## Format Rules (Read First)9394These rules govern every output produced by this codex. They are quality enforcement mechanisms, not style preferences.95961. **Take positions. Never hedge with weasel words.** "Likely," "may," "could," and "seems" are banned from conclusions. Flag uncertainty with explicit confidence levels: **H (>70% confident)**, **M (40-70%)**, **L (<40%)**. Example: *"The beachhead segment is 10-50 person design agencies hitting Figma collaboration limits (H)"* not *"SMBs could be a good target market."*97982. **Per-cell evidence tier annotation is mandatory in all comparison matrices.** Every cell in a segment scoring table, channel economics comparison, or positioning matrix must carry an inline evidence tier tag: `(T1)`, `(T2)`, `(T3)` etc. Where evidence is absent: `(T6: inferred)`. A matrix with untagged cells is incomplete.991003. **The O→I→R→C→W cascade applies to ALL strategic recommendations**, not just final sections. Format: Observation [evidence tier] → Implication [mechanism] → Response [specific action + owner + timeline] → Confidence [H/M/L + assumption] → Watch Indicator [observable signal + threshold].1011024. **Begin with Framework Selection (Step 0)** before applying any framework. Identify the stage (new market entry, expansion, feature launch, pivot); select the 3-4 load-bearing frameworks; note which to skip.1031045. **Contradictions between frameworks are signal, not noise.** When two frameworks reach different conclusions (e.g., segment scoring says enterprise but channel economics says PLG/SMB), surface the contradiction explicitly and state which to weight more heavily and why.1051066. **Flag time-sensitive claims.** Any claim based on data older than 6 months must carry `[POTENTIALLY STALE — verify before presenting]`. Market conditions change faster than competitive positions.1071087. **Flag thin-evidence conclusions.** If a key strategic conclusion rests only on Tier 4-6 evidence, prepend it with `[EVIDENCE-LIMITED: validate with Tier 1-2 before acting]`.1091108. **First reference to any framework includes a one-line explanation.** Not everyone reading a GTM strategy knows what "PLG" or "CAC" or "beachhead" means. Example: *"Product-led growth (PLG) — users adopt the product through self-serve trial before any sales contact."* This makes the document navigable by non-creators.1111129. **The Executive Summary uses zero framework jargon.** A VP who has never heard of "beachhead strategy" or "CAC payback period" must be able to read the Executive Summary and make a decision. Framework terms appear in the body, not the summary.113114---115116## Output Template (Mandatory Document Skeleton)117118Every GTM Strategy Document MUST follow this exact structure. Copy this skeleton and fill it in. Do not reorder sections, skip sections, or invent new top-level sections. If a framework was skipped in Step 0, note "Skipped — not load-bearing for this stage" in that section.119120```markdown121# GTM Strategy: [Product — e.g., "Vanta Analytics Self-Serve Launch"]122123> **Date:** [YYYY-MM-DD] | **Stage:** [new_market_entry / existing_market_expansion / feature_launch / pivot] | **Confidence band:** [Overall H/M/L] | **Staleness window:** [Date after which key claims need revalidation]124125---126127## How to Read This Document128129[Reader Navigation table — by time available and by role. See Reader Navigation section above.]130131## Notation Key132133[Symbol definitions table. See Notation Key above.]134135---136137## Executive Summary138139[≤300 words. Zero jargon. A VP reads only this and decides whether to fund the GTM. Must answer: What are we launching? For whom? Why now? What's the entry point? What does success look like in 6 months? What kills this? Final sentence = the recommended action in bold.]140141---142143## Step 0: Framework Selection144145| Stage | Primary frameworks (apply in full) | Supporting frameworks (scan only) | Skipped (why) |146|---|---|---|---|147| [e.g., "New market entry"] | [e.g., Market Entry Thesis, Segment Selection, Channel Strategy] | [e.g., Distribution & Growth Mechanics] | [e.g., "Competitive Positioning — no direct competitors yet"] |148149---150151## 1. Market Entry Thesis152153### Why This Market154155[Market selection rationale — size, growth, structural opportunity]156157### Why Now (Timing Thesis)158159| Timing Signal | Evidence | Confidence |160|--------------|----------|------------|161| [e.g., "Regulatory change creating demand"] | [specific evidence] (TX) | H/M/L |162| [e.g., "Incumbent distracted by platform migration"] | [specific evidence] (TX) | H/M/L |163| [e.g., "Cost curve crossing — AI makes X viable at Y price"] | [specific evidence] (TX) | H/M/L |164165### The Wedge166167[What is the specific gap in the incumbent's armor? What gives you disproportionate advantage in a specific segment? This is NOT "we're better" — it's "we can win THIS slice because of THIS structural advantage."]168169### Wedge Defensibility Assessment170171| Dimension | Assessment | Evidence |172|-----------|-----------|----------|173| Time to replicate | [months/years] | (TX) |174| Capital to replicate | [$X] | (TX) |175| Structural barrier | [what prevents copying — counter-positioning, data moat, regulatory, network effects] | (TX) |176| **Verdict** | [Durable moat / Temporary arbitrage / Speed-dependent] | H/M/L |177178### Go/Wait/Pivot Decision Table179180| Signal | Market Ready | Market NOT Ready |181|--------|-------------|-----------------|182| Product readiness | → **GO**: launch beachhead | → **WAIT**: build MVP, re-assess in [X weeks] |183| Product NOT ready | → **BUILD**: market is ready, accelerate product | → **PIVOT**: wrong market or wrong product |184185---186187## 2. Segment Selection & Prioritization188189### Beachhead Candidates190191| Segment | Description | Size (est.) | Evidence |192|---------|------------|-------------|----------|193| [Segment A] | [Specific enough to find 100 prospects by name] | [$ or # users] (TX) | [How you know this segment exists] |194| [Segment B] | [Same specificity] | [$ or #] (TX) | [Evidence] |195| [Segment C] | [Same specificity] | [$ or #] (TX) | [Evidence] |196197### ICP Scoring Matrix198199| Criterion | Weight | Segment A | Segment B | Segment C |200|-----------|:------:|:---------:|:---------:|:---------:|201| Acute pain (validated) | 25% | [1-5] (TX) | [1-5] (TX) | [1-5] (TX) |202| Willingness to pay | 20% | [1-5] (TX) | [1-5] (TX) | [1-5] (TX) |203| Accessibility (can you reach them?) | 20% | [1-5] (TX) | [1-5] (TX) | [1-5] (TX) |204| Reference-ability (will they tell others?) | 15% | [1-5] (TX) | [1-5] (TX) | [1-5] (TX) |205| Expansion potential (leads to adjacent segments?) | 10% | [1-5] (TX) | [1-5] (TX) | [1-5] (TX) |206| Competitive vacuum (incumbents weak here?) | 10% | [1-5] (TX) | [1-5] (TX) | [1-5] (TX) |207| **Weighted Score** | | **[X.X]** | **[X.X]** | **[X.X]** |208209### Expansion Path210211[Beachhead → Adjacent Segment 1 → Adjacent Segment 2 → Mainstream]212[For each transition: what evidence or milestone triggers expansion? What do you carry from the previous segment (references, product features, channel)?]213214---215216## 3. Channel Strategy with Unit Economics217218### Channel Selection Matrix219220| Channel | Segment Fit | CAC (est.) | Payback (mo.) | LTV/CAC | Scalability | Evidence |221|---------|:-----------:|:----------:|:-------------:|:-------:|:-----------:|:--------:|222| [Direct sales] | [H/M/L] | [$X] (TX) | [X mo.] (TX) | [X:1] (TX) | [H/M/L] | [source] |223| [PLG / self-serve] | [H/M/L] | [$X] (TX) | [X mo.] (TX) | [X:1] (TX) | [H/M/L] | [source] |224| [Content/SEO] | [H/M/L] | [$X] (TX) | [X mo.] (TX) | [X:1] (TX) | [H/M/L] | [source] |225| [Paid acquisition] | [H/M/L] | [$X] (TX) | [X mo.] (TX) | [X:1] (TX) | [H/M/L] | [source] |226| [Partnership/channel] | [H/M/L] | [$X] (TX) | [X mo.] (TX) | [X:1] (TX) | [H/M/L] | [source] |227| [Community] | [H/M/L] | [$X] (TX) | [X mo.] (TX) | [X:1] (TX) | [H/M/L] | [source] |228229### Primary Channel Deep-Dive230231[For the #1 selected channel: full conversion funnel, unit economics at each stage, evidence requirements before scaling budget]232233### Channel Sequencing234235| Phase | Channel | Budget | Success Criteria to Add Next Channel |236|-------|---------|--------|--------------------------------------|237| Phase 1 | [ONE channel] | [$X] | [Metric ≥ threshold, e.g., "CAC < $200 on 50+ conversions"] |238| Phase 2 | [Add second] | [$X] | [Metric ≥ threshold] |239| Phase 3 | [Add third] | [$X] | [Metric ≥ threshold] |240241---242243## 4. Launch Sequencing & Gating244245### Phase Plan246247| Phase | Duration | Audience | Gate Criteria (must ALL be true to proceed) | Kill Criteria (if ANY true, stop) |248|-------|----------|----------|----------------------------------------------|-----------------------------------|249| **Alpha** (internal) | [X weeks] | [Internal team, N users] | [List specific metrics] | [List specific thresholds] |250| **Closed Beta** (design partners) | [X weeks] | [N design partners] | [List specific metrics] | [List specific thresholds] |251| **Open Beta** (waitlist) | [X weeks] | [N users from waitlist] | [List specific metrics] | [List specific thresholds] |252| **GA** (general availability) | [X weeks] | [Target segment] | [List specific metrics] | [List specific thresholds] |253| **Scale** | [Ongoing] | [Expansion segments] | [List specific metrics] | [List specific thresholds] |254255### Launch Risk Register256257| Risk | Phase | Severity (1-5) | Probability (H/M/L) | Mitigation | Owner |258|------|-------|:--------------:|:--------------------:|------------|-------|259| [Risk 1] | [Phase] | [X] | [H/M/L] | [Specific action] | [Role] |260| [Risk 2] | [Phase] | [X] | [H/M/L] | [Specific action] | [Role] |261262---263264## 5. Competitive Positioning for Launch265266### Positioning Statement267268> For **[target customer]** who **[need/job-to-be-done]**, **[product]** is a **[market category]** that **[key benefit]**. Unlike **[primary alternative]**, we **[key differentiator]**.269270### Battlecards (per competitor)271272**vs. [Competitor A]:**273| They'll Say | You Say | Evidence |274|------------|---------|----------|275| "[Objection 1]" | "[Counter + proof point]" | (TX) |276| "[Objection 2]" | "[Counter + proof point]" | (TX) |277278**vs. [Competitor B]:**279[Same structure]280281### Positioning Validation Checklist282283- [ ] Tested with ≥5 prospects before launch284- [ ] Positioning resonates with target segment (not just internal team)285- [ ] Differentiation is verifiable (not aspirational)286- [ ] Category choice is intentional (creating new vs. entering existing)287288---289290## 6. Success Metrics & Failure Criteria291292### Leading Indicators (weekly review)293294| Metric | Target | Goodhart Countermeasure | Antidote Metric |295|--------|--------|------------------------|-----------------|296| [e.g., Activation rate] | [≥X%] | [How it could be gamed] | [What to also watch] |297| [e.g., Time-to-value] | [≤X days] | [How it could be gamed] | [What to also watch] |298299### Lagging Indicators (monthly review)300301| Metric | Target (6-mo) | Target (12-mo) |302|--------|:-------------:|:--------------:|303| [e.g., Revenue] | [$X] | [$X] |304| [e.g., Retention] | [≥X%] | [≥X%] |305306### Failure Criteria (HARD stops — not "reassess")307308| Condition | Timeframe | Action |309|-----------|-----------|--------|310| [e.g., "<50 beta signups after 4 weeks of outreach"] | [By date] | **STOP:** [Specific action — pivot, kill, or redesign] |311| [e.g., "CAC >3x target after 100 conversions"] | [By date] | **STOP:** [Specific action] |312| [e.g., "NPS <20 from design partners"] | [By date] | **STOP:** [Specific action] |313314### Review Cadence315316| Cadence | What's Reviewed | Decision Authority | Escalation |317|---------|----------------|-------------------|------------|318| Weekly | Leading indicators | PM | Flag to VP if 2+ metrics miss for 2+ weeks |319| Monthly | Lagging indicators + gate criteria | PM + VP | Kill/pivot decision if failure criteria met |320| Quarterly | Full GTM strategy review | VP/GM | Strategy re-architecture if market conditions shift |321322---323324## 7. Distribution & Growth Mechanics325326### Growth Model327328| Model | Applicability | Evidence | Investment Required |329|-------|:------------:|----------|:-------------------:|330| Viral (user invites user) | [H/M/L/N/A] | [Why or why not] (TX) | [$X] |331| Content (SEO/thought leadership) | [H/M/L/N/A] | [Why or why not] (TX) | [$X] |332| Sales-led | [H/M/L/N/A] | [Why or why not] (TX) | [$X] |333| Product-led (PLG) | [H/M/L/N/A] | [Why or why not] (TX) | [$X] |334| Platform/marketplace | [H/M/L/N/A] | [Why or why not] (TX) | [$X] |335336### Flywheel Design337338[Which actions create compounding advantages? Draw the loop: More X → More Y → Better Z → More X]339340### Reference Customer Strategy341342| Slot | Target Profile | Selection Criteria | Storytelling Value |343|:----:|---------------|--------------------|--------------------|344| 1 | [Specific company type] | [Why this customer matters as a reference] | [What story they tell] |345| 2 | [Specific company type] | [Why] | [Story] |346| 3-5 | [Remaining slots] | [Criteria] | [Stories] |347348---349350## Strategic Recommendations (O→I→R→C→W Cascade)351352**Recommendation 1: [Title]**353- **Observation** [TX]: [What we see]354- **Implication**: [Why it matters — the mechanism]355- **Response**: [Specific action + owner + timeline]356- **Confidence**: [H/M/L] — assumes [key assumption]357- **Watch**: [Observable signal]; if [threshold], re-assess358359**Recommendation 2: [Title]**360[Same structure]361362**Recommendation 3: [Title]**363[Same structure]364365---366367## Cross-Framework Contradictions368369| Contradiction | Framework A says | Framework B says | Resolution / Which to weight |370|---|---|---|---|371| [e.g., "Segment scoring vs. channel economics"] | [Segment A scores highest] | [Channel economics favor Segment B's motion] | [Which matters more and why] |372373---374375## Assumption Registry376377| # | Assumption | Framework it underpins | Confidence | Evidence | What would invalidate this |378|---|---|---|---|---|---|379| 1 | | | H/M/L | (TX) | |380| 2 | | | H/M/L | (TX) | |381| 3 | | | H/M/L | (TX) | |382383---384385## Adversarial Self-Critique386387**Weakness 1: [Title]**388[Steelmanned argument against this GTM strategy. What assumption is made? What evidence would disprove it? Scenario where this launch is catastrophically wrong.]389390**Weakness 2: [Title]**391[Same depth]392393**Weakness 3: [Title]**394[Same depth]395396---397398## Revision Triggers399400| Trigger | What to re-assess | Timeline |401|---|---|---|402| [Observable event — e.g., "Competitor launches competing product"] | [Which sections break] | [When to check] |403| [e.g., "Key assumption invalidated"] | [Which sections break] | [When to check] |404405---406407## Sources408409[All sources cited in the strategy, with evidence tier and date.]410```411412**Rules for using this template:**4131. **Do not skip sections.** If a section isn't applicable, write "Skipped — [reason]" and move on.4142. **Every table cell with a rating, estimate, or claim must have an evidence tier tag** — `(T1)` through `(T6)`.4153. **Section headers are conclusions, not labels.** Replace generic headers (e.g., "Channel Strategy") with insight headers (e.g., "PLG Is the Only Viable Channel — Direct Sales CAC Is 5x Too High") after completing the section.4164. **The Executive Summary is written last** but appears first. Do not write it until all sections are complete.4175. **Failure Criteria must be specific and time-bound.** "Revenue is too low" is not a failure criterion. "<$50K ARR after 6 months with ≥$200K GTM spend" is.418419---420421## Domain Frameworks422423> This section IS the knowledge weapon. Each framework is encoded with its scoring rubrics, decision tables, and application methodology — not merely referenced. A PM using this skill produces a GTM strategy that requires these frameworks; without them, the output degrades to a generic launch plan.424425### Framework 1: Market Entry Thesis426427The structural argument for why this market, why now, and what gives you a disproportionate right to win a specific slice. Without a market entry thesis, a GTM strategy is a plan to spend money without a theory of why it will work.428429**The Three Pillars:**430431| Pillar | Question | What "Good" Looks Like | What "Bad" Looks Like |432|--------|----------|------------------------|-----------------------|433| **Why This Market** | Is there a structural opportunity, not just a large TAM? | "Regulatory change X creates $Y of newly addressable demand in segment Z" | "The market is $50B and growing" |434| **Why Now** | What timing signal makes this the right moment? | "Incumbent is mid-platform migration; 18-month window before they stabilize" | "AI is changing everything" |435| **What's the Wedge** | Where is the gap in the incumbent's armor? | "Design agencies with 15+ Figma users hit collaboration limits the incumbent can't fix without re-architecting" | "Our product is better" |436437**Timing Thesis — The Four Forces:**438439| Force | Signal | Example | Evidence Tier Needed |440|-------|--------|---------|---------------------|441| **Technology shift** | New capability makes previously impossible product viable at target price | "LLM costs dropped 90% in 12 months — AI-native analytics now viable at $50/user/mo" | T1-T2 (cost data, product benchmarks) |442| **Regulatory change** | New rules create demand or remove barriers | "GDPR created demand for privacy-first analytics; EU AI Act will do the same for explainable AI" | T1 (regulatory text, enforcement timeline) |443| **Behavior change** | User expectations shifted by adjacent products | "Users now expect natural language interfaces after ChatGPT — SQL-based tools feel broken" | T2-T3 (user research, adoption data) |444| **Cost curve crossing** | Economics that didn't work now work | "Cloud compute at $X means we can offer real-time analytics at SMB pricing" | T1 (pricing data, unit economics model) |445446**Decision Table — Should We Enter?**447448| Market Ready? | Product Ready? | Decision |449|:------------:|:--------------:|----------|450| ✅ Yes | ✅ Yes | **GO** — launch into beachhead segment |451| ✅ Yes | ❌ No | **BUILD** — market window is open; accelerate product; set deadline |452| ❌ No | ✅ Yes | **WAIT** — monitor timing signals; re-assess in [X weeks] |453| ❌ No | ❌ No | **PIVOT** — wrong market or wrong product; return to Problem Framing |454455**Wedge Identification Method:**456457A wedge is not "our product is better." A wedge is a structural advantage in a specific segment that incumbents cannot easily replicate. The wedge is what gets you the first 10 customers without competing on brand, distribution, or scale — advantages you don't have yet.458459| Wedge Type | Mechanism | Example | Durability |460|-----------|-----------|---------|-----------|461| **Counter-positioning** | Incumbent can't copy you without cannibalizing their core | Canva vs. Adobe: self-serve design threatens Adobe's enterprise sales motion | High — structural |462| **Underserved segment** | Incumbent ignores a segment because it's too small or too different | Notion serving individual knowledge workers while Confluence focuses on enterprise IT | Medium — until segment grows large enough to attract attention |463| **Technology discontinuity** | New technology enables 10x better/cheaper solution in a niche | AI-native code review replacing manual reviewer workflows | Medium — until incumbents adopt the same technology |464| **Distribution advantage** | You can reach the segment cheaper than incumbents | Built-in marketplace distribution (Shopify apps, Salesforce AppExchange) | Low-Medium — marketplace rules change |465| **Regulatory arbitrage** | New regulation creates requirements incumbents aren't built to meet | GDPR-compliant analytics when incumbents are built on data collection | Medium — until incumbents adapt |466467**Anti-pattern: "Large TAM Therefore Enter"**468469The sentence "The market is $50B so even 1% = $500M" contains zero strategic content. It doesn't explain:470- Why you can capture any share at all471- Which segment of the TAM is accessible to you472- What your wedge is against players who already have distribution, brand, and scale473- Why now rather than 2 years ago or 2 years from now474475If your market entry thesis is "big market + good product = success," you don't have a market entry thesis. You have a hope.476477---478479### Framework 2: Segment Selection & Prioritization480481The single most consequential GTM decision: who to target first. Get this wrong and everything downstream fails — wrong channels, wrong messaging, wrong product priorities. A beachhead segment (the first market niche you dominate completely before expanding) must be specific enough to find 100 prospects by name.482483**Segment Definition Rules:**484485| Rule | Bad Example | Good Example | Why |486|------|-----------|-------------|-----|487| **Name 100 prospects** | "SMBs" | "10-50 person design agencies using Figma who hit collaboration limits at 15+ users" | If you can't name 100 companies that fit the definition, the segment is too vague to target |488| **Observable behavior** | "Companies that need better analytics" | "Companies posting Looker admin job postings while complaining about LookML complexity on forums" | Behavior is targetable; need-states are not |489| **Willingness to pay** | "Price-sensitive small businesses" | "Design agencies paying $15+/user/mo for Figma who would pay $10/user/mo for a collaboration add-on" | Willingness to pay must be specific enough to model unit economics |490| **Reachable** | "Enterprise companies globally" | "US-based mid-market SaaS companies whose Head of Data attends dbt community events" | You need a channel to actually reach these people |491492**ICP Scoring Rubric:**493494| Criterion | Weight | Score 5 | Score 3 | Score 1 |495|-----------|:------:|---------|---------|---------|496| **Acute pain** | 25% | Validated with ≥5 interviews; customers actively seeking solutions | Some evidence of pain from secondary sources | Assumed pain; no direct validation |497| **Willingness to pay** | 20% | Customers have budget allocated; comparable products exist at target price | Budget exists but not allocated; price sensitivity unclear | No evidence of willingness to pay |498| **Accessibility** | 20% | Clear channel exists; can reach 80%+ of segment through 1-2 channels | Reachable through 3+ channels, none dominant | No clear way to reach the segment efficiently |499| **Reference-ability** | 15% | Segment is vocal (conference speakers, bloggers, community participants) | Moderately connected; will provide references if asked | Private; won't be public references |500| **Expansion potential** | 10% | Adjacent segments are 5x+ larger and share buying criteria | Adjacent segments exist but different buying criteria | Dead-end segment; no expansion path |501| **Competitive vacuum** | 10% | No incumbent actively serving this segment | Incumbent serves it poorly; opportunity to displace | Strong incumbent with high switching costs |502503**Decision Table — Beachhead Selection:**504505| Weighted Score | Decision |506|:--------------:|----------|507| ≥4.0 | **Strong beachhead** — proceed to channel strategy |508| 3.0-3.9 | **Viable but risky** — validate the weakest scoring criterion before committing |509| <3.0 | **Weak beachhead** — find a better segment or return to Problem Framing |510511**Expansion Path — Crossing the Chasm Connection:**512513The beachhead is not the destination. It's the first pin in the bowling alley (Geoffrey Moore's metaphor for sequential niche domination that builds to mainstream adoption). Each segment transition must be planned:514515| Transition | Trigger to Expand | What Carries Over | What Changes |516|-----------|-------------------|-------------------|--------------|517| Beachhead → Adjacent 1 | [Metric threshold — e.g., "50%+ share in beachhead, ≥10 references"] | [Product features, brand in adjacent community] | [Messaging, channel mix, possibly pricing] |518| Adjacent 1 → Adjacent 2 | [Next metric threshold] | [Broader product, more references] | [New channel, enterprise motion?] |519| Adjacent 2 → Mainstream | [Market pull — inbound exceeds outbound] | [Brand, product maturity, reference library] | [Everything — this is the chasm crossing] |520521---522523### Framework 3: Channel Strategy with Unit Economics524525Channels are not "marketing tactics." Channels are the economic engine of your GTM. A channel that doesn't have viable unit economics is a way to lose money efficiently.526527**Channel Taxonomy with Fit Indicators:**528529| Channel | Best For | Worst For | Typical CAC Range | Time to Signal |530|---------|---------|-----------|:------------------:|:--------------:|531| **Direct sales** | Enterprise ($50K+ ACV), complex products, relationship-driven | SMB, self-serve products, price-sensitive segments | $5K-$50K | 3-6 months |532| **PLG (product-led growth)** | SMB, developer tools, prosumer products, low ACV with high volume | Enterprise (long sales cycles), regulated industries | $50-$500 | 1-3 months |533| **Content/SEO** | Considered purchases, educational buyers, long sales cycles | Impulse purchases, time-sensitive launches | $100-$2K | 6-18 months |534| **Paid acquisition** | Proven unit economics to scale, retargeting, brand awareness | Unproven products (too expensive to learn via paid), low-LTV products | $200-$5K | 1-4 weeks |535| **Partnership/channel** | Established ecosystems, marketplace distribution, co-selling | Products without clear partner value prop, early-stage products | $500-$5K | 3-12 months |536| **Community** | Developer tools, PLG products, identity-driven products | Enterprise B2B, transactional products | $200-$2K | 6-18 months |537| **Outbound** | Mid-market, defined ICP, products with clear ROI story | Mass-market consumer, products without clear buyer persona | $1K-$10K | 1-3 months |538| **Events/conferences** | Enterprise, relationship-driven sales, brand-building in niche | Broad consumer, low ACV, early-stage products without demo-ready product | $2K-$20K | 1-6 months |539540**Per-Channel Unit Economics Template:**541542For the primary channel, calculate:543544```545Awareness → Interest → Trial/Demo → Activation → Paid Conversion → Retention → Expansion546547Funnel Stage | Volume | Conversion | Cost/Stage | Cumulative CAC548─────────────────────────────────────────────────────────────────────────────549Awareness (impressions)| [X] | [X%] | $[X] | $[X]550Interest (clicks/signups)| [X] | [X%] | $[X] | $[X]551Trial/Demo | [X] | [X%] | $[X] | $[X]552Activation | [X] | [X%] | $[X] | $[X]553Paid conversion | [X] | [X%] | $[X] | $[X] ← This is your CAC554─────────────────────────────────────────────────────────────────────────────555Payback period: [X months] = CAC / (Monthly revenue per customer)556LTV/CAC: [X:1] = (ARPU × Avg. lifetime months × Gross margin) / CAC557```558559**Minimum Viable Channel Rule:**560561Start with ONE channel. Prove it works (positive unit economics on ≥50 conversions). Then add a second. Multi-channel from day 1 is a failure mode — you learn nothing because no channel gets enough investment to produce statistically meaningful signal.562563| Channel Count | Stage | Criteria |564|:------------:|-------|----------|565| 1 | Launch → Product-market fit | Primary channel producing repeatable conversions |566| 2 | Growth | Primary channel proven; second channel shows early positive signal |567| 3+ | Scale | First two channels have positive unit economics at scale |568569**Evidence Requirements Before Scaling:**570571| Evidence Level | What It Means | Budget Implication |572|:-------------:|--------------|-------------------|573| **Hypothesis** (no data) | You think this channel will work based on analogy or logic | $0 — don't spend until you have signal |574| **Signal** (<50 conversions) | Early data suggests viability but sample size is too small | Cap at 10% of GTM budget |575| **Proof** (50-200 conversions) | Unit economics are clear; conversion funnel is mapped | Scale to 30% of GTM budget |576| **Proven** (200+ conversions) | Repeatable, predictable, scalable | Unlimited (within LTV/CAC constraints) |577578---579580### Framework 4: Launch Sequencing & Gating581582Every launch has phases. Every phase has gates. Every gate has kill criteria. A launch without gates is a launch without learning — you'll discover problems at GA that should have been caught in beta.583584**Phase Taxonomy:**585586| Phase | Purpose | Audience | Duration | What You Learn |587|-------|---------|----------|----------|----------------|588| **Alpha** | Internal validation | Internal team (10-50 users) | 2-4 weeks | Major bugs, UX failures, performance issues |589| **Closed Beta** | Design partner validation | 5-20 hand-picked customers | 4-8 weeks | Product-market fit signal, activation flow, early retention |590| **Open Beta** | Broader validation | 50-500 from waitlist | 4-8 weeks | Channel viability, support load, pricing validation |591| **GA** | Market launch | Target segment | Ongoing | Growth rate, unit economics, competitive response |592| **Scale** | Expansion | Adjacent segments | Ongoing | Cross-segment fit, channel economics at scale |593594**Gate Criteria Rubric:**595596Each phase transition requires ALL gates to pass. If any gate fails, you stay in the current phase, fix the issue, and re-evaluate.597598| Gate Category | Alpha → Beta | Beta → Open Beta | Open Beta → GA | GA → Scale |599|--------------|:---:|:---:|:---:|:---:|600| **Usage** | ≥X DAU/WAU ratio | ≥X activation rate | ≥X retention (day 30) | ≥X retention (day 90) |601| **Satisfaction** | No P0 bugs open | NPS ≥X from design partners | NPS ≥X from open beta | NPS ≥X from GA cohort |602| **Economics** | N/A | Design partners willing to pay | CAC < $X on ≥50 conversions | LTV/CAC ≥ 3:1 |603| **Support** | <X tickets/user/week | <X tickets/user/week | Support scalable (self-serve ≥80%) | Support cost < X% of revenue |604| **Positioning** | N/A | Positioning tested with ≥5 prospects | Win rate ≥X% vs. primary alternative | Win rate stable or improving |605606**Kill Criteria — Hard Stops:**607608Kill criteria are not "reassess" criteria. They are specific, time-bound conditions that mean "stop spending money on this GTM." The purpose of kill criteria is to prevent sunk cost escalation — continuing a failing launch because you've already invested.609610| Kill Signal | Threshold | What It Means | Action |611|-------------|-----------|--------------|--------|612| Zero activation | <5% of beta users complete core action after 30 days | Product doesn't deliver value quickly enough, or value prop is wrong | Kill or pivot product, not GTM |613| No willingness to pay | <10% of beta users willing to pay any amount | Product is useful but not valuable enough to pay for | Re-examine pricing or pivot to different monetization |614| CAC death spiral | CAC > LTV after 100+ conversions | Channel economics are fundamentally broken | Kill channel, try different channel, or reduce CAC via product improvement |615| Competitive wipeout | Primary competitor matches your wedge within beta period | Wedge was speed-dependent and you lost the race | Pivot to different wedge or different segment |616617**Minimum Viable Launch (MVL):**618619The MVL is the smallest launch that produces learning, not the biggest launch you can afford. The purpose of each phase is to answer a specific question:620621| Phase | Question It Answers | MVL Size |622|-------|--------------------|---------:|623| Alpha | Does the product work? | 10-50 internal users |624| Beta | Do target customers want this? | 5-20 design partners |625| Open Beta | Can we acquire customers through our primary channel? | 50-200 users via primary channel |626| GA | Do unit economics work at scale? | 200+ customers |627628---629630### Framework 5: Competitive Positioning for Launch631632Positioning is not messaging. Positioning is the strategic decision about what mental real estate you occupy in the buyer's mind relative to alternatives. Messaging is how you communicate that position. Get positioning wrong and no amount of brilliant messaging will fix it.633634**April Dunford's Positioning Framework (adapted for GTM):**635636| Element | Question | Output |637|---------|----------|--------|638| **Competitive alternatives** | What would customers use if your product didn't exist? (Include "do nothing" and "manual workaround") | List of 3-5 real alternatives |639| **Unique attributes** | What do you have that alternatives don't? (Be specific — "AI-powered" is not unique in 2026) | 2-3 genuinely differentiated capabilities |640| **Value for customer** | What does your unique capability enable the customer to do? (Customer language, not product language) | Value statement in customer's words |641| **Target customer** | Who cares most about this value? (This should match your beachhead segment) | Specific ICP definition |642| **Market category** | What frame of reference helps the customer understand what you are? | Category name — existing or new |643644**Positioning Statement Template:**645646> For **[target customer with specific pain]** who **[currently do X with Y limitations]**, **[product]** is a **[market category]** that **[delivers specific value]**. Unlike **[primary competitive alternative]**, **[product]** **[key differentiator that matters to this segment]**.647648**Positioning Validation:**649650Test positioning with ≥5 prospects from the target segment BEFORE launch. Iterate based on:651652| Signal | Interpretation | Action |653|--------|---------------|--------|654| Prospect immediately understands what you do | Category choice is correct | Proceed |655| Prospect says "oh, like [competitor]?" correctly | Positioning is clear relative to alternatives | Proceed |656| Prospect says "oh, like [wrong category]?" | Category choice is wrong | Reframe the category |657| Prospect doesn't understand why they'd switch from current solution | Value for customer is unclear or insufficient | Sharpen the differentiation |658| Prospect says "that's interesting but not for us" | Target customer is wrong, or you're talking to wrong person | Check segment selection |659660**Battlecard Structure:**661662For each primary competitor, build a battlecard that sales and marketing can use:663664| Section | Content |665|---------|---------|666| **Quick take** | 2-sentence summary of how we win against this competitor |667| **Their pitch** | What they'll say about themselves (and what's true vs. marketing) |668| **Our wedge** | Where w669670…(truncated)