Skip to main content
ClaudeWave
Skill1.3k estrellas del repoactualizado 2d ago

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.

Instalar en Claude Code
Copiar
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
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

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.

## Scoring

**Goal: 10/10.** Rate any tech go-to-market strategy 0-10 against chasm-crossing principles: proper beachhead selection, whole product strategy, and positioning for pragmatist buyers. Low scores mean early-market tactics applied to the mainstream. Report the current score and the 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%) -- 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) for detailed buyer psychographics.

## Why the Chasm Exists

- **Reference gap:** The early majority won't buy without references from other early majority companies -- but none exist until someone crosses first. Classic catch-22.
- **Whole product gap:** Early adopters tolerate incomplete products; the early majority demands complete, integrated solutions. The MVP that wowed visionaries is unshippable to pragmatists.
- **Positioning gap:** "Revolutionary" excites early adopters and terrifies the early majority, who read "disruptive" as 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 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) for segment evaluation frameworks.

### 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.
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", or "opinionated software". Also trigger when cutting scope to ship faster, running small teams, avoiding long-term roadmaps, or eliminating meetings. 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", "eliminate-reduce-raise-create", or "uncontested market". Also trigger when comparing pricing strategies, exploring new market categories, finding underserved customer segments, or asking how to stop competing on price. Covers the Four Actions Framework, buyer utility map, and value-cost trade-offs. 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 architecture", "use case boundary", "onion architecture", "screaming architecture", or "framework independence". Also trigger when decoupling business logic from databases or frameworks, defining module boundaries, or debating where to put business rules. Covers component principles, boundaries, and SOLID. For code 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 "code review", "naming conventions", "function too long", "code smells", "readable code", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing pull requests for readability, refactoring messy functions, debating comment styles, or improving error handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture, 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", "viral loop", "referral program", or "organic growth". Also trigger when designing shareable features, crafting social media 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", or "outcome-based roadmap". Also trigger when setting up regular customer feedback loops, prioritizing which experiments to run, or connecting 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", "split testing", or "conversion funnel". 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", "replication lag", "partitioning strategy", "consistency vs availability", "stream processing", "ACID transactions", "eventual consistency", or "LSM tree vs B-tree". Also trigger when choosing between SQL and NoSQL, 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.