The Business Context for Market Sizing and Opportunity Attractiveness

Market size answers "is this worth a company?" not "is this true?"

Customer discovery proves pain in a segment. Market sizing asks whether that segment can support a venture return profile, a corporate investment hurdle, or a multi-year roadmap. Opportunity attractiveness adds competition, timing, and execution fit. Investors use sizing to sanity-check ambition; operators use it to prioritize metros and verticals.

RelayOps targets 80-200 technician residential-heavy HVAC/plumbing firms with dispatch rebalance software. This lesson frames why sizing matters after discovery, what TAM (total addressable market, revenue if you won 100% of a category*), SAM (serviceable addressable market, revenue you could serve with your model*), and SOM (serviceable obtainable market, realistic share in a planning horizon*) mean for early B2B SaaS, and how honesty beats hype.

Why size after discovery, not before

Sizing before discovery produces fantasy spreadsheets. Sizing after discovery anchors on:

• Beachhead definition from Unit 2
• Price hypothesis from synthesis (Unit 4 Core ~$2,800/month)
• Sales motion assumptions (inside sales, 75-day cycle)
• Churn and expansion expectations from pilots

RelayOps order: problem evidence → segment → price → size. Reversing the order invites TAM theater.

Attractiveness is more than dollars

Attractive markets can be small but winnable (tight vertical SaaS) or large but frozen (regulated oligopolies). RelayOps pursues mid-size SAM with reachable founders network.

Who uses sizing outputs

CEOs set expansion sequencing (Phoenix before Boston).

CFOs model cash needs versus SOM ramp.

Investors compare SOM to return requirements.

Product avoids features for segments outside SAM.

Honest communication

RelayOps investor slide shows TAM/SAM/SOM with assumptions footnoted, not a single $50B circle. Lenders and boards respect ranges and sensitivity, not false precision.

Link to validation decisions (Unit 6)

Sizing feeds continue / pivot / kill at seed stage. If SOM at realistic share cannot support $10M ARR (annual recurring revenue, subscription revenue recognized yearly*) in 7 years, either expand segment definition with evidence or accept lifestyle business outcomes.

Part A: Beachhead economics inputs

Part B: Attractiveness snapshot

Competition: incumbent suites strong but scheduling wedge weak (I2). Growth: field service labor shortage increases overtime cost pressure. Fit: founder network dense in Sun Belt.

Part C: Strategic question

"Can RelayOps reach $15M ARR on beachhead SAM in 7 years?" Unit 5 Lesson 2 quantifies.

Part D: Managerial read

Do not expand TAM to all field service before proving SOM in Segment A metros.

Check: inputs tied to discovery ✓

Metro-level sizing and operator planning

National SAM impresses; metro SAM wins. RelayOps operators plan Phoenix (180 firms) and Dallas (165 firms) before Boston expansion. Metro sizing includes drive-time for services, reference density, and association presence.

Metro models answer: "Can two AEs support 22 logos in 36 months here?" If not, SOM in that metro is fantasy. Unit 5 Lesson 2 quantifies; Lesson 1 frames why operators need metro discipline.

Timing sizing with fundraising narrative

Sizing supports fundraising narrative only when tied to milestones investors can audit. RelayOps seed story: "$85M adjusted SAM, $8M year-5 SOM base, proven by 40 logos month 18." Each number links to discovery evidence and sales capacity assumptions.

Timing matters: sizing before price evidence invites skepticism. RelayOps waited until Core pricing ~$2,800/month stabilized from Unit 4 synthesis before locking SAM revenue math.

Part A: Dallas inputs

165 Segment A firms; founder network 12 ops leaders; 0 references today.

Part B: 3-year SOM

20 logos feasible with 2 AEs at 10 deals/year each after Phoenix references.

Part C: Entry trigger

Enter when Phoenix ≥3 references and services playbook <30 hrs/logo.

Part D: Managerial read

Dallas sequenced after Phoenix density; national ads deferred. Check: 20 logos × $33.6k = $672k ARR ✓

Advisor uses $18B TAM; RelayOps bottom-up SAM $141M.

