Product-Market Fit

Product-market fit is a pattern in behavior and economics, not a feeling

Product-market fit (PMF, the condition where a defined segment repeatedly buys, uses, and retains a product that solves an urgent job) is one of the most abused phrases in startups. Founders claim PMF after three friendly pilots; investors deny PMF when NRR (net revenue retention, revenue from existing customers including expansion minus churn) is still noisy. RelayOps needs disciplined signals before scaling founder-led sales into a hired team.

PMF is segment-specific. RelayOps may have fit with 90-technician Phoenix residential HVAC firms while failing with 150-technician commercial-only operators. Maya Chen must name the segment in every fit claim.

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 402 (Product-Market Fit and Startup Experimentation) 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 402 Unit 3 dives into PMF measurement, cohort retention, and Sean Ellis survey methodology. ENT 301 teaches the integrated threshold: when RelayOps graduates from experiment mode to repeatable GTM in Unit 4.

This lesson covers qualitative and quantitative PMF signals, the Sean Ellis test, retention and expansion patterns, and false positives that trap dispatch software companies.

Sean Ellis test and qualitative pull

The Sean Ellis test asks active users: "How would you feel if you could no longer use this product?" with choices very disappointed, somewhat disappointed, not disappointed. A common PMF heuristic: 40% or more very disappointed responses among qualified active users suggests strong fit for that segment.

Qualified users matter. Surveying IT admins who never dispatch underestimates pull. RelayOps surveys dispatch managers and lead dispatchers who ran at least 10 emergency jobs through the system in the past 14 days.

Qualitative pull includes unprompted referrals, customers asking for faster rollout to additional branches, and champions defending usage when owners grumble about change. Maya logs pull quotes in the CRM next to usage charts.

Quantitative PMF signals for B2B SaaS

RelayOps tracks logo retention after pilot, gross revenue retention (revenue kept from existing customers excluding expansion), net revenue retention with seat expansion, weekly active dispatchers per logo, and emergency job throughput versus baseline dispatch time.

Early PMF pattern for RelayOps: three Phoenix logos renew without discounting, median dispatch time improvement holds into month 4, seat count grows with seasonal hiring, support tickets per logo fall after week 6.

Vanity PMF: founder friendships, LOI (letter of intent, non-binding interest) without usage, and press mentions. HeatRoute Dispatch (contrast case) had five LOIs and one active dispatcher.

RelayOps PMF signal dashboard (illustrative thresholds):

Cohort retention and expansion

PMF shows up in cohort curves: logo-month retention should flatten, not cliff after pilot. RelayOps plots MRR by signup cohort for Phoenix beachhead. Expansion revenue appears when firms add technicians in summer without sales-heavy discounting.

If retention cliffs at month 3 when summer ends, fit may be seasonal pain only. Maya tests whether overtime savings persist in shoulder season before claiming year-round fit.

NRR above 100% with small logo count can mislead; one customer's seat expansion skews aggregates. Report medians and logo-level stories alongside averages.

False PMF positives in operations software

False positives include: owner-mandated usage that collapses when mandate lifts; discounted pilots that renew only with 50% off; single champion doing all data entry while peers bypass; integration projects that stall daily usage.

RelayOps runs spot checks: dispatcher interviews without managers present, timestamp audits, and renewal conversations that ask what happens if price returns to list.

PMF claims without segment label are another false positive. National fit narrative from three Phoenix firms is premature.

Graduation criteria to Unit 4 GTM scale

ENT 301 uses PMF graduation triggers before Unit 4 tactics accelerate: at least three renewed beachhead logos, Sean Ellis at or above 35% with path to 40%, payback under 12 months on founder-led CAC, and documented ICP (ideal customer profile, description of accounts that win fastest) attributes shared with ENT 403.

Without graduation, hiring SDRs (sales development representatives, outbound prospecting reps) burns cash into a leaky bucket. Maya should not delegate founder-led sales until fit signals stabilize across logos, not one hero account.

Jordan's product roadmap after PMF shifts from RAT features to retention features: reliability, audit exports, and dispatcher UX speed, not new wedges.

Desert Cool, SunLine, and Valley Pro complete 90-day pilots. Maya compiles PMF evidence for seed investors.

