wondelai/skills

crossing-the-chasm

Navigate the technology adoption lifecycle from early adopters to mainstream market.

Quelltext ansehen
Originales Skill-Dokument

Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.

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.

aus demselben Repository

Weitere Skills

Alle Skills
wondelai
Community

hundred-million-offers

Create irresistible offers using the Value Equation, bonus stacking, risk-reversing guarantees, and ethical scarcity. Use when the user mentions "grand slam offer", "make my offer more compelling", "what bonuses should I add", "guarantee strategy", "offer naming", or "people say its too expensive". Also trigger when packaging a product for higher perceived value, justifying premium pricing instead of discounting, designing a money-back guarantee, or structuring tiers to maximize conversions. Covers the MAGIC naming formula and starving-crowd targeting. For product positioning, see obviously-awesome. For outbound sales, see predictable-revenue.

Installationen
2
GitHub Stars
2242
Aktualisiert
10. Sept.
wondelai
Community

negotiation

Prepare and execute negotiations using tactical empathy, calibrated questions, and the Ackerman method. Use when the user mentions "salary negotiation", "contract terms", "handling objections", "mirroring and labeling", "difficult conversation", "deal terms", "BATNA", "anchoring", "how do I ask for a raise", "get a better deal", or "they wont budge on price". Also trigger when preparing for a vendor negotiation, resolving a pricing dispute, or navigating a high-stakes conversation where both sides need to feel heard. Covers accusation audits, Black Swan discovery, and the "Thats Right" technique. For persuasion in product and marketing, see influence-psychology.

Installationen
2
GitHub Stars
2242
Aktualisiert
10. Sept.
wondelai
Community

clean-architecture

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.

Installationen
1
GitHub Stars
2239
Aktualisiert
10. Sept.
wondelai
Community

refactoring-ui

Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent design tokens, creating dark mode themes, improving data-visualization clarity, or polishing UI details before launch. Covers grayscale-first workflow, constrained design scales, shadows, and component styling. For typeface selection, see web-typography. For usability audits, see ux-heuristics.

Installationen
3
GitHub Stars
2226
Aktualisiert
10. Sept.