Mmcp.market

beachhead-segment skill

by phuryn·phuryn/pm-skills·27k stars·MIT

Identify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.

A100/100content scan

Is the beachhead-segment skill safe?

Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-09-28.

No findings.

Install the beachhead-segment skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/phuryn/pm-skills.git /tmp/pm-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-skills/pm-go-to-market/skills/beachhead-segment ~/.claude/skills/beachhead-segment
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

Beachhead Segment

Overview

Identify the first beachhead market segment for product launch. This skill evaluates potential market segments against key criteria to find your initial winning segment that enables fast PMF validation and adjacent expansion.

When to Use

  • Choosing a first market for your product
  • Targeting an initial customer segment
  • Planning initial market entry strategy
  • Deciding where to focus limited resources
  • Validating GTM assumptions with early adopters

Key Evaluation Criteria

1. Burning Pain Point

Does this segment experience an acute, unmet problem?

  • Daily frustration with the status quo
  • Significant productivity loss or cost impact
  • Emotional urgency to find a solution
  • Current workarounds are expensive or fragile
  • Problem is getting worse over time

2. Willingness to Pay

Does this segment have budget and motivation to pay for a solution?

  • Documented budget allocation for this problem area
  • ROI is clear and compelling (value > cost)
  • Economic impact of problem justifies solution cost
  • Decision-maker has autonomy or influence over budget
  • No free or DIY alternatives that fully satisfy need

3. Winnable Market Share

Can you realistically capture 60-70% of this segment in 3-18 months?

  • Segment is large enough but not oversaturated
  • Limited competition or easy differentiation
  • Market players are fragmented or complacent
  • Your product has clear competitive advantage
  • You have unique access or distribution advantage

4. Referral Potential

Will customers naturally refer or recommend to others?

  • Segment contains professional communities
  • Customers interact with adjacent segments (expansion opportunity)
  • High word-of-mouth culture in this industry
  • Network effects within the segment
  • Solving problem for one creates demand in adjacent segments

How It Works

Step 1: List Potential Segments

Brainstorm all possible target segments:

  • Industry verticals (SaaS, healthcare, manufacturing, etc.)
  • Company size (SMB, mid-market, enterprise)
  • Job titles or roles
  • Geographic regions
  • Use cases or use-case variations
  • Customer maturity level

Step 2: Research Pain Points

Validate burning pain in each segment:

  • Customer interviews and discovery calls
  • Problem validation through surveys
  • Market research and analyst reports
  • Competitor positioning and customer reviews
  • Quantify cost/impact of the problem
  • Identify current workarounds and limitations

Step 3: Assess Willingness to Pay

Determine budget and economic viability:

  • Segment's budget for this problem category
  • ROI calculation (value gained vs cost)
  • Current spending on solutions or workarounds
  • Budget decision-making process
  • Typical deal size expectations
  • Pricing sensitivity in the segment

Step 4: Evaluate Winnability

Assess realistic market share potential:

  • Total addressable market (TAM) size
  • Competitive landscape and positioning
  • Your differentiation or unfair advantage
  • Distribution access to this segment
  • Time and resources required
  • Market growth and momentum

Step 5: Identify Referral Pathways

Map expansion opportunities:

  • Adjacent segments that reference segment influences
  • Network effects within the segment
  • Professional communities and associations
  • Customer-to-customer recommendations
  • Natural expansion path to adjacent markets
  • Viral or network effects from solving core pain

Step 6: Select Beachhead

Choose your primary launch segment:

  • Highest combined score across four criteria
  • Most achievable for your current resources
  • Shortest path to PMF and revenue
  • Best reference for adjacent expansion
  • Most enthusiastic early customer cohort

Input Format

Use $ARGUMENTS to pass:

  • Product description and capabilities
  • Initial market research and validation data
  • Potential segment options
  • Constraints and limitations
  • Timeline and resource constraints
  • Current customer data or feedback

Output

A beachhead segment analysis including:

  • Top 3-5 recommended segments with scoring
  • Primary beachhead segment recommendation
  • Pain point validation and evidence
  • Willingness to pay assessment and pricing guidance
  • Realistic market share and revenue projections
  • Referral and expansion pathways to adjacent segments
  • 90-day customer acquisition plan for beachhead
  • Post-beachhead expansion roadmap

Framework

Based on Geoffrey Moore's beachhead market strategy in "Crossing the Chasm." Focuses on finding the smallest winnable, referenceable market that validates PMF and enables expansion.

Tips

  • Start absurdly specific. A niche beachhead is better than a vague mass market
  • Choose the segment most likely to evangelize your solution
  • Validate all four criteria with at least 10 customer interviews
  • Select segment with fastest path to revenue and references
  • Ensure beachhead can reference to adjacent market segments
  • Focus all resources on dominating the beachhead (not diluting efforts)
  • Plan exit from beachhead only after 60%+ market share

Further Reading

  • 5 GTM Principles You Should Know as a PM
  • Product-Led Growth 101, Part 1/2
  • How to Design a Value Proposition Customers Can't Resist?
  • How to Achieve Product-Market Fit? Part I: Market and Value Proposition

More skills from phuryn/pm-skills

  • Aab-test-analysisAnalyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
  • Aanalyze-feature-requestsAnalyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
  • Aansoff-matrixGenerate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.
  • Abrainstorm-experiments-existingDesign experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
  • Abrainstorm-experiments-newDesign lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
  • Abrainstorm-ideas-existingBrainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
  • Abrainstorm-ideas-newBrainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.
  • Abrainstorm-okrsBrainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
  • Abusiness-modelGenerate a Business Model Canvas with all 9 building blocks. Use when creating a business model, documenting how a business creates value, or analyzing an existing business model.
  • Acode-reviewReview code for actionable defects. Correctness is the core; performance and security are optional sub-cases of the same engine. Anchors on agreements between participants across a boundary, forces a violating execution, and refutes every candidate before reporting. Use when asked to review changes, find bugs, audit a codebase, or check whether a fix is safe.
  • Acohort-analysisPerform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
  • Acompetitive-battlecardCreate sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'

All agent skills → · MCP servers