Related guide summary
Runway is often described as a simple division problem: cash on hand divided by monthly burn. That formula is fine as a starting point, but it becomes dangerously misleading when the inputs are optimistic, incomplete, or detached from planned hiring and revenue timing.
The real job of runway planning is not to produce a single dramatic number for a board slide. It is to understand how much decision room the company has under multiple operating paths and what assumptions would force a financing, hiring freeze, or change in pace.
A credible runway estimate should survive stress. If it only works when revenue ramps perfectly, collections arrive on time, and every hire lands late, then you do not have runway. You have a hopeful spreadsheet.
Use net burn, but know what sits underneath it
Net burn should reflect the recurring cash the business actually consumes after collections, not just a high-level expense total. Payroll, contractor spend, infrastructure, software, sales tools, founder draws, taxes, and one-off obligations can all distort the picture if you exclude them selectively.
Revenue assumptions need the same discipline. Bookings are not cash, pipeline is not revenue, and revenue is not necessarily collections. A runway model built on optimistic invoice timing can overstate survival by months.
A simple rule helps here: if a line item will hit cash with high probability, include it. If a revenue line depends on unclosed deals or untested retention, haircut it until you can defend it.
Model hiring before you commit to it
Many founders calculate runway using current burn and then discuss hiring as if it is a separate future decision. In practice, planned hires are part of the runway question. The moment you consider adding headcount, your burn profile changes and the cash timeline should move with it.
This is why runway should be built as a month-by-month operating path, not just a static average. Adding three hires in month two is different from adding them in month six. The same is true for office commitments, vendor contracts, or marketing ramp plans.
Good runway models let you see the trade-off directly: how many months of cash you give up in exchange for faster product, sales, or support capacity.
Run three scenarios, not one
An honest runway model usually needs at least a base case, a downside case, and a managed case. The base case is what you think happens if the business performs as expected. The downside case assumes slower sales, weaker collections, or delayed product outcomes. The managed case shows what runway looks like if you actively cut or delay spend when the business misses plan.
This matters because the company rarely runs out of cash without warning. Most teams see leading indicators of stress earlier. A scenario model helps you decide which levers to pull before the situation becomes urgent.
The goal is not prediction precision. It is decision readiness. A runway estimate becomes useful when it tells you what to do if reality is worse than the headline plan.
Runway is a governance tool, not just a finance metric
The best founders use runway to create timing discipline. When does the company need to start fundraising if the downside case starts unfolding? What milestone must be reached before approving the next senior hire? At what point does a pricing change become necessary rather than optional?
Thinking this way makes runway operational. It connects cash life to product, sales, hiring, and fundraising decisions rather than leaving it isolated in a finance tab.
If your runway number cannot tell you when to change behavior, it is incomplete. The math may be correct, but the management system is not.
Example: a founder hiring two months too early
EXAMPLE: A startup has Rs. 4,000,000 in the bank, Rs. 350,000 in monthly revenue, and Rs. 700,000 in monthly expenses. The simple runway number is about 11.4 months because net burn is Rs. 350,000. If the team hires two people at a combined fully loaded cost of Rs. 300,000 per month, net burn nearly doubles and runway drops to about 6.2 months.
That change may still be correct if the hires unlock revenue quickly. The mistake is treating the hiring decision as free because the company still has cash today. Runway planning should show the month when the new cost begins, the delay before revenue arrives, and the downside case if the revenue does not arrive.
Use the calculator twice: once with the team exactly as it is today, and once with every planned hire, vendor, and tool added on the month it will actually start. The gap between those two results is the governance conversation the founder needs to have before signing offer letters.
Common questions
Should runway be based on current bank balance or committed cash?
Use cash that is truly available to operate the business. Signed but unfunded capital or soft verbal commitments should not be treated as cash on hand.
How often should founders update runway?
At minimum monthly, and usually more often when hiring, collections, or fundraising timing is uncertain.
Is gross burn enough for investor reporting?
Gross burn is useful, but investors also care about net burn because it reflects how quickly cash is actually leaving after revenue and collections.