Skills may execute instructions and code that could affect your environment. Marketplace scans reduce risk but do not guarantee safety. Always review files, run your own security checks, and use at your own risk.
crossing-the-chasm
Security Scan Summary
Status: Safe
Source: Syntic Skills registry
Automated security scan completed with no high-risk patterns detected. Manual review is still required.
About This Skill
Use when planning tech go-to-market from early adopters to mainstream -- beachhead selection, whole product, positioning against incumbents, or growth stalling after early adopters.
Downloadable SKILL.md
Download SKILL.md and place it in your Syntic skills folder. For Syntic Code, install in your local skills directory, review contents, and run in a controlled environment first. Acknowledge the risk notice above to enable the download.
---
name: crossing-the-chasm
description: Use when planning tech go-to-market from early adopters to mainstream -- beachhead selection, whole product, positioning against incumbents, or growth stalling after early adopters.
category: Product & Growth
version: 1.0.0
tools: []
---
# 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.
For modern PLG/freemium B2B SaaS, remap every step below (chasm, beachhead, whole product, metrics) for self-serve trials and free tiers -- watch for 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 — visionaries want to be first, tolerate bugs, and buy the future vision with no references needed; pragmatists want proven solutions that "just work," buy present value, and need references from peers before they'll buy.
**Why this matters:** You can't market to both simultaneously -- visionary testimonials scare off pragmatists.
**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; whole-product potential via partners.
| 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.
### 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, complementary products/services (integrations, partner solutions), installation and setup, training/support/documentation, 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.
### Step 3: Define the Battle
**Position against the competition.**
**Positioning formula:** For [target customer], who [need/opportunity], our product is a [category] that [key benefit]. Unlike [primary competitive alternative], our product [primary differentiation].
**Example (early Workday):** For mid-market companies who need modern HR and finance systems, Workday is a cloud-based ERP with consumer-grade UX. Unlike Oracle and SAP, it needs no IT infrastructure and deploys in months, not years.
**Competitive positioning:** The market alternative is often NOT a direct competitor -- it's manual processes or legacy systems. Differentiate on a dimension you dominate and make the incumbent's strength irrelevant: Salesforce's "No software" turned feature-rich Siebel's complexity into a weakness.
### 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 and low risk; position as evolution, not revolution; prove with ROI calculators, free trials, pilots; sell through channels pragmatists trust (analysts, integrators). Shift the language itself: "Revolutionary new approach" → "Proven solution for [problem]"; "Be the first" → "Join 500 companies like yours"; "Change everything" → "Improve [specific metric] by X%."
## 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.
## 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 |
## Source
Based on *Crossing the Chasm* and *Inside the Tornado* by Geoffrey A. Moore, a consultant whose work at The Chasm Group has shaped enterprise tech go-to-market strategy for over 30 years.
Bundle Download
Includes SKILL.md and bundled support files where provided. Risk acknowledgement is required.
Install Targets
Syntic App
- 1. Create a dedicated folder for this skill in your local skills library.
- 2. Place SKILL.md into that folder.
- 3. Restart Syntic and invoke this skill on matching tasks.
Syntic Code (CLI)
- 1. Save SKILL.md in your local Syntic Code skills directory.
- 2. Keep related files in the same skill folder.
- 3. Run in a safe environment and validate outputs.
Source
https://github.com/wondelai/skills/blob/main/crossing-the-chasm/SKILL.md
Open Source LinkRelated Skills
blue-ocean-strategy
Use when the user wants to create uncontested market space via value innovation, mentions blue/red ocean...
Product & Growthcold-start-problem
Use when launching or scaling a marketplace, social, or collaboration product with network effects --...
Product & Growthcontinuous-discovery
Use when building a weekly cadence of customer interviews, an Opportunity Solution Tree, assumption testing...
Product & Growthhundred-million-offers
Use when creating or improving an offer -- value equation, bonus stacking, guarantees, ethical scarcity...