Files
skills/public/beachhead-segment.md
zeekayandHanzo Dev 65c3b27843 160 marketing, growth and PM skills, on our own connectors
Four MIT collections ported — growthOS, openclaw-marketing-skills,
Marketing-Skills and pm-skills — as 160 skills, 12 agents and 45
commands, each naming its origin in its own frontmatter so the tree can
be checked against THIRD_PARTY_NOTICES rather than trusted. Sixteen names
appeared in more than one collection and none of the copies were
identical; the longest wins, which lands on the more developed text where
they genuinely diverge.

A fifth collection is deliberately absent. awesome-growth-hacking-skills
carries NO licence, which leaves its author every right by default — and
it is a list of links rather than a collection of skills, so there is
nothing in it to port and no permission to port it with. It is cited as a
directory to read.

THE CONNECTOR SKILLS ARE REWRITTEN, not ported. They arrived installing
vendor SDKs, running OAuth flows of their own, and ending with long-lived
credentials in JSON files under .agents/ and ~/.growthos/ at mode 600.
That is a secret on a disk with no rotation path, protected from other
users and not from the agent — and one auth implementation per skill.
Hanzo holds these connectors in Go, per user, sealed in KMS, so `connect`
is the one home for the flow and the platform skills defer to it by
provider id: google_ads, meta_ads, x. It is reachable as HTTP or as MCP
tools at api.hanzo.ai/v1/mcp — the same routes, typed once in Go, so a
tool and a curl cannot disagree.

Two had nothing real behind them and now say so. There is no
search_console provider, so that skill names what does answer the same
questions (google_analytics, google_bigquery) and states that the remedy
is a provider in hanzoai/cloud rather than a vendor SDK here. And
getxapi-connect was a wrapper around a paid reseller of X's public data
with the vendor's key in an env var; it is `listen` now, on our own x
connector — a skill named after a vendor makes the vendor the capability
and dies with it.

The skills referenced paths that only existed inside the source repo, so
the shared material they read is ported to reference/ and the paths
rewritten. Three skills need the growthOS APPLICATION rather than its
data; per the estate's own split an application belongs in hanzoai/ads,
social, email or sms as a cloud plugin, so those three say what they need
instead of carrying an import that resolves to nothing.

Third-party product names are out of our prose and kept in the notices,
which is where the licence requires them and the only place they belong.
A skill's persona names a role, not somebody else's product.


Co-authored-by: Hanzo Dev <[email protected]>
2026-09-15 01:27:26 -07:00

5.8 KiB

name, description, source
name description source
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. phuryn/pm-skills

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