The Runway Mistake That Almost Killed Our Company — And How We Fixed It

We had 14 months of runway. Or so we thought. The real number was closer to nine. By the time we figured that out, we had six weeks to either cut costs, close a bridge, or shut down. Here's what happened — and what we learned.

How We Got Our Runway Wrong

Our burn rate calculation was straightforward. Monthly expenses from our bank account, divided into cash on hand. Simple math. The problem was that our "monthly expenses" number was based on the last three months of spending — which happened to be unusually low. We'd paused two hiring processes, delayed a software renewal, and pushed a contractor invoice into the next quarter.

We weren't lying to ourselves intentionally. We just weren't accounting for the expenses that were coming, only the ones that had already hit.

By month four, three of those delayed costs landed at once. Our burn jumped from $62K to $94K overnight. Our 14-month runway became nine months, and we hadn't updated our investors or adjusted our hiring plan.

The Difference Between Cash and Runway

Cash in the bank is a number. Runway is a forecast. They are not the same thing, and treating them as equivalent is one of the most common and dangerous mistakes early-stage founders make.

Real runway accounts for committed expenses that haven't been invoiced yet. Hiring offers that have been accepted but haven't started. Software contracts with annual renewals coming up. Tax obligations. Payroll timing differences. Marketing spend that scales with revenue.

If your runway calculation doesn't include all of this, it's not a runway calculation. It's a bank balance dressed up as a forecast.

What Live Burn Tracking Actually Looks Like

After the near-miss, we moved everything into LEDGE. The first thing that changed was our burn rate stopped being a monthly calculation and became a daily one. Every transaction that hit our account updated the forecast automatically.

We set threshold alerts — if projected runway dropped below ten months, we got a notification. If monthly burn exceeded our budget by more than 8%, we got a notification. These weren't vanity metrics on a dashboard we checked once a week. They were active signals that changed how we made decisions.

Within the first month of using live burn tracking, we caught a vendor invoice that had been double-processed, a SaaS subscription we'd forgotten to cancel after switching tools, and a payroll timing error that would have overstated our expenses by $12K for the quarter.

How to Build a Runway Model That Actually Works

The starting point is separating fixed costs from variable costs and from one-time costs. Fixed costs are your baseline burn — salaries, rent, recurring software. Variable costs scale with your business — paid acquisition, contractor hours, hosting. One-time costs are everything else — equipment, legal fees, recruiting.

Layer in your committed future costs — offers accepted, contracts signed, renewals scheduled. Then build two scenarios: one at current growth, one at flat growth. The gap between those two scenarios is your strategic decision space.

Review this model every two weeks, not every month. Two weeks is short enough that you catch problems before they become crises. Monthly reviews mean you're always operating on information that's at least 30 days old.

Runway is the most important number in your company at every stage until you're profitable. Treat it accordingly.