How to Build a Burn Model for Your Business?

A startup’s cash balance can look healthy until two late invoices collide with payroll and a cloud bill. A Burn Model makes that timing visible by projecting cash inflows, expenses, and remaining runway month by month. It is not merely a polished spreadsheet for investors. It is a working decision tool. Small errors compound.

The stakes are real. CB Insights’ 2021 review examined 111 startup post-mortems. It found that 38% cited running out of cash or failing to raise new capital. That figure reflects reported reasons among failed startups, not the failure rate of all businesses. Use it as a warning, not a forecast. Still, it reinforces a practical point: cash planning deserves attention alongside sales growth, especially when revenue arrives unevenly.

A useful model separates fixed costs, variable costs, expected revenue, and one-time spending. For example, a small software company might track three salaries, monthly hosting fees, and a large annual insurance payment. Then test what happens if a customer pays 30 days late or hiring starts a month early. Compare a base case with conservative and stronger scenarios, and update actual results regularly. The assumptions will be wrong sometimes. That is normal—and worth examining. The useful question is whether the model reveals a cash shortfall early enough to change course. This guide explains how to build a Burn Model, choose practical inputs, and use its forecasts to make clearer operating decisions.

Table of Contents [Hide]

1 Define the Burn Model’s Scope and Key Metrics

2 Collect Historical Cash Flow and Operating Data

3 Forecast Revenue, Expenses, and Working Capital

4 Calculate Monthly Burn Rate, Cash Balance, and Runway

5 Test Assumptions and Update the Model Regularly

Define the Burn Model’s Scope and Key Metrics

A burn model is only useful when its boundaries are explicit. Decide whether it tracks cash leaving the business, net cash burn after customer receipts, or both. These figures answer different questions. For a monthly operating view, set a consistent period and include payroll, rent, software, inventory, taxes, and other recurring payments. Keep financing proceeds and unusual one-time costs visible, but separate them from normal operations. Otherwise, one large invoice can distort the trend.

Choose metrics that connect spending to available cash. Track opening and closing cash, gross cash outflow, cash collected, net burn, and runway. Define each formula in plain language. For example, net burn equals cash outflow minus cash received during the period. Runway can be estimated by dividing available cash by average net burn, but this assumes the burn rate stays steady. It often does not. Seasonal sales and delayed customer payments can change the picture quickly.

Set the model’s scope by team, entity, and forecast horizon, then document exclusions. A 12-month forecast may support hiring decisions; a weekly cash view may reveal a near-term gap. Use actual bank and accounting records where possible, and label estimates clearly. Test a slower-collections case too. It matters. Neat spreadsheets can hide weak assumptions, especially when expenses are copied forward without checking renewal dates. Review inputs monthly, identify who owns each estimate, and revise them when evidence changes. A little friction is healthy.

Collect Historical Cash Flow and Operating Data

A useful burn model begins with a clean record of cash moving in and out, not a guessed monthly average. Gather at least 12 months of bank transactions, payroll records, invoices, payment processor statements, and loan schedules. Use the dates cash actually cleared. An invoice sent in March but paid in April belongs in April’s cash inflow. Keep the raw files.

Next, group transactions into consistent categories: payroll, rent, software, inventory, taxes, customer receipts, and financing. Separate recurring expenses from one-time costs, such as a laptop replacement or office deposit. Don’t remove unusual payments without documenting why. A founder may call a cost “one-off,” but the next quarter can prove otherwise. That distinction matters.

Reconcile each month’s totals against bank balances and investigate gaps before forecasting. A spreadsheet row labeled “miscellaneous” can hide several different spending patterns. Add notes for delayed customer payments, annual insurance premiums, or hiring dates, since timing changes the cash runway. Check whether reported revenue matches cash received; they are not always the same. Some records will be incomplete. Mark estimates clearly, and revisit them when better evidence appears. A practical check is to trace one payroll payment from the ledger to the bank statement.

Forecast Revenue, Expenses, and Working Capital

How to Build a Burn Model for Your Business?

Forecast Revenue, Expenses, and Working Capital

A useful burn model connects monthly cash movement to the operating choices behind it. Start with opening cash, then forecast revenue, expenses, and working capital month by month. Build revenue from concrete drivers, such as expected orders, average sale value, and payment timing. If sales depend on a new contract, show the date it may begin rather than treating it as guaranteed. Use a base case and a slower-sales case. That matters.

Separate committed costs from flexible ones. Include payroll, rent, software, insurance, taxes, and planned hiring. Record when cash actually leaves the account; an expense recognized this month may be paid later. Avoid applying one growth rate to every cost. Headcount may rise in steps, while shipping costs may follow sales more closely. A common mistake is making the forecast look precise when the assumptions are still rough. Keep them visible.

Working capital can shorten your runway even when revenue is growing. Map customer collection days, supplier payment terms, inventory purchases, and deposits. A large invoice due in 60 days does not pay next week’s wages. Track those timing gaps explicitly. Review actual results against the forecast each month, and revise assumptions when collections slip or hiring changes. The spreadsheet will still be wrong sometimes. Make the reasons easy to inspect.

Calculate Monthly Burn Rate, Cash Balance, and Runway

A useful burn model starts with cash movements, not accounting profit. For each month, list opening cash, customer receipts, payroll, rent, software, taxes, and other payments. Net burn equals cash outflows minus cash inflows. Keep one-time costs separate from recurring expenses. That matters. A large equipment payment can distort a single month’s rate.

Carry the ending cash balance into the next month: opening cash plus receipts, minus outflows. Then estimate runway by dividing available cash by average monthly net burn.

If the business holds $420,000 and burns $60,000 monthly, the simple estimate is seven months.

But cash rarely moves evenly. A delayed invoice or annual insurance bill can change the picture quickly.

Build a month-by-month forecast for at least a year, and mark assumptions beside the numbers. Use realistic collection dates, not just invoice dates. Compare actual results with the forecast every month; investigate gaps instead of quietly adjusting them away.

I’ve found that a model can look precise while relying on rough guesses. Keep it visible. Test a slower-sales case and a higher-cost case, then note which expenses can truly be reduced. Runway is an estimate, not a promise, so refresh it when hiring plans or customer payments change.

Test Assumptions and Update the Model Regularly

A burn model is useful only when its assumptions face regular tests. Start with a weekly cash view: opening balance, customer receipts, payroll, rent, and supplier payments. Then label each input as confirmed, estimated, or uncertain. A signed contract is not the same as cash in the bank. Model the payment delay, too. In “Cash Is King: Flows, Balances, and Buffer Days” (2016), a study of small businesses estimated a median cash buffer of 27 days. That is a thin cushion. Compare your runway with actual payment timing, not just monthly averages.

Update the model every month, and after any major change, such as a delayed launch or a new hire. Run a base case, a slower-sales case, and a cost-overrun case. A 2021 review, “The Top 12 Reasons Startups Fail,” found that running out of cash appeared in 38% of 111 reviewed startup post-mortems. Treat that as a warning, not a prediction. Check forecast receipts against bank deposits, and compare planned hiring dates with signed offers. If actual costs keep beating the estimate, change the assumption; do not hide the gap in a new spreadsheet tab. No forecast is clean. I have seen small timing errors make a confident runway look safer than it is. Keep a brief note on why each assumption changed. That record makes the next review more honest.