beachhead-segment
Skill2 starsChanged 3 months agoMITView on GitHub
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.
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
No free or DIY alternatives that fully satisfy need
- Distinctive: line 59
Use cases or use-case variations
- Distinctive: line 107
Use $ARGUMENTS to pass:
- Distinctive: line 130
Start absurdly specific. A niche beachhead is better than a vague mass market
- Distinctive: line 134
Ensure beachhead can reference to adjacent market segments
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 versions9 projects use a version of this.
Word for word · 8
- phuryn/claude-code-advanced★ 4100% same
- skytiger6724/qwen-skills★ 2100% same
- daviszhen/agent-skills★ 1100% same
- miovrag/claude-skills★ 1100% same
- xeroc/skills★ 1100% same
- maeng777/claude-skills★ 0100% same
- stefanomartiradonna/claude-skills★ 0100% same
- vijaysuperpositionist/skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 1
- Usermuse/em-plugin★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository383 other files it gives its agents.
- 37signals-waySkill
- ab-test-analysisSkill
- advisor-orchestrator-workerSkill
- ai-ml-engineeringSkill
- algorithmic-artSkill
- analyze-feature-requestsSkill
- animation-vocabularySkill
- apple-designSkill
- emil-design-engSkill
- find-animation-opportunitiesSkill
- improve-animationsSkill
- pick-ui-librarySkill
- prototypeSkill
- review-animationsSkill
- ansoff-matrixSkill
- api-and-interface-designSkill
- api-design-best-practicesSkill
- app-store-changelogSkill
- auth-authorizationSkill
- blue-ocean-strategySkill
- brainstorm-experiments-existingSkill
- brainstorm-experiments-newSkill
- brainstorm-ideas-existingSkill
- brainstorm-ideas-newSkill
- brainstorm-okrsSkill
- brand-guidelinesSkill
- browser-testing-with-devtoolsSkill
- bug-hunt-swarmSkill
- business-modelSkill
- canvas-designSkill
- ci-cd-and-automationSkill
- claude-apiSkill
- clean-architectureSkill
- clean-codeSkill
- cli-creatorSkill
- code-review-and-qualitySkill
- code-review-skillSkill
- code-simplificationSkill
- cohort-analysisSkill
- cold-start-problemSkill
- commit-archaeologistSkill
- competitive-battlecardSkill
- competitor-analysisSkill
- contagiousSkill
- context-engineeringSkill
- continuous-discoverySkill
- architecture-blueprint-generatorSkill
- azure-architecture-autopilotSkill
- cli-masterySkill
- codeqlSkill
- conventional-commitSkill
- create-implementation-planSkill
- csharp-asyncSkill
- diagnoseSkill
- dotnet-best-practicesSkill
- draw-io-diagram-generatorSkill
- git-commitSkill
- github-actions-efficiencySkill
- java-springbootSkill
- mcp-cliSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

