crossing-the-chasm — Claude Code skill: reaching mainstream market
Framework for the transition from early adopters to mainstream buyers. Identifies your beachhead, defines the complete product pragmatists need, and plots the first move when growth stalls after enthusiasts.
npx skills add wondelai/skills --skill crossing-the-chasm -a claude-codeWhat crossing-the-chasm does
This skill implements Geoffrey Moore's crossing-the-chasm playbook — a roadmap for tech products stuck between visionaries and the mainstream. The core insight: early adopters and pragmatists are separated by a chasm. Enthusiasts embrace new technology; pragmatists demand proven solutions. One pitch repels both.
Inside: a diagnostic (score your go-to-market on a 0-10 scale using seven criteria), beachhead selection with an evaluation matrix, whole-product assembly across four layers (generic, expected, augmented, potential), D-Day strategy, incumbent positioning, and scaling patterns. Includes a separate path for B2B SaaS with freemium — the dynamics shift there.
Use it to chart go-to-market for a startup or refocus a stalled product. Best when traction flatlines after early users, the team debates first big customer targets, or you need to justify focused positioning instead of trying to reach everyone.
What it helps with
- choose a market segment to dominate first
- diagnose why growth stops after early adopters
- build the complete product pragmatists actually need
- position against entrenched competitors
- shift messaging from visionary language to pragmatic value
Example prompts for the agent
- Which beachhead should we target for crossing-the-chasm?
- Help me define the whole product for our segment
- Score our go-to-market strategy: are we close to crossing?
How to install crossing-the-chasm
1Skills CLI (Vercel)
npx skills add wondelai/skills --skill crossing-the-chasm -a claude-code2Manually: put the files in place
~/.claude/skills/crossing-the-chasm/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/crossing-the-chasm/
1Skills CLI (Vercel)
npx skills add wondelai/skills --skill crossing-the-chasm -a codex2Manually: put the files in place
.agents/skills/crossing-the-chasm/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wondelai/skills --skill crossing-the-chasm -a cursor2Manually: put the files in place
.cursor/skills/crossing-the-chasm/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wondelai/skills crossing-the-chasm2Manually: put the files in place
.github/skills/crossing-the-chasm/SKILL.md1Skills CLI (Vercel)
npx skills add wondelai/skills --skill crossing-the-chasm -a gemini-cli2Platform CLI
gemini skills install https://github.com/wondelai/skills --path crossing-the-chasmManually: put the files in place
.devin/skills/crossing-the-chasm/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add wondelai/skills --skill crossing-the-chasm -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about crossing-the-chasm
How do I install crossing-the-chasm in Claude Code?
Run npx skills add wondelai/skills --skill crossing-the-chasm -a claude-code, then find the skill at ~/.claude/skills/crossing-the-chasm/SKILL.md.
What does crossing-the-chasm do?
It maps a step-by-step strategy to move from early adopters to mainstream: pick your target segment, assemble the complete product, reposition your messaging, and execute first sale. Scores your current position on a 0-10 scale and names gaps to close.
Does the strategy differ for freemium B2B SaaS?
Yes. The skill includes a separate section remapping every step for free trials and self-serve: how social proof builds differently, what the chasm crossing signal looks like, and why 1,000 free users may not mean you've crossed.
Source text
SKILL.md · MIT
---
name: crossing-the-chasm
description: 'Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs mainstream", "tech go-to-market", "bowling pin strategy", "technology adoption lifecycle", "pragmatist buyers", "growth stalled after early adopters", or "our go-to-market plan". Also trigger when planning go-to-market for a technical product. Covers the D-Day analogy, bowling-pin strategy, the tornado, and positioning against incumbents. For product positioning, see obviously-awesome. For new market creation, see blue-ocean-strategy.'
license: MIT
metadata:
author: wondelai
version: "1.4.1"
---
# Crossing the Chasm Framework
Strategic framework for marketing and selling disruptive technology products, particularly the transition from early adopters to mainstream customers.
## Core Principle
**There is a chasm between early adopters and the mainstream market.** Most tech companies fail not because they can't build great products, but because they can't cross from visionaries who love new technology to pragmatists who just want solutions that work. The two groups want fundamentally different things -- what wins over innovators actively repels the early majority -- so you must change your strategy, and your whole product, to cross.
If the product is modern PLG/freemium B2B SaaS, read [references/b2b-saas.md](references/b2b-saas.md) first -- it remaps every step below (the chasm, beachhead, whole product, metrics) for self-serve trials, free tiers, and the false-signal trap where 1,000 free users looks like a crossing but isn't.
## Scoring
**Goal: 10/10.** Score any tech go-to-market by the Quick Diagnostic at the end: count the rows answered "yes" and map the 7 rows onto a 0-10 scale (roughly 1.4 points per satisfied row).
- **9-10:** single dominable beachhead chosen, 10+ in-segment references, whole product complete via partners, evolution-not-revolution positioning, pragmatist-aligned channel -- adoption is accelerating. You've crossed.
- **5-6:** beachhead picked but whole product or references still thin, or positioning still reads "revolutionary." You're mid-chasm; ship the missing whole-product layers and case studies.
- **<=3:** multiple beachheads (or none), visionary messaging, MVP-grade product. Classic early-market tactics aimed at the mainstream -- the most common reason to stall.
Report the score, name the failing diagnostic rows, and give the fix for each.
## The Technology Adoption Life Cycle
```
Innovators → Early Adopters → [CHASM] → Early Majority → Late Majority → Laggards
2.5% 13.5% 34% 34% 16%
```
**The Chasm:** The gap between early adopters (13.5%) and early majority (34%) -- where most tech products die.
### The Five Buyer Groups
| Segment | % Market | Psychology | What They Buy | What They Need |
|---------|----------|------------|---------------|----------------|
| **Innovators** | 2.5% | Technology enthusiasts | The newest, coolest tech | Product exists, technical specs |
| **Early Adopters** | 13.5% | Visionaries seeking advantage | Change, revolution, competitive edge | Vision, big potential, strategic value |
| **[THE CHASM]** | — | — | — | — |
| **Early Majority** | 34% | Pragmatists | Productivity improvements | Whole product, references, de-risked |
| **Late Majority** | 34% | Conservatives | Avoid being left behind | Commodity, support, low risk |
| **Laggards** | 16% | Skeptics | Only when forced | Cheap, simple, necessary |
**Critical insight:** Early adopters and early majority look similar but want opposite things:
| Early Adopters (Visionaries) | Early Majority (Pragmatists) |
|------------------------------|------------------------------|
| Want to be first | Want proven solutions |
| Tolerate bugs and workarounds | Need it to "just work" |
| Buy the future vision | Buy present value |
| Need no references | Need references from peers |
| Want custom solutions, high risk tolerance | Want standards, low risk tolerance |
**Why this matters:** You can't market to both simultaneously -- visionary testimonials scare off pragmatists.
See: [references/buyer-segments.md](references/buyer-segments.md) when you need to identify which group a specific prospect belongs to, or to write segment-specific messaging -- it has full psychographics and buying triggers per group.
**The reference catch-22:** Pragmatists won't buy without references from other pragmatists -- but none exist until someone crosses first. This is *why* the chasm is a chasm and not a slope: the social proof the early majority requires cannot accumulate gradually. Breaking it is the whole game (Steps 1-2 below).
## The D-Day Strategy: Crossing the Chasm
**Bad approach:** Try to be everything to everyone (stall in the chasm). **Good approach:** Target a single beachhead, dominate it, expand from a position of strength.
### Step 1: Target the Point of Attack
**Choose a single, narrowly defined market segment.**
**Beachhead characteristics:** specific ("orthopedic surgical centers with 5-10 surgeons", not "healthcare"); urgent, expensive pain; accessible via known channels; a compelling reason to buy (you're 10x better for their problem); whole-product potential via partners; vocal reference potential.
| Criteria | Good Beachhead | Bad Beachhead |
|----------|----------------|---------------|
| **Size** | Big enough to matter, small enough to dominate | Too small to build on, or too big to own |
| **Pain** | Urgent, expensive problem | Nice-to-have |
| **Access** | Clear channels to reach | Scattered, hard to reach |
| **Competition** | Weak or non-existent | Entrenched incumbents |
| **Word-of-mouth** | They talk to each other | Siloed, isolated |
**Example (Salesforce):** not "CRM for all businesses" but "sales force automation for inside sales teams at B2B SaaS startups."
**Process:** Brainstorm 20+ segments, score each against the criteria, choose ONE (resist keeping options open), commit to dominating it.
See: [references/beachhead-selection.md](references/beachhead-selection.md) when running the brainstorm-and-score step above -- it has the scoring matrix, weighting, and the target-customer characterization worksheet to pick the one segment.
### Step 2: Assemble the Invasion Force
**Create the "whole product" for your beachhead segment.**
Whole product layers: Generic (what you ship) → Expected (minimum viable) → Augmented (what pragmatists actually need) → Potential (what it could become).
**Example: marketing automation software**
| Layer | What It Includes |
|-------|------------------|
| **Generic** | Email sending, list management |
| **Expected** | Templates, analytics, API |
| **Augmented** | CRM integration, training, support, services, best-practice playbooks |
| **Potential** | AI optimization, personalization, account-based marketing |
**Critical:** The early majority buys the augmented product; ship only the generic and they won't buy.
**Whole product checklist:**
- [ ] Core technology (your product)
- [ ] Complementary products/services (integrations, partner solutions)
- [ ] Installation and setup (onboarding, migration)
- [ ] Training, support, documentation, best practices
- [ ] Industry-specific adaptations
- [ ] Risk mitigation (security, compliance, SLAs)
**Partnerships:** Identify gaps between generic and augmented, partner with companies that fill them, go to market jointly for the beachhead.
See: [references/whole-product.md](references/whole-product.md) when mapping your gaps -- it extends the layers above with a 12-row gap-analysis matrix, the 80% rule, support-tier SLAs, and a planning canvas.
### Step 3: Define the Battle
**Position against the competition.**
**Positioning formula:**
- For [target customer]
- Who [statement of need/opportunity]
- Our product is a [product category]
- That [statement of key benefit]
- Unlike [primary competitive alternative]
- Our product [statement of primary differentiation]
**Example (early Workday):** For mid-market companies who need modern HR and finance systems, Workday is a cloud-based ERP that delivers consumer-grade UX and fast implementation. Unlike Oracle and SAP, it requires no IT infrastructure and deploys in months, not years.
**Competitive positioning:** The market alternative is often NOT a direct competitor -- it's manual processes, spreadsheets, or legacy systems. Differentiate on a dimension you dominate and make the incumbent's strength irrelevant: Salesforce's "No software" positioning turned feature-rich Siebel's complexity into a weakness.
See: [references/positioning.md](references/positioning.md) when filling in the formula above or choosing the competitive alternative to displace -- it has the claim-and-evidence structure and the "make the incumbent's strength irrelevant" patterns.
### Step 4: Launch the Invasion
**Execute the go-to-market strategy.**
| Customer Type | How They Buy | Sales Strategy |
|---------------|--------------|----------------|
| **Early adopters** | Direct, evangelical CEO | Direct sales, founder-led |
| **Early majority** | Risk-averse, need proof | Channel partners, references, content marketing |
| **Late majority** | Commodity, low-touch | Self-service, inside sales |
**For crossing (early majority):** lead with references and case studies; message whole-product completeness, ease, and low risk; position as evolution ("Better X", not "new category"); prove with ROI calculators, free trials, pilots; sell through channels pragmatists trust (analysts, integrators, consultants).
**Messaging shift:**
| Early Adopter Messaging | Early Majority Messaging |
|-------------------------|--------------------------|
| "Revolutionary new approach" | "Proven solution for [problem]" |
| "Be the first" | "Join 500 companies like yours" |
| "Change everything" | "Improve [specific metric] by X%" |
| "Visionary" | "Pragmatic" |
See: [references/go-to-market.md](references/go-to-market.md) when building the launch plan -- it details channel selection by buyer type, the reference-and-case-study engine, and pricing/pilot tactics for pragmatists.
## Bowling Pin Strategy
**After dominating the beachhead, expand to adjacent segments** -- each pin knocks down the next: Beachhead → Adjacent #1 → Adjacent #2 → Adjacent #3.
**Adjacency criteria:** similar needs (whole product transfers), reference credibility (beachhead customers influence the adjacent segment), incremental effort (don't start from scratch).
**Example (Salesforce):** inside sales at tech startups → inside sales at all B2B companies → all sales teams → customer service → marketing → full CRM platform.
**Anti-pattern:** Jumping to distant segments before dominating the beachhead.
See: [references/expansion.md](references/expansion.md) when sequencing your next 2-3 segments -- adjacency scoring and the bowling-pin ordering rules. For full worked arcs (Salesforce, VMware, Zoom, Atlassian) and stuck-in-the-chasm failures (Palm, Segway), see [references/case-studies.md](references/case-studies.md) when you need a pattern-match for your own situation.
## The Tornado: After the Chasm
**Once you cross, demand accelerates (the "tornado"):** rapid mainstream adoption, a shift from solution selling to product selling, commodity dynamics, and market-leader consolidation.
**Strategic shift:** before the chasm -- whole product, customization, high touch; during the tornado -- standardization, scalability, distribution.
**Gorilla/chimp/monkey dynamics:** the gorilla (market leader, 80%+ share) takes most of the profit; chimps (strong #2-#3) survive in niches; monkeys struggle. Become the gorilla in your beachhead, then expand.
## Common Mistakes
| Mistake | Why It Fails | Fix |
|---------|-------------|------|
| **Selling to early majority like early adopters** | Wrong messaging, wrong product | Build whole product, emphasize proof |
| **Multiple beachheads** | Spread too thin, own nothing | Choose ONE segment, dominate it |
| **Incomplete whole product** | Pragmatists won't buy | Partner to fill gaps |
| **"Revolutionary" positioning** | Scares off early majority | Frame as evolution, proven solution |
| **Skipping references** | No social proof for pragmatists | Invest in case studies, testimonials |
## Quick Diagnostic
Audit any tech go-to-market, and re-run it as the completion gate before declaring the chasm crossed. Each "If No" is a chasm symptom; act on the failing rows first.
| Question | If No | Action |
|----------|-------|--------|
| Have we chosen a single, narrowly defined beachhead with an urgent, expensive problem? | You're in the chasm | Define one narrow target market; resist multiple beachheads |
| Can we plausibly dominate this segment? | Wrong beachhead | Choose a narrower or different segment |
| Do we have 10+ reference customers from that exact segment? | Pragmatists won't buy | Build lighthouse customers and case studies |
| Is the whole product complete -- partnerships in place to fill the gaps? | Product won't meet pragmatist needs | Identify generic-to-augmented gaps, partner to fill them |
| Does positioning emphasize proven value over revolution? | Wrong message for the early majority | Reframe: evolution, not revolution |
| Is the distribution channel aligned with pragmatist buying behavior? | You reach visionaries, not pragmatists | Sell through analysts, integrators, references, channel |
| Are adoption metrics accelerating (entering the tornado)? | Still stuck before the chasm | Re-check the rows above -- something is still early-market |
## Further Reading
For the complete methodology:
- [*"Crossing the Chasm"*](https://www.amazon.com/Crossing-Chasm-3rd-Disruptive-Mainstream/dp/0062292986?tag=wondelai00-20) by Geoffrey A. Moore (3rd Edition)
- [*"Inside the Tornado"*](https://www.amazon.com/Inside-Tornado-Strategies-Developing-Hypergrowth/dp/0060745819?tag=wondelai00-20) by Geoffrey A. Moore (sequel: managing hypergrowth)
## About the Author
**Geoffrey A. Moore** is a consultant, venture partner, and author whose work at The Chasm Group and Chasm Institute has shaped go-to-market strategy for enterprise technology companies for over 30 years. *Crossing the Chasm* has sold over a million copies and is required reading at business schools and tech companies worldwide.
© wondelai · MIT · wondelai/skills