1. Three board objections to advisor framing?
2. Honest one-sentence size statement?
3. Attractiveness dimension beyond dollars for RelayOps?
4. Month 18 falsifier tied to SOM?

Solution

1. Objections: wrong denominator; ignores beachhead; hides competition and cycle capacity.

2. Statement: "SAM is ~$141M for our wedge in Segment A; we plan $8M year-5 ARR via 220 logos, not 0.1% of unrelated TAM."

**3. Buyer urgency on overtime during labor shortage.

4. Falsifier: <25 logos month 18 triggers SOM path review.

Check: sizing linked to operating proof ✓

Lender versus investor sizing emphasis

Lenders care cash coverage and payback; investors care SOM and multiple. RelayOps CFO one-pager emphasizes payback sensitivity for lender conversation; deck emphasizes SAM defensibility for equity.

Same underlying model, different emphasis paragraphs.

Expansion sequencing and brand

Winning Phoenix before Dallas builds reference brand in tight community. Sizing context lesson ties metro order to word-of-mouth coefficient, not vanity geographic ambition.

Sizing after pricing lock

RelayOps treats sizing after pricing lock as operational discipline for mid-market HVAC and plumbing dispatch discovery, not a one-time workshop topic. Founders document decisions in the opportunity decision memo and segment strategy memo so Maya Chen and Jordan Okonkwo align daily calendar choices with beachhead rules.

In practice, sizing after pricing lock connects to measurable leading indicators: qualified interviews, shadow medians, assumption register statuses, and pilot telemetry. When indicators diverge from thesis language, the team runs a forcing function review within five business days rather than waiting for quarter-end board meetings.

Corporate innovation teams can mirror the same discipline: name owners, dates, falsifiers, and budget hooks before scaling a discovery squad. Without sizing after pricing lock, ventures default to activity metrics (meetings held) instead of learning metrics (assumptions supported or falsified).

Operator metro cadence

RelayOps uses operator metro cadence in weekly synthesis and monthly validation committee reviews. Customer success, sales, and engineering read the same RelayOps anchor facts: Segment A 80-250 technician residential-heavy HVAC and plumbing, same-day rebalance job, Core pricing near $2,800 per month, COO overtime trigger near 8 percent.

Operator metro cadence prevents drift after competitive shocks such as ServiceSuite QuickReroute. Advantage pillar narratives update while Problem and Segment pillars remain stable unless new evidence crosses kill thresholds written in Unit 1 and Unit 6.

Operators should be able to explain operator metro cadence to a dispatcher, a COO, and a seed investor without changing the core claim. That tri-audience test is the ENT 401 standard for applied validation work.

Part A: Baseline

Beachhead Segment A; 9 paid logos Month 9; cold OT -4%; warm OT -9%.

Part B: Intervention

Apply lesson concept to cold cohort playbook for next 30 days.

Part C: Expected movement

Cold OT toward -7%; DAU toward 68%; services toward 28 hours per logo.

Part D: Managerial read

Link intervention to validation pillar grades. Check: metrics named ✓

RelayOps cold pipeline 22 opportunities; 6 in contract; IT median 52 days.

1. Name two leading indicators for next 30 days.
2. Which Unit 3 assumption register rows move?
3. Write one falsifier sentence.
4. Continue, pivot, or kill if cold OT stays -4% at Day 90?

Solution

1. Cold OT median and IT median days on new pipeline. 2. A2 adoption and A3 integration rows. 3. If cold OT median above -4% at Day 90 with ritual shipped, pivot packaging or segment narrow. 4. Conditional continue until Day 90; pivot if falsifier hits.

Check: falsifier linked to pillar ✓

RelayOps applied review: connecting this lesson to validation

Every ENT 401 lesson supports the same Month 9 validation decision for RelayOps, the B2B SaaS dispatch and scheduling venture serving mid-market HVAC and plumbing firms with 80 to 250 technicians. Maya Chen and Jordan Okonkwo founded RelayOps after operating dispatch at Summit Climate. Their beachhead job is same-day crew rebalance under absenteeism and demand spikes, sold to COOs on overtime reduction near an 8 percent trigger, with Core pricing near $2,800 per month and CRM read integration in phase one.

