Customer Segments and Jobs to Be Done: Case Analysis and Recommendations

Case analysis turns patterns into a segment strategy memo

Unit 2 began with definitions, moved to field practice, and examined trade-offs. This lesson integrates those threads into a segment strategy memo you could hand to a co-founder, product lead, or seed investor. The memo specifies who RelayOps serves first, which job is in scope, what evidence supports the choice, and what changes would falsify the strategy.

RelayOps builds dispatch and scheduling software for mid-market field-service companies. By end of Unit 2, founders have 32 interviews, 11 shadows, and pilot interest from four Segment A firms. Your task is to read like an operator: weigh evidence, name risks, and recommend segment and job focus for the next 90 days.

Case facts: RelayOps discovery snapshot (Week 10)

Qualitative pattern: Segment A stories cluster on heat-week absenteeism triggers. Commercial-heavy stories cluster on multi-day chain breaks (different job).

Competitive note: Incumbent scheduling module cited in 19/22 Segment A accounts; complaints focus on slow reroute and skill visibility, not missing maps.

Analytical sequence: from facts to recommendation

Step 1: Validate segment inclusion rules. 22 interviews; 3 miscounted as A but were 240+ tech → adjusted n=19 true A.

Step 2: Recalculate pain rate. 15/19 = 79% top-three pain. Exceeds 40% Gate 1 threshold. ✓

Step 3: Compare jobs within A. Same-day rebalance mentioned unprompted in 14/19; next-day routing in 9/19 but ranked lower severity.

Step 4: Trade-off check. Pursuing commercial chain job would drop pain alignment and lengthen sales cycle (Unit 2 Lesson 3).

Step 5: Recommend core job + wedge for pilot. Same-day skill-aware rebalance under 120 seconds core loop; CRM read integration phase 1.

Step 6: Define falsifiers. If pilot adoption <50% dispatcher daily active use at week 6, revisit job definition before segment expansion.

Segment strategy memo outline

Executive summary: One paragraph decision.

Beachhead definition: Inclusion, exclusion, anti-segment.

Primary job statement: JTBD format with situation.

Evidence: Quant tables + three verbatims.

Trade-offs accepted: Even-over statements.

90-day plan: Interviews, shadows, pilot customers, metrics.

Risks and mitigations: Pre-mortem items with tests.

Expansion optionality: Phase 2 segment triggers.

RelayOps memo headline: "Dominate same-day rebalance for 80-200 tech residential-heavy HVAC/plumbing in Sun Belt metros before adjacent expansion."

Recommendations for product, go-to-market, and hiring

Product: Build rebalance loop + minimal overtime dashboard; defer next-day optimizer and Spanish UI unless pilot shows language blocker >30% of users.

Go-to-market: Association webinars, founder outbound to ops leaders, reference pilot in Phoenix; no national enterprise conference spend in Q4.

Hiring: First engineering hire must ship integration + mobile loop; no data science hire until post-pilot signal.

Customer success: Pilot playbook capped at 6 weeks implementation; refuse custom ERP projects outside scope.

Link forward to Unit 3 (interviews)

Unit 3 deepens how to run discovery conversations now that who and which job are set. Interview guides will test falsifiers listed in this memo (integration time, dispatcher adoption, COO budget trigger).

Part A: Executive summary

RelayOps will focus exclusively on Segment A firms (80-200 technicians, residential-heavy HVAC/plumbing) and the same-day rebalance job under absenteeism and demand spikes. Evidence from 19 qualified interviews shows 79% top-three pain and consistent overtime spend. Three LOIs support a Q4 pilot. Commercial-heavy and electrical permit segments remain deferred explore with monthly caps.

Part B: Primary job statement

When same-day demand spikes and absenteeism hits before noon, operations leaders must reassign skill-matched technicians without breaking arrival promises, so they avoid overtime premiums and SLA penalties while maintaining crew utilization above target.

Part C: 90-day metrics

Check: targets align with Unit 1 gates ✓

Part D: Board questions answered

Why not bilingual UI first? Sync pain frequency higher; language friction subset manageable with dispatcher champions bilingual.

Why Phoenix first? Network density + heat spikes maximize learning events per calendar week.

Writing falsifiers that connect to instruments

A falsifier is useless if no instrument measures it. RelayOps segment memo falsifier: "If pilot dispatcher daily active use below 50% at week 6, revisit job definition." Instrument: product analytics plus shadow spot-checks. Another falsifier: "If fewer than 60% qualified interviews cite same-day rebalance top three in Month 4, revisit beachhead." Instrument: coded interview tags.

