ENT 301 · Unit 4 · Lesson 1 of 5
Beachhead Markets
Go-to-Market
Lesson
Win one segment deeply before you narrate a nation
A beachhead market (a narrowly chosen first segment where a startup can deliver disproportionate value and learn faster than incumbents) is the geographic and firmographic pin on which RelayOps stakes its first repeatable sales motion. Maya Chen and Jordan Okonkwo are tempted to sell "any field service company with dispatch pain." That story raises money in slides and wastes money in pipelines.
RelayOps's beachhead is 80-to-200 technician residential-heavy HVAC and plumbing firms in Sun Belt metros, starting Phoenix then Dallas. ENT 401 interviews and Unit 2 pilots sharpened filters: single dispatch center, owner accessible, overtime pain above 10% on peak weeks.
RelayOps is a B2B (business-to-business, selling to companies) SaaS (software as a service, subscription software delivered over the internet) venture improving dispatch and scheduling for mid-market field-service companies and the anchor venture for ENT 301. Founders Maya Chen (CEO, former dispatch manager at regional HVAC operator Summit Climate) and Jordan Okonkwo (CTO, former platform engineer) left Summit Climate in 2025 after living dispatch-center chaos firsthand. Their initial beachhead is 80-to-200 technician residential-heavy HVAC and plumbing firms, later expanding to commercial HVAC in Phoenix and Dallas with 50 to 150 field technicians. Discovery work confirmed 10 to 15 percent overtime on peak weeks and missed first-visit appointment windows tied to same-day capacity loss when dispatchers rebalance schedules across phone calls, whiteboards, and legacy CRM tabs without a live view of technician skill, location, and parts. Competitors include ServiceTitan (heavy and expensive for mid-market), spreadsheets and whiteboards (status quo).
Throughout this course, RelayOps evolves from opportunity hypothesis to scaled venture. Elective depth lives in ENT 403 (Startup Go-to-Market and Founder-Led Sales) when you want a full unit on that phase. ENT 301 teaches the integrated journey so you can advise founders, invest, or launch with disciplined evidence. ENT 403 (Startup Go-to-Market and Founder-Led Sales) provides textbook depth on beachhead selection and ICP design. ENT 301 connects beachhead choice to PMF graduation and distribution capital allocation.
This lesson teaches beachhead sizing, ICP attributes, segment scoring, and when to expand geography versus deepen density.
Beachhead selection criteria
Strong beachheads share five traits: acute pain (emergency dispatch delays cost revenue), budget authority reachable (dispatch manager or owner can sign pilot), reference density (owners talk at association meetings), reachable channels (founder network and trade groups), and expansion path (adjacent plumbing, commercial HVAC later).
RelayOps rejects segments that fail any must-have. Enterprise utilities with 18-month procurement fail authority. One-truck operators fail ACV (annual contract value, yearly revenue per customer). National rollouts fail reachable channels at pre-seed.
Beachhead is not forever. It is the segment where learning per dollar is highest for the next 12 months.
Ideal customer profile (ICP) for RelayOps
The ICP (ideal customer profile, firmographic and behavioral traits of accounts that win fastest*) translates beachhead narrative into prospect filters. RelayOps ICP v2 after pilots: 70-120 technicians, residential mix above 60%, one primary dispatch center, Phoenix metro, ServiceTitan or legacy CRM present, owner COO accessible, peak-week overtime above 10%.
ICP differs from TAM (total addressable market, entire theoretical demand). Phoenix ICP might be 85 firms; TAM nationwide is thousands. Investors need both, but GTM spends against ICP counts.
Negative ICP attributes matter: split dispatch centers, commercial-only mix, mandated enterprise security reviews before pilot.
RelayOps ICP scorecard (0-2 per attribute, target ≥14/20):
| Attribute | 0 | 1 | 2 |
|---|---|---|---|
| Technician count | <50 or >200 | 50-69 or 151-200 | 70-150 |
| Residential mix | <40% | 40-59% | ≥60% |
| Dispatch centers | 3+ | 2 | 1 |
| Overtime pain | <5% | 5-9% | ≥10% |
| Owner access | No intro | Manager only | Owner engaged |
| CRM readiness | Paper only | Mixed | Digital CRM |
Density versus geography expansion
After three Phoenix logos, Maya debates Dallas expansion versus Phoenix density (fourth and fifth logos). Density improves referral loops, association word-of-mouth, and support efficiency. Geography tests portability of ICP.
Rule of thumb: deepen density until referral contributes 25% of qualified pipeline or ICP list is 50% contacted, then expand geography with the same ICP scorecard.
Dallas should replicate Phoenix ICP, not restart segment debate. Valley Pro failure already showed commercial-mix risk.
Beachhead sizing arithmetic
Count ICP firms bottom-up. If 85 Phoenix firms match ICP and RelayOps closes 15% in 18 months, that is 13 logos. At $118,800 ACV (100 techs × $99 × 12), 13 logos ≈ $1.54M ARR in one metro. That is enough for seed narrative without claiming national share.
Check assumptions: close rate, ACV, and sales cycle. Founder-led cycle is 60-90 days; pipeline needs 3× coverage for annual logo target.
Maya maintains ICP spreadsheet with score, stage, and disqualification reason. "Not a fit" is valuable data.
Linking beachhead to ENT 403 GTM playbook
ENT 403 converts ICP into prospect lists, messaging, and founder-led pipeline stages. ENT 301 requires beachhead discipline before spending on paid ads or channel partners.
When ICP attributes change after losses, version the ICP (v2, v3) and backfill CRM records. Sales calls should screen with scorecard, not gut feel.
Jordan builds product for ICP dispatch workflows, not hypothetical enterprise personas.
Worked example: RelayOps Phoenix ICP qualification day
Maya reviews six prospects from an association list. Only two should enter founder-led pipeline this month.
Part A: Scoring
| Firm | Techs | Res mix | Centers | Overtime | Owner | CRM | Score |
|---|---|---|---|---|---|---|---|
| Desert Peak | 88 | 70% | 1 | 12% | Yes | Digital | 12 |
| Metro Comm HVAC | 140 | 20% | 2 | 8% | No | Digital | 7 |
| SunLine | 78 | 65% | 1 | 11% | Yes | Mixed | 11 |
| QuickChill | 45 | 80% | 1 | 9% | Yes | Paper | 8 |
Target ≥10 for pipeline; ≥14 for priority.
Part B: Pipeline decision
Priority: Desert Peak (12). Active nurture: SunLine (11, already customer). Disqualify for now: Metro Comm (commercial mix, weak owner access). QuickChill: too small for ACV; revisit if hires techs.
Dallas list uses same scorecard without changing weights mid-quarter.
Part C: Check
If Maya closes 2 of 4 qualified Phoenix ICP firms in 90 days, close rate 50% on tiny sample; document as exploratory, not scalable benchmark until n≥10.
Check: Desert Peak 12 ≥ 10 ✓; Metro Comm 7 < 10 disqualified ✓.
Part D: Managerial read
Investor question "Is market big enough?" answer with ICP count times ACV, not national TAM. Show expansion adjacency (plumbing) as option, not current focus.
Worked example: Nationwide day-one trap
FieldSync (fictional) marketed to all contractors nationwide and burned $600,000 on ads with no ICP scorecard. CAC exceeded $40,000 per logo with 9-month cycles. RelayOps's Phoenix beachhead concentrates references and support hours.
Managerial read: beachhead is a learning strategy, not a permanent ceiling.
Common mistakes beginners make
| Mistake | Reality |
|---|---|
| Defining beachhead as any customer with pain | Use scored ICP attributes and disqualification rules |
| Expanding geography before density and referrals mature | Deepen one metro until pipeline math proves repeatability |
| Confusing TAM slides with ICP prospect counts | Bottom-up ICP list drives founder calendar |
| Ignoring negative ICP signals from churned pilots | Version ICP after losses like product semver |
| Letting custom deals bend ICP to close one logo | Custom work outside ICP destroys payback and focus |
Practice problem
RelayOps Phoenix ICP list: 85 firms. Target: 12 logos in 18 months. Current: 3 logos, 22 qualified opportunities, founder-led close rate 25% on qualified, ACV $118,800.
Tasks: (1) How many logos still needed? (2) At 25% close rate, how many qualified opps needed for remaining logos? (3) Is 22 pipeline opps sufficient? Show check.
Solution
Logos needed: 12 - 3 = 9.
Qualified opps needed: 9 / 0.25 = 36.
Gap: 36 - 22 = 14 more qualified opportunities required. Pipeline insufficient today. Check: 9÷0.25=36 ✓; 36-22=14 ✓.
Key takeaways
- Beachhead is the segment where learning and win rate per dollar are highest now.
- ICP scorecards turn narrative into qualify-or-disqualify discipline.
- Density before geography protects support, referrals, and PMF signal quality.
- Bottom-up ICP math beats TAM theater for founder-led planning.
- ENT 403 expands beachhead into full GTM operating system.
After this lesson
- Score five real or fictional HVAC firms with the RelayOps ICP table.
- Compute ARR if RelayOps hits 12 logos at your chosen per-technician price.
- Continue to Early Positioning: how RelayOps frames the wedge versus ServiceTitan.
Applying Beachhead Markets at RelayOps
When RelayOps applies beachhead markets, Maya Chen and Jordan Okonkwo anchor decisions in field evidence, not slide optimism. Their beachhead (80-to-200 technician residential-heavy HVAC and plumbing firms, later expanding to commercial HVAC in Phoenix and Dallas with 50 to 150 field technicians) experiences 10 to 15 percent overtime on peak weeks and missed first-visit appointment windows. Discovery interviews suggested $89 to $149 per technician per month in discovery interviews. Competitors include ServiceTitan (heavy and expensive for mid-market), spreadsheets and whiteboards (status quo). Every framework in this lesson should translate into a falsifiable claim about that segment, not generic startup advice.
Consider how go-to-market, positioning, and founder-led sales changes capital allocation. RelayOps started with roughly $400k runway and ~$45k monthly burn before seed. A one-month delay on the wrong opportunity costs more than a month of disciplined interviews. That is why beachhead markets is a CEO-level skill, not a brainstorming exercise.
Document owners alongside metrics. Maya owns discovery synthesis; Jordan owns build scope tied to assumption ranks; both sign kill criteria before pilots. When definitions live in a shared glossary (pilot versus beta, activation versus login), the team avoids comparing incompatible cohort charts after Dallas expansion.
Extended RelayOps scenario: cross-functional read
Imagine RelayOps's quarterly review for beachhead markets. An angel investor asks whether dispatch pain justifies another build sprint. A pilot COO asks whether overtime reduction pays for software. A dispatcher lead asks whether the console survives Monday heat-wave call volume. A weak go-to-market, positioning, and founder-led sales answer pleases one stakeholder. A strong answer links evidence: interview prevalence, timed shadow data, pilot median dispatch time, and renewal intent.
Work a conservative arithmetic example. Suppose RelayOps targets 100-technician firms at $28 per technician per month ($2,800 MRR per logo). Closing 18 beachhead logos yields $50,400 MRR ($605k ARR). If CAC (customer acquisition cost, sales and marketing to win one paying customer) is $18,000 per logo, payback in months equals CAC divided by monthly gross profit. At 80% gross margin on MRR, monthly profit ~$2,240; payback ~8 months. Check: 18,000 / 2,240 ≈ 8.0 ✓. Founders who skip this math raise before they know whether GTM is repeatable.
Stakeholder conflict is normal. Jordan may push feature breadth; Maya must protect RAT (riskiest assumption test, cheapest experiment that falsifies the highest-impact uncertain belief) scope. Beachhead Markets gives language to negotiate with pre-registered metrics rather than charisma. If evidence is descriptive only, label it and fund the next test instead of scaling spend.
For deeper study on this unit's specialty, see ENT 403 (Startup Go-to-Market and Founder-Led Sales). ENT 301 integrates the full arc; electives provide textbook-depth units you can take after this core course.
Technical mechanics and checks (RelayOps patterns)
For beachhead markets, show work the way finance shows reconciliations. Opportunity scorecards print weighted criteria and explicit kill rules. Interview synthesis tables show code frequency with qualified denominators only. MVP scorecards list assumption rank, build weeks, runway share, and kill criteria. Cap tables after SAFE conversion show pre-money, post-money, and founder ownership with check lines.
Use plain-language hypotheses before instruments. Example: "If fewer than six of ten operations leaders rank same-day rebalance in top-three pains, RelayOps deprioritizes hypothesis H1." That hypothesis is falsifiable without code. Weak hypotheses hide inside feature roadmaps.
Spreadsheet grain matters. Customer-level tables suit funnel conversion; logo-month tables suit retention; assumption-level tables suit experiment backlogs. RelayOps forbids ambiguous metrics like "engagement" without operational definitions tied to dispatch jobs routed per active day.
Common executive questions (and disciplined answers)
Executives ask short questions that require long disciplined answers. "How sure are we?" maps to evidence labels (exploratory, descriptive, causal), not bravado. "What is the dollar impact?" maps to overtime saved, slots recovered, or MRR with stated assumptions. "Can we ship faster?" maps to risk of untested adoption during live emergencies. "Why not copy ServiceTitan?" maps to wedge focus and beachhead economics, not feature envy.
RelayOps's credible answer format for beachhead markets is three bullets: recommendation, evidence strength, and next test if limitations matter. A fourth bullet states what would falsify the recommendation within 60 days. That discipline prevents founders from becoming either bottlenecks or rubber stamps for investor narratives.
Judgment under uncertainty (RelayOps decision log)
Founders who master beachhead markets keep a decision log: date, decision, evidence at time, dissent captured, review date. When RelayOps chose emergency-queue MVP over full suite parity, the log recorded HeatRoute's LOI-to-active failure mode as contrast case. When Phoenix beat Dallas on retention, the log triggered segment screener review rather than blaming sales tone.
Your workbook should mirror that log format for one venture you follow. If you cannot write dissent and kill criteria, you have a story, not a decision. Beachhead Markets is how teams convert stories into capital-efficient learning.
Applying Beachhead Markets at RelayOps
When RelayOps applies beachhead markets, Maya Chen and Jordan Okonkwo anchor decisions in field evidence, not slide optimism. Their beachhead (80-to-200 technician residential-heavy HVAC and plumbing firms, later expanding to commercial HVAC in Phoenix and Dallas with 50 to 150 field technicians) experiences 10 to 15 percent overtime on peak weeks and missed first-visit appointment windows. Discovery interviews suggested $89 to $149 per technician per month in discovery interviews. Competitors include ServiceTitan (heavy and expensive for mid-market), spreadsheets and whiteboards (status quo). Every framework in this lesson should translate into a falsifiable claim about that segment, not generic startup advice.
Consider how go-to-market, positioning, and founder-led sales changes capital allocation. RelayOps started with roughly $400k runway and ~$45k monthly burn before seed. A one-month delay on the wrong opportunity costs more than a month of disciplined interviews. That is why beachhead markets is a CEO-level skill, not a brainstorming exercise.
Document owners alongside metrics. Maya owns discovery synthesis; Jordan owns build scope tied to assumption ranks; both sign kill criteria before pilots. When definitions live in a shared glossary (pilot versus beta, activation versus login), the team avoids comparing incompatible cohort charts after Dallas expansion.
Extended RelayOps scenario: cross-functional read
Imagine RelayOps's quarterly review for beachhead markets. An angel investor asks whether dispatch pain justifies another build sprint. A pilot COO asks whether overtime reduction pays for software. A dispatcher lead asks whether the console survives Monday heat-wave call volume. A weak go-to-market, positioning, and founder-led sales answer pleases one stakeholder. A strong answer links evidence: interview prevalence, timed shadow data, pilot median dispatch time, and renewal intent.
Work a conservative arithmetic example. Suppose RelayOps targets 100-technician firms at $28 per technician per month ($2,800 MRR per logo). Closing 18 beachhead logos yields $50,400 MRR ($605k ARR). If CAC (customer acquisition cost, sales and marketing to win one paying customer) is $18,000 per logo, payback in months equals CAC divided by monthly gross profit. At 80% gross margin on MRR, monthly profit ~$2,240; payback ~8 months. Check: 18,000 / 2,240 ≈ 8.0 ✓. Founders who skip this math raise before they know whether GTM is repeatable.
Stakeholder conflict is normal. Jordan may push feature breadth; Maya must protect RAT (riskiest assumption test, cheapest experiment that falsifies the highest-impact uncertain belief) scope. Beachhead Markets gives language to negotiate with pre-registered metrics rather than charisma. If evidence is descriptive only, label it and fund the next test instead of scaling spend.
For deeper study on this unit's specialty, see ENT 403 (Startup Go-to-Market and Founder-Led Sales). ENT 301 integrates the full arc; electives provide textbook-depth units you can take after this core course.
Lesson exercise
28 minICP Scorecard and Pipeline Math
Deliverable
ICP scores, pipeline gap calc, ARR scenario, and expansion recommendation in your ENT 301 workbook.
Rubric
- • Scores use ≥10 pipeline and ≥14 priority rules
- • Commercial-heavy firms disqualified with reason
- • Pipeline gap 14 opps shown with check
- • Density rule cited before geography