정보
이 스킬은 기술 채택 라이프사이클을 탐색하기 위한 "캐즘 극복" 프레임워크를 제공하며, 특히 제품을 얼리 어답터에서 주류 시장으로 이동시키는 데 중점을 둡니다. 볼링핀 접근법이나 기존 시장 선도자와의 포지셔닝 전략 같은 핵심 전략을 다룹니다. 기술 제품의 시장 진출을 계획할 때나 얼리 어답터 이후 성장이 정체되었을 때 활용하세요.
빠른 설치
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-chasmClaude 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은(는) wondelai이(가) 만든 Claude Skill입니다. Skill은 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)을 위한 프로덕션 검증된 설정을 제공합니다. 콘텐츠 콜렉션은 Markdown/MDX 파일을 Zod 검증이 포함된 타입 안전한 데이터 콜렉션으로 변환해주는 TypeScript 최우선 도구입니다. 블로그, 문서 사이트 또는 콘텐츠 중심의 Vite + React 애플리케이션을 구축할 때 타입 안전성과 자동 콘텐츠 검증을 보장하기 위해 사용하세요. Vite 플러그인 구성과 MDX 컴파일부터 배포 최적화 및 스키마 검증에 이르기까지 모든 것을 다룹니다.
이 스킬은 개발자들이 Polymarket 예측 시장 플랫폼을 활용한 애플리케이션을 구축할 수 있도록 지원하며, 거래 및 시장 데이터를 위한 API 통합 기능을 포함합니다. 또한 WebSocket을 통한 실시간 데이터 스트리밍을 제공하여 실시간 거래와 시장 활동을 모니터링할 수 있습니다. 이를 통해 거래 전략을 구현하거나 실시간 시장 업데이트를 처리하는 도구를 생성하는 데 활용할 수 있습니다.
이 스킬은 개발자들이 명령어, 파일, LSP 작업 등 25개 이상의 이벤트 유형에 연결되는 OpenCode 플러그인을 만들 수 있도록 돕습니다. JavaScript/TypeScript 모듈을 위한 플러그인 구조, 이벤트 API 명세, 구현 패턴을 제공합니다. OpenCode AI 어시스턴트의 라이프사이클을 사용자 정의 이벤트 기반 로직으로 가로채거나, 모니터링하거나, 확장해야 할 때 사용하세요.
SGLang은 RadixAttention 프리픽스 캐싱을 활용하여 JSON, 정규식, 에이전트 워크플로우를 위한 고속 구조화 생성에 특화된 고성능 LLM 서빙 프레임워크입니다. 특히 반복되는 프리픽스가 있는 작업에서 상당히 빠른 추론 속도를 제공하여 복잡한 구조화 출력 및 다중 턴 대화에 이상적입니다. 제약 디코딩이 필요하거나 광범위한 프리픽스 공유가 있는 애플리케이션을 구축할 때는 vLLM과 같은 대안보다 SGLang을 선택하십시오.
