beachhead-segment
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.
- Installs
- 2.8K
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/phuryn/pm-skills --skill beachhead-segment- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads beachhead-segment automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
FAQ
What does the beachhead-segment skill do?
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.
How do I install beachhead-segment?
Run npx skills add https://github.com/phuryn/pm-skills --skill beachhead-segment in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/beachhead-segment/ (personal) or .claude/skills/beachhead-segment/ (project).
Which AI agents can use beachhead-segment?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is beachhead-segment safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains beachhead-segment?
It is published by phuryn in phuryn/pm-skills. It has 2,771 recorded installs.
More from phuryn/pm-skills
create-prd
phuryn/pm-skills
Create a lean, decision-ready Product Requirements Document with an 8-section template: summary, contacts, background, objective, market segments, value propositions (6-part JTBD template), solution, and release. Lean by default (about one to two pages), with a fuller spec on request. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
pre-mortem
phuryn/pm-skills
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go wrong.
prioritization-frameworks
phuryn/pm-skills
Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates — RICE, ICE, Kano, MoSCoW, Opportunity Score, and more. Use when selecting a prioritization method, comparing frameworks like RICE vs ICE, or learning how different prioritization approaches work.
outcome-roadmap
phuryn/pm-skills
Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
strategy-red-team
phuryn/pm-skills
Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.
competitor-analysis
phuryn/pm-skills
Analyze competitors with strengths, weaknesses, and differentiation opportunities. Identifies direct competitors and maps the competitive landscape. Use when doing competitive research, preparing a competitive brief, or finding differentiation opportunities.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.