MCP HubMCP Hub
스킬 목록으로 돌아가기

crossing-the-chasm

wondelai
업데이트됨 Yesterday
5 조회
1,096
121
1,096
GitHub에서 보기
메타ai

정보

이 스킬은 개발자들이 제프리 무어의 '채즘 극복' 프레임워크를 활용해 기술 제품을 초기 수용자 단계에서 주류 시장으로 전환하는 데 도움을 줍니다. 시장 진출 과제를 해결하기 위한 볼링핀 접근법과 D-데이 비유 같은 전략을 제공합니다. 스타트업이 초기 실적은 있으나 확장에 어려움을 겪거나, 혁신적인 기술의 출시를 계획할 때 사용하세요.

빠른 설치

Claude Code

추천
기본
npx skills add wondelai/skills -a claude-code
플러그인 명령대체
/plugin add https://github.com/wondelai/skills
Git 클론대체
git 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 for transitioning 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 foundation: Early adopters and mainstream customers want fundamentally different things. What wins over innovators actively repels the early majority. You must change your strategy—and your whole product—to cross the chasm.

Scoring

Goal: 10/10. When evaluating go-to-market strategy for tech products, rate 0-10 based on alignment with chasm-crossing principles. A 10/10 means proper beachhead selection, whole product strategy, and positioning for pragmatist buyers; lower scores indicate early-market tactics applied to mainstream market. Always provide current score and improvements needed to reach 10/10.

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%). This is where most tech products die.

The Five Buyer Groups

Segment% MarketPsychologyWhat They BuyWhat They Need
Innovators2.5%Technology enthusiastsThe newest, coolest techProduct exists, technical specs
Early Adopters13.5%Visionaries seeking advantageChange, revolution, competitive edgeVision, big potential, strategic value
[THE CHASM]
Early Majority34%PragmatistsProductivity improvementsWhole product, references, de-risked
Late Majority34%ConservativesAvoid being left behindCommodity, support, low risk
Laggards16%SkepticsOnly when forcedCheap, simple, necessary

Critical insight: Early adopters and early majority look similar but want completely opposite things.

Early Adopters (Visionaries):

  • Want to be first
  • Willing to work around bugs
  • Buy the future vision
  • Don't need references
  • Want custom solutions
  • High risk tolerance

Early Majority (Pragmatists):

  • Want proven solutions
  • Need it to "just work"
  • Buy present value
  • Need references from peers
  • Want standards
  • Low risk tolerance

Why this matters: You can't market to both simultaneously. Visionary testimonials scare off pragmatists. "Revolutionary" positioning is a red flag to the early majority.

See: references/buyer-segments.md for detailed buyer psychographics.

Why the Chasm Exists

The reference gap:

  • Early majority won't buy without references from other early majority companies
  • But no early majority companies exist until someone crosses first
  • Classic catch-22

The whole product gap:

  • Early adopters tolerate incomplete products
  • Early majority demands complete, integrated solutions
  • Your MVP that wowed visionaries is unshippable to pragmatists

The positioning gap:

  • "Revolutionary" excites early adopters, terrifies early majority
  • "Disruptive" = risky, expensive, unproven
  • Pragmatists want evolution, not revolution

The D-Day Strategy: Crossing the Chasm

Bad approach: Try to be everything to everyone (stall in chasm)

Good approach: Target a single beachhead, dominate it, expand from position of strength.

Step 1: Target the Point of Attack

Choose a single, narrowly defined market segment.

Beachhead characteristics:

  • Specific: Not "healthcare" but "orthopedic surgical centers with 5-10 surgeons"
  • Urgent pain: Problem is costing them real money/time
  • Accessible: You can reach them (conferences, publications, channels)
  • Compelling reason to buy: Your solution is 10x better for their specific problem
  • Whole product potential: You can assemble partners to deliver complete solution
  • Reference potential: They'll be vocal advocates

Target segment criteria:

CriteriaGood BeachheadBad Beachhead
SizeBig enough to matter, small enough to dominateToo small (can't build on) or too big (can't own)
PainUrgent, expensive problemNice-to-have
AccessClear channels to reachScattered, hard to reach
CompetitionWeak or non-existentEntrenched incumbents
Word-of-mouthThey talk to each otherSiloed, isolated

Example: Salesforce

  • Bad: "CRM for all businesses"
  • Good: "Sales force automation for inside sales teams at B2B SaaS startups"

Process:

  1. Brainstorm 20+ possible segments
  2. Score each on criteria above
  3. Choose ONE (resist temptation to keep options open)
  4. Commit to dominating it

