On this page5
A person planning the week on a large wall calendar
Remaining company runway is available cash divided by expected burn over the same period; the result is an estimate, not a certain date. Show the cash, burn rate, and assumptions behind the estimate, then use a forecast range and review triggers to keep it current.
What you’ll learn
- How to define the cash available for the estimate
- How to calculate burn over a consistent period
- Which assumptions can move the runway estimate
- When to refresh the forecast and act on a change
What cash counts toward remaining company runway?
Start with a cash balance tied to a specific date. A balance without a date can be misleading: receipts, payroll, and other payments may have changed what is available since it was checked.
Separate cash the company can use for ordinary expenses from funds that are restricted or otherwise unavailable. A balance in an account does not necessarily mean the whole amount can cover expected burn. Keep committed payments visible too. If a payment is due soon, show whether it is already reflected in the starting balance or needs to be subtracted from it. Do not count it twice.
For each figure, record its source and when someone last checked it. That makes it easier to spot stale inputs before they shape a decision. Brainis maintains a live model of company state with sources, freshness, and confidence. See company state for how Brainis describes that record.
Important: Keep restricted or committed funds separate from cash you can use to cover expected burn.
The aim is not to make the cash number look precise. It is to define what the number includes, what it excludes, and which upcoming payments could change it. If people use different definitions of available cash, they can reach different runway estimates from the same account balance.
How do you calculate runway from burn rate?
Divide available cash by expected net burn over the same period. If cash is stated at a point in time and burn is monthly, the result is an estimate in months. If you use a different period, keep both inputs on that same basis.
Use a period that fits the records and the decision. A short period may reflect recent changes but can be distorted by irregular receipts or bills. A longer period may smooth those movements while hiding a recent shift. Whichever period you choose, show it beside the inputs rather than presenting the result by itself.
Example: A fictional small design studio has $480,000 available after setting aside committed payments. Its expected net burn is $60,000 per month, so the calculation gives eight months of runway at that burn rate. If a large client payment is delayed or spending changes, the estimate changes too; eight months is not a promised end date.
Show the cash balance, burn estimate, period, and result together. Note which movements are included in net burn, such as operating costs and incoming revenue. The estimate is a planning aid, not a guarantee that cash will run out on a particular day. For more on choosing a useful forecast period, read business forecast horizon.
Which assumptions can change the estimate?
Keep observed cash movements separate from expectations about what comes next. Past payroll payments are recorded movements. A planned hire, a possible change in revenue, or a renewal that may not happen is an assumption about the future. Mixing these together makes it hard to see what the estimate depends on.
For each assumption, write down its source or why you chose it. For example, a hiring change might come from an approved plan, while a revenue change might reflect a customer decision that is not final. Make the status clear. An assumption is not an observed result, even when the team has a good reason to use it.
Then identify which assumptions have the greatest effect on remaining company runway. Change one assumption at a time and see how much the result moves. If a possible revenue delay shifts the estimate more than a small cost change, that delay deserves more attention in the review. The point is not to model every detail. It is to show which uncertainties could change the decision.
Brainis maintains a live model of company state with sources, freshness, and confidence. A record with those details can help you see which inputs are observed and which need review. Learn more about company state.
A business owner reviewing plans at a desk in the evening
How should you show a runway forecast range?
Avoid presenting one forecast date as certain when the inputs depend on assumptions. Build a small set of plausible cases from those assumptions. Keep the cash definition and time period consistent across cases, and show which inputs differ. For instance, cases might use different expectations for revenue timing or planned costs.
Present the resulting range and explain what moves the result toward either end. The lower end might follow if a major receipt arrives later or spending rises. The higher end might follow if revenue holds and planned costs stay lower. State these as conditions, not as promises. This gives the team something concrete to watch as events unfold.
Brainis models alternative futures before recommending a path. Its predictions carry ranges and a model version, and are preserved unchanged when reality arrives. Read about the world model, ranges instead of certainty, and writing predictions down.
Tip: Keep the original forecast intact when new results arrive, then record the update separately.
Preserving the earlier forecast makes the comparison useful. If you overwrite it with the latest estimate, you lose the evidence of what the team expected before the outcome was known. Keep the original assumptions and range, then record new information and the revised view as a separate update. That lets a later review distinguish a changed forecast from the one people first used to decide.
When should you review runway and decide what to do?
Set review triggers around changes that could move the estimate: available cash, expected burn, or an assumption with a large effect. A trigger might be a receipt arriving later than expected, a spending plan changing, or new information that weakens a revenue assumption. Choose triggers that would lead you to check the forecast, rather than treating every small movement as a crisis.
When a trigger occurs, refresh the estimate and record which inputs changed. Compare the new view with the prior forecast and, when the outcome is known, with what actually happened. That comparison can show whether the difference came from a changed assumption, an unexpected event, or an estimate that needs a better basis.
Predicted and actual outcomes are recorded in the Decision Ledger and improve the next recommendation. Use the review to decide what action follows from the changed estimate, then name an owner and a next review point. A forecast without an owner may be noticed but not acted on. A clear owner and follow-up make the remaining company runway a working input to decisions, not a number that sits untouched in a report.
The estimate should change when its evidence changes. Keep the prior view, make the new inputs visible, and agree on what the team will do if the next trigger is reached. That gives you a repeatable way to review the forecast without mistaking it for certainty.
Brainis Team
Notes on running a company with Brainis, from the people building it and running on it.