Falsifiers should name owners and dates. Owner Maya, date Month 4 review, prevents orphan conditions. Segment strategy without dated falsifiers becomes marketing narrative.

Presenting segment recommendations to skeptical stakeholders

Skeptical stakeholders include lead investors, industry advisors, and early engineers who fear narrow TAM. RelayOps presentation sequence: (1) show qualified denominator recalculation, (2) show job story side-by-side with deferred segment, (3) show even-over statements, (4) show expansion phase gates with triggers, (5) show falsifiers.

Resist opening with TAM circles. Open with Tuesday job story and overtime PDF artifact. Operators trust operators; investors trust discipline. RelayOps Phoenix-first recommendation cites 180-firm metro SAM and reference density math, not national ambition.

Engineers need wedge clarity: same-day rebalance under 120 seconds, not "scheduling platform." Segment case memos include non-goals list to reduce fear of endless scope.

Part A: Three falsifiers

Part B: Month 3 status

F1: 62% (pass). F2: 79% (pass). F3: 112s prototype median (pass).

Part C: Action

Maintain beachhead; widen upper tech bound conditional on second 230-tech shadow.

Part D: Managerial read

Falsifier drill prevents vague "pilot feels good" meetings. Check: all falsifiers have instruments ✓

Month 5: pain rate holds but DAU is 48% week 6 in two pilots.

1. Which falsifier triggered?
2. List three diagnostic interviews or shadows before changing segment.
3. Could segment be right while job definition is wrong? Explain.
4. Write executive summary sentence if job revision needed.

Solution

1. F1 triggered (DAU <50%).

2. Diagnostics: shadow with phone peak simulation; dispatcher job story on paper workaround; COO interview on adoption incentives.

3. Yes: segment fit may hold while job executor loop misses paper+phone parallel workflow (I2b mechanism).

4. Summary: "Segment A remains beachhead; revise job success metric to beat paper+phone baseline during phone peaks, not CRM tabs alone."

Check: falsifier triggers job refinement not automatic segment pivot ✓

Competitive complaints as wedge definition

Incumbent scheduling complaints in 19/22 Segment A accounts define wedge language: slow reroute, weak skill visibility, not missing maps. Case memos must cite competitive workarounds or incumbents look invincible.

Wedge refinement from complaints: RelayOps emphasizes skill-aware mobile rebalance under two minutes integrated to board dispatchers already use.

Hiring implications in segment memos

Segment choice drives hiring profiles. RelayOps first engineering hire: integration + mobile loop experience, not ML researcher. First AE: industry network in HVAC/plumbing, not generic SaaS hunter. Memos without hiring implications leave HR guessing.

Memo version control

RelayOps treats memo version control 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, memo version control 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 memo version control, ventures default to activity metrics (meetings held) instead of learning metrics (assumptions supported or falsified).

Pilot selection criteria

RelayOps uses pilot selection criteria 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.

Pilot selection criteria 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 pilot selection criteria 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.

New data arrives: 2 of 3 pilot LOI firms are 220-240 technicians (slightly above beachhead). Pain stories still match Segment A job.

1. Recalculate whether to widen beachhead upper bound to 250 technicians.
2. Write inclusion rule change (if any) in one sentence.
3. Identify one risk of widening versus staying strict.
4. Update even-over statement for product scope.

Solution

1. Analysis: 220-240 firms show same job stories; integration load moderate; 2 LOIs valuable. Widen upper bound if shadows confirm identical workflow (not yet: only 1 shadow at 230-tech firm).

2. Rule: "Include HVAC/plumbing firms up to 250 technicians when ≥60% residential same-day mix and dispatcher workflow matches Segment A shadow template."

3. Risk: Services timeline stretch and enterprise feature requests increase; Gate 2 integration assumption stressed.

4. Even-over: "RelayOps will preserve 6-week implementation cap even over accepting 250-tech accounts that demand custom ERP work."

Conditional widen after second shadow match. ✓

Key takeaways

• Segment strategy memos convert discovery data into 90-day focus.
• Recalculate rates with qualified denominators only.
• One core job and wedge per pilot phase.
• RelayOps doubles down on Segment A same-day rebalance with explicit falsifiers.
• Unit 3 interview design tests the risks named in this memo.

1. Draft a one-page segment strategy memo for RelayOps or your venture using the outline.
2. List three falsifiers that would force you to revisit beachhead or job choice.
3. Return to the unit page for the Unit 2 knowledge quiz, then begin Unit 3: Interview Design and Field Research.