关于
This skill provides the "Crossing the Chasm" framework for navigating the technology adoption lifecycle, specifically to help transition products from early adopters to the mainstream market. It covers key concepts like the bowling pin strategy, the D-Day analogy, and positioning for pragmatist buyers. Use it when planning a go-to-market strategy for a technical product or when growth stalls after the early adopter phase.
快速安装
Claude Code
推荐npx skills add wondelai/skills -a claude-code/plugin add https://github.com/wondelai/skillsgit clone https://github.com/wondelai/skills.git ~/.claude/skills/crossing-the-chasm在 Claude Code 中复制并粘贴此命令以安装该技能
技能文档
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.
GitHub 仓库
常见问题
什么是 crossing-the-chasm Skill?
crossing-the-chasm 是一个 Claude Skill,作者为 wondelai。Skill 将 Claude 按需加载的说明和资源打包,让 Claude 无需额外提示即可执行与 crossing-the-chasm 相关的任务。
如何安装 crossing-the-chasm?
使用本页的安装命令:将 crossing-the-chasm 作为插件添加到 Claude Code,或将其仓库克隆到 skills 目录,然后重启 Claude 以加载该 Skill。
crossing-the-chasm 属于哪个分类?
crossing-the-chasm 属于元分类。
crossing-the-chasm 可以免费使用吗?
可以。crossing-the-chasm 已收录在 AIMCP,可免费安装。
相关推荐技能
Content Collections 是一个 TypeScript 优先的构建工具,可将本地 Markdown/MDX 文件转换为类型安全的数据集合。它专为构建博客、文档站和内容密集型 Vite+React 应用而设计,提供基于 Zod 的自动模式验证。该工具涵盖从 Vite 插件配置、MDX 编译到生产环境部署的完整工作流。
这个Claude Skill为开发者提供完整的Polymarket预测市场开发支持,涵盖API调用、交易执行和市场数据分析。关键特性包括实时WebSocket数据流,可监控实时交易、订单和市场动态。开发者可用它构建预测市场应用、实施交易策略并集成实时市场预测功能。
该Skill帮助开发者创建OpenCode插件,用于接入命令、文件、LSP等25+种事件。它提供了插件结构、事件API规范和JavaScript/TypeScript实现模式,适合需要拦截操作、扩展功能或自定义事件处理的场景。开发者可通过它快速构建响应式模块来增强OpenCode AI助手的能力。
SGLang是一个专为LLM设计的高性能推理框架,特别适用于需要结构化输出的场景。它通过RadixAttention前缀缓存技术,在处理JSON、正则表达式、工具调用等具有重复前缀的复杂工作流时,能实现极速生成。如果你正在构建智能体或多轮对话系统,并追求远超vLLM的推理性能,SGLang是理想选择。
