Beachhead strategy

Geoffrey Moore's bowling pin strategy: win a narrow beachhead — one segment where you can be the obvious default — then knock into adjacent pins where the same reference customers and product modules transfer.

A DevOps analytics startup might beachhead on "Series B+ fintechs on Kubernetes with a platform team of 5+," become the default there, then expand to health-tech with similar stacks, then to broader mid-market. Each pin reuses proof, integrations and case studies.

Beachheads also clarify positioning: you are allowed to say no to non-ICP inbound so the team learns one sales narrative deeply. See founder-led sales.

Your first SAM should be painfully narrow — one persona, one geo, one stack — even if TAM is global. The pitch says "we start here; the wedge expands to that." Confusing the beachhead with the TAM is how teams boil the ocean and miss product-market fit.

When product and sales fight, translate: sales asks for features that expand win rate on ICP. Product should push back on features that only close non-ICP logos that will churn — that is an NRR tax disguised as a deal.

Common mistakes

• Horizontal "everyone" GTM because the TAM slide looks bigger.
• Saying yes to non-ICP inbound and never learning one narrative.
• Building features to close logos that will churn.

Check yourself

1. Why is a narrow beachhead better than a $50B horizontal TAM? You can become the default in one segment and reuse proof. Horizontal GTM dies from too many narratives.
2. A non-ICP deal needs a one-off feature. What is the hidden cost? NRR tax — they churn, and the narrative fragments.

Key takeaways

• Win a narrow beachhead, then knock adjacent pins.
• Each pin should reuse proof, integrations and case studies.
• Say no to non-ICP inbound so one narrative gets good.
• Features that only close the wrong logos are an NRR tax.

Further learning

Turn the beachhead into a number of meetings: GTM funnel metrics.