Demand Signals and False Positives

Demand signals lie politely; your job is to classify them

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.

Founders celebrate weak signals because fundraising culture rewards motion. Demand signals range from vanity (booth scans) to decision-grade (renewed paid pilots). False positives occur when social approval masquerades as budget commitment. RelayOps classifies every signal before Jordan expands the roadmap or Maya adjusts pricing.

ENT 401 evidence synthesis warns that enthusiasm, LOIs, and demo applause outperform shadows in founder memory because they feel like progress. This lesson builds a signal taxonomy tied to RelayOps's path from $89-$149 stated WTP to $33,600 ACV contracts.

With $400,000 runway, mistaking a false positive for demand burns a quarter. RelayOps treats signal classification as weekly hygiene alongside assumption updates.

Signal strength hierarchy

Strongest signals: multi-quarter paid contracts, pilot renewals at target price, daily active usage on core workflow. Mid signals: refundable deposits, signed pilot SOW with metrics, intro to economic buyer. Weak signals: verbal "I'd buy," LinkedIn likes, conference badge scans, non-binding LOIs without metrics.

RelayOps maps each signal to evidence level from Lesson 1. Promotion to MVP requires at least two independent mid signals across roles, not one strong friendship.

RelayOps demand signal taxonomy:

LOIs, pilots, and contracts are not interchangeable

An LOI (letter of intent, non-binding interest document) signals intent, not obligation. RelayOps requires LOIs to include success metrics, timeline, and economic buyer signature to rise above weak.

Paid pilots with kill criteria are stronger than enterprise LOIs without deployment. HeatRoute's 12 LOIs and 2 active pilots (ENT 402 contrast) illustrate LOI inflation.

Contracts require procurement paths. Mid-market owner-signed SOWs under $10k/month often bypass lengthy procurement; know your threshold.

Revealed versus stated preference

Stated preference is what people say in interviews. Revealed preference is what they do when time and money move. RelayOps stated WTP band $89-$149/tech is level 3 until deposit or SOW.

Discounted pilots reveal revealed preference only if price still supports unit economics. $49/tech pilots teach wrong anchors.

Shadow behavior (dispatcher still on whiteboard after interview praise) is negative revealed preference.

False positive patterns in B2B ops software

Pattern 1: Champion loves product; dispatcher never interviewed. Pattern 2: Owner wants digital transformation slide; COO not engaged. Pattern 3: IT says integration easy; security review later takes 120 days. Pattern 4: Summer pain remembered in winter interview; budget frozen.

RelayOps runs signal triangulation: any high signal must appear across role, artifact, and time (repeat mention in second interview).

Using kill criteria on weak demand

Demand kill criteria: if <3 paid pilots signed within 90 days of validation start at ≥$80/tech, pause MVP scaling and revisit wedge. If LOI-to-pilot conversion <25%, stop counting LOIs in investor updates.

Kill criteria protect against narrative capture by one enthusiastic logo.

Desert Cool (92 technicians) provides mixed signals: dispatcher loves interview, COO absent, owner offers LOI without metrics, later agrees to $5,000 deposit.

Part A: Signal classification

Part B: Triangulation actions

Require COO interview before SOW. Tie deposit to published pilot metrics (median dispatch time, usage %). Price pilot $99/tech × 92 = $9,108/month within WTP band.

Check: 92 × 99 = 9,108 ✓

Part C: Decision

Count Desert Cool as qualified lead, not closed demand. MVP gate opens only after COO signs SOW or owner budget email confirming $9k/month pilot line.

Part D: Managerial read

Do not put Desert Cool in "5 customers" slide. Put in "2 deposits, 1 COO pending, triangulation in progress."

HeatRoute reported "12 LOIs." Only 2 converted to active pilots; 0 renewed. RelayOps investor updates separate LOIs, paid pilots, and renewals with conversion ratios.

Pipeline: 8 LOIs, 2 deposits, 1 paid pilot at $49/tech, dispatcher DAU (daily active users, unique users per day) 40% on emergency queue.

Tasks: (1) Classify strongest and weakest signals. (2) Compute monthly pilot revenue at 100 techs for $49 vs $99 price. (3) Recommend one pipeline hygiene rule.

Solution

(1) Strongest: paid pilot usage with DAU (if COO engaged). Weakest: LOIs without deposits. $49 pilot teaches bad price anchor.

(2) $49: 100 × 49 = $4,900/month. $99: $9,900/month. Delta $5,000/month.

(3) Rule: no LOI counts in updates without metrics + economic buyer; minimum pilot price $80/tech.

Check: 100 × 99 = 9,900 ✓

Key takeaways

• Classify demand signals by strength and evidence level.
• LOIs are weak unless paired with metrics and buyers.
• Revealed preference requires money, time, or usage.
• Triangulate across roles and repeated time windows.
• Publish conversion ratios, not vanity pipeline counts.

1. Audit a fictional pipeline with signal taxonomy.
2. What is RelayOps demand kill criterion on pilot count?
3. Continue to Lesson 5: From Insight to Opportunity Thesis.

Applying Demand Signals and False Positives at RelayOps

When RelayOps applies demand signals and false positives, 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 demand signals and false positives 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 demand signals and false positives. 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. Demand Signals and False Positives 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 demand signals and false positives, 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 demand signals and false positives 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 demand signals and false positives 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. Demand Signals and False Positives is how teams convert stories into capital-efficient learning.

Applying Demand Signals and False Positives at RelayOps

When RelayOps applies demand signals and false positives, 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 demand signals and false positives 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 demand signals and false positives. 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. Demand Signals and False Positives 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 demand signals and false positives, 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.