From Insight to Opportunity Thesis

Insights become capital decisions when written as a thesis

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 401 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. This lesson closes Unit 1 and sets the gate for business model and MVP work in Unit 2.

Scattered interview notes do not fund the next $90,000 build sprint. An opportunity thesis is a one- to three-page document that states segment, job, evidence, economics, assumptions, kill criteria, and next experiment. ENT 401 validation decisions unit treats the thesis as a board-grade artifact; RelayOps uses it to decide whether to enter ENT 402-style MVP work.

The thesis is not a pitch deck. It is an internal decision memo Maya and Jordan sign, with dissent noted. Investors read the thesis to see if founders distinguish evidence from hope.

RelayOps thesis target after Unit 1: 80-200 technician residential-heavy HVAC/plumbing in Phoenix and Dallas; job is same-day rebalance under live call load; ACV path $33,600; top risk A3 adoption; gate to MVP requires three paid pilot SOWs or equivalent deposits with COO engagement.

Thesis components and evidence appendix

Required sections: problem frame, beachhead segment, job story, evidence summary with levels, market attractiveness score, unit economics preview, assumption ledger top five, demand signals with conversion, kill criteria, next 90-day plan.

Evidence appendix holds anonymized quotes, overtime tables, shadow timers, IT review durations. Appendix beats slide superlatives.

RelayOps opportunity thesis outline:

Synthesis methods: affinity, frequency, outliers

Affinity clustering groups codes into themes (tool fragmentation, overtime). Frequency ranks themes by prevalence. Outlier analysis examines divergent accounts: why did two firms report low pain? Outliers may be segment mismatches or different workflows.

RelayOps outliers often are commercial-heavy firms outside beachhead; screener tightens.

Dissent and pre-mortems

Strong theses document dissent. Jordan may dissent that mobile web is insufficient; Maya may dissent that integration can wait. Dissent forces explicit bets.

Pre-mortem: imagine MVP failed at month 6; list causes. Top pre-mortem items become monitor metrics in thesis.

Gate decisions: persevere, pivot, pause

Persevere to MVP when gate criteria met and kill criteria not triggered. Pivot changes segment, job, or wedge while preserving learning. Pause stops burn when evidence fails.

RelayOps pause triggers: COO hook <30%, A3 RAT kill, zero paid pilots by day 90 validation.

Gate is binary for spending; learning can continue cheaply after pause.

Handoff to Unit 2 and ENT 402

Thesis hands to business model design and MVP scope. ENT 402 picks up assumption A3 with emergency queue MVP, kill criteria on usage and dispatch time.

Thesis version number updates when definitions change (e.g., activation metric). Version discipline prevents comparing incompatible cohorts later.

Week 12 validation summary: 22 dispatcher interviews, 11 COO, 7 IT; 3 paid pilot deposits; 1 signed SOW at $99/tech for 88 techs; A3 RAT 72% task completion; scorecard 56.

Part A: Evidence summary

P1 loop >10 min: 18/22 (82%). COO overtime hook: 7/11 (64%). IT review median 68 days. WTP stated median $102/tech. Paid pilots: 1 SOW + 2 deposits = 3 firms.

Part B: Economics check

SOW firm: 88 × $99 × 12 = $104,544 ACV.

Target blended ACV near $33,600 requires smaller firms or lower price; adjust SOM plan: 12 logos year-1 at ~$40k ACV weighted.

Check: 88 × 99 × 12 = 104,544 ✓

Part C: Gate decision

Kill criteria not triggered. Gate criteria met (3 paid commitments, COO hook >30%, A3 RAT pass). Persevere to Unit 2 MVP with emergency queue scope. Dissent logged: Jordan wants mobile app in v1; deferred per assumption rank.

Part D: Managerial read

Angel read: thesis shows level-labeled evidence, conversion ratios, and explicit dissent. Weak read: "customers love us." Strong read: "3/11 COOs signed or deposited; dispatcher code saturation at 22 interviews; A3 RAT 72%; proceed under published kill criteria."

CoolFlow (fictional) raised on 18-slide deck with TAM and logos. No assumption ledger, no kill criteria. When pilots failed, founders debated anecdotes for months. RelayOps thesis prevents ambiguous postmortems.

Validation results: 8/20 COO hooks, 2 paid pilots, A3 RAT 58% completion, scorecard 54.

Tasks: (1) Evaluate kill triggers (hook <30%, A3 <60%, pilots <3). (2) Recommend persevere, pivot, or pause. (3) If pivot, name one element to change.

Solution

(1) Hook 40% no kill; A3 58% triggers kill; pilots 2 triggers demand kill.

(2) Pause MVP build; continue cheap RAT redesign and COO recruiting. Do not persevere on partial evidence.

(3) Pivot wedge test: schedule optimization only if emergency RAT fails twice; or tighten segment to 100-150 tech firms with higher pain scores.

Check: A3 58% < 60% kill threshold ✓

Key takeaways

• Opportunity thesis converts insights into signed decision memos.
• Include evidence appendix with levels, not only narrative.
• Document dissent and pre-mortem causes explicitly.
• Gate criteria are numeric; persevere, pivot, or pause accordingly.
• Version the thesis as metrics and definitions evolve.

1. Draft a one-page thesis outline for RelayOps with gate criteria.
2. What dissent would you log between CEO and CTO on mobile scope?
3. Continue to Unit 2, Lesson 1: Designing the Business Model.

Applying From Insight to Opportunity Thesis at RelayOps

When RelayOps applies from insight to opportunity thesis, 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 customer validation and interview evidence 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 from insight to opportunity thesis 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 from insight to opportunity thesis. 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 customer validation and interview evidence 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. From Insight to Opportunity Thesis 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 401. 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 from insight to opportunity thesis, 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 from insight to opportunity thesis 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 from insight to opportunity thesis 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. From Insight to Opportunity Thesis is how teams convert stories into capital-efficient learning.

Applying From Insight to Opportunity Thesis at RelayOps

When RelayOps applies from insight to opportunity thesis, 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 customer validation and interview evidence 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 from insight to opportunity thesis 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 from insight to opportunity thesis. 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 customer validation and interview evidence 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. From Insight to Opportunity Thesis 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 401. 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 from insight to opportunity thesis, 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.