mcpbeat Sign in

Beachhead Segment Agent Skill

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.

1k tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
24819
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/phuryn/pm-skills --skill beachhead-segment

The instruction itself

20 sections, as written by the author

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

Other skills for the same job

different authors, same section of the catalogue
Doc Coauthoring
by anthropics
vendor ×10

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

4k tokens
File Organizer
by frostant
×10

Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.

3k tokens
Domain Name Brainstormer
by frostant
×8

Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.

1k tokens
Brainstorming
by ZhanlinCui
×4

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

626 tokens
Planning With Files
by ZhanlinCui
×3

Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.

9k tokens scripts
Scientific Brainstorming
by christophacham
×3

Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.

5k tokens
GitHub Project Management
by ComeOnOliver
×3

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

14k tokens
Grill Me
by ComeOnOliver
×3

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

3k tokens

How to use it

Copy the folder

Take phuryn/beachhead-segment from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.