Crossing the Chasm

How do you choose and price a beachhead?#

1. Diagnose before you prescribe#

Look for the specific signature: early wins followed by stalled conversion, lengthening proof cycles, repeated objections about integration and continuity rather than capability, weak peer references, and delivery that only works when a founder is in the room. Then rule out the cheaper explanations — weak value, a broken sales motion, the wrong price, an unqualified pipeline. A chasm diagnosis that survives those alternatives is worth acting on.

2. Score candidate segments#

Use explicit weights so the choice is auditable. Score each criterion 1–5.

Segment C has the most urgent problem and the best expansion story and still loses, because a pragmatist beachhead is won on homogeneity and completeness, not on prize size. Market size belongs in the model as a constraint — large enough to matter, small enough to dominate — not as a scoring criterion. And the weights are a judgement you are publishing, not a discovery: change them and the ranking can change, so state them before scoring, not after.

3. Specify the whole product#

List everything the customer needs beyond the core technology — implementation, data migration, integrations, security review artefacts, compliance evidence, training, support hours, procurement terms, change management, and outcome measurement — then decide build, partner, or document for each. The partner column is usually larger than founders expect; see Build vs. Buy vs. Partner and Distribution Channels.

4. Price the bet#

Focus is a capital allocation, so put a number on it.

Worked example: what one beachhead costs#

ClaimBridge (hypothetical) sells denial-prevention workflow software to revenue-cycle teams at regional hospitals. Segment A above contains 1,200 addressable accounts. ACV is $85,000, contribution margin after variable delivery and support is 74%, fully loaded acquisition cost per customer is $62,000, and closing the whole-product gap — two clearinghouse integrations plus a security certification — is a one-time $340,000.

Step 1 — unit economics of one customer

annual contribution = $85,000 × 74%          = $62,900
CAC payback         = $62,000 ÷ ($62,900/12) = 11.8 months

Step 2 — how much pipeline reference density requires

The team judges that twelve referenceable customers make the segment's peer network self-sustaining. At a 22% win rate against the named alternative:

qualified opportunities needed = 12 ÷ 0.22 = 54.5 → 55

Step 3 — the total commitment

Step 4 — what it buys

annual contribution at 12 customers = 12 × $62,900 = $754,800
months to repay at full run rate    = $1,084,000 ÷ ($754,800/12) = 17.2 months
segment ceiling at 100% penetration = 1,200 × $85,000 = $102.0m ARR
accounts needed for $10m ARR        = 10,000,000 ÷ 85,000 = 118  (9.8% of the segment)

The segment is large enough to build a real company on and small enough that 118 accounts is a describable sales plan. That is the shape you want.

Caveats that carry the answer. The 17.2-month figure assumes all twelve customers are live and contributing at full rate from day one; if they land evenly across the year, first-year contribution is closer to $377,400 and the investment is still under water at month twelve. The 74% contribution margin assumes onboarding and escalation labour stays inside it — the first thing that breaks when founder-led delivery scales, which is why this connects directly to Customer Success. The 22% win rate rests on a handful of decisions and cannot distinguish 22% from 35%. And none of this tests whether a chasm exists; it prices a concentration bet on the assumption that one does.

Set exit criteria before you start#

Write them down at the same time as the investment: maximum proof duration, minimum win rate against the named alternative, required reference count, required gross retention, and a ceiling on whole-product spend. A beachhead is a testable strategic commitment. Without exit criteria, "focus" is indistinguishable from refusing to update.

What are the common mistakes?#

• Treating the lifecycle as a schedule. The curve is a description of a distribution, not a timetable. Adoption in your market may be continuous, platform-mediated, or mandated by regulation.
• Calling every slowdown a chasm. Weak value, poor qualification, a broken hand-off, or a price that does not clear procurement all look identical from the dashboard.
• Choosing the largest TAM. Beachhead quality is homogeneity, reachability, and reference potential. Prize size is a constraint you check, not the thing you optimise.
• Defining the segment demographically. "Mid-market healthcare" is not a beachhead. "Revenue-cycle teams at 200–600 bed regional hospitals running Epic, facing a payer policy change" is.
• Confusing one famous logo with reference density. A marquee customer helps credibility and rarely helps a pragmatist peer, who wants someone with the same constraints and no special treatment.

When does the framework break?#

When adoption is not reference-mediated. Low-risk consumer products, viral social products, and anything distributed through an established platform's marketplace can spread without organisational reference-checking. See Cloud Marketplaces and Product-Led Growth.

When the change is mandatory. Regulation, a payer requirement, or a platform deprecation can compress or eliminate the transition entirely — and creates a deadline the framework has nothing to say about.

When the segment is not economically viable. Reference density cannot repair low willingness to pay, prohibitive acquisition cost, or custom delivery that destroys contribution. Run Willingness to Pay and Contribution Margin before running the beachhead scorecard, not after.

When the framework is used as a narrative rather than a test. Because the case evidence is retrospective and success-selected, the framework will always produce a plausible story about why a stall is a chasm and focus is the answer. That story is unfalsifiable unless you attach exit criteria and denominators to it.