Crossing the Chasm: Marketing and Selling Disruptive Products to Mainstream Customers

Why this book exists

In the 1980s, Geoffrey Moore was a marketing consultant to Silicon Valley technology companies. He worked with dozens of companies that had built impressive products, generated initial market enthusiasm, secured significant venture funding, and then failed to scale into mainstream markets. The pattern was consistent enough that Moore began to theorize about why. The standard explanation — that the products were not good enough — did not fit. Many of the failed companies had products that were technically excellent and clearly superior to incumbents. They had also won the loyalty of early adopter customers who would not have invested time in inferior products.

Moore's diagnosis emerged from observing the buying patterns of the customers who came after the early adopters. The next wave of customers — what Moore called the early majority — did not buy for the same reasons or in the same way as early adopters. Early adopters bought disruptive technology because they sought competitive advantage from being first; they were willing to absorb the risk and incompleteness of new products in exchange for the upside. Early majority customers were the opposite: they sought reliable productivity solutions, were highly risk-averse, and refused to buy until peers in their reference network had already validated the solution. The marketing approaches that won with early adopters — emphasizing innovation, capability, and vision — actively repelled early majority customers, who wanted to hear about completeness, reliability, and references.

This insight produced Crossing the Chasm, published in 1991. The book was an immediate hit in Silicon Valley and has remained continuously in print since, with multiple updates reflecting evolving examples. It has become one of the most influential business books in the history of the technology industry; every modern tech founder and product leader has either read it directly or absorbed its frameworks through second-hand exposure.

The technology adoption lifecycle

The book's foundational framework is the technology adoption lifecycle, adapted from Everett Rogers's 1962 sociological model. The lifecycle divides any market for a new technology into five segments, each with distinctive buying motivations and behaviors:

Innovators (technology enthusiasts). Buy new technology because they love technology itself. They are willing to experiment with rough early versions and provide detailed feedback. They are not a commercial market in their own right but they validate that the technology works at all.

Early adopters (visionaries). Buy new technology because they believe it will give them a strategic competitive advantage. They are willing to accept incompleteness and risk in exchange for being first. They will champion the product internally, work with the vendor to fill gaps, and provide case studies. They are the first commercial customers.

Early majority (pragmatists). Buy proven technology that solves a defined business problem reliably. They refuse to be first. They want references from peers, complete solutions, and risk mitigation. They represent the largest market segment and the gateway to scale.

Late majority (conservatives). Buy technology only when it has become a clear standard and the risk of not having it is greater than the risk of buying it. They want simple, supported, low-cost solutions.

Laggards (skeptics). Resist new technology, sometimes indefinitely. Buy only when forced by external pressure (regulation, obsolescence of alternatives, expiration of older systems).

The five segments move sequentially through the market. Innovators come first; laggards come last. The transitions between segments are not smooth; there are gaps and discontinuities that Moore calls the chasm (between early adopters and early majority) and bowling alleys (between adjacent segments of the early majority).

The lifecycle framework matters because it explains a phenomenon that previously had no good explanation: why so many promising technology products that won early traction failed to scale. The answer is that early traction comes from a different segment than scale, and the strategies that win the first do not win the second.

The chasm: why it kills companies

The chasm between early adopters and early majority is the deepest discontinuity in the lifecycle, and it is the chasm that gives the book its title. Moore's central argument is that the chasm kills more technology companies than any other strategic mistake.

The chasm is wide because the two segments have fundamentally incompatible buying motivations. Early adopters want change; the early majority wants stability. Early adopters tolerate incompleteness; the early majority demands completeness. Early adopters seek competitive advantage; the early majority seeks risk reduction. Early adopters value vision and capability; the early majority values references and reliability.

The marketing and sales strategies that succeed with early adopters actively fail with the early majority. A pitch that emphasizes "be the first to revolutionize your business with this groundbreaking technology" resonates with early adopters and repels pragmatists. A demo that showcases raw capability impresses early adopters and concerns pragmatists who worry about implementation complexity. A reference list of innovative-but-small companies excites early adopters and signals risk to pragmatists who want to see peers their own size already using the product.