See: references/beachhead-selection.md for segment evaluation frameworks.

Step 2: Assemble the Invasion Force

Create the "whole product" for your beachhead segment.

Whole product layers:

Generic Product (what you ship)
    ↓
Expected Product (minimum to be viable)
    ↓
Augmented Product (what pragmatists actually need)
    ↓
Potential Product (what it could become)

Example: Marketing automation software

LayerWhat It Includes
GenericEmail sending, list management
ExpectedTemplates, analytics, API
AugmentedCRM integration, training, support, professional services, best practices playbooks
PotentialAI optimization, advanced personalization, account-based marketing

Critical: Early majority buys the augmented product. If you only deliver generic product, they won't buy.

Whole product checklist:

  • Core technology (your product)
  • Complementary products/services (integrations, partner solutions)
  • Installation and setup (onboarding, migration)
  • Training and support
  • Documentation and best practices
  • Industry-specific adaptations
  • Risk mitigation (security, compliance, SLAs)

Partnerships:

  • Identify gaps between generic and augmented product
  • Partner with companies that fill gaps
  • Joint go-to-market for beachhead segment

See: references/whole-product.md for whole product planning.

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: Workday (early positioning)

  • For mid-market companies
  • Who need modern HR and finance systems
  • Workday is a cloud-based ERP
  • That provides consumer-grade UX and fast implementation
  • Unlike Oracle and SAP
  • Workday requires no IT infrastructure and deploys in months, not years

Competitive positioning:

Identify the market alternative:

  • What do customers use today?
  • Often it's NOT a direct competitor—it's manual processes, spreadsheets, or old systems

Frame the competition:

  • Don't pick fights you can't win
  • Differentiate on dimension you dominate
  • Make their strength irrelevant

Example: Salesforce vs. Siebel

  • Siebel strength: Feature-rich, enterprise-grade
  • Salesforce positioning: "No software" (cloud-based, fast setup)
  • Result: Made Siebel's strength (complexity) a weakness

See: references/positioning.md for competitive positioning frameworks.

Step 4: Launch the Invasion

Execute the go-to-market strategy.

Distribution strategy:

Customer TypeHow They BuySales Strategy
Early adoptersDirect, evangelical CEODirect sales, founder-led
Early majorityRisk-averse, need proofChannel partners, references, content marketing
Late majorityCommodity, low-touchSelf-service, inside sales

For crossing the chasm (early majority):

  • Lead with references: Case studies, testimonials, peer recommendations
  • Whole product messaging: Emphasize completeness, ease, low risk
  • Positioning: Evolutionary, not revolutionary ("Better X" not "New category")
  • Proof: ROI calculators, free trials, pilot programs
  • Channels: Where pragmatists go for advice (analysts, integrators, consultants)

Messaging shift:

Early Adopter MessagingEarly 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 for launch strategies.

Bowling Pin Strategy

After dominating beachhead, expand to adjacent segments.

Beachhead → Adjacent #1 → Adjacent #2 → Adjacent #3
   [Pin]      [Pin]         [Pin]         [Pin]

