Beachhead Segment · Finch Skill #306 · free · MIT
Pick one shore. Win it before you sail on.
Give your assistant the product, the candidate markets and what you know about them. It scores each segment on four criteria, names the single beachhead to land on, and plans the first 90 days and the route out.
Burning painAn acute, unmet problem felt daily
Willingness to payBudget, clear ROI, no free fix
Winnable share60-70% reachable in 3-18 months
Referral potentialCustomers who talk to the next segment
What it is
A disciplined first-market choice
One instruction file, based on Geoffrey Moore’s beachhead strategy in Crossing the Chasm. It walks a capable assistant through six steps: list segments, research pain, assess willingness to pay, judge winnability, map referral paths, then select.
Its stance is deliberate: start absurdly specific, put every resource into the beachhead, and only move on after 60% or more of it is yours.
Who it is for
- Founders choosing a first market with a small team
- Product and GTM leads planning a launch or a new line
- Operators deciding whether to expand or deepen first
- Advisors and students applying beachhead strategy to a real case
Safe water
Works well for
- Choosing the first segment for a launch
- Testing an expansion plan against focus
- Deciding where limited sales effort goes
- Validating GTM assumptions with early adopters
Hazards
Not designed for
- Measuring market size; it uses figures you supply or labels them assumptions
- Live competitor or pricing research
- Replacing interviews (the Skill asks for at least 10)
- Revenue forecasts you can bank on
What you bring, what you get
You bring
- Product description and capabilities
- Segment options you are weighing
- Research, interviews or validation data
- Current customers and feedback
- Time, budget and team constraints
You get
- 3-5 segments scored on four criteria
- One primary beachhead, with evidence
- Pricing guidance and share projections
- Referral and expansion paths
- A 90-day acquisition plan and post-beachhead roadmap
Where it runs
Any AI assistant that can read a Skill file, including Claude Code and Codex. Download the free plaintext package from Finch, then install it with your assistant’s Skill method or ask it to read SKILL.md.
No extra API key, script or service. You still need access to an assistant model, which may have its own subscription or usage cost. The Skill does no web research of its own.
Limits and licence
Scores are structured judgment. Segment sizes, shares and revenue figures are only as good as your inputs; check every item marked as an assumption.
MIT licence, Copyright (c) 2026 Pawel Huryn. Source: phuryn/pm-skills at commit 2a12295a7717, path pm-go-to-market/skills/beachhead-segment. The package adds a README, NOTICE, provenance note and a cover; the instructions are unchanged.
How it was checked
One Claude Code run on a fictional company produced all eight parts the Skill promises: five segments scored, one beachhead chosen, a 90-day plan and an expansion roadmap. It also judged the company’s draft plan and recommended deferring a second-city launch. It flagged the Skill’s own 60-70% share target as not credible within 12 months for this case, and said Seattle could not be scored credibly without data. The package downloaded back from Finch matched the audited files byte for byte. Native client installation, repeat runs and real outcomes were not tested.