Part A: Signal table

VD = very disappointed.

Part B: Interpretation

Emerging PMF, not strong: two of three renewals (67%), one near Sean Ellis threshold, one failure with low usage. Segment pattern: residential-heavy firms with owner mandate and champion dispatcher succeed; Valley Pro's commercial mix and split dispatch centers failed adoption.

PMF is partial and segment-bound. Do not claim universal fit.

Part C: Next actions

Tighten ICP: 80-110 tech residential-heavy, single dispatch center. Delay Dallas until Valley Pro loss autopsy finishes. Run Sean Ellis only on qualified active dispatchers. Target fourth logo before hiring first AE (account executive, quota-carrying salesperson).

Check: 2/3 renewal = 67% ✓; Desert Cool meets usage ≥ 75% ✓.

Part D: Managerial read

Investor question "Do you have PMF?" answer: "We have emerging fit in a defined Phoenix ICP with two full-price renewals; we are not scaling geography until Sean Ellis and usage hold on logo four."

HeatRoute Dispatch announced PMF with five LOIs and one live dispatcher. Revenue was 90% services. RelayOps treats LOIs as exploratory demand, not fit, until paid usage and renewal data arrive.

Managerial read: bind fit claims to behavior and cash, not signatures.

RelayOps has 4 beachhead logos: A renews 100 techs at $99, B renews 60 techs at $89 (50% discount), C churns at pilot end, D expands 70 to 85 techs at $99. Founder-led CAC averaged $17,000. Gross margin 80%.

Tasks: (1) Compute year-one MRR after renewals. (2) Compute blended payback using total MRR and total CAC for renewed logos only. (3) State whether PMF graduation is met with one sentence citing two criteria from this lesson.

Solution

Renewed MRR: A 100×$99=$9,900; B 60×$89=$5,340; D 85×$99=$8,415; total=$23,655 MRR.

Renewed logos CAC: 3×$17,000=$51,000. Monthly GP: 23,655×0.80=$18,924. Payback: 51,000/18,924≈2.69 months.

Graduation not fully met: revenue retention emerging but only two of four logos healthy at list price; Sean Ellis and fourth-logo repeatability still required. Check: 9,900+5,340+8,415=23,655 ✓; 51,000/18,924≈2.69 ✓.

Key takeaways

• PMF is segment-specific behavior plus economics, not founder conviction.
• Sean Ellis and usage metrics complement renewal and expansion data.
• False positives include mandated usage, discounts, and LOI theater.
• RelayOps graduates to scaled GTM only after repeatable beachhead renewals.
• ENT 402 provides deeper cohort and instrumentation playbooks for PMF measurement.

1. Design a Sean Ellis survey screen for RelayOps dispatch managers with qualification rules.
2. List three false PMF signals you have seen in B2B software and how to falsify them.
3. Continue to Pivot, Persevere, or Stop: decision discipline when signals conflict.

Applying Product-Market Fit at RelayOps

When RelayOps applies product-market fit, 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 business models, MVPs, and experimentation 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 product-market fit 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 product-market fit. 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 business models, MVPs, and experimentation 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. Product-Market Fit 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 402 (Product-Market Fit and Startup Experimentation). 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 product-market fit, 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 product-market fit 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 product-market fit 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. Product-Market Fit is how teams convert stories into capital-efficient learning.

Applying Product-Market Fit at RelayOps

When RelayOps applies product-market fit, 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 business models, MVPs, and experimentation 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 product-market fit 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 product-market fit. 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 business models, MVPs, and experimentation 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. Product-Market Fit 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 402 (Product-Market Fit and Startup Experimentation). 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 product-market fit, 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 product-market fit 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 product-market fit 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. Product-Market Fit is how teams convert stories into capital-efficient learning.

Applying Product-Market Fit at RelayOps

When RelayOps applies product-market fit, 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 business models, MVPs, and experimentation 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 product-market fit 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 product-market fit. 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 business models, MVPs, and experimentation 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. Product-Market Fit 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 402 (Product-Market Fit and Startup Experimentation). ENT 301 integrates the full arc; electives provide textbook-depth units you can take after this core course.