Runway is cash on hand divided by net monthly burn: the time the company has left at its current spending. It is the central planning number of a pre-revenue company, and its honesty depends entirely on the burn figure used (net of reliably incoming cash, with one-offs normalized out) and on which future inflows the model dares to count.
The planning discipline runs on scenarios. A base case with committed cash only; a downside where the grant slips a quarter and the hire happens anyway; an extension case showing which costs could stop. The number that matters in each: where the cash-out date lands relative to the next milestone, because runway that ends 1 month after a key technical demonstration is not runway, it is a coin flip on an R&D schedule.
The raise timing rule follows directly: the next fundraise starts while runway still covers the full process, 12 months is the comfortable software threshold and 15 is safer on deep tech diligence timelines, less than 9 puts the company negotiating under visible pressure, and every investor can read a runway from a burn table as fast as the founder can. Extending runway is also not 1 lever but 3: cut burn, add non-dilutive money, or bridge; each has a cost, and the cheapest is usually the one decided earliest.