Companies in the chasm typically experience the following pattern: early adopter sales grow rapidly, the company scales its sales and marketing organization to maintain growth, the early adopter pool exhausts (it is small, perhaps 10-15% of the total market), the company's growth stalls, the company cannot understand why the strategies that worked are no longer working, the company runs out of funding before figuring it out, and the company fails or is acquired at a discount.

The book is direct: most failed tech startups failed in the chasm. The failure is not random; it is structural. Companies that do not develop a deliberate chasm-crossing strategy almost always fall in.

The beachhead strategy

Moore's prescription for crossing the chasm is the beachhead strategy. Rather than trying to win across many market segments simultaneously (which dilutes effort and fails to produce the credibility pragmatists require), the company should pick one specific narrow segment as the beachhead, dominate it completely, then expand to adjacent segments using the credibility built in the beachhead.

The beachhead segment should meet specific criteria:

• Compelling reason to buy. The segment must have a problem the product uniquely solves, severely enough that buying is the obvious choice.
• Whole product feasibility. The team must be able to deliver a complete solution (not just core product but all surrounding pieces) for this specific segment within a reasonable timeline.
• Manageable size. The segment must be small enough that the company can credibly dominate it, but large enough that domination produces meaningful revenue and references.
• Access to influencers. The segment must have identifiable opinion leaders and a connected reference network so that early wins propagate to other buyers in the segment.

Moore's metaphor is the D-Day landing. The Allies did not invade Europe across all coastlines simultaneously. They picked Normandy, concentrated overwhelming force on the beachhead, secured it, then expanded outward. Tech companies should follow the same logic.

The beachhead strategy is hard for founders to accept emotionally because it requires deliberate narrowing of focus at the moment the company is trying to expand. Founders want to chase every promising prospect; the beachhead strategy demands that they refuse most of them in favor of dominating one segment. The discipline is hard but necessary.

The whole product concept

A central concept that the book popularizes: the whole product. The whole product is not just the core technology the company builds — it is the complete bundle that constitutes a usable solution for the pragmatist buyer. Components of the whole product include:

• Core product. The technology the company builds.
• Integrations. Connectors to systems the pragmatist already uses (data sources, infrastructure, downstream tools).
• Documentation. Manuals, tutorials, knowledge base articles that enable the pragmatist to use the product without ongoing vendor support.
• Training and certification. Programs that let the pragmatist's team become proficient with the product.
• Professional services. Implementation, customization, ongoing optimization services.
• Support. Responsive customer support with appropriate SLAs.
• References. Customers in the pragmatist's segment who have used the product successfully and will speak to it.
• Ecosystem. Partner companies that provide complementary services, third-party tools that extend the product, and a community of users.

Early adopters will tolerate gaps in the whole product because they will fill the gaps themselves. Pragmatists will not. A product that has only the core technology but lacks documentation, integrations, references, and ecosystem support is incomplete for the pragmatist buyer regardless of how technically excellent the core technology is.

The whole product concept is one of the most-cited frameworks from the book. It shapes how modern tech companies think about what they need to build (not just the technology) and how they decide when they are ready to enter a new market segment.

Marketing to pragmatists

The book devotes significant attention to how marketing must shift when targeting the early majority. The key shifts:

References over thought leadership. Pragmatists buy what other pragmatists are already using. The most important marketing asset is a list of named reference customers in the buyer's segment. Thought leadership content matters less than concrete case studies.

Risk reduction over capability demonstration. Pragmatists want to know what could go wrong and how the vendor will help them avoid it. Capability demos that impressed early adopters now need to be paired with detailed implementation methodology, support commitments, and customer-success processes.

Whole-product positioning over technology positioning. Pragmatist buyers want a complete solution, not a piece of technology they must integrate. Marketing should emphasize the full solution and the ecosystem around it, not the underlying tech.

Vertical-specific messaging over horizontal pitch. Pragmatists want to see themselves in the marketing — companies of their size, in their industry, with their problems. Vertical-specific landing pages, case studies, and sales motions outperform horizontal positioning.

Standard-pricing over custom-pricing. Pragmatists want to know what the product costs without protracted negotiation. Published pricing, simple packaging, and predictable contract terms reduce buyer friction.

