What Is Cash Runway?
Cash runway is the number of months a company can continue operating at its current net burn rate before running out of cash. The formula fits in one line:
Cash Runway (months) = Total Cash ÷ Monthly Net Burn
A company with $1.8M in cash and $220K monthly net burn has 8.2 months of runway. That single number dictates when to hire, when to fundraise, and when to reallocate capital before options disappear.
CFOs, finance operations managers, and founder-operators at companies burning between $100K and $2M a month rely on this metric more than any other. At high burn, they recalculate weekly. At low burn, monthly is enough. The number itself is not complicated. Getting it right is.
Most definitions stop here. They hand you the formula and move on. The real problem is that the inputs feeding the formula are stale, miscategorized, or flatly wrong in most operating environments. This guide covers the formula, a worked example, the five failure modes that break the number, and the weekly cadence that keeps it honest.
Table of Contents
Cash Runway vs Burn Rate
Cash runway and burn rate measure different things: burn rate is monthly net cash outflow, and runway is how long current liquidity lasts at that pace. One is a speed. The other is a distance.
| Metric | What It Answers |
|---|---|
| Burn Rate | How much cash do we spend (net of revenue) per month? |
| Cash Runway | How many months until cash hits zero at the current burn? |
| Unit | Dollars per month vs. months remaining |
| Action Trigger | Cut costs or grow revenue vs. fundraise, bridge, or restructure |
Burn rate is the input. Runway is the output. When burn changes, runway moves. A 15% spike in monthly burn from a single infrastructure contract can shave two months off your runway overnight. Reporting one without the other tells half the story.
Board decks that show burn rate alone let the audience feel comfortable without answering the only question that matters: how long do we have?
The Cash Runway Formula (With a Worked Example)
The cash runway formula is total cash divided by monthly net burn, expressed in months. The discipline is in what you feed it.
Cash Runway (months) = Total Cash ÷ Monthly Net Burn
Defining the Variables
Total Cash. Cash on hand plus near-cash equivalents such as money market funds and short-term treasuries. Accounts receivable is not cash. Until the payment clears the bank, it does not exist in the formula.
Monthly Net Burn. Gross monthly cash outflows minus gross monthly cash inflows. A positive number means cash is leaving the business faster than it arrives.
Cash Runway Example: Apex Ventures
Example. Apex Ventures has $1.8M in the bank. Gross monthly burn (payroll, rent, vendors, infrastructure) is $340K. Gross monthly revenue is $120K. Net monthly burn = $340K − $120K = $220K. Cash runway = $1.8M ÷ $220K = 8.2 months.
That 8.2-month figure tells Apex they need to begin fundraising conversations now, not in three months. A typical Series A process takes four to six months from first meeting to wire. Waiting until month five means negotiating from weakness.
Two Ways the Formula Gets Weaponized
The first mistake is using gross burn instead of net burn. Gross burn ignores inflows entirely, which inflates the resulting runway figure and makes the picture look safer than it is. If Apex used $340K gross burn instead of $220K net burn, the formula would show 5.3 months. The gap between 5.3 and 8.2 months is the difference between a bridge round and a fire sale.
The second mistake is using the last 30 days of burn instead of a trailing-3-month average. One quiet month of vendor payments produces a low burn that flatters the number. One heavy month of annual renewals crushes it. Neither is representative.
The formula is simple. The inputs are where the truth slips.
What Counts as a Good Cash Runway?
A good cash runway is at least 18 months for most venture-backed companies, adjusted for stage, burn volatility, and fundraising market conditions. In practice, the right number depends on three variables: your stage, your burn volatility, and how healthy the fundraising market is when your current cash runs out.
Stage. Pre-seed and seed companies need 18 to 24 months. The fundraise cycle is long and the revenue base is thin. Growth-stage companies target 12 to 18 months. Mature or profitable businesses do not use a fixed-month rule. Cash-flow positive is the target.
Burn volatility. Lumpy enterprise contracts create unpredictable inflow gaps that demand a longer buffer. Steady SaaS ARR with monthly billing allows a shorter buffer because inflows are more predictable.
Fundraising market health. In 2021, 12 months of runway was comfortable. By 2023, 18 to 24 months became the survivable floor.
CB Insights found that 70% of VC-backed startups that shut down since 2023 failed because they ran out of capital. Since 2023, the runway that kept you alive doubled. The companies that did not adjust did not survive. CB Insights, “Top Reasons Startups Fail” (March 2026).
Why Your Runway Number Is Wrong
Your runway number is wrong because the inputs are stale, miscategorized, or overstated. The reason is almost never the formula.
Stale data. The spreadsheet is 15 to 30 days behind the bank. Every number you cite in a board meeting is a month old. The decision you make with it belongs to a reality that has already moved on.
Manual mapping. A human categorizes every transaction. Humans miss, mis-tag, and overwrite. A $14K software renewal tagged as a one-time expense instead of recurring changes the burn rate. Nobody catches it until the quarterly close.
Phantom receivables. Invoices are treated as cash before they clear. The runway extends on paper. The bank balance does not move. A company with $400K in outstanding invoices and 90-day DSO is carrying four months of fictional cash in the model.
[Image: Finance team analyzing cash flow data in a meeting.]
Category drift. Last quarter’s “one-time expense” becomes this quarter’s recurring line. Burn rate creeps upward by 3% to 5% per quarter. Nobody flags the drift because each individual reclassification looks small. The operational cadence to catch these reclassifications, built around a cash runway ontology, is the gap most finance teams do not close.
Scenario blind spots. The board asks “what if revenue drops 20%?” The spreadsheet takes two days to answer. By then the question has moved to “what if we lose two enterprise accounts simultaneously?” The model never catches up to the conversation.
The runway number is downstream of the operating data. When the data is wrong, the runway is wrong. The only fix is live data, grounded in the operation.
How to Extend Your Cash Runway
You extend cash runway by reducing net burn and improving cash timing without breaking the revenue engine. Five levers move the number.
1. Accelerate Receivables
Collect faster. Offer a 2% early-pay discount on net-30 terms to shift cash forward by two to three weeks. For a company with $200K in monthly receivables, that discount costs $4K and pulls roughly $180K forward. The runway math almost always favors the trade.
2. Renegotiate Vendor Terms
Push payables from net-30 to net-60. Every 30 days of vendor float is 30 days of runway. Start with the three largest vendor contracts. Most vendors prefer extended terms to losing the account entirely.
3. Cut the Three Biggest Line Items, Not the Easiest Ones
Payroll, cloud infrastructure, and real estate are usually the top three. Cutting coffee perks and team lunches does not move the number. One renegotiated cloud contract or one floor of office space returned to the landlord creates months of additional runway.
4. Pause Non-Critical Hiring
One senior hire delayed by a quarter is a full month of runway recovered. Evaluate every open role against a single question: does this hire generate revenue or reduce burn within 90 days? If the answer is no, pause it.
5. Raise a Bridge, Not a Full Round
A bridge buys time at lower dilution than a full round raised from a position of weakness. A bridge round can restore the buffer while you rebuild the metrics a full round demands.
What does not work: across-the-board percentage cuts that demoralize everyone and save too little. Freezing marketing entirely breaks the pipeline that funds the next round. One-off asset sales dressed up as strategy buy a month and signal desperation to anyone watching.
How to Measure Cash Runway Accurately (What to Track Weekly)
You measure cash runway accurately by updating cash and burn inputs on a weekly cadence from bank-level sources, not month-end spreadsheets. Five inputs need weekly attention.
- Cash balance. Pulled from the bank API, not from the spreadsheet. The spreadsheet is a copy. The bank is the source.
- Trailing-3-month net burn. Not the last 30 days. Not a point estimate. The trailing average absorbs one-offs and seasonal swings.
- Projected 90-day cash flow. Updated weekly as invoices clear and expenses post. This is the forward view that the static formula cannot give you.
- Collections aging. Days sales outstanding by customer, not averaged across the book. One slow-paying enterprise account can distort the entire receivables picture.
- Runway sensitivity. How much the runway moves if net burn changes by ±10%. This single calculation prepares you for the board question before it lands.
The right cadence depends on where you sit. Weekly updates at high burn or below 12 months of runway. Bi-weekly at 12 to 18 months. Monthly at 18 months or above, or when the business is cash-flow positive.
A runway number updated quarterly is a historical artifact. A runway number updated weekly is a decision tool. This is the cadence a live cash flow ontology produces automatically.
How Truzer.ai Approaches Cash Runway
Truzer.ai approaches cash runway by recalculating it from live operating data mapped to an ontology, not from static spreadsheets and stale exports. Truzer.ai is a new entrant in this category, built on a different assumption than the legacy FP&A stack.
Most existing runway tools are spreadsheets or FP&A templates running on data that is 15 to 30 days stale. The forecasting layer guesses because it has no live connection to the operation. The AI is generating estimates, not operating on live transaction-level reality.
Truzer takes a different approach. It is built as a live digital twin of the business. Every bank transaction, invoice, expense, and contract maps to the ontology in real time. Cash runway recalculates the moment a transaction clears. Scenario modeling runs live against the ontology, not against a stale snapshot. When a board member asks “what if revenue drops 20%,” the answer surfaces in seconds. It is grounded in the same data the bank holds.
Deployment takes 48 hours from first connector to live control tower. Truzer connects to existing bank feeds, QuickBooks, Xero, NetSuite, SAP, Stripe, payroll systems, and operational data including Foundry-native deployment paths. No rip-and-replace. No six-month implementation.
Security is the first question, not a footnote. Truzer enforces AES-256 encryption at rest, TLS 1.3 in transit, scoped tokens with role-based access control, and isolated AI inference environments with zero external API calls. The AI is grounded in ontology, not in generic training data.Truzer is new. This guide does not pretend otherwise. The thesis is simple: runway accuracy depends on live operating data, and the ontology is the structure that keeps that data honest. See the cash flow ontology build itself live or explore the single control tower for the whole operation.
