Files of Beachhead market selection
wondelai/
Show the full text279 lines
Beachhead Market Selection
Choosing the right beachhead market segment is the single most consequential decision in crossing the chasm. Get it right, and you build an unassailable position from which to expand. Get it wrong, and you burn through resources chasing a market that can never become a stronghold.
This reference provides a complete framework for identifying, evaluating, and committing to a beachhead segment.
Why One Segment, Not Many
The instinct to pursue multiple segments simultaneously is the most common and most fatal mistake in chasm-crossing. Here is why focus on a single segment is non-negotiable:
The resource constraint: You must build a whole product for the beachhead. Each segment requires different integrations, training, references, and positioning. Attempting two segments means delivering half a whole product to each -- and pragmatists won't buy half a solution.
The reference constraint: Pragmatists buy based on peer references. "500 companies use us" means nothing. "30 orthopedic surgery centers like yours use us" means everything. References only count within a segment.
The word-of-mouth constraint: Pragmatists talk to people like themselves. A win at a hospital doesn't help you sell to a bank. Concentration creates viral growth within the segment; dispersion creates silence.
Step 1: Brainstorm 20+ Candidate Segments
Cast the widest possible net before narrowing. Use these prompts to generate candidates:
Segment Generation Prompts
- By industry vertical: Which industries have the problem you solve? List every one.
- By company size: Within each industry, which company size tier feels the pain most?
- By job function: Which roles are most affected by the problem?
- By use case: What specific workflow or process does your product improve?
- By geography: Are there regions where the problem is more acute?
- By technology stack: Who uses complementary technology that creates an opportunity?
- By regulatory environment: Are there compliance mandates that create urgency?
- By existing behavior: Who is already solving this with painful workarounds?
Example: B2B Data Analytics Platform
| # | Candidate Segment |
|---|---|
| 1 | Financial services risk teams (50-500 employees) |
| 2 | Healthcare claims processing departments |
| 3 | E-commerce merchandising teams |
| 4 | SaaS product analytics teams |
| 5 | Manufacturing quality control departments |
| 6 | Retail supply chain planners |
| 7 | Insurance underwriting teams |
| 8 | Government data reporting offices |
| 9 | Pharmaceutical clinical trial analysts |
| 10 | Real estate portfolio analysts |
| 11 | Media ad-tech operations teams |
| 12 | Logistics fleet optimization teams |
| 13 | Telecom network planning teams |
| 14 | University research departments |
| 15 | Nonprofit donor analytics teams |
| 16 | Agricultural yield optimization teams |
| 17 | Energy grid management teams |
| 18 | Construction project estimation teams |
| 19 | Legal discovery and compliance teams |
| 20 | HR people analytics teams |
| 21 | Marketing attribution teams at DTC brands |
| 22 | Cybersecurity threat intelligence teams |
Rule of thumb: If you can't generate 20 candidates, you don't understand your market well enough yet. Talk to more customers and prospects before proceeding.
Step 2: Score Each Segment
Scoring Criteria
Rate each segment on a 1-5 scale for each criterion:
Criterion 1: Target Customer Pain (Weight: High)
How urgent and expensive is the problem for this segment?
| Score | Description |
|---|---|
| 1 | Nice-to-have; no budget allocated for this problem |
| 2 | Recognized problem but low priority |
| 3 | Known pain point with some budget; competes with other priorities |
| 4 | Significant pain causing measurable losses; active solution search |
| 5 | Hair-on-fire problem; the segment is desperate for a solution now |
Criterion 2: Whole Product Feasibility (Weight: High)
Can you deliver a complete solution for this segment within 6-12 months?
| Score | Description |
|---|---|
| 1 | Massive gaps; would take 2+ years and many partnerships |
| 2 | Major gaps in several areas; unclear how to fill them |
| 3 | Moderate gaps; achievable with 2-3 key partnerships |
| 4 | Small gaps; one partnership or one quarter of development fills them |
| 5 | Your current product, with minor additions, is already the whole product |
Criterion 3: Segment Accessibility (Weight: Medium)
Can you reach and engage decision-makers in this segment?
| Score | Description |
|---|---|
| 1 | No channels, no connections, no presence |
| 2 | Weak access; would require significant investment to reach |
| 3 | Some access through one channel (e.g., one conference, one publication) |
| 4 | Good access through multiple channels; some existing relationships |
| 5 | Strong existing relationships; team members from this industry; clear channels |
Criterion 4: Competitive Landscape (Weight: Medium)
How strong is existing competition in this segment?
| Score | Description |
|---|---|
| 1 | Dominant incumbent with deep entrenchment and switching costs |
| 2 | Strong competitor with established position |
| 3 | Competitors exist but none dominant; fragmented market |
| 4 | Weak or distracted competitors; segment underserved |
| 5 | No direct competition; segment uses manual workarounds |
Criterion 5: Word-of-Mouth Potential (Weight: High)
Do members of this segment communicate with each other frequently?
| Score | Description |
|---|---|
| 1 | Isolated; no community, no shared channels |
| 2 | Minimal interaction; occasional conferences |
| 3 | Moderate interaction; industry associations, periodic events |
| 4 | Strong community; active forums, frequent events, peer networks |
| 5 | Tight-knit community; everyone knows everyone; constant communication |
Criterion 6: Segment Size (Weight: Medium)
Is the segment large enough to build a business but small enough to dominate?
| Score | Description |
|---|---|
| 1 | Fewer than 20 potential customers; cannot sustain a business |
| 2 | 20-50 customers; very small but possible |
| 3 | 50-200 customers; good size for beachhead |
| 4 | 200-1,000 customers; strong beachhead with room to grow |
| 5 | 1,000-5,000 customers; large beachhead, may be difficult to dominate |
Note on size: A segment of 5,000+ companies is likely too broad and should be subdivided. A score of 5 can actually be a warning sign.
Segment Evaluation Scorecard Template
| Segment | Pain (x2) | Whole Product (x2) | Access (x1) | Competition (x1) | Word-of-Mouth (x2) | Size (x1) | Total (/45) |
|---|---|---|---|---|---|---|---|
| Financial risk teams | 4 (8) | 3 (6) | 4 (4) | 3 (3) | 3 (6) | 4 (4) | 31 |
| SaaS product analytics | 5 (10) | 5 (10) | 5 (5) | 2 (2) | 5 (10) | 4 (4) | 41 |
| Healthcare claims | 4 (8) | 2 (4) | 2 (2) | 4 (4) | 3 (6) | 3 (3) | 27 |
| [Your segment] |
Interpretation:
- 35-45: Strong beachhead candidate -- investigate further
- 25-34: Possible but has significant weaknesses to address
- Below 25: Likely not a viable beachhead
Step 3: Deep-Dive the Top 3 Candidates
For the top 3 scoring segments, conduct deeper validation:
Validation Checklist
- Talk to 5+ potential customers in the segment. Do they confirm the pain? Would they pay?
- Map the whole product. What exactly is needed beyond your core product? Who could partner?
- Identify existing references. Do you already have any customers in this segment?
- Test messaging. Does the positioning statement resonate when you say it out loud?
- Assess team fit. Does your team have domain knowledge? Credibility?
- Model the economics. What is the realistic deal size? How many deals to reach $X revenue?
- Map the competition. What will incumbents do when you enter?
Step 4: Choose ONE and Commit
After scoring and validation, select a single segment. This is not a reversible decision made lightly -- it is a strategic commitment that shapes your product, hiring, partnerships, and messaging for the next 12-24 months.
Commitment Checklist
- The entire leadership team agrees on the beachhead
- Product roadmap is adjusted to serve this segment's whole product needs
- Marketing messaging is rewritten for this segment
- Sales team is trained on this segment's buying process
- Partnership conversations are initiated for whole product gaps
- Success metrics are defined for segment dominance
Common Beachhead Mistakes
Mistake 1: Too Broad
Example: "Our beachhead is healthcare."
Healthcare includes hospitals, clinics, pharma companies, insurance companies, medical device makers, and dozens of other sub-segments. Each has different buyers, different pain points, different procurement processes, and different competitive landscapes.
Fix: "Our beachhead is radiology departments at community hospitals with 100-300 beds in the US Midwest."
Mistake 2: Too Narrow
Example: "Our beachhead is left-handed orthodontists in Portland, Oregon."
A segment of 12 potential customers cannot sustain a business or generate meaningful word-of-mouth.
Fix: Expand to a segment with 50-1,000 potential customers that still has tight internal communication networks.
Mistake 3: Multiple Beachheads
Example: "We're targeting both fintech startups and healthcare enterprises."
These segments have nothing in common. Different buyers, different sales cycles, different integrations, different compliance requirements. You'll build half a whole product for each and dominate neither.
Fix: Choose the one with the higher score. Return to the other after dominating the first.
Mistake 4: Choosing Based on Size Alone
Example: "The enterprise HR market is $50B, so that's our beachhead."
Large markets have entrenched incumbents. You cannot dominate a $50B market as a startup. You need a segment small enough to own.
Fix: Find the underserved niche within the large market.
Mistake 5: Choosing Based on Existing Customers
Example: "We have three enterprise customers in three different industries, so we'll target all three."
Existing customers in different segments do not constitute a beachhead. They are early adopters who bought for different reasons.
Fix: Evaluate which of those industries has the best beachhead characteristics, and focus there.
Examples: Good vs Bad Beachhead Choices
Salesforce (Good)
- Bad choice: CRM for all businesses
- Good choice (actual): Sales force automation for inside sales teams at B2B tech companies in Silicon Valley
- Why it worked: Tight community (everyone knows each other), urgent pain (managing growing sales pipelines), accessible (Salesforce founders were embedded in this community), weak competition (Siebel was too complex and expensive), strong word-of-mouth (sales leaders move between startups)
Slack (Good)
- Bad choice: Team communication for all companies
- Good choice (actual): Internal messaging for engineering teams at tech startups
- Why it worked: Engineers talk to each other constantly (conferences, GitHub, Twitter), startup teams adopt tools bottom-up, engineering teams have the most acute IRC/email pain, viral expansion from team to team
Segway (Bad)
- Attempted beachhead: Everyone who walks
- Problem: No specific segment with urgent pain. Tourists don't have urgent transportation pain. Commuters have infrastructure constraints. Law enforcement has procurement cycles. No segment was concentrated enough to dominate.
- Result: Stuck in the chasm permanently.
Scenarios Worksheet
Scenario A: Enterprise SaaS with 5 Early Adopter Customers
Your 5 early adopter customers are in: financial services (2), healthcare (1), retail (1), and manufacturing (1).
Do not try to serve all four industries. Evaluate which has the best beachhead characteristics. Financial services has two customers (more references), but check: Are they similar companies? Is the word-of-mouth network strong? Can you build the whole product?
Scenario B: Developer Tool with Strong Open Source Adoption
You have 10,000 developers using the free version. Only 50 are paying.
Do not try to convert all 10,000. Find the segment within those 10,000 where the pain is most acute and the willingness to pay is highest. Which teams are using the tool most intensively? What do they have in common? That commonality is your beachhead.
Scenario C: Horizontal Platform (Analytics, AI, Communication)
Your platform could serve any industry. The temptation to stay horizontal is overwhelming.
Resist it. Pick the vertical where you have the most unfair advantage: existing relationships, domain expertise on your team, strongest early adopter success, or weakest competition. Go deep. You can go broad later.
Scenario D: Marketplace or Network-Effect Business
You need both sides of the market. Pick the beachhead for the supply side first (they're harder to attract), in the geography or vertical where you can achieve the highest density fastest.
From Beachhead to Expansion
Once you dominate your beachhead (see: expansion.md), the bowling pin strategy takes over. But "domination" means:
- 30-50%+ market share within the segment
- Strong reference base (10+ vocal advocates)
- Repeatable sales process with predictable metrics
- Whole product fully assembled
- Competition acknowledges your leadership in this niche
Until you hit these markers, you have not earned the right to expand. Expanding prematurely from an unconquered beachhead is the second most common chasm-crossing failure.
| 1 | # Beachhead Market Selection |
| 2 | |
| 3 | Choosing the right beachhead market segment is the single most consequential decision in crossing the chasm. Get it right, and you build an unassailable position from which to expand. Get it wrong, and you burn through resources chasing a market that can never become a stronghold. |
| 4 | |
| 5 | This reference provides a complete framework for identifying, evaluating, and committing to a beachhead segment. |
| 6 | |
| 7 | ## Why One Segment, Not Many |
| 8 | |
| 9 | The instinct to pursue multiple segments simultaneously is the most common and most fatal mistake in chasm-crossing. Here is why focus on a single segment is non-negotiable: |
| 10 | |
| 11 | **The resource constraint:** You must build a whole product for the beachhead. Each segment requires different integrations, training, references, and positioning. Attempting two segments means delivering half a whole product to each -- and pragmatists won't buy half a solution. |
| 12 | |
| 13 | **The reference constraint:** Pragmatists buy based on peer references. "500 companies use us" means nothing. "30 orthopedic surgery centers like yours use us" means everything. References only count within a segment. |
| 14 | |
| 15 | **The word-of-mouth constraint:** Pragmatists talk to people like themselves. A win at a hospital doesn't help you sell to a bank. Concentration creates viral growth within the segment; dispersion creates silence. |
| 16 | |
| 17 | ## Step 1: Brainstorm 20+ Candidate Segments |
| 18 | |
| 19 | Cast the widest possible net before narrowing. Use these prompts to generate candidates: |
| 20 | |
| 21 | ### Segment Generation Prompts |
| 22 | |
| 23 | **By industry vertical:** Which industries have the problem you solve? List every one. |
| 24 | **By company size:** Within each industry, which company size tier feels the pain most? |
| 25 | **By job function:** Which roles are most affected by the problem? |
| 26 | **By use case:** What specific workflow or process does your product improve? |
| 27 | **By geography:** Are there regions where the problem is more acute? |
| 28 | **By technology stack:** Who uses complementary technology that creates an opportunity? |
| 29 | **By regulatory environment:** Are there compliance mandates that create urgency? |
| 30 | **By existing behavior:** Who is already solving this with painful workarounds? |
| 31 | |
| 32 | ### Example: B2B Data Analytics Platform |
| 33 | |
| 34 | | # | Candidate Segment | |
| 35 | |---|-------------------| |
| 36 | | 1 | Financial services risk teams (50-500 employees) | |
| 37 | | 2 | Healthcare claims processing departments | |
| 38 | | 3 | E-commerce merchandising teams | |
| 39 | | 4 | SaaS product analytics teams | |
| 40 | | 5 | Manufacturing quality control departments | |
| 41 | | 6 | Retail supply chain planners | |
| 42 | | 7 | Insurance underwriting teams | |
| 43 | | 8 | Government data reporting offices | |
| 44 | | 9 | Pharmaceutical clinical trial analysts | |
| 45 | | 10 | Real estate portfolio analysts | |
| 46 | | 11 | Media ad-tech operations teams | |
| 47 | | 12 | Logistics fleet optimization teams | |
| 48 | | 13 | Telecom network planning teams | |
| 49 | | 14 | University research departments | |
| 50 | | 15 | Nonprofit donor analytics teams | |
| 51 | | 16 | Agricultural yield optimization teams | |
| 52 | | 17 | Energy grid management teams | |
| 53 | | 18 | Construction project estimation teams | |
| 54 | | 19 | Legal discovery and compliance teams | |
| 55 | | 20 | HR people analytics teams | |
| 56 | | 21 | Marketing attribution teams at DTC brands | |
| 57 | | 22 | Cybersecurity threat intelligence teams | |
| 58 | |
| 59 | **Rule of thumb:** If you can't generate 20 candidates, you don't understand your market well enough yet. Talk to more customers and prospects before proceeding. |
| 60 | |
| 61 | ## Step 2: Score Each Segment |
| 62 | |
| 63 | ### Scoring Criteria |
| 64 | |
| 65 | Rate each segment on a 1-5 scale for each criterion: |
| 66 | |
| 67 | #### Criterion 1: Target Customer Pain (Weight: High) |
| 68 | |
| 69 | How urgent and expensive is the problem for this segment? |
| 70 | |
| 71 | | Score | Description | |
| 72 | |-------|-------------| |
| 73 | | 1 | Nice-to-have; no budget allocated for this problem | |
| 74 | | 2 | Recognized problem but low priority | |
| 75 | | 3 | Known pain point with some budget; competes with other priorities | |
| 76 | | 4 | Significant pain causing measurable losses; active solution search | |
| 77 | | 5 | Hair-on-fire problem; the segment is desperate for a solution now | |
| 78 | |
| 79 | #### Criterion 2: Whole Product Feasibility (Weight: High) |
| 80 | |
| 81 | Can you deliver a complete solution for this segment within 6-12 months? |
| 82 | |
| 83 | | Score | Description | |
| 84 | |-------|-------------| |
| 85 | | 1 | Massive gaps; would take 2+ years and many partnerships | |
| 86 | | 2 | Major gaps in several areas; unclear how to fill them | |
| 87 | | 3 | Moderate gaps; achievable with 2-3 key partnerships | |
| 88 | | 4 | Small gaps; one partnership or one quarter of development fills them | |
| 89 | | 5 | Your current product, with minor additions, is already the whole product | |
| 90 | |
| 91 | #### Criterion 3: Segment Accessibility (Weight: Medium) |
| 92 | |
| 93 | Can you reach and engage decision-makers in this segment? |
| 94 | |
| 95 | | Score | Description | |
| 96 | |-------|-------------| |
| 97 | | 1 | No channels, no connections, no presence | |
| 98 | | 2 | Weak access; would require significant investment to reach | |
| 99 | | 3 | Some access through one channel (e.g., one conference, one publication) | |
| 100 | | 4 | Good access through multiple channels; some existing relationships | |
| 101 | | 5 | Strong existing relationships; team members from this industry; clear channels | |
| 102 | |
| 103 | #### Criterion 4: Competitive Landscape (Weight: Medium) |
| 104 | |
| 105 | How strong is existing competition in this segment? |
| 106 | |
| 107 | | Score | Description | |
| 108 | |-------|-------------| |
| 109 | | 1 | Dominant incumbent with deep entrenchment and switching costs | |
| 110 | | 2 | Strong competitor with established position | |
| 111 | | 3 | Competitors exist but none dominant; fragmented market | |
| 112 | | 4 | Weak or distracted competitors; segment underserved | |
| 113 | | 5 | No direct competition; segment uses manual workarounds | |
| 114 | |
| 115 | #### Criterion 5: Word-of-Mouth Potential (Weight: High) |
| 116 | |
| 117 | Do members of this segment communicate with each other frequently? |
| 118 | |
| 119 | | Score | Description | |
| 120 | |-------|-------------| |
| 121 | | 1 | Isolated; no community, no shared channels | |
| 122 | | 2 | Minimal interaction; occasional conferences | |
| 123 | | 3 | Moderate interaction; industry associations, periodic events | |
| 124 | | 4 | Strong community; active forums, frequent events, peer networks | |
| 125 | | 5 | Tight-knit community; everyone knows everyone; constant communication | |
| 126 | |
| 127 | #### Criterion 6: Segment Size (Weight: Medium) |
| 128 | |
| 129 | Is the segment large enough to build a business but small enough to dominate? |
| 130 | |
| 131 | | Score | Description | |
| 132 | |-------|-------------| |
| 133 | | 1 | Fewer than 20 potential customers; cannot sustain a business | |
| 134 | | 2 | 20-50 customers; very small but possible | |
| 135 | | 3 | 50-200 customers; good size for beachhead | |
| 136 | | 4 | 200-1,000 customers; strong beachhead with room to grow | |
| 137 | | 5 | 1,000-5,000 customers; large beachhead, may be difficult to dominate | |
| 138 | |
| 139 | **Note on size:** A segment of 5,000+ companies is likely too broad and should be subdivided. A score of 5 can actually be a warning sign. |
| 140 | |
| 141 | ## Segment Evaluation Scorecard Template |
| 142 | |
| 143 | | Segment | Pain (x2) | Whole Product (x2) | Access (x1) | Competition (x1) | Word-of-Mouth (x2) | Size (x1) | Total (/45) | |
| 144 | |---------|-----------|--------------------|--------------|--------------------|---------------------|------------|-------------| |
| 145 | | Financial risk teams | 4 (8) | 3 (6) | 4 (4) | 3 (3) | 3 (6) | 4 (4) | 31 | |
| 146 | | SaaS product analytics | 5 (10) | 5 (10) | 5 (5) | 2 (2) | 5 (10) | 4 (4) | 41 | |
| 147 | | Healthcare claims | 4 (8) | 2 (4) | 2 (2) | 4 (4) | 3 (6) | 3 (3) | 27 | |
| 148 | | *[Your segment]* | | | | | | | | |
| 149 | |
| 150 | **Interpretation:** |
| 151 | 35-45: Strong beachhead candidate -- investigate further |
| 152 | 25-34: Possible but has significant weaknesses to address |
| 153 | Below 25: Likely not a viable beachhead |
| 154 | |
| 155 | ## Step 3: Deep-Dive the Top 3 Candidates |
| 156 | |
| 157 | For the top 3 scoring segments, conduct deeper validation: |
| 158 | |
| 159 | ### Validation Checklist |
| 160 | |
| 161 | [ ] **Talk to 5+ potential customers** in the segment. Do they confirm the pain? Would they pay? |
| 162 | [ ] **Map the whole product.** What exactly is needed beyond your core product? Who could partner? |
| 163 | [ ] **Identify existing references.** Do you already have any customers in this segment? |
| 164 | [ ] **Test messaging.** Does the positioning statement resonate when you say it out loud? |
| 165 | [ ] **Assess team fit.** Does your team have domain knowledge? Credibility? |
| 166 | [ ] **Model the economics.** What is the realistic deal size? How many deals to reach $X revenue? |
| 167 | [ ] **Map the competition.** What will incumbents do when you enter? |
| 168 | |
| 169 | ## Step 4: Choose ONE and Commit |
| 170 | |
| 171 | After scoring and validation, select a single segment. This is not a reversible decision made lightly -- it is a strategic commitment that shapes your product, hiring, partnerships, and messaging for the next 12-24 months. |
| 172 | |
| 173 | ### Commitment Checklist |
| 174 | |
| 175 | [ ] The entire leadership team agrees on the beachhead |
| 176 | [ ] Product roadmap is adjusted to serve this segment's whole product needs |
| 177 | [ ] Marketing messaging is rewritten for this segment |
| 178 | [ ] Sales team is trained on this segment's buying process |
| 179 | [ ] Partnership conversations are initiated for whole product gaps |
| 180 | [ ] Success metrics are defined for segment dominance |
| 181 | |
| 182 | ## Common Beachhead Mistakes |
| 183 | |
| 184 | ### Mistake 1: Too Broad |
| 185 | |
| 186 | **Example:** "Our beachhead is healthcare." |
| 187 | |
| 188 | Healthcare includes hospitals, clinics, pharma companies, insurance companies, medical device makers, and dozens of other sub-segments. Each has different buyers, different pain points, different procurement processes, and different competitive landscapes. |
| 189 | |
| 190 | **Fix:** "Our beachhead is radiology departments at community hospitals with 100-300 beds in the US Midwest." |
| 191 | |
| 192 | ### Mistake 2: Too Narrow |
| 193 | |
| 194 | **Example:** "Our beachhead is left-handed orthodontists in Portland, Oregon." |
| 195 | |
| 196 | A segment of 12 potential customers cannot sustain a business or generate meaningful word-of-mouth. |
| 197 | |
| 198 | **Fix:** Expand to a segment with 50-1,000 potential customers that still has tight internal communication networks. |
| 199 | |
| 200 | ### Mistake 3: Multiple Beachheads |
| 201 | |
| 202 | **Example:** "We're targeting both fintech startups and healthcare enterprises." |
| 203 | |
| 204 | These segments have nothing in common. Different buyers, different sales cycles, different integrations, different compliance requirements. You'll build half a whole product for each and dominate neither. |
| 205 | |
| 206 | **Fix:** Choose the one with the higher score. Return to the other after dominating the first. |
| 207 | |
| 208 | ### Mistake 4: Choosing Based on Size Alone |
| 209 | |
| 210 | **Example:** "The enterprise HR market is $50B, so that's our beachhead." |
| 211 | |
| 212 | Large markets have entrenched incumbents. You cannot dominate a $50B market as a startup. You need a segment small enough to own. |
| 213 | |
| 214 | **Fix:** Find the underserved niche within the large market. |
| 215 | |
| 216 | ### Mistake 5: Choosing Based on Existing Customers |
| 217 | |
| 218 | **Example:** "We have three enterprise customers in three different industries, so we'll target all three." |
| 219 | |
| 220 | Existing customers in different segments do not constitute a beachhead. They are early adopters who bought for different reasons. |
| 221 | |
| 222 | **Fix:** Evaluate which of those industries has the best beachhead characteristics, and focus there. |
| 223 | |
| 224 | ## Examples: Good vs Bad Beachhead Choices |
| 225 | |
| 226 | ### Salesforce (Good) |
| 227 | |
| 228 | **Bad choice:** CRM for all businesses |
| 229 | **Good choice (actual):** Sales force automation for inside sales teams at B2B tech companies in Silicon Valley |
| 230 | **Why it worked:** Tight community (everyone knows each other), urgent pain (managing growing sales pipelines), accessible (Salesforce founders were embedded in this community), weak competition (Siebel was too complex and expensive), strong word-of-mouth (sales leaders move between startups) |
| 231 | |
| 232 | ### Slack (Good) |
| 233 | |
| 234 | **Bad choice:** Team communication for all companies |
| 235 | **Good choice (actual):** Internal messaging for engineering teams at tech startups |
| 236 | **Why it worked:** Engineers talk to each other constantly (conferences, GitHub, Twitter), startup teams adopt tools bottom-up, engineering teams have the most acute IRC/email pain, viral expansion from team to team |
| 237 | |
| 238 | ### Segway (Bad) |
| 239 | |
| 240 | **Attempted beachhead:** Everyone who walks |
| 241 | **Problem:** No specific segment with urgent pain. Tourists don't have urgent transportation pain. Commuters have infrastructure constraints. Law enforcement has procurement cycles. No segment was concentrated enough to dominate. |
| 242 | **Result:** Stuck in the chasm permanently. |
| 243 | |
| 244 | ## Scenarios Worksheet |
| 245 | |
| 246 | ### Scenario A: Enterprise SaaS with 5 Early Adopter Customers |
| 247 | |
| 248 | Your 5 early adopter customers are in: financial services (2), healthcare (1), retail (1), and manufacturing (1). |
| 249 | |
| 250 | **Do not** try to serve all four industries. Evaluate which has the best beachhead characteristics. Financial services has two customers (more references), but check: Are they similar companies? Is the word-of-mouth network strong? Can you build the whole product? |
| 251 | |
| 252 | ### Scenario B: Developer Tool with Strong Open Source Adoption |
| 253 | |
| 254 | You have 10,000 developers using the free version. Only 50 are paying. |
| 255 | |
| 256 | **Do not** try to convert all 10,000. Find the segment within those 10,000 where the pain is most acute and the willingness to pay is highest. Which teams are using the tool most intensively? What do they have in common? That commonality is your beachhead. |
| 257 | |
| 258 | ### Scenario C: Horizontal Platform (Analytics, AI, Communication) |
| 259 | |
| 260 | Your platform could serve any industry. The temptation to stay horizontal is overwhelming. |
| 261 | |
| 262 | **Resist it.** Pick the vertical where you have the most unfair advantage: existing relationships, domain expertise on your team, strongest early adopter success, or weakest competition. Go deep. You can go broad later. |
| 263 | |
| 264 | ### Scenario D: Marketplace or Network-Effect Business |
| 265 | |
| 266 | You need both sides of the market. Pick the beachhead for the supply side first (they're harder to attract), in the geography or vertical where you can achieve the highest density fastest. |
| 267 | |
| 268 | ## From Beachhead to Expansion |
| 269 | |
| 270 | Once you dominate your beachhead (see: expansion.md), the bowling pin strategy takes over. But "domination" means: |
| 271 | |
| 272 | 30-50%+ market share within the segment |
| 273 | Strong reference base (10+ vocal advocates) |
| 274 | Repeatable sales process with predictable metrics |
| 275 | Whole product fully assembled |
| 276 | Competition acknowledges your leadership in this niche |
| 277 | |
| 278 | Until you hit these markers, you have not earned the right to expand. Expanding prematurely from an unconquered beachhead is the second most common chasm-crossing failure. |
| 279 |
Discussion
Browse more free Claude skills.