These shifts are uncomfortable for founders who built their early traction on a different style of marketing. The new style feels less exciting and more conservative; some founders resist it on aesthetic grounds. But the new style is what pragmatist buyers respond to, and resisting it leaves the company stuck in the chasm.

Bowling pin segments

After crossing the chasm into the beachhead, the company expands by selecting adjacent segments — the next bowling pins. The metaphor is bowling: knocking down the first pin (the beachhead) creates kinetic energy that knocks down adjacent pins (related segments) more easily than approaching them cold.

Adjacent segments are typically chosen by sharing one of two dimensions with the beachhead:

• Same vertical, different use case. If the beachhead was "marketing teams at mid-market manufacturing companies using the product for lead scoring," an adjacent segment might be the same companies using the product for customer retention analysis.
• Same use case, different vertical. If the beachhead was "marketing teams at mid-market manufacturing companies using the product for lead scoring," an adjacent segment might be marketing teams at mid-market financial services companies using the product for lead scoring.

Each successive segment knocked down adds more reference customers, more whole-product capability, and more credibility. The company eventually reaches the tornado phase — the part of the early majority where the entire segment is buying simultaneously and competitive dynamics determine winner-take-most outcomes.

The bowling pin model gives the company a roadmap for expansion that maintains the discipline of focus while allowing for systematic growth. It is the alternative to the failed strategy of "selling to anyone who will buy."

The tornado

A specific phase in the lifecycle that Moore identifies: the tornado. The tornado is the period when the early majority adopts a category broadly and rapidly, often within 12-18 months. During the tornado, the market grows at extraordinary rates, customers buy whatever they can get, and a small number of vendors capture most of the market.

The tornado is the opportunity to win category leadership. Vendors that have crossed the chasm and built whole products are positioned to capture the tornado; vendors that have not are usually crushed by competitors that have. The post-tornado market is dominated by 1-3 vendors who win 70%+ of the long-term market share; the rest fight for scraps.

The book provides specific advice for operating during the tornado: ship product, ship fast, prioritize sales capacity over engineering elegance, lock in distribution and reference customers, and accept that the company will be operationally chaotic for the duration. The tornado is exhausting but transformative; companies that survive it emerge as category leaders.

Worked examples from the book and updates

The book is rich with examples, though many of the original 1991 examples are now historical curiosities (Documentum, Verilog, early enterprise software). The updated editions add modern examples (Salesforce, Workday, ServiceNow, and others). The patterns are remarkably consistent across decades — the same chasm dynamics that killed companies in 1985 killed companies in 2005 and continue to kill companies in 2026.

Modern companies whose growth stories illustrate the chasm-crossing pattern include:

Salesforce. Crossed the chasm by focusing on sales teams at mid-market companies with a specific use case (sales force automation), built the whole product around that beachhead (integrations, certification programs, partner ecosystem, AppExchange), and expanded from the beachhead through adjacent segments over a decade.

Slack. Crossed the chasm by focusing on engineering and product teams at small-to-mid tech companies (the beachhead), built the whole product for that segment (integrations, bot ecosystem, search), and expanded from there to broader knowledge worker teams.

Stripe. Crossed the chasm by focusing on developer-led commerce at startups (the beachhead — companies where developers, not procurement teams, chose payment processors), built the whole product for developers (clean API, documentation, libraries, testing tools), and expanded from there to broader merchant categories.

Snowflake. Crossed the chasm by focusing on data analytics teams at mid-market companies (the beachhead), built the whole product for cloud data warehousing (performance, ease of use, ecosystem), and expanded from there to broader enterprise data infrastructure.

Each of these companies executed the chasm-crossing playbook explicitly. The patterns repeat: pick a beachhead, build the whole product, market to pragmatists, expand to adjacent segments, ride the tornado when it arrives.

What the book does badly

The book has limitations:

Original examples are dated. Even the updated editions retain many 1990s examples that feel historical. Readers should focus on the frameworks rather than the specific company stories.

Consumer product applicability is limited. The book is heavily B2B-oriented. Consumer product growth dynamics (viral mechanics, network effects, content-driven discovery) operate differently from the B2B sales-led dynamics the book describes. Consumer founders should treat the book's frameworks as partially applicable and supplement with consumer-specific resources.

