Skip to main content
ClaudeWave
Skill2.1k repo starsupdated today

crossing-the-chasm

# crossing-the-chasm This Claude Code skill applies Geoffrey Moore's chasm framework to help technology companies transition from early adopter markets to mainstream adoption. Use it when assessing go-to-market strategy for disruptive products, selecting beachhead segments, defining whole product requirements, or positioning offerings to pragmatist buyers rather than visionaries. The skill rates strategies against chasm-crossing principles and identifies gaps between early-market and mainstream tactics.

Install in Claude Code
Copy
git clone --depth 1 https://github.com/wondelai/skills /tmp/crossing-the-chasm && cp -r /tmp/crossing-the-chasm/crossing-the-chasm ~/.claude/skills/crossing-the-chasm
Then start a new Claude Code session; the skill loads automatically.

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](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 |
|-------|------------------|
| **Ge
37signals-waySkill

Build lean, opinionated products using the 37signals philosophy from "Getting Real", "Rework", and "Shape Up". Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", "opinionated software", "we have too many meetings", "how do we ship faster", or "stop overbuilding". Also trigger when cutting scope to ship sooner, running a small team, or avoiding long-term roadmaps. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.

blue-ocean-strategySkill

Create uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "the market is too crowded", "how do we stand out", or "escape the price war". Also trigger when exploring a new market category, or finding underserved or non-customers. Covers the Four Actions Framework, Six Paths, buyer utility map, and value-cost trade-offs. For real strategy formulation and bad-strategy detection, see good-strategy-bad-strategy. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.

clean-architectureSkill

Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters (hexagonal)", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.

clean-codeSkill

Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "clean up this code", "this function is too long", "code smells", "naming conventions", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing a pull request for readability, untangling a messy function, debating comment styles, or improving error-handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture and dependency rules, see clean-architecture.

contagiousSkill

Engineer word-of-mouth and virality using the STEPPS framework (Social Currency, Triggers, Emotion, Public, Practical Value, Stories). Use when the user mentions "go viral", "word of mouth", "shareable content", "social currency", "why people share", "referral program", "nobody is sharing it", or "make this spread". Also trigger when designing shareable features, crafting social campaigns, or building products that spread through peer recommendation. Covers environmental triggers and high-arousal emotional content. For sticky messaging, see made-to-stick. For persuasion tactics, see influence-psychology.

continuous-discoverySkill

Build a weekly cadence of customer touchpoints using Opportunity Solution Trees, assumption mapping, and interview snapshots. Use when the user mentions "continuous discovery", "opportunity solution tree", "weekly interviews", "assumption testing", "discovery habits", "product trio", "outcome-based roadmap", "how do I talk to customers regularly", "we keep building things nobody uses", or "connect research to the roadmap". Also trigger when setting up regular customer feedback loops, prioritizing which experiments to run, or tying discovery insights to delivery work. Covers experience mapping, co-creation, and prioritizing opportunities. For interview technique, see mom-test. For team structure, see inspired-product.

cro-methodologySkill

Audit websites and landing pages for conversion issues and design evidence-based A/B tests. Use when the user mentions "landing page isnt converting", "conversion rate", "A/B test", "why visitors leave", "objection handling", "bounce rate", "conversion funnel", "increase signups", or "people add to cart but dont buy". Also trigger when diagnosing why signups are low, designing experiment hypotheses, or auditing checkout flows for friction points. Covers funnel mapping, persuasion assets, and objection/counter-objection frameworks. For overall marketing strategy, see one-page-marketing. For usability issues, see ux-heuristics.

ddia-systemsSkill

Design data systems by understanding storage engines, replication, partitioning, transactions, and consistency models. Use when the user mentions "database choice", "which database should I use", "SQL or NoSQL", "replication lag", "partitioning strategy", "consistency vs availability", "stream processing", "ACID transactions", "eventual consistency", "my queries are slow at scale", or "data is inconsistent across replicas". Also trigger when choosing a datastore, designing data pipelines, or debugging distributed-system consistency issues. Covers data models, batch/stream processing, and distributed consensus. For system design, see system-design. For resilience, see release-it.