This subsection ties lesson concepts to pillars investors grade: Problem, Segment, Solution, Economics, Market, and Advantage. Problem and Segment stay strong when qualified operations leaders rank rebalance pain in top three weekly pains and spend on overtime or scheduling modules. Solution weakens when cold cohort dispatcher daily active use sits near 63 percent while warm cohorts reach 76 percent. Economics weakens when customer acquisition cost payback stretches past 20 months and services hours per logo exceed 28. Advantage weakens when ServiceSuite QuickReroute bundles free reroute features that narrow speed-based differentiation.

Operators should translate every abstract framework in this lesson into calendar events, owners, and falsifiers. Founders should write what would change their mind before the next board meeting. Investors should ask for cold cohort tables, not blended averages. Learners should practice explaining RelayOps decisions to three audiences without changing the underlying evidence chain from Units 1 through 6.

Corporate innovators can map the same structure: opportunity memo, segment rules, interview instruments, insight portfolio, sizing brief, validation scorecard. The vocabulary changes by industry; the sequence does not. Selection before segmentation, segmentation before instrument design, instruments before synthesis, synthesis before sizing honesty, sizing before continue or pivot or kill.

Managerial stakes when this lesson is misunderstood

Teams that skip this lesson's discipline usually show predictable failure signatures within two quarters. Sales promises outrun evidence. Engineering builds features no economic buyer funds. Services teams drown in custom integration work. Marketing speaks at category level while dispatchers live at Tuesday morning chaos level. Finance models heroic TAM instead of obtainable SOM tied to account executive productivity.

RelayOps guards against those signatures with written memos, assumption registers, insight portfolios, and Month 12 thresholds. A lesson is not academic when it prevents a $195,000 monthly burn company from raising seed extension on warm cohort fiction. A lesson is not academic when it helps a corporate squad kill an innovation theater project before a seven-figure build.

Re-read the worked examples and practice problems with this validation lens. Each exercise should produce a decision, an owner, and a metric. If an answer only restates theory, revise until a RelayOps operator could execute it Monday morning in Phoenix or Dallas metros where reference density strategy concentrates learning and word-of-mouth among HVAC and plumbing operations leaders.

Study integration checklist for ENT 401 learners

Before moving to the next lesson, confirm you can: (1) state RelayOps beachhead in one sentence with inclusion and exclusion rules; (2) name the core job in situation-motivation-outcome form; (3) cite at least one falsifier with an instrument; (4) identify which validation pillar your lesson topic affects most; (5) describe what warm versus cold cohort split would do to your conclusion if ignored.

If any item is difficult, return to the worked example and practice problem sections. ENT 401 is cumulative by design. Unit 5 sizing fails when Unit 2 segment definition is vague. Unit 6 validation fails when Unit 3 assumption thresholds are missing. Unit 4 synthesis fails when Unit 1 evidence strength hierarchy is ignored.

RelayOps remains the anchor venture so you can see those links across 24 lessons without resetting context. The depth bar from the lesson authoring guide requires prose that teaches, not bullets that index. This integration subsection is intentionally repetitive on anchor facts because repetition builds fluency beginners need before running real discovery programs.

RelayOps applied review: connecting this lesson to validation

Every ENT 401 lesson supports the same Month 9 validation decision for RelayOps, the B2B SaaS dispatch and scheduling venture serving mid-market HVAC and plumbing firms with 80 to 250 technicians. Maya Chen and Jordan Okonkwo founded RelayOps after operating dispatch at Summit Climate. Their beachhead job is same-day crew rebalance under absenteeism and demand spikes, sold to COOs on overtime reduction near an 8 percent trigger, with Core pricing near $2,800 per month and CRM read integration in phase one.