It under-covers freemium and product-led growth. The book's go-to-market emphasis is sales-led, with limited treatment of self-serve and freemium models that have become dominant in modern SaaS. Modern PLG companies cross the chasm differently than the sales-led companies the book describes.

It is long-winded in places. Moore's writing style is academic and sometimes repetitive. Modern readers benefit from skimming chapters they find dense and focusing on the core framework chapters.

These critiques do not undermine the core value of the book. The chasm framework remains the most influential lens on technology market dynamics ever published.

How to use the book in practice

The most effective adoption pattern for a founder or PM:

1. Read the book once cover to cover. Absorb the technology adoption lifecycle, the chasm dynamics, the beachhead strategy, and the whole product concept.
2. Diagnose your current position. Are you in the early adopter phase, approaching the chasm, in the chasm, crossing into the early majority, or already in the mainstream? The diagnosis informs your next move.
3. Identify your beachhead. If you are approaching or in the chasm, define your beachhead segment using the criteria in the book. Be ruthless about narrowing focus.
4. Audit your whole product. Map the components of the whole product for your beachhead segment. Identify gaps and prioritize closing them.
5. Shift marketing and sales. Move from early-adopter messaging to pragmatist-appropriate messaging. Invest in references, risk reduction, and whole-product positioning.
6. Plan the bowling pin expansion. Once the beachhead is dominated, identify the next adjacent segments and the sequence of expansion.

Founders who execute this playbook consistently outperform founders who do not. The book is one of the highest-ROI strategic reads in the technology canon.

The book's place in the modern PM and founder canon

Crossing the Chasm is one of the foundational texts of modern technology business strategy. It pairs with:

• Inside the Tornado by Geoffrey Moore — the follow-up that deepens the tornado phase analysis.
• The Innovator's Dilemma by Clayton Christensen — the framework for why incumbents lose to disruptive entrants.
• Play Bigger by Ramadan, Peterson, Lochhead, and Maney — the modern follow-on on category creation.
• From Impossible to Inevitable by Aaron Ross and Jason Lemkin — the modern playbook for scaling B2B sales after the chasm.

Together these texts form a coherent curriculum for technology business strategy. Crossing the Chasm is the foundational text; the others build on its frameworks.

On the chasm in AI products specifically

For PMs and founders building AI products in 2026, the chasm framework applies with high relevance. AI products are currently in the early-adopter phase across most categories — companies are experimenting, exploring, and building proofs of concept. The transition to the early majority (companies adopting AI as a reliable, complete solution for specific business problems) is just beginning.

The chasm-crossing playbook applies. AI startups should pick narrow beachheads (specific use cases for specific buyer segments), build whole products around them (not just the AI model, but integrations, evaluation tooling, monitoring, compliance, and reference customers), market to pragmatist buyers (with risk-reduction language, peer references, and complete solution positioning), and expand through bowling-pin adjacencies.

AI companies that follow this playbook are positioned to cross the chasm and capture meaningful market share when the AI tornado arrives in their category. Companies that pursue early adopters indefinitely without preparing for the pragmatist transition will fall in the chasm, regardless of how technically impressive their AI capabilities are.

On B2B vs B2C applicability

The book's frameworks were developed for B2B technology products and apply most directly there. The chasm dynamics — pragmatist risk aversion, reference dependency, whole product requirements — are most pronounced in B2B markets where buying decisions are large, deliberate, and committee-driven.

For B2C consumer products, the chasm framework still applies but in modified form. Consumer products cross a different kind of chasm — from enthusiast early adopters to mainstream consumers who require simpler interfaces, lower friction, and more accessible pricing. The marketing tactics differ (viral mechanics over reference selling, brand over case studies) but the strategic pattern (narrow focus, complete solution, mainstream-appropriate positioning) is similar.

For B2B SaaS specifically, the book is canonical. For consumer products, it is foundational but should be supplemented with consumer growth resources.

On the relationship to disruptive innovation

The book is sometimes paired with Clayton Christensen's The Innovator's Dilemma, and the two are complementary but distinct. Christensen explains why incumbents fail to respond to disruptive entrants; Moore explains why disruptive entrants fail to scale beyond early adopters. Together they cover both sides of the same dynamic.

