Introduction
Ask a founder how much runway they have, and you’ll almost always get a confident number. Ask them to walk you through exactly how they got that number, and the confidence usually drops. Most runway estimates are built on a mental shortcut — “bank balance divided by roughly what we spend” — rather than an actual, itemized calculation.
This isn’t a criticism. Founders are busy, and a rough estimate feels good enough most of the time. The trouble is that “good enough” tends to fail exactly when it matters most — right when spending patterns shift, a big invoice lands, or a slow revenue month coincides with a planned hire. This article looks at where these mental shortcuts break down, and what a more dependable way of tracking runway actually looks like.
What Cash Runway Actually Measures
At its core, cash runway answers one question: if nothing changes, how many months until the bank account hits zero?
The formula is simple:
Runway (months) = Usable Cash ÷ Monthly Net Burn
The word doing the most work in that formula isn’t “runway” — it’s “usable.” Most founders plug in their full bank balance without asking whether all of that cash is actually free to spend, or whether some of it is already spoken for. That single gap is where a lot of runway estimates start going wrong.
The Blind Spots That Distort Runway Estimates
Blind Spot 1: Treating the Full Bank Balance as Usable
The habit: Checking the bank balance and using that number directly in the runway calculation.
Why it feels reasonable: The balance is right there, visible, and easy to check anytime.
What it misses: Payroll due in three days, a vendor invoice about to clear, taxes owed at quarter-end — none of this shows up as a separate line item in your account balance, but all of it reduces what’s actually available to spend going forward.
A better habit: Before calculating runway, subtract anything already committed to be paid in the next two to four weeks. What’s left is your actual usable cash.
Blind Spot 2: Using Last Quarter’s Average Spend, Not This Month’s Actual Spend
The habit: Calculating burn rate as an average over the last three or six months.
Why it feels reasonable: Averaging smooths out noise and feels statistically more “stable” than looking at one month in isolation.
What it misses: If your team just doubled in size, or you just signed a new annual software contract, your current spending is meaningfully different from your historical average — and that average is quietly hiding the shift.
A better habit: Use your most recent full month’s actual numbers as your primary reference point, and only use a longer average as a secondary check, not the main input.
Blind Spot 3: Counting Invoiced Revenue as Collected Revenue
The habit: Including revenue that’s been invoiced to customers, even if payment hasn’t actually arrived yet.
Why it feels reasonable: An invoice sent to a reliable customer feels like money that’s essentially already yours.
What it misses: Payment delays are common, especially with larger clients on 30, 60, or 90-day payment terms. Counting invoiced-but-uncollected revenue as available cash overstates your runway by exactly the amount that hasn’t arrived yet.
A better habit: Only count revenue that has actually hit your bank account when calculating net burn, not revenue that’s been billed but not yet received.
Blind Spot 4: Ignoring That Burn Rate Changes When Spending Changes Categories
The habit: Tracking one single “burn rate” number without noticing which category of spending is driving changes in it.
Why it feels reasonable: One number is easier to watch than several.
What it misses: A rising burn rate driven by hiring engineers to build a new feature is a very different situation from a rising burn rate driven by unplanned tool subscriptions piling up. The single number tells you burn is rising, but not why, which matters for deciding what to do about it.
A better habit: Break burn into two or three broad categories (people costs, tools and infrastructure, marketing/sales) so a shift in runway also tells you where it’s coming from.
Blind Spot 5: Assuming a Funding Round Will Close on Schedule
The habit: Calculating runway as if an in-progress funding round will definitely close by the expected date, and factoring that expected cash into planning.
Why it feels reasonable: After weeks of investor conversations and verbal interest, a round can feel close to certain.
What it misses: Funding rounds slip — sometimes by weeks, sometimes by months — for reasons entirely outside a founder’s control. A runway plan that assumes a round closes exactly on time has no buffer if it doesn’t.
A better habit: Calculate your “no-round” runway separately, based only on cash currently in hand, and treat any incoming funding as an upside, not a planning assumption.
Blind Spot 6: Checking Runway Only When Something Feels Off
The habit: Recalculating runway reactively, usually triggered by a moment of worry rather than a fixed schedule.
Why it feels reasonable: If things seem to be going fine, recalculating feels like unnecessary effort.
What it misses: By the time something “feels off” enough to trigger a recalculation, the situation has often already been deteriorating for a while unnoticed. Reactive checking catches problems late by design.
A better habit: Set a fixed monthly date, separate from how the business “feels” that month, to recalculate runway using actual numbers.
How to Build a More Reliable Runway Number
Step 1: Pull your actual bank balance today, not from memory or a rounded estimate.
Step 2: Subtract near-term committed payments — payroll, rent, upcoming vendor invoices — to get usable cash.
Step 3: Use last month’s actual net burn, calculated from real collected revenue minus real expenses, not invoiced revenue or historical averages.
Step 4: Break burn into two or three categories so you can see what’s driving any change.
Step 5: Calculate runway using only cash in hand, excluding any funding that hasn’t actually closed.
Step 6: Set a recurring monthly date to repeat this process, regardless of how the business feels that month.
A Practical Walkthrough
A ten-person startup checks its bank account and sees ₹45 lakh. Using the “obvious” method, and an average monthly burn of ₹6 lakh calculated over the last two quarters, the founder estimates 7.5 months of runway.
Digging deeper changes the picture. Payroll due in four days is ₹4 lakh, bringing usable cash down to ₹41 lakh. Last month’s actual spend was ₹7.5 lakh, not the six-month average of ₹6 lakh, because the team added two new hires recently. Of the ₹2 lakh in “revenue” counted that month, ₹50,000 was an invoice sent but not yet paid.
Recalculating with real numbers: usable cash of ₹41 lakh, actual net burn of ₹7.5 lakh minus ₹1.5 lakh in actually-collected revenue equals ₹6 lakh net burn, giving roughly 6.8 months of runway — close to the original estimate in this case, but for entirely different, more defensible reasons, and this method would have caught a much larger gap in a month with a bigger invoice delay or committed payment.
This example is illustrative only and uses simplified, hypothetical figures.
What Happens When These Blind Spots Go Unchecked
Consequence: A funding search starts later than it should. If runway looks longer than it actually is, fundraising outreach often starts too close to the actual cash-out date, leaving little room if the process takes longer than hoped.
Consequence: Hiring decisions get made against a number that isn’t real. A new hire that seems affordable based on an inflated runway estimate can quietly accelerate an actual cash problem that wasn’t visible in the original math.
Consequence: The team is blindsided by a sudden cash conversation. When runway has actually been shorter than believed for months, the moment this becomes clear often arrives suddenly and stressfully, rather than as a gradual, manageable realization.
A Quick Diagnostic Checklist
- Does your runway number subtract committed near-term payments, or just use the raw bank balance?
- Is your burn rate based on last month’s actual numbers, or an older average?
- Are you counting only collected revenue, not invoiced-but-unpaid amounts?
- Can you tell which spending category is driving any recent change in burn?
- Have you calculated runway assuming no new funding arrives, as a baseline?
- Do you recalculate this on a fixed schedule, regardless of how things feel that month?
Key Terms
- Usable Cash: Bank balance minus any payments already committed for the near term.
- Net Burn: Total cash spent minus cash actually collected (not invoiced) in a given period.
- Runway: The number of months a business can operate at its current burn rate before running out of cash.
- Committed Payment: Money already obligated to be paid soon — payroll, rent, a pending invoice — reducing what’s truly available.
- No-Round Runway: A runway estimate that assumes no new funding arrives, used as a conservative baseline.
- Spend Category: A grouping of expenses (people, tools, marketing) used to identify what’s actually driving a change in burn rate.
Frequently Asked Questions
1. Why isn’t my bank balance the same as my usable cash?
Because some of that balance is already committed to near-term payments like payroll or vendor invoices that haven’t cleared yet, even though they still show up in your account balance today.
2. Should I count revenue as soon as I send an invoice?
No — only count revenue once it’s actually been received in your account. Invoiced-but-unpaid revenue overstates your real cash position.
3. Is it safe to plan around an expected funding round closing on time?
It’s safer to calculate a separate “no-round” runway based only on cash you currently have, and treat any incoming funding as a buffer rather than a certainty.
4. Why does it matter which category of spending is driving my burn rate?
Because the right response differs — rising burn from strategic hiring is a different situation than rising burn from unplanned or forgotten subscriptions.
5. How often should I actually recalculate runway?
On a fixed monthly schedule, not only when something feels concerning — reactive checking tends to catch problems later than a regular schedule would.
6. Is using an average burn rate over several months a bad idea?
It’s useful as a secondary reference, but your most recent month’s actual numbers should be the primary input, especially after any recent change in team size or spending.
7. What’s the biggest single blind spot founders have with runway?
Treating the full bank balance as available cash without subtracting near-term committed payments first.
Conclusion
A runway number is only as reliable as the inputs behind it, and most of the danger isn’t in the math — it’s in what gets left out before the math even starts. Usable cash instead of raw balance, actual collected revenue instead of invoiced amounts, and a fixed recalculation schedule instead of a reactive one are what separate a runway estimate you can actually plan around from one that quietly falls apart the moment something changes.