Runway, the number of months a company can survive at its current burn, is one of the few metrics every founder claims to watch, and one of the most commonly miscalculated, because the simple version of the calculation assumes a smoothness that most young companies do not have. When you divide cash by average monthly burn you get a comforting number, and the comfort is often false, because it hides the fact that money does not actually arrive in the neat monthly increments the average implies. Revenue is lumpy, expenses are uneven, and a company that looks safe on the average can hit a cash crisis in a specific month that the average smoothed away. The founders who run out of money are frequently the ones whose spreadsheet said they were fine.
The deeper issue is that runway is not really about the average at all; it is about timing, the specific question of whether there is cash in the account on the specific day each obligation comes due. A company can be profitable over a year and still fail in a single month where a large payment goes out before a large payment comes in, and the annual average would never have warned you. Managing runway well means thinking about the shape of the cash over time, the peaks and troughs, rather than the smooth line the average draws, because it is the trough, not the average, that kills a company, and the trough is invisible to anyone looking only at the summary number.
Why the average lies
The average burn calculation is seductive because it produces a single clean number, and dangerous for exactly the same reason, because a single number cannot represent an uneven reality. Revenue that arrives in occasional lumps, a big contract, a milestone payment, a seasonal surge, looks the same in the average as revenue that arrives steadily, but the two are completely different for survival, because the lumpy version means long stretches with little coming in punctuated by moments of plenty, and it is the long stretches that have to be survived. A founder who plans against the average is planning against a reality that does not exist.
Expenses lie in the average too, because they are not uniform either: some obligations are large and periodic rather than smooth, and a month that happens to contain several of them can burn far more than the average suggests. Combine lumpy revenue with lumpy expenses and the actual month-to-month cash position swings widely around the comforting average, which means the real risk lives in the specific bad month where a trough in revenue coincides with a peak in expenses. That month is where companies die, and it is precisely the month the average was designed, unintentionally, to hide from you.
Plan against the timing, not just the amount
The correction is to stop managing runway as a single number and start managing it as a timeline, projecting the actual cash position month by month, or even week by week, so that the troughs become visible before you fall into them. This means mapping when money is genuinely expected to arrive, not when you hope it will, and when obligations genuinely come due, and looking at the balance at each point rather than the average across all of them. The projection reveals the dangerous months in advance, while there is still time to act, which is the entire value of doing it, because a cash crisis seen three months out is a manageable problem and the same crisis seen three days out is an emergency.
It is the trough, not the average, that kills a company, and the trough is invisible to anyone looking only at the summary number.
Seeing the troughs early changes what you can do about them, turning panic into planning. A founder who knows a difficult month is coming can pull in revenue ahead of it, defer expenses past it, arrange a buffer before it, or simply prepare, none of which is possible for a founder blindsided by a shortfall the average never flagged. The discipline of projecting cash over time rather than trusting the average is not sophisticated finance; it is basic survival for any company whose money does not arrive smoothly, which is to say most of them. The tools can be simple, but the shift from average to timeline is what actually protects the company.
Build the buffer the lumps require
The structural protection against lumpy cash is a buffer larger than a company with smooth revenue would need, because the buffer has to be big enough to carry the company through the longest trough it is likely to face, not just the average gap. Founders serving lumpy revenue who hold only a thin reserve are gambling that no bad month arrives before the next lump, and that gamble is lost often enough to end companies that were fundamentally sound. The buffer is not idle money; it is the thing that lets a viable business survive the timing mismatches that would otherwise kill it, and sizing it to the real shape of the cash rather than the average is what makes it adequate.
For founders in markets where payment timelines are long or unpredictable, and where large customers may pay slowly, this discipline matters even more, because the troughs are deeper and the lumps less controllable, which makes both the timeline projection and the buffer more essential rather than less. The whole approach comes down to refusing the false comfort of the average and managing the reality of the lumps: project the actual cash over time so the dangerous months are visible in advance, act on them while there is room to act, and hold a buffer sized to the real troughs rather than the smoothed line. The company that does this survives the lumpy period that sinks the one trusting a single reassuring number.