Runway and Burn

Runway is the calendar on your decision rights

Runway (months of cash remaining at current net burn) is not an accounting trivia question. It is the boundary on which opportunities you may pursue without raising prices on desperation. RelayOps starts this lesson with ~$400k cash and ~$45k monthly net burn, roughly 8.9 months before revenue improvements or new capital.

Gross burn counts all cash outflows. Net burn subtracts cash inflows from customers and grants. Founders who quote gross burn to sound disciplined still run out of cash at the net number.

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 404 (Entrepreneurial Finance, SAFEs and Cap Tables) 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. Runway math forces sequencing: customer discovery, MVP, pilots, founder-led sales, then measured scale.

Runway formulas and scenario bands

Base runway months = cash balance / net monthly burn. RelayOps: $400,000 / $45,000 ≈ 8.9 months. Check: 400,000 / 45,000 ≈ 8.9 ✓

Scenario bands beat false precision. Base case holds burn flat. Downside adds one hire and slower sales (+$12k burn, −$8k revenue). Upside models three logos per quarter accelerating collections.

Always state whether runway includes committed but unpaid invoices or excludes expected SAFE proceeds.

Burn composition and zero-revenue stress

Zero-revenue stress test: if pilots pause, net burn equals gross burn. RelayOps gross ~$45,000 per month. That is the maximum decision latency before payroll risk.

Founders should pre-negotiate burn levers: contractor pause, GTM freeze, founder salary deferral. Maya documents levers with trigger dates, not vibes.

Revenue timing and collection lag

B2B annual prepay improves runway; monthly billing with net-30 terms delays cash. RelayOps offers annual prepay with 10% discount to improve cash, trading margin for runway months.

Deferred revenue is a liability, not cash heroism. Bridge MRR growth to cash collected.

Example: December ARR adds $12k MRR but cash lands January if net-30. Cash forecast must lag MRR bridge by terms column per logo.

Runway gates for strategic decisions

RelayOps decision gates: below 6 months runway, freeze discretionary hires; below 4 months, activate SAFE marketing or bridge; below 3 months, cut semi-fixed GTM and renegotiate contracts.

Gates should be written when calm. Investors respect founders who already modeled cuts.

Document gate triggers in board consent agenda so new directors inherit discipline rather than renegotiating under stress.

Connecting runway to milestone plans

Each month of runway should map to a milestone: pilot renewal rate, dispatch median, founder hours per logo, CAC payback cohort. Unmapped runway is hope.

ENT 404 models post-seed runway after $1.8M SAFE closes; ENT 301 keeps pre-seed discipline visible.

Cash buffer policy and fundraising timing

Experienced founders raise before runway crisis. RelayOps targets closing SAFE with at least 5 months cash remaining to avoid distressed terms. Buffer policy: minimum 3 months operating cash post-close after planned hires.

Bridge financing (short-term capital before a larger round) often signals avoidable planning failure. If used, document maturity, conversion terms, and impact on cap table before signing.

Weekly cash standup: CEO reviews 13-week cash forecast with actuals variance over $2,000 explained. Jordan reviews deferred infrastructure spend that could spike burn.

Starting cash $400,000. Base net burn $45,000 months 1-3. Month 4: SAFE $1,800,000 closes. Post-raise burn $57,000 with two hires. Revenue ramps $8k MRR month 2 to $55k MRR month 12.

Part A: Pre-raise months 1-3

Month 1 ending cash: $400,000 − $45,000 + $8,000 revenue = $363,000.

Month 2: $363,000 − $45,000 + $12,000 = $330,000.

Month 3: $330,000 − $45,000 + $18,000 = $303,000.

Check: three-month cash decline $97,000 before raise ✓

Part B: Post-raise month 4

Cash in: SAFE $1,800,000. Month 4 net: $303,000 + $1,800,000 − $57,000 + $22,000 MRR = $2,068,000.

Post-raise runway at $57,000 net burn with flat revenue: $2,068,000 / $57,000 ≈ 36.3 months. Check: 2,068,000 / 57,000 ≈ 36.3 ✓

Part C: Milestone tie

Target ARR $3,200,000 by month 18 requires ~$267k MRR. At $28 per technician, ~9,530 active technicians or ~106 logos at 90 tech average.

Runway without ARR milestone is idle capital; milestone without runway is fantasy.

Part D: Managerial read

Investor question: "Why not run leaner and extend pre-raise runway?" Answer: beachhead competitors move; delay risks losing pilot references. Raise maps to falsifiable ARR and retention gates, not vanity spend.

DispatchNow reported 14 months runway using gross burn and including $500k LOI (letter of intent, non-binding interest) as cash. Net burn was 11 months; LOI never converted. RelayOps excludes non-binding pipeline from cash forecasts.

RelayOps holds $320,000 cash. Net burn $48,000. Expected month-end collections $14,000. A $25,000 annual prepay lands next month. Compute runway in months (a) ignoring prepay, (b) including prepay in month-one cash. Show checks.

Solution

(a) Effective month-one net burn ≈ $48,000 − $14,000 = $34,000. Runway ≈ $320,000 / $34,000 ≈ 9.4 months. Check: 320,000 / 34,000 ≈ 9.41 ✓

(b) Month-one cash after collections and prepay: $320,000 − $34,000 + $25,000 = $311,000 if prepay arrives end of month. Runway ≈ $311,000 / $34,000 ≈ 9.1 months then. Prepay helps level but does not change structural burn. Check ✓

Name two RelayOps burn levers Maya can pull at the 6-month gate.

Solution

Pause contractor expansion and freeze discretionary conference spend. Secondary: defer founder salary top-up and reduce paid pilot discounts.

Key takeaways

• Runway equals cash divided by net burn, not gross burn.
• Scenario bands expose downside hiring and upside revenue timing.
• Pre-write cut triggers at 6, 4, and 3 months runway.
• SAFE proceeds reset runway only after close, not at term sheet.
• Each runway month should map to a measurable milestone.

1. Draft a three-scenario runway table for RelayOps through month 12.
2. List your venture's burn levers with dollar amounts.
3. Continue to Lesson 3: Bootstrapping versus External Capital.

Applying Runway and Burn at RelayOps

When RelayOps applies runway and burn, 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 startup finance, runway, and fundraising instruments 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 runway and burn 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 runway and burn. 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 startup finance, runway, and fundraising instruments 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. Runway and Burn 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 404 (Entrepreneurial Finance, SAFEs and Cap Tables). 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 runway and burn, 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 runway and burn 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 runway and burn 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. Runway and Burn is how teams convert stories into capital-efficient learning.

Applying Runway and Burn at RelayOps

When RelayOps applies runway and burn, 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 startup finance, runway, and fundraising instruments 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 runway and burn 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 runway and burn. 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 startup finance, runway, and fundraising instruments 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. Runway and Burn 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 404 (Entrepreneurial Finance, SAFEs and Cap Tables). 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 runway and burn, 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 runway and burn 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 runway and burn 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. Runway and Burn is how teams convert stories into capital-efficient learning.

Applying Runway and Burn at RelayOps

When RelayOps applies runway and burn, 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 startup finance, runway, and fundraising instruments 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 runway and burn 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 runway and burn. 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 startup finance, runway, and fundraising instruments 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. Runway and Burn 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 404 (Entrepreneurial Finance, SAFEs and Cap Tables). 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 runway and burn, 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.