This subsection ties lesson concepts to pillars investors grade: Problem, Segment, Solution, Economics, Market, and Advantage. Problem and Segment stay strong when qualified operations leaders rank rebalance pain in top three weekly pains and spend on overtime or scheduling modules. Solution weakens when cold cohort dispatcher daily active use sits near 63 percent while warm cohorts reach 76 percent. Economics weakens when customer acquisition cost payback stretches past 20 months and services hours per logo exceed 28. Advantage weakens when ServiceSuite QuickReroute bundles free reroute features that narrow speed-based differentiation.

Operators should translate every abstract framework in this lesson into calendar events, owners, and falsifiers. Founders should write what would change their mind before the next board meeting. Investors should ask for cold cohort tables, not blended averages. Learners should practice explaining RelayOps decisions to three audiences without changing the underlying evidence chain from Units 1 through 6.

Corporate innovators can map the same structure: opportunity memo, segment rules, interview instruments, insight portfolio, sizing brief, validation scorecard. The vocabulary changes by industry; the sequence does not. Selection before segmentation, segmentation before instrument design, instruments before synthesis, synthesis before sizing honesty, sizing before continue or pivot or kill.

Managerial stakes when this lesson is misunderstood

Teams that skip this lesson's discipline usually show predictable failure signatures within two quarters. Sales promises outrun evidence. Engineering builds features no economic buyer funds. Services teams drown in custom integration work. Marketing speaks at category level while dispatchers live at Tuesday morning chaos level. Finance models heroic TAM instead of obtainable SOM tied to account executive productivity.

RelayOps guards against those signatures with written memos, assumption registers, insight portfolios, and Month 12 thresholds. A lesson is not academic when it prevents a $195,000 monthly burn company from raising seed extension on warm cohort fiction. A lesson is not academic when it helps a corporate squad kill an innovation theater project before a seven-figure build.

Re-read the worked examples and practice problems with this validation lens. Each exercise should produce a decision, an owner, and a metric. If an answer only restates theory, revise until a RelayOps operator could execute it Monday morning in Phoenix or Dallas metros where reference density strategy concentrates learning and word-of-mouth among HVAC and plumbing operations leaders.

Study integration checklist for ENT 401 learners

Before moving to the next lesson, confirm you can: (1) state RelayOps beachhead in one sentence with inclusion and exclusion rules; (2) name the core job in situation-motivation-outcome form; (3) cite at least one falsifier with an instrument; (4) identify which validation pillar your lesson topic affects most; (5) describe what warm versus cold cohort split would do to your conclusion if ignored.

If any item is difficult, return to the worked example and practice problem sections. ENT 401 is cumulative by design. Unit 5 sizing fails when Unit 2 segment definition is vague. Unit 6 validation fails when Unit 3 assumption thresholds are missing. Unit 4 synthesis fails when Unit 1 evidence strength hierarchy is ignored.

RelayOps remains the anchor venture so you can see those links across 24 lessons without resetting context. The depth bar from the lesson authoring guide requires prose that teaches, not bullets that index. This integration subsection is intentionally repetitive on anchor facts because repetition builds fluency beginners need before running real discovery programs.

RelayOps advisor says "US field service software is $18B TAM; you need 0.1% to win." List three problems with this statement for RelayOps board. Rewrite one sentence framing size honestly.

Solution

Problems: (1) TAM not filtered to beachhead segment or wedge; (2) 0.1% of wrong denominator meaningless; (3) ignores competition and sales cycle capacity.

Rewrite: "RelayOps SAM is mid-market HVAC/plumbing dispatch wedge in US, roughly $140M at our ACV; we model $8M SOM in 5 years by winning 240 accounts in priority metros."

Key takeaways

• Size markets after beachhead and price evidence exist.
• TAM/SAM/SOM serve different decisions; do not collapse them.
• Attractiveness includes competition, urgency, and execution fit.
• RelayOps sizes wedge in Segment A, not all field service software.
• Honest ranges beat heroic TAM circles.

1. List your beachhead inputs needed before any spreadsheet (segment, ACV, cycle).
2. Name two attractiveness dimensions beyond revenue dollars.
3. Continue to Lesson 2: Tools and Techniques for Market Sizing and Opportunity Attractiveness.