beachhead-segment
The beachhead-segment skill identifies the optimal first market segment for product launch by evaluating potential segments against four criteria: presence of acute, unmet pain points, customer budget and motivation to pay, realistic market share capture potential within 18 months, and natural referral potential within professional communities. Use this when selecting an initial target market, planning market entry strategy, or validating go-to-market assumptions with early adopters before expanding to adjacent segments.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/beachhead-segment && cp -r /tmp/beachhead-segment/pm-go-to-market/skills/beachhead-segment ~/.claude/skills/beachhead-segmentSKILL.md
# 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](https://www.productcompass.pm/p/5-gtm-principles-with-frameworks-templates) - [Product-Led Growth 101, Part 1/2](https://www.productcompass.pm/p/product-led-growth-101-12) - [How to Design a Value Proposition Customers Can't Resist?](https://www.productcompass.pm/p/how-to-design-value-proposition-template) - [How to Achieve Product-Market Fit? Part I: Market and Value Proposition](https://www.productcompass.pm/p/how-to-achieve-the-product-market)
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
Analyze 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.
Perform 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.
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.
Brainstorm 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.
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.