# How the Beachhead-Segment Skill Identifies Optimal First Markets in PM-Skills

> Discover how the beachhead-segment skill pinpoints your best first markets. It analyzes pain, payment, share, and referrals via a 6-step process for a ranked shortlist and 90-day plan.

- Repository: [Pawel Huryn/pm-skills](https://github.com/phuryn/pm-skills)
- Tags: how-to-guide
- Published: 2026-06-22

---

**The beachhead-segment skill evaluates candidate markets against four quantitative criteria—burning pain, willingness to pay, winnable market share, and referral potential—through a six-step workflow to produce a ranked shortlist and 90-day acquisition plan.**

The beachhead-segment skill in the `phuryn/pm-skills` repository provides a structured framework for product managers to pinpoint the most promising initial market segment. Located at [`pm-go-to-market/skills/beachhead-segment/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-go-to-market/skills/beachhead-segment/SKILL.md), this implementation follows Geoffrey Moore's *Crossing the Chasm* methodology to ensure the selected segment is small, referenceable, and fast to validate.

## The Four Evaluation Criteria

According to the source code in [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md) (lines 19-49), the skill assesses every candidate segment through four quantitative lenses:

### Burning Pain

Measures the **severity and urgency** of the problem the product solves. Segments scoring high here exhibit acute, unavoidable pain points that demand immediate resolution rather than nice-to-have improvements.

### Willingness to Pay

Evaluates **budget reality and ROI justification**. This criterion verifies that the target segment has allocated funds for solutions in this category and can demonstrate concrete return-on-investment metrics within a defined payback period.

### Winnable Market Share

Projects **realistic capture of 60-70% market share within 3-18 months**. The skill analyzes total addressable market (TAM), competitive density, and differentiation moats to confirm the segment is defensible and not dominated by entrenched incumbents.

### Referral Potential

Assesses **natural word-of-mouth and network effects**. High-scoring segments contain interconnected buyers—such as industry communities or professional networks—where satisfied early adopters organically influence adjacent prospects.

## The Six-Step Decision Workflow

The "How It Works" section (lines 51-100) enumerates a systematic six-step process that transforms raw market data into an actionable recommendation:

1. **List all plausible segments** based on product capabilities and initial market research.
2. **Research and validate pain points** through customer interviews, surveys, and usage analytics.
3. **Assess budget and ROI** by analyzing procurement cycles, existing spend on alternatives, and financial approval chains.
4. **Evaluate winnability** using TAM calculations, competitive SWOT analysis, and technical differentiation mapping.
5. **Map referral pathways** by identifying community hubs, industry forums, and influencer networks within each segment.
6. **Score and select** the top segment using a composite scoring matrix that weights the four criteria.

## Input Schema and CLI Usage

The skill expects a structured JSON payload as defined in lines 106-114 of [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md). Users invoke the skill via the PM-Skills CLI or programmatically through the underlying JSON schema:

```json
{
  "product": "AI‑powered time‑tracking SaaS",
  "capabilities": [
    "automatic activity detection",
    "real‑time productivity dashboards"
  ],
  "marketResearch": {
    "segments": [
      {"name":"Remote tech startups (10‑50 employees)", "painScore":8, "budget":50000},
      {"name":"Consulting firms (100‑200 employees)", "painScore":6, "budget":120000},
      {"name":"Legal practices (5‑15 employees)", "painScore":9, "budget":30000}
    ]
  },
  "constraints": {
    "teamSize": 3,
    "budget": 250000,
    "timelineMonths": 4
  }
}

```

This input format includes the product description, capability array, candidate segments with preliminary scoring, and execution constraints that bound the recommendation.

## Scoring and Output Artifacts

After processing, the skill produces deliverables specified in lines 115-124 of the source file. The output includes a ranked table, primary recommendation, and concrete go-to-market tactics:

```markdown

## Top Recommended Beachhead Segments

| Rank | Segment                              | Pain | Willingness to Pay | Winnable Share | Referral Potential | Composite Score |
|------|--------------------------------------|------|--------------------|----------------|--------------------|-----------------|
| 1    | Remote tech startups (10‑50 emp)    | 9    | 8                  | 7              | 6                  | 30 |
| 2    | Legal practices (5‑15 emp)          | 9    | 7                  | 6              | 5                  | 27 |
| 3    ... (others) ...

### Primary Recommendation

**Remote tech startups (10‑50 employees)** – highest combined score, clear budget, strong pain, and a community of founder forums that drive referrals.

#### 90‑Day Acquisition Plan

1. Target LinkedIn founder groups (2 hrs/week).  
2. Offer a 30‑day free pilot to 5 early‑adopter startups.  
3. Capture case studies → use as reference for adjacent segments.

```

The composite score aggregates the four criteria into a comparable metric, while the 90-day acquisition plan provides immediate tactical steps for market entry.

## Framework and Technical Implementation

The methodology is rooted in **Geoffrey Moore's *Crossing the Chasm*** beachhead strategy, as referenced in lines 126-128 of [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md). This ensures the chosen segment serves as a referenceable foothold for adjacent market expansion.

The skill is discoverable by the PM-Skills CLI through a metadata header that declares the skill name and description, enabling automated tooling to index and invoke the capability. The implementation resides within the `pm-go-to-market` suite, with additional context available in [`pm-go-to-market/README.md`](https://github.com/phuryn/pm-skills/blob/main/pm-go-to-market/README.md) and plugin registration handled via [`.claude-plugin/plugin.json`](https://github.com/phuryn/pm-skills/blob/main/.claude-plugin/plugin.json).

## Summary

- The beachhead-segment skill uses **four quantitative criteria** to objectively compare market opportunities.
- A **six-step workflow** systematically validates pain points, budgets, winnability, and referral potential before scoring.
- Input follows a strict JSON schema (lines 106-114) accepting product details, segment research, and constraints.
- Output delivers a **ranked shortlist**, primary recommendation, and **90-day acquisition plan** (lines 115-124).
- The framework is based on **Geoffrey Moore's beachhead strategy** from *Crossing the Chasm* (lines 126-128).

## Frequently Asked Questions

### What input format does the beachhead-segment skill require?

The skill accepts a JSON payload containing the product description, capability array, market research data with candidate segments, and execution constraints. This schema is defined in lines 106-114 of [`pm-go-to-market/skills/beachhead-segment/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-go-to-market/skills/beachhead-segment/SKILL.md).

### How does the skill calculate the composite score for each segment?

The composite score aggregates ratings across the four evaluation criteria—burning pain, willingness to pay, winnable market share, and referral potential—into a single comparable metric. Each criterion is assessed during the six-step workflow, then combined to rank segments relative to one another.

### What is the theoretical basis for the beachhead-segment skill?

The methodology derives from Geoffrey Moore's *Crossing the Chasm*, specifically the beachhead strategy for selecting a small, referenceable initial market. This ensures the segment is defensible, fast to validate, and capable of generating referrals for adjacent segments.

### Where is the skill definition stored in the repository?

The core definition resides at [`pm-go-to-market/skills/beachhead-segment/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-go-to-market/skills/beachhead-segment/SKILL.md), with CLI discoverability managed through [`.claude-plugin/plugin.json`](https://github.com/phuryn/pm-skills/blob/main/.claude-plugin/plugin.json) in the `pm-go-to-market` folder.