How to Calculate Runway in Excel

Excel is often the first tool founders reach for when calculating runway. It works for simple cases. Understanding where it stops working is equally important.

The basic formula approach

The simplest way to calculate runway in Excel is a single division. Place your cash balance in one cell, your monthly net burn in another, and divide.

A1: Cash on Hand    B1: $500,000

A2: Monthly Net Burn    B2: $40,000

A3: Runway (months)    B3: =B1/B2

This produces a clean number: 12.5 months in this example. It is easy to build, easy to understand, and easy to share. It is also an oversimplification that ignores most of the variables that affect when your cash actually runs out.

The formula assumes burn rate is constant, revenue is stable, and no irregular expenses exist. For a very early-stage company with minimal revenue and predictable costs, this may be close enough. For anything more complex, it will produce a number that feels precise but may not be accurate.

The month-by-month cash schedule

A more rigorous approach is to build a cash schedule that models each month individually. This allows you to account for variable expenses, uneven revenue, and known one-time costs.

Structure

Create columns for each future month. In each column, list your expected expenses by category (payroll, rent, software, etc.) and expected revenue. Subtract total expenses from total revenue to get net cash flow for that month. Apply this to the running cash balance.

Runway endpoint

The month in which your running cash balance reaches zero (or a minimum threshold you define) is your runway endpoint. This approach naturally surfaces cash crunches that a simple division would miss, such as a quarter where a large tax payment coincides with a slow revenue month.

This is closer to how runway calculation actually works in practice. It trades the simplicity of a single formula for the accuracy of modeling real cash flow patterns over time.

Common spreadsheet pitfalls

Hardcoded assumptions that go stale

Most Excel runway models start with a set of assumptions: headcount, average salary, revenue growth rate. These are entered once and rarely updated. Within weeks, the model drifts from reality. A hire that was planned but not yet made, a customer that churned, a vendor price increase that was not reflected. The model looks correct but produces a number that no longer matches the business.

Formula errors that compound silently

A broken reference, a misplaced parenthesis, a cell that was overwritten during a copy-paste operation. Spreadsheet errors are notoriously difficult to detect because the output still looks like a plausible number. Research consistently shows that a significant percentage of complex spreadsheets contain at least one material error. In a runway model, a single mistake in the burn calculation propagates through every subsequent month.

Version control problems

When multiple people edit a runway model, or when different versions exist for different audiences (board deck, internal planning, investor update), the numbers begin to diverge. Which version is authoritative? Often, no one is sure. This is the opposite of the canonical runway concept, where a single authoritative figure is referenced by everyone.

Optimistic revenue baked into the model

Founders building runway models in Excel frequently include projected revenue growth. This is understandable but dangerous. The moment projections enter the runway calculation, the output becomes a forecast rather than a fact. If the projection does not materialize, the actual runway is shorter than the model suggested. Separating confirmed data from assumptions is critical, and spreadsheets make this distinction easy to blur.

Structural limitations of spreadsheet-based runway

Beyond individual pitfalls, spreadsheets have structural characteristics that limit their effectiveness for ongoing runway management.

Static by nature

A spreadsheet is a snapshot. It reflects the moment it was last updated. It does not pull live bank balances, track actual spending in real time, or adjust when a new expense is committed. Keeping it current requires manual effort, and that effort competes with every other demand on a founder's time.

Poor at modeling decisions

Founders regularly need to answer questions like: “If I hire two engineers, how does that change my runway?” or “What happens if we lose our largest customer?” In Excel, answering these questions means manually changing cells, noting the result, then changing them back. This is workable for one scenario but cumbersome for the kind of iterative decision analysis that good financial planning requires.

No separation between fact and assumption

In a spreadsheet, confirmed expenses and projected expenses look the same. Collected revenue and forecasted revenue occupy identical cells. There is no structural distinction between data and guesses. This makes it difficult to produce a deterministic runway figure, one based solely on confirmed, factual inputs.

Practical guidance for founders using Excel

If you are calculating runway in Excel today, these practices will improve the reliability of your output.

Separate confirmed data from projections

Use distinct sections or color coding to distinguish between actual trailing data and forward-looking assumptions. Calculate runway twice: once using only confirmed figures, and once including projections. The gap between those two numbers is a measure of how much you are relying on assumptions.

Update at a consistent cadence

Set a recurring time, weekly or biweekly, to update your model with actual figures. This prevents drift and ensures the number you reference in decisions is reasonably current. Stale data is worse than no data because it carries false confidence.

Include irregular costs explicitly

Add a dedicated section for known non-recurring or irregular expenses: tax payments, insurance renewals, equipment purchases. Including them in the month they are expected to hit, rather than averaging them out, produces a more honest cash schedule.

Know when the spreadsheet has outgrown its purpose

There is a point at which the complexity of maintaining an accurate spreadsheet model exceeds the benefit of doing it manually. When you find yourself spending more time updating the model than using its output, or when multiple versions exist and no one agrees on which is correct, the spreadsheet has become a liability rather than a tool.