Founders building disruptive products should read both books. Christensen explains why the incumbent will be slow to respond (giving the founder time to establish the beachhead); Moore explains how the founder should use that time to cross the chasm and establish category leadership before the incumbent recovers.

On the discipline of refusing customers

A specific point worth expanding: the beachhead strategy requires refusing customers who don't fit the beachhead. This is one of the hardest disciplines for founders to maintain. Revenue is revenue; turning down willing buyers feels like leaving money on the table.

But customers outside the beachhead dilute focus. They consume engineering capacity for features specific to their segment that don't help the beachhead. They produce references that don't carry weight with beachhead buyers. They make the whole product more complex to maintain.

Moore is direct: refuse customers outside the beachhead, at least until the beachhead is dominated. The short-term revenue loss is more than recouped by the focused execution that produces beachhead leadership. Founders who cannot maintain this discipline rarely cross the chasm.

The discipline is hardest at the moment when early adopter revenue is plateauing and new revenue from any source feels welcome. This is exactly the moment when the discipline is most important. Stay focused.

Closing thought

The chasm between early adopters and the early majority is the most dangerous transition in the technology product lifecycle. Most disruptive products fail in the chasm, not because they are technically deficient but because their go-to-market strategies cannot bridge the gap between two fundamentally different buyer segments.

Crossing the Chasm is the canonical text on how to make the bridge. The beachhead strategy, the whole product concept, the pragmatist-appropriate marketing, and the bowling pin expansion together constitute the playbook that has been executed dozens of times by category-defining tech companies over three decades.

For PMs and founders working on technology products with mainstream-market ambitions, this book is foundational reading. Its frameworks have shaped the strategic thinking of every modern tech company and remain the right starting point for any team planning a market expansion. Read it once for the philosophy; reference specific chapters when executing chasm-crossing moves; supplement with current resources for modern examples and PLG-specific tactics.

The book is one of the small number of business books that genuinely deserve their canonical status. The chasm is real, the playbook works, and the alternative — pursuing growth without strategic discipline — kills companies. Take the framework seriously.

Annotated highlights worth marking

• The chapter introducing the technology adoption lifecycle and the chasm.
• The chapter on the beachhead strategy and segment selection criteria.
• The whole product chapter — the framework that shapes how to build for pragmatists.
• The chapter on marketing to pragmatists and the shifts from early-adopter marketing.
• The bowling pin and tornado chapters that cover the expansion path after the beachhead.

A worked example: a B2B SaaS startup crossing the chasm

Consider a B2B SaaS startup four years in, $5M ARR, 80 customers, growth slowing. The team applies the chasm framework.

Diagnosis: the team has won early adopters (innovative companies willing to experiment with new categories) but is struggling to win the next wave. Customer conversations reveal that prospects who are not early adopters consistently raise concerns about implementation risk, peer references, and complete solution requirements. The company is approaching the chasm.

Beachhead identification: the team analyzes their existing customers and identifies a cluster of 25 mid-market financial services companies who have used the product successfully for a specific use case (compliance reporting). This cluster meets the beachhead criteria: compelling reason to buy (regulatory pressure), whole product feasibility (the integrations and certifications needed are achievable), manageable size (the U.S. mid-market financial services segment is large enough to be meaningful), and access to influencers (the segment has identifiable opinion leaders and reference networks).

Whole product audit: the team maps what a mid-market financial services compliance reporting customer needs. They identify gaps: a specific SOC 2 certification that the segment requires, integrations with three core systems used by mid-market financial services, a dedicated customer success process for the regulatory implementation, vertical-specific case studies, and a partner ecosystem with the segment's standard consulting firms. They prioritize closing these gaps over the next two quarters.

Marketing shift: the team rebrands the website and sales messaging around the financial services compliance use case. Existing capabilities are repositioned around this specific use case. New marketing assets emphasize references, risk reduction, and the complete solution. Generic horizontal positioning is removed.

Sales motion shift: the sales team is restructured around the beachhead segment. Generic outbound is paused. The team focuses sales effort entirely on mid-market financial services prospects. References from existing financial services customers are used aggressively in every sales process.