Adjacency criteria:

  • Similar needs (so whole product transfers)
  • Reference credibility (beachhead customers influence adjacent segment)
  • Incremental effort (don't start from scratch)

Example: Salesforce expansion

  • Beachhead: Inside sales teams at tech startups
  • Pin 2: Inside sales at all B2B companies
  • Pin 3: All sales teams (field sales too)
  • Pin 4: Customer service teams
  • Pin 5: Marketing teams
  • → Full CRM platform

Anti-pattern: Jumping to distant segments before dominating beachhead.

See: references/expansion.md for segment expansion strategies.

The Tornado: After the Chasm

Once you cross the chasm, demand accelerates (the "tornado").

Tornado characteristics:

  • Rapid mainstream adoption
  • Shift from solution selling to product selling
  • Commodity dynamics emerge
  • Market leaders consolidate

Strategic shift in tornado:

  • Before chasm: Whole product, customization, high-touch
  • During tornado: Standardization, scalability, distribution

Gorilla/chimp/monkey dynamics:

  • Gorilla: Market leader (80%+ market share)
  • Chimps: Strong #2 and #3 (niche players)
  • Monkeys: Everyone else (struggling)

Goal: Become the gorilla in your beachhead, then expand.

Common Mistakes

MistakeWhy It FailsFix
Selling to early majority like early adoptersWrong messaging, wrong productBuild whole product, emphasize proof
Multiple beachheadsSpread too thin, own nothingChoose ONE segment, dominate it
Incomplete whole productPragmatists won't buyPartner to fill gaps
"Revolutionary" positioningScares off early majorityFrame as evolution, proven solution
Skipping referencesNo social proof for pragmatistsInvest in case studies, testimonials

Quick Diagnostic

Audit any tech product go-to-market:

QuestionIf NoAction
Have we chosen a single beachhead segment?You're in the chasmDefine narrow target market
Do we have references from that segment?Pragmatists won't buyBuild lighthouse customers
Is the whole product complete?Product won't meet needsIdentify gaps, build partnerships
Does positioning emphasize proven value?Wrong message for early majorityReframe: evolution not revolution
Can we dominate this segment?Wrong beachheadChoose narrower or different segment

Chasm-Crossing Checklist

Before declaring victory:

  • Single, narrowly defined beachhead segment chosen
  • Segment has urgent, expensive problem
  • We can assemble whole product for segment
  • 10+ reference customers from beachhead segment
  • Positioning emphasizes proven value, not revolution
  • Distribution channel aligned with pragmatist buying behavior
  • Partnerships in place to deliver whole product
  • Metrics show adoption accelerating (moving into tornado)

Reference Files

Further Reading

This skill is based on Geoffrey Moore's Crossing the Chasm framework. For the complete methodology:

About the Author

Geoffrey A. Moore is a consultant, venture partner, and author focused on disruptive innovation and market development. His work at The Chasm Group and Chasm Institute has influenced go-to-market strategy for enterprise technology companies for over 30 years. Crossing the Chasm has sold over 1 million copies and is required reading at many business schools and tech companies. Moore serves on the boards of several technology companies and advises Fortune 500 firms on technology adoption.

GitHub 저장소

wondelai/skills
경로: crossing-the-chasm
0
agent-skillsai-skillsclaude-codeclaude-code-marketplaceclaude-code-pluginclaude-code-skills

연관 스킬

content-collections

메타

이 스킬은 콘텐츠 콜렉션(Content Collections)을 위한 프로덕션 검증된 설정을 제공합니다. 콘텐츠 콜렉션은 Markdown/MDX 파일을 Zod 검증이 포함된 타입 안전한 데이터 콜렉션으로 변환해주는 TypeScript 최우선 도구입니다. 블로그, 문서 사이트 또는 콘텐츠 중심의 Vite + React 애플리케이션을 구축할 때 타입 안전성과 자동 콘텐츠 검증을 보장하기 위해 사용하세요. Vite 플러그인 구성과 MDX 컴파일부터 배포 최적화 및 스키마 검증에 이르기까지 모든 것을 다룹니다.

스킬 보기

polymarket

메타

이 스킬은 개발자들이 Polymarket 예측 시장 플랫폼을 활용한 애플리케이션을 구축할 수 있도록 지원하며, 거래 및 시장 데이터를 위한 API 통합 기능을 포함합니다. 또한 WebSocket을 통한 실시간 데이터 스트리밍을 제공하여 실시간 거래와 시장 활동을 모니터링할 수 있습니다. 이를 통해 거래 전략을 구현하거나 실시간 시장 업데이트를 처리하는 도구를 생성하는 데 활용할 수 있습니다.

스킬 보기

creating-opencode-plugins

메타

이 스킬은 개발자들이 명령어, 파일, LSP 작업 등 25개 이상의 이벤트 유형에 연결되는 OpenCode 플러그인을 만들 수 있도록 돕습니다. JavaScript/TypeScript 모듈을 위한 플러그인 구조, 이벤트 API 명세, 구현 패턴을 제공합니다. OpenCode AI 어시스턴트의 라이프사이클을 사용자 정의 이벤트 기반 로직으로 가로채거나, 모니터링하거나, 확장해야 할 때 사용하세요.

스킬 보기

sglang

메타

SGLang은 RadixAttention 프리픽스 캐싱을 활용하여 JSON, 정규식, 에이전트 워크플로우를 위한 고속 구조화 생성에 특화된 고성능 LLM 서빙 프레임워크입니다. 특히 반복되는 프리픽스가 있는 작업에서 상당히 빠른 추론 속도를 제공하여 복잡한 구조화 출력 및 다중 턴 대화에 이상적입니다. 제약 디코딩이 필요하거나 광범위한 프리픽스 공유가 있는 애플리케이션을 구축할 때는 vLLM과 같은 대안보다 SGLang을 선택하십시오.

스킬 보기