Crossing The Chasm logo

Crossing The Chasm

OrganizationPopular
wondelai
crossing-the-chasm

Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs mainstream", "tech go-to-market", "bowling pin strategy", "technology adoption lifecycle", "pragmatist buyers", "growth stalled after early adopters", or "our go-to-market plan". Also trigger when planning go-to-market for a technical product. Covers the D-Day analogy, bowling-pin strategy, the tornado, and positioning against incumbents. For product positioning, see obviously-awesome. For new market creation, see blue-ocean-strategy.

Overview

Publisherwondelai
Repositoryskills
Skill namecrossing-the-chasm
Stars
2.2K
Forks
228
Bundled files
8
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 8 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by wondelai on GitHub. Read the source before you install it.

Installation

Install the Crossing The Chasm AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/wondelai/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/crossing-the-chasm .claude/skills/crossing-the-chasm
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Crossing The Chasm in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Crossing The Chasm on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Crossing The Chasm is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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% 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 opposite things:

Early Adopters (Visionaries)Early Majority (Pragmatists)
Want to be firstWant proven solutions
Tolerate bugs and workaroundsNeed it to "just work"
Buy the future visionBuy present value
Need no referencesNeed references from peers
Want custom solutions, high risk toleranceWant 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.

CriteriaGood BeachheadBad Beachhead
SizeBig enough to matter, small enough to dominateToo small to build on, or too big to 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): 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

LayerWhat It Includes
GenericEmail sending, list management
ExpectedTemplates, analytics, API
AugmentedCRM integration, training, support, services, best-practice playbooks
PotentialAI 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 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 (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 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 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

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 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.

QuestionIf NoAction
Have we chosen a single, narrowly defined beachhead with an urgent, expensive problem?You're in the chasmDefine one narrow target market; resist multiple beachheads
Can we plausibly dominate this segment?Wrong beachheadChoose a narrower or different segment
Do we have 10+ reference customers from that exact segment?Pragmatists won't buyBuild lighthouse customers and case studies
Is the whole product complete -- partnerships in place to fill the gaps?Product won't meet pragmatist needsIdentify generic-to-augmented gaps, partner to fill them
Does positioning emphasize proven value over revolution?Wrong message for the early majorityReframe: evolution, not revolution
Is the distribution channel aligned with pragmatist buying behavior?You reach visionaries, not pragmatistsSell through analysts, integrators, references, channel
Are adoption metrics accelerating (entering the tornado)?Still stuck before the chasmRe-check the rows above -- something is still early-market

Further Reading

For the complete methodology:

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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Crossing The Chasm AI skill do?

Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs mainstream", "tech go-to-market", "bowling pin strategy", "technology adoption lifecycle", "pragmatist buyers", "growth stalled after early adopters", or "our go-to-market plan". Also trigger when planning go-to-market for a technical product. Covers the D-Day analogy, bowling-pin strategy, the tornado, and positioning against incumbents. For product positioning, see obviously-awesome. For new market cr...

Why use Crossing The Chasm on TypingMind?

Because you install it once and use it with any model. Crossing The Chasm is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Crossing The Chasm in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/wondelai/skills/tree/main/crossing-the-chasm. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Crossing The Chasm?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Crossing The Chasm?

As many as you like. As long as a model supports skills, you can use Crossing The Chasm with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Crossing The Chasm AI skill free?

Yes. It is published on GitHub by wondelai under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