crossing-the-chasm
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
- 最近更新
- 2026-09-07
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- crossing-the-chasm
- license
- MIT
- metadata
- { "author": "wondelai", "version": "1.4.0" }
- 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.
02 资源文件 8
- 参考文档references/b2b-saas.md19.0 KB
- 参考文档references/beachhead-selection.md13.7 KB
- 参考文档references/buyer-segments.md13.8 KB
- 参考文档references/case-studies.md20.4 KB
- 参考文档references/expansion.md12.7 KB
- 参考文档references/go-to-market.md13.9 KB
- 参考文档references/positioning.md13.0 KB
- 参考文档references/whole-product.md13.1 KB
03 SKILL.md 正文
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 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 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 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 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 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 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 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 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" by Geoffrey A. Moore (3rd Edition)
- "Inside the Tornado" 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.
04 同仓库更多 Skills
scrapling-official
Scrape web pages using Scrapling with anti-bot bypass (like Cloudflare Turnstile), stealth headless browsing, spiders framework, adaptive scraping, and JavaScript rendering. Use when asked to scrape, crawl, or extract data from websites; web_fetch fails; the site has anti-bot protections; write Python code to scrape/crawl; or write spiders.
working-with-legacy-code
Safely change and test untested codebases using Feathers' "Working Effectively with Legacy Code". Use when the user mentions "legacy code", "no tests", "untested codebase", "how do I test this", "seams", "characterization tests", "golden master", "sprout method", "afraid to change this code", "monster method", "dependency breaking", or "inherited a messy codebase". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout/wrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.
web-typography
Select, pair, and implement typefaces for web projects. Use when the user mentions "font pairing", "which typeface", "line height", "responsive typography", "web font loading", "type hierarchy", "variable fonts", "FOUT/FOIT", "typographic scale", or "the text is hard to read". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.
ux-heuristics
Evaluate and improve interface usability using heuristic analysis. Use when the user mentions "usability audit", "users are confused", "form usability", "navigation problems", "Nielsen heuristics", "cognitive walkthrough", or "is this easy to use". Also trigger when reviewing a design for usability issues, improving form-completion rates, or evaluating information architecture and navigation. Covers Krug's laws, Nielsen's 10 heuristics, severity ratings, dark-pattern recognition, and accessibility. For visual design fixes, see refactoring-ui. For conversion-focused audits, see cro-methodology.
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same problems", or "get the whole team aligned". Also trigger when a growing company needs meeting structure, goal-setting frameworks, or a systematic way to solve recurring organizational issues. Covers the six EOS components: Vision, People, Data, Issues, Process, Traction. For team motivation design, see drive-motivation. For lean experimentation, see lean-startup.
top-design
Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "Awwwards quality", "make my site stunning", "scroll animations", "parallax storytelling", "cinematic web design", "portfolio site", or "brand experience". Also trigger when elevating a standard landing page into a memorable digital experience. Covers dramatic typography, purposeful motion, scroll-based composition, and performance-optimized animation. For foundational UI, see refactoring-ui. For type selection, see web-typography.