TL;DR
- Runway is the number of months a company can continue operating on its current cash balance before running out of money, calculated as cash on hand divided by monthly net burn.
- The formula is runway = cash balance ÷ monthly net burn, where net burn is gross cash outflow minus incoming revenue; using gross burn instead understates runway, sometimes by half.
- The venture convention is to raise before runway drops below 18–24 months, because a raise takes three to six months of diligence and the next year of runway is needed to demonstrate the milestones the round prices.
- Runway is only as reliable as the burn and revenue inputs feeding it, so subscription businesses should model it as a range across revenue scenarios, not a single point.
- A runway below 12 months concentrates every decision on survival: pricing, hiring, and spend all get re-ranked by the same deadline, which is exactly when revenue reliability becomes a funding question.
What Is Runway? — A Working Definition
Runway is the measure of how long a company can operate before its cash runs out, expressed in months. It is the survival metric of startup finance: the number that converts a cash balance and a monthly burn rate into a deadline the board can act on.
The concept is borrowed from aviation—runway is how much distance you have to take off or stop—and the metaphor holds. A startup has a finite amount of cash, burns a portion of it every month, and runway describes how many of those months remain before the cash position forces a decision: raise, cut, or change the business. Carta, Investopedia, and Brex all converge on the same definition, which makes runway one of the more stable concepts in startup finance.
Runway matters because it is the metric that forces prioritization. A company with twenty-four months of runway can afford to invest in product experiments and let growth compound; a company with eight months must re-rank every decision by the same deadline. The same business looks very different at different runway lengths, which is why investors ask about runway before they ask about almost anything else.
The definition hides a subtlety that determines whether the number is useful: runway is a forward-looking estimate, not a fact. It assumes the burn rate and revenue holding steady, when in reality both move every month. The discipline of runway management is not computing the number once—it is recomputing it on the same cadence as the cash statement, and building in the assumptions explicitly.
How to Calculate Runway: The Formula and the Input Choices
The formula is short: runway = cash balance ÷ monthly net burn. Cash balance is what sits in the bank today; monthly net burn is gross cash outflow minus incoming revenue. The quotient is the number of months the company can operate at current levels before the balance hits zero.
The input choices are where the calculation lives or dies. Net burn, not gross burn, is the convention for planning runway—gross burn ignores revenue entirely, so a company collecting meaningful monthly revenue gets a runway figure that is misleadingly short. Carta, Stripe, and Brex all use net burn for the planning number, with gross burn reserved for the stress-test: what happens if revenue stopped tomorrow.
A worked example makes the mechanics concrete. A company holds $2.0M in cash, spends $280K monthly across payroll, cloud, and marketing, and collects $180K in monthly subscription revenue. Net burn is $100K, and runway is 20 months. The same company quoting gross burn gets 7 months—a difference of more than a year, and the kind of error that changes whether a raise feels urgent.
Three rules keep the calculation honest. First, use cash-basis numbers, not accrual: a recognized but unpaid invoice is not cash on hand, and accrued expenses that have not cleared are not yet burn. Second, exclude one-time infusions—a new round, a grant, a large prepaid contract—from monthly revenue, or runway spikes for a month and collapses the month after. Third, recompute monthly, because runway decays with every operating month and the assumptions behind it drift faster than the cash balance does.
The 18–24 Month Rule: When Startups Should Raise
The venture convention holds that a startup should raise before runway drops below 18 to 24 months. The logic is structural rather than arbitrary: a raise takes three to six months of diligence and negotiation, and the next eight to twelve months of runway are needed to demonstrate the milestones the round actually prices. Raising at 18–24 months leaves enough air for both.
The two windows inside the rule are worth separating. The first is the transaction window: from the moment a term sheet conversation starts to the moment cash lands, three to six months typically pass, during which runway continues to burn. The second is the proof window: the next year of runway exists to show the metrics the next round will be priced on. A company that raises at twelve months of runway is already under time pressure; a company that raises at six is negotiating from weakness.
The rule is a guideline, not a law, and the exceptions explain the spirit. A company that has just raised and is executing on a clear plan can sit comfortably below 18 months temporarily. A company with strong growth and visible demand can raise faster than the average window. The underlying principle never changes: runway is the buffer that keeps negotiation leverage intact, and the board should never discover the buffer has vanished at the same moment it needs the leverage most.
The corollary is the 12-month red line. Below a year of runway, every decision—hiring, pricing, spend, even which bugs get fixed—gets re-ranked by the survival deadline, and the business starts trading future capability for present cash. Teams that plan to raise at 18 months and cut the burn at 12 have left the negotiation six months late; teams that start the raise conversation at 20 months keep the leverage.
Why Runway Must Be Modeled as a Range, Not a Point
A single runway number is an assumption wearing the costume of a fact. It assumes net burn holds steady, which it almost never does, and for subscription businesses the assumption is the most fragile one in the model: monthly revenue moves with renewals, expansions, downgrades, and payment failures, and each movement changes net burn without a single cost change.
The failure mechanism is familiar to any founder who has watched a "sixteen months of runway" slide age into a "nine months" reality by the next quarter. The reasons are rarely exotic. A cohort of customers fails to renew. A round of downgrades arrives. A spike in failed renewals—cards expired, soft declines unretried—converts booked MRR into involuntary churn, and the revenue side of the net burn equation shrinks while costs stay flat. Each effect is small in a single month; compounded over a quarter, they rewrite the runway.
The honest version of runway planning is a range across three scenarios. Model one where net burn holds at current levels, one where revenue grows at plan, and one where involuntary churn rises because renewal failures go unaddressed. The spread between the scenarios is the real risk the board should discuss, and the scenario that matters for the raise calendar is the conservative one, not the base case.
For subscription teams, the range discipline connects directly to payment reliability. Revenue that fails to collect is not just a booking problem—it is a runway problem, because it raises net burn without a single expense line changing. Teams that treat failed renewals as a revenue-leak problem rather than an accounting footnote will find their runway model stops surprising them, which is the actual point of the exercise.
Common Misconceptions About Runway
"Runway = cash ÷ gross burn." Using gross burn understates runway, sometimes by half, because it ignores incoming revenue entirely. The planning convention across Carta, Stripe, and Brex is net burn; gross burn is for stress-testing the worst case where revenue stops.
"Runway is a fixed number until you raise." It is a decaying estimate that moves with assumptions. Revenue composition, downgrades, and failed renewals all change net burn month to month, which is why runway should be modeled as a range and recomputed on the same cadence as the cash statement.
"More runway is always better." Excessively long runway can mean under-investment—capital sitting idle instead of converting into growth. The goal is enough runway to execute the plan and raise with leverage, typically 18–24 months, not the maximum possible duration.
"Runway matters only for startups burning cash." Any business with a cash cycle needs the concept, but it is most urgent for pre-profit companies where the cash balance is finite and the next funding event is a decision point. Profitable companies still monitor runway against expansion plans and market shocks.
How Runway Connects to Billing and Payment Infrastructure
Runway is a finance metric with an operational root, and for subscription businesses the root is revenue reliability. Every percentage point of recurring revenue that fails to collect is a permanent reduction in the monthly inflow side of the net burn equation, which means it is also a permanent reduction in runway—compounded across every future month.
This is the connection most runway explainers miss. When teams fix the inflow side—recovering failed renewals before they become involuntary churn, retrying soft declines on a backup path, keeping payment methods current—they extend runway without a single cost cut. The same causal chain that runs through burn rate runs through runway: failed collection → lower MRR → higher net burn → shorter runway. The mechanics of multi-path retry are covered in Clink's smart routing article; this glossary entry only needs the framing, that runway is as much a collection problem as a cost problem.
Teams evaluating infrastructure that unifies billing and payment routing should therefore ask a runway-focused question rather than a feature question: what happens to the model when renewal collection improves? Because subscription data and processor connections are separable in that architecture, retry policies apply consistently across markets, which makes the improvement auditable rather than anecdotal. Clink does not publish a public rate card as of June 2026; packaging is discussed through Contact Sales. For the cash-burn companion metric, see what is a burn rate; for the revenue base behind the model, see ARR meaning.
Conclusion
Runway is the survival metric that converts a cash balance and a monthly burn rate into a deadline the board can act on. The formula is simple—cash on hand divided by monthly net burn—and the discipline is in the inputs: net burn rather than gross, cash-basis rather than accrual, and a range of revenue scenarios rather than a single point.
For subscription businesses, the twist is that the revenue side of the equation is not static. Renewals, expansions, downgrades, and failed collections move net burn every month, which means runway is as much a collection problem as a cost problem. The 18–24 month raise convention exists because runway is the buffer that keeps negotiation leverage intact, and the teams that model it honestly—across scenarios, recomputed monthly, with revenue reliability treated as a runway variable—are the ones whose board decks survive contact with reality.