Book: Crossing the Chasm — Marketing and Selling Disruptive Products to Mainstream Customers
Author: Geoffrey Moore
My take: The Chasm is a pattern I’ve seen play out repeatedly in regulatory technology adoption. Customs enforcement agencies that invested in “transformative” scanning and data tools often stalled — not because the technology failed, but because no one built the Whole Product around it. This book gives a name to a gap I’ve always felt but never had the vocabulary for.
The Technology Adoption Life Cycle is not a continuous curve. It is a broken one. Between the Early Adopters who want a change agent and the Early Majority who want a productivity improvement, there is a treacherous, often fatal gap — the Chasm.
Most innovations fail not because they are technically wrong, but because companies attempt to bridge this gap with a single undifferentiated strategy — when the two groups have fundamentally incompatible buying motives. Visionaries want novelty and disruption. Pragmatists want proven stability and a reference.
The prescription is counterintuitive: when you need the entire market, stop trying to sell to the entire market. Pick one niche. Win it completely. Build from there.
Visionaries vs. Pragmatists
The fatal mismatch at the centre of the Chasm. Visionaries buy for competitive advantage; Pragmatists buy to reduce risk. The features that thrill one group actively terrify the other.
Buying motiveCore conflict
The AI-driven audit tool loved by the tech-forward boutique firm is rejected by the Big Four — not because it doesn’t work, but because it lacks the 10-year track record that signals “safe to adopt.”
The Beachhead Strategy
Concentrate all resources on winning one narrow, specific market segment. Dominate it completely. Use that victory as the launchpad — and the reference — for adjacent segments.
Niche firstFocus
Salesforce did not try to replace all enterprise software at once. They solved one very specific problem for sales teams — and used that base to expand. Beachhead, then bowling alley.
The Whole Product
Customers do not buy a product. They buy a complete solution to a specific problem. The Whole Product includes the core technology plus integration, training, support, maintenance, and documentation — everything required for the customer to succeed.
Complete solutionNot just the tool
In customs enforcement, a “smart scanner” is not the product. The product is the scanner plus data integration with existing manifest systems, officer training, and a maintenance SLA. Missing any component means the Whole Product is missing.
The Pragmatist's Catch-22
Pragmatists only buy from vendors with established references. But those references can only come from Pragmatists who have already bought. This circular dependency is where most brilliant innovations go to die — not from technical failure, but from adoption paralysis.
References requiredThe death loop
Breaking the loop requires finding the one segment where pain is acute enough that a Pragmatist will act without a reference — and then weaponising that first win relentlessly.
The Bowling Alley
After the beachhead, growth comes not from a broad push but from rolling wins into adjacent niches. Each segment victory creates the reference and the capability base to enter the next lane.
Adjacent segmentsSequenced growth
Winning “automated tax auditing for retail” creates the credibility and technical depth to enter “automated tax auditing for manufacturing.” Same product, transferable proof.
Position Against the Status Quo
Pragmatists don’t switch because the new product is better. They switch when the old way becomes more dangerous than the new way. The reframe is not “why you should adopt this” — it is “why staying where you are is now the riskier choice.”
Risk reframeChange catalyst
“The cost of staying on the legacy system” lands harder than “the benefits of the new one.” The compliance risk of inaction is more persuasive than the features of the solution.
You’ve built a breakthrough. Your first customers love it. Revenue is climbing. You think you’ve made it.
Then, suddenly, the phone stops ringing. The sales cycle doubles. The product that solved everything is being rejected by the people who need it most.
You haven’t failed. You haven’t hit a plateau. You’ve hit the Chasm — and most innovations never get out of it.
In finance and regulation, we see this constantly: massive technology investments that worked perfectly in the pilot and stalled completely at scale.
The structural problem to name
The adoption curve we draw is a smooth bell. The one that actually exists has a gap in the middle — and that gap is lethal.
Visionaries want disruption. Pragmatists want proof. These two groups don’t just have different preferences — they have incompatible buying logics.
The Catch-22: Pragmatists require references from other Pragmatists before they buy. But you can’t get those references until a Pragmatist buys. This is where brilliant ideas go to die.
Selling harder, pitching broader, adding features — none of these cross the Chasm. They are the wrong tools for a structural problem.
The counterintuitive reframe to drive home
To reach the whole market, stop trying to sell to the whole market.
Pick a single niche with a single hair-on-fire problem. Go deep, not wide. Solve it so completely that they have no choice but to become your reference.
The beachhead is not a consolation prize — it is the only viable path across.
Define your Whole Product before you pitch. If it requires integration you haven’t built and training you haven’t written, you don’t have a product — you have a demo.
You don’t cross the Chasm by being technically better. You cross it by becoming the safe, proven standard within a specific community that trusts each other.
How to land it for a finance and regulatory audience
In our world, we are often the Pragmatists. We are the gatekeepers that say no to a thousand visionary pitches.
Understanding the Chasm makes us better buyers — we stop chasing novelty and start asking: “Where is the Whole Product? Where are the references from people like us?”
For anyone trying to drive institutional change: stop pitching the technology. Start pitching the beachhead. Name the specific pain point. Name the specific group. Win there first.
Name your beachhead before you move. For any new initiative, identify one specific group with one specific problem so painful they will act without a full reference list. If you can’t name them precisely, you are standing at the edge of the Chasm.
Map the Whole Product, not just the tool. Before rolling out any new system, list everything a sceptical end user needs to succeed: training, integration, documentation, support escalation. If any element is missing, the rollout will fail — regardless of how good the core product is.
Target the pain, not the persona. Find the stakeholder whose current situation is so costly they are willing to absorb the risk of a new solution. Stop pitching general efficiency and start pitching resolution of a specific, quantifiable problem.
Reframe every proposal against the status quo. The question is not “why should you adopt this?” It is “what is the cost of not adopting this?” Calculate the compliance risk, the financial leakage, or the operational exposure of staying on the legacy path.
Treat references as more valuable than revenue. In the Chasm, one high-profile win in a key niche is worth more than ten dispersed sales. Accept a smaller, less profitable project if it generates the reference that unlocks the mainstream.
Protect the roadmap from Visionary feature requests. Early adopters will ask for endless customisations that the Early Majority does not want. Build for the pragmatist’s requirements, not the innovator’s whims. The features that thrill visionaries actively confuse pragmatists.