Twelve months later: the team has won 60 new mid-market financial services customers and is recognized as the leader in that segment. Total customer count is 140, revenue is $15M ARR, and the growth rate has accelerated. The team is now planning the next bowling pin: mid-market healthcare companies with similar compliance reporting needs, where the financial services references will carry partial credibility.

This pattern — diagnose the chasm, pick a beachhead, build the whole product, shift marketing and sales, dominate the beachhead, expand through bowling pins — is the playbook the book describes and the playbook that produces category-leading tech companies.

Annotated highlights worth marking

• The opening chapter on the technology adoption lifecycle and the chasm.
• The beachhead strategy chapter — the operational heart of the chasm-crossing playbook.
• The whole product chapter — the framework that shapes what to build for pragmatists.
• The chapter on the differences between early-adopter and pragmatist marketing.
• The bowling pin and tornado chapters that cover the expansion path beyond the beachhead.

On the rise of platform plays as a chasm-crossing strategy

A pattern that has emerged since the book was published: some companies cross the chasm by becoming platforms rather than products. Stripe became the payments platform that developers at every kind of company use; AWS became the compute platform that every kind of company uses; Twilio became the communications platform across many use cases. By becoming platforms, these companies sidestepped the segment-specific beachhead requirement and instead built capabilities that thousands of segments could use independently.

The platform strategy is not always available — it requires a capability that is genuinely general-purpose enough to be platformized — but when it works it can produce category leadership faster than the traditional bowling pin sequence. Modern founders should consider whether their product has platform potential as part of their chasm-crossing analysis.

That said, even platform plays require a beachhead. AWS started with EC2 and S3 for web startups; Stripe started with payment processing for developers; Twilio started with SMS for consumer apps. The beachhead provided the initial revenue and credibility; the platform expansion came after.

On the relationship between chasm-crossing and product strategy

A subtle point: chasm-crossing has direct implications for product strategy. The beachhead segment determines what the product must do; the whole product requirements determine what supporting capabilities the product must include; the pragmatist marketing requirements determine how the product must present itself.

PMs whose teams are crossing the chasm cannot operate independently of the broader chasm-crossing strategy. The roadmap is constrained by the beachhead choice; new features should be evaluated for whether they support whole-product completeness in the beachhead segment; the timing of expansion features should align with the bowling pin sequence.

This is one reason senior product leaders must read this book. Strategy at the executive level shapes the roadmap at the PM level. PMs who do not understand the chasm-crossing logic risk making roadmap decisions that conflict with the broader go-to-market strategy.

On the role of customer success in chasm-crossing

A function that did not exist as a named discipline when the book was first published but which has become central to modern chasm-crossing: customer success. The customer success function — proactively ensuring that customers reach value with the product, expand their usage over time, and renew confidently — is a core component of the whole product for pragmatist buyers.

Pragmatists buy with the expectation that the vendor will help them succeed, not just sell them software. The customer success function delivers on that expectation through onboarding programs, regular business reviews, proactive outreach when usage signals concerns, and expansion conversations as the customer's needs grow.

For SaaS companies crossing the chasm, building the customer success organization is one of the most important investments. CS sits at the intersection of product, sales, and support; it requires its own leader, its own headcount, and its own metrics (typically net revenue retention and customer health scores). Companies that under-invest in CS struggle to retain pragmatist customers; companies that invest properly build the renewal and expansion engine that compounds revenue over time.

On building the partner ecosystem

Another chasm-crossing component the book covers and which deserves expansion: the partner ecosystem. Pragmatist buyers want vendors that come with an ecosystem of complementary partners — consulting firms that implement the product, training organizations that certify users, technology integrations that connect the product to other systems they use, and resellers or channel partners in their geography.

Building the partner ecosystem is multi-year work. Major SaaS companies often have dedicated partnership organizations of dozens to hundreds of people. Early-stage startups should not try to build a full ecosystem at once, but should identify the few partners most important for their beachhead and invest in those relationships explicitly.

For PMs and founders crossing the chasm, the partner ecosystem is often the last component of the whole product to mature. Plan for it; invest in it deliberately; recognize that the ecosystem is a competitive moat that takes years to build but is hard for competitors to replicate quickly.

On pricing in the chasm

A specific tactical area the book addresses: pricing strategy must shift as the company crosses the chasm. Early-adopter pricing is often custom, negotiated, and reflects the value of being on the leading edge. Pragmatist pricing must be standard, predictable, and benchmarked against alternatives.

The transition is hard because early-adopter customers may have negotiated favorable terms that the company needs to maintain (to keep them as references) while introducing standard pricing for new pragmatist buyers. Many companies handle this by grandfathering early adopter contracts and shifting to standard pricing for all new customers.

The principles for pragmatist pricing: publish your pricing publicly when possible; offer simple tiers with predictable upgrade paths; benchmark against the closest alternative the buyer would compare to; include the components of the whole product (support, training, professional services) in pricing transparently rather than as surprise add-ons; and avoid heavy discounting that signals price flexibility (which pragmatists distrust).

For PMs and founders pricing technology products, the shift from custom early-adopter pricing to standard pragmatist pricing is one of the most under-appreciated aspects of chasm-crossing. The book covers it but it deserves more attention than most teams give it.

On the discipline of saying no to expansion

A particular wisdom that recurs throughout the book: expansion before chasm-crossing is fatal. Many companies try to expand into multiple segments simultaneously because each segment has willing buyers and turning them away feels wrong. The expansion dilutes focus, prevents whole-product completion in any single segment, and leaves the company stuck in the early-adopter market across many segments rather than dominant in one.

The discipline of saying no to expansion until the beachhead is dominated is one of the most counterintuitive lessons in the book. Founders are conditioned to pursue every opportunity; the book asks them to pursue one opportunity intensely and refuse the others.

The pattern that works: dominate the beachhead, build the credibility and whole product that domination provides, then deliberately expand into the next bowling pin. Each expansion is sequenced and disciplined, not opportunistic. Companies that maintain this discipline across multiple bowling pin expansions become category leaders; companies that diffuse their efforts across many simultaneous expansions stay sub-scale.

On the role of analysts and category creators

A topic the book covers and which deserves expansion: industry analysts (Gartner, Forrester, IDC) play a critical role in chasm-crossing for B2B technology. Pragmatist buyers rely heavily on analyst reports to validate vendor choices. A favorable position in the relevant Gartner Magic Quadrant or Forrester Wave can dramatically accelerate sales; an unfavorable position can stall sales.

For tech companies approaching the chasm in categories where analysts matter (most enterprise B2B categories), investing in analyst relations is one of the highest-leverage chasm-crossing moves. The investment includes regular analyst briefings, participation in analyst surveys, customer reference coordination, and content that supports analyst inquiries. Companies that under-invest in analyst relations struggle to win pragmatist buyers regardless of product quality.

For categories where analysts matter less (consumer products, developer tools, some PLG B2B), the analyst investment is less critical. The community-led equivalent — being well-regarded on Reddit, Hacker News, Twitter, or in relevant professional communities — plays a similar validation role.

On positioning vocabulary

A specific tactical insight: the language a company uses to describe itself shapes how pragmatist buyers categorize and evaluate it. Companies should be explicit about the category they are in (or creating) and use consistent language across all customer-facing surfaces.

Moore is direct that fuzzy positioning is one of the most common chasm-crossing mistakes. Founders often describe their company in ways that excite early adopters (using novel terms, emphasizing technological capability) but confuse pragmatists (who want to know "what is this thing and how does it compare to alternatives I know"). The shift from early-adopter to pragmatist positioning requires sharper categorization and more conventional vocabulary.

The recommended exercise: write a one-sentence positioning statement using the formula "for [target customer], [product name] is the [category] that [unique value]." Iterate the sentence until it is unambiguous to a pragmatist who has never heard of the product. The discipline of the one-sentence statement forces clarity that fuzzy positioning lacks.

Final word

For technology founders and PMs with mainstream-market ambitions, Crossing the Chasm is foundational. The framework has shaped how serious tech businesses are built. Read it, apply it, and let it guide your go-to-market strategy. Few business books deserve their canonical status more.