Pivot, Persevere, or Stop

Startups die from drift more often than from decisive stops

Every experiment ends with a forced choice: persevere (stay the course with defined iteration), pivot (change one strategic element while keeping learning), or stop (wind down the hypothesis and redeploy capital). RelayOps cannot afford a fourth zombie pilot that consumes Maya's calendar without moving the assumption map.

Pivot is not failure theater. A pivot changes customer segment, wedge job, channel, or revenue model while preserving useful assets. Jordan's SMS infrastructure and dispatch audit log might survive a pivot from emergency speed to compliance documentation if data shows owners buy audit trails when speed gains stall.

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 emphasizes kill criteria and gate reviews. ENT 301 places those gates in the full venture arc: what RelayOps tells investors, employees, and pilot customers when evidence conflicts.

This lesson teaches decision gates, pivot types, stop rules, and communication when Phoenix evidence is mixed.

Decision gates and kill criteria

Decision gates are calendar checkpoints with pre-registered choices. RelayOps Gate 1 (pilot week 4): if emergency usage below 60%, stop new feature work and run dispatcher interviews. Gate 2 (week 8): if median dispatch time above 7 minutes, pivot wedge or stop pilot. Gate 3 (month 6): if fewer than two renewals among three pilots, pivot ICP or stop geographic expansion.

Kill criteria protect runway and morale. They are not pessimism; they are pre-commitment devices. Maya shares kill criteria with owners before signatures so exits are mutual, not ambush.

Teams drift when gates lack owners. Maya owns commercial gates; Jordan owns reliability gates; both sign the gate memo.

Pivot typology for RelayOps

Common pivot types: zoom-in pivot (one feature becomes the product; emergency queue only), customer segment pivot (residential HVAC to plumbing only), channel pivot (founder-led to association-partner referrals), revenue pivot (per-tech to per-dispatch-center pricing), technology pivot (voice intake instead of web console).

RelayOps should change one major element per pivot, not five. If Valley Pro failed on adoption, try plumbing single-center firms before abandoning dispatch software entirely.

Preserve assets: customer relationships, glossary, pilot SOW templates, and SMS delivery code survive most pivots.

Persevere with bounded iteration

Persevere is valid when kill criteria are not triggered and the next iteration has a new falsifiable hypothesis. SunLine at 68% usage might persevere with champion clinic, not AI routing.

Bounded iteration means time-box and metric-box. "Improve onboarding" is not bounded. "Raise live entry from 68% to 75% in 10 days via shadowing" is bounded.

Persevere becomes drift when the same failing tactic repeats without new learning. Third onboarding webinar without usage lift should trigger pivot conversation.

Stop rules and capital redeployment

Stop when kill criteria fire twice on the same hypothesis after good-faith iteration, when payback exceeds 18 months at beachhead with no retention improvement, or when founders lose authentic advantage in the segment.

Stopping a hypothesis is not shutting the company unless the core thesis is falsified. RelayOps might stop Dallas expansion while persevering in Phoenix.

Redeploy capital: Maya's time returns to ICP interviews; Jordan's time returns to reliability debt; remaining runway funds the next RAT.

Communicating pivot, persevere, or stop

Customers need clarity: what changes in scope, price, support, and timeline. Investors need honesty: which assumption failed, what asset remains, what next test costs.

Employees need a single narrative. "We are iterating onboarding" differs from "We are pivoting wedge to audit trail value."

Document decisions in a decision log: date, choice, evidence, dissent, review date. ENT 406 scaling lessons return to this discipline at larger headcount.

Week 8: SunLine usage 71% (above kill), median dispatch time 7.4 minutes (above 7 minute gate), 3 dispatcher complaints about SMS delays in basements.

Part A: Options scored

Kill on time not triggered for usage; time gate breached.

Part B: Decision

Persevere 14 days with SMS failover vendor and basement retry logic; parallel message audit trail savings to owner. If median time still above 7 minutes at day 14, pivot messaging to compliance and dispatch accountability while keeping emergency module.

Not stop: usage proves desirability; failure mode is feasibility.

Part C: Customer comms

Email to SunLine owner: "We hit usage targets; dispatch time missed by 0.4 minutes primarily on basement SMS. We are swapping gateways with a 14-day checkpoint. If unresolved, we will shift ROI story to audit and overtime documentation you requested."

Check: 7.4 > 7.0 gate ✓; 71% > 60% kill ✓.

Part D: Managerial read

Investors should hear which gate fired and which assumption class is in play. Mixed signals are normal; undisciplined response is optional.

CoolFlow Dispatch extended a failing Dallas pilot nine months without gate memos, calling it "almost there." Engineers left; the owner churned angry. One documented Gate 2 pivot on messaging or stop would have saved $400,000. RelayOps uses written gates to avoid affection for sunk costs.

Managerial read: love the learning, not the pilot logo.

Valley Pro churned (41% usage). Desert Cool and SunLine renewed. Dallas expansion waitlist has 6 firms; 2 resemble Valley Pro commercial mix, 4 resemble Desert Cool. Runway 7 months at $45,000 burn. Maya wants Dallas now; Jordan wants plumbing-only ICP test in Phoenix.

Tasks: (1) Recommend persevere, pivot, or stop for Dallas timing. (2) State one gate metric for the recommended path. (3) Write two-sentence investor update.

Solution

Recommend pivot timing: delay Dallas 60 days; persevere Phoenix while running plumbing-only ICP sprint (bounded 30-day interview plus one pilot). Dallas expansion stop for commercial-mix lookalikes until gate passes.

Gate metric: fourth logo renewal at ≥70% emergency usage and median dispatch ≤5.5 minutes before spending travel CAC in Dallas.

Investor update: "Phoenix shows emerging PMF in residential-heavy ICP with two renewals; Valley Pro loss narrowed our segment filter. We deferred Dallas two months to close logo four and test plumbing beachhead rather than scale mixed evidence." Check: runway 7×45k=$315k remaining ✓.

Key takeaways

• Gates and kill criteria force persevere, pivot, or stop before drift sets in.
• Change one strategic element per pivot and preserve reusable assets.
• Persevere requires bounded iteration with new falsifiers, not hope.
• Stop hypotheses and geographies independently when evidence supports.
• Communicate decisions to customers, investors, and team with explicit assumptions.

1. Write three decision gates for RelayOps's next 90 days with owners and metrics.
2. Draft a professional pilot exit email when kill criteria fire.
3. Continue to Unit 4 Go-to-Market: beachhead markets and ICP precision.

Applying Pivot, Persevere, or Stop at RelayOps

When RelayOps applies pivot, persevere, or stop, 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 pivot, persevere, or stop 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 pivot, persevere, or stop. 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. Pivot, Persevere, or Stop 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 pivot, persevere, or stop, 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 pivot, persevere, or stop 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 pivot, persevere, or stop 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. Pivot, Persevere, or Stop is how teams convert stories into capital-efficient learning.

Applying Pivot, Persevere, or Stop at RelayOps

When RelayOps applies pivot, persevere, or stop, 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 pivot, persevere, or stop 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 pivot, persevere, or stop. 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. Pivot, Persevere, or Stop 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 pivot, persevere, or stop, 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 pivot, persevere, or stop 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 pivot, persevere, or stop 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. Pivot, Persevere, or Stop is how teams convert stories into capital-efficient learning.

Applying Pivot, Persevere, or Stop at RelayOps

When RelayOps applies pivot, persevere, or stop, 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 pivot, persevere, or stop 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 pivot, persevere, or stop. 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. Pivot, Persevere, or Stop 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.