A dashboard showing "$140K burn, 10 months runway" isn't enough. Investors need to see whether the number includes annual software payments, a planned engineering hire, changing revenue, and the $400K SAFE that just landed in the account.
What should a startup burn rate dashboard include?
The summary tab needs current cash, gross burn, net burn, runway, burn multiple, and the projected zero-cash month. Put actual versus budget beside each burn metric and show the prior-month movement.
Use a structure like this:
| Dashboard output | Base case | Slower hiring | Faster hiring |
|---|---|---|---|
| Cash on hand | $1,400,000 | $1,400,000 | $1,400,000 |
| Current monthly net burn | $140,000 | $140,000 | $140,000 |
| Average forecast net burn | $151,000 | $128,000 | $176,000 |
| Runway | 9.3 months | 10.9 months | 8.0 months |
| Cash-out month | May 2027 | July 2027 | April 2027 |
| Burn multiple | 2.1x | 1.8x | 2.5x |
Those figures tell a board something actionable. Delaying 2 hires extends runway by 1.6 months. Accelerating them pulls the financing deadline forward by roughly 5 weeks. That is a decision, not dashboard decoration.
The model underneath should have 4 tabs: Assumptions, Actuals, Forecast, and Summary. Charts and KPI cards belong on Summary. Hardcoded inputs don't.
How are gross burn, net burn, runway, and burn multiple calculated?
Gross burn is operating cash paid during the month, before customer cash receipts. If payroll, contractors, hosting, sales, rent, and other operating payments total $180,000, gross burn is $180,000.
Net burn is operating cash out minus operating cash in. If the company collects $40,000 from customers, net burn is $140,000. Use cash collections rather than booked revenue when calculating cash runway. An annual contract recognized over 12 months doesn't pay 12 months of payroll unless the customer has paid it.
Runway is the number of months until projected cash reaches the minimum operating threshold, not merely current cash divided by last month's burn. The shortcut is useful as a snapshot:
=IF(Current_Net_Burn<=0,"Cash Flow Positive",Current_Cash/Current_Net_Burn)
The financing-grade answer comes from a monthly cash forecast:
=Prior_Month_Cash
+ Customer_Collections
+ Capital_Received
- Operating_Cash_Out
- Debt_Repayment
- Capex
Burn multiple is net burn divided by net new ARR over the same period:
=IF(Net_New_ARR<=0,NA(),Net_Burn/Net_New_ARR)
Craft Ventures defines burn multiple as “Net Burn / Net New ARR” and grades below 1x as amazing, 1x to 1.5x as great, 1.5x to 2x as good, 2x to 3x as suspect, and above 3x as bad. Those are directional operating benchmarks, not accounting rules. See David Sacks' original burn multiple framework.
Keep the periods consistent. Dividing March burn by trailing-12-month net new ARR quietly understates the ratio and creates the kind of spreadsheet argument that eats 20 minutes of a board meeting.
Why should runway come from a cash waterfall?
A static runway formula assumes burn remains unchanged. Startups don't behave that politely.
Consider a seed-stage SaaS company with 30 paying logos, $280 ARPU, $8,400 MRR, and 4% monthly logo churn. Its plan includes 3 pricing tiers, a shifting customer mix, 2 engineering hires, and annual insurance paid in January. Last month's net burn won't represent the next 9 months.
A cash waterfall catches those changes month by month. It also prevents fundraising proceeds from flattering operating performance. A $400,000 SAFE increases cash, but it doesn't reduce net burn.
Every forecast month should satisfy this control:
=Ending_Cash-(Beginning_Cash+Capital_Received+Customer_Collections-Operating_Cash_Out-Other_Cash_Out)
The result must be $0. Apply conditional formatting when the absolute value exceeds $1. A model that misses cash by $37 is still a model that doesn't foot.
For actual months, add a second reconciliation:
=Model_Ending_Cash-Bank_Statement_Ending_Cash
That control also needs to equal $0. If it doesn't, don't update the board deck yet.
What runway scenarios should investors see?
Show a base case and at least 2 operating alternatives. A generic optimistic/base/pessimistic switch is less useful than scenarios tied to decisions the company can actually make.
Suppose the base plan hires a senior engineer in September at $15,000 monthly fully loaded and an account executive in November at $12,000. The faster plan starts both in August. The slower plan moves them to January.
| Hiring plan | 12-month payroll outflow | Lowest cash balance | Runway |
|---|---|---|---|
| Slower hiring | $1,020,000 | $86,000 | 10.9 months |
| Base case | $1,104,000 | $0 | 9.3 months |
| Faster hiring | $1,176,000 | $0 | 8.0 months |
The sensitivity table should test the assumptions that can move the financing date: hiring start month, cash collections, monthly logo churn, and sales efficiency. Don't build a 10-by-10 rainbow grid just because Sheets allows it.
Google states that a spreadsheet supports “up to 10 million cells” in its Drive file limits documentation. A useful burn model should consume a microscopic fraction of that. Oversized models usually hide weak structure, not sophisticated thinking.
How should SaaS metrics connect to the burn dashboard?
Revenue forecasts need customer shape, not a flat growth percentage. Start with logos by tier, ARPU, new logos, expansion, contraction, and churn.
For 30 logos at $280 blended ARPU, opening MRR is $8,400. At 4% monthly logo churn, the model loses roughly 1.2 logos per month before new sales. If the company adds 4 logos monthly, ending logos are approximately 32.8 and MRR reaches about $9,184 before expansion or pricing changes.
The burn dashboard shouldn't reproduce the entire revenue model. It should pull 4 outputs from it: customer collections, ending MRR, net new ARR, and CAC payback.
A pricing change belongs in the sensitivity table because it can improve runway without touching payroll. Suppose blended ARPU rises from $280 to $325 while sales and marketing spend remains $12,000 per month. If the company acquires 4 new logos monthly, CAC is $3,000.
At an 80% gross margin, CAC payback changes from 13.4 months to 11.5 months:
=3000/(280*80%)
=3000/(325*80%)
That 1.9-month improvement matters only if the price increase doesn't damage win rate or churn. Model all 3 variables together. Price up and conversion unchanged is a pitch deck assumption, not a sensitivity analysis.
How should fundraising and SAFE dilution appear?
Cash runway and ownership dilution are connected, but they shouldn't be mashed into one calculation. Financing proceeds feed the cash waterfall. SAFE conversion and the priced round feed a separate capitalization schedule.
Assume the company has 10,000,000 pre-round shares, a $500,000 post-money SAFE with a $5 million valuation cap, another $300,000 post-money SAFE with an $8 million cap, and a $3 million Series A at a $12 million pre-money valuation. The priced-round investor owns 20% immediately after the new-money issuance, before any option-pool top-up:
=3000000/(12000000+3000000)
The SAFE math depends on the agreement terms, capitalization definition, discounts, option-pool treatment, and whether the instruments are pre-money or post-money. Y Combinator publishes separate US post-money SAFE forms and warns founders to use the correct version in its SAFE financing documents.
Don't present a single dilution percentage until the cap table schedule reconciles pre-round holders, every SAFE, the option pool, and the new investor to exactly 100.00%:
=SUM(Post_Money_Ownership_Percentages)
The control result must be 100.00%. The burn dashboard can then show the financing date, capital raised, post-round cash, and fully diluted founder ownership without pretending those numbers came from the same formula.
Which charts belong on a startup burn rate dashboard?
Use 3 charts. A monthly gross-versus-net-burn line shows whether revenue is absorbing more of the cost base. A projected cash-balance line shows the financing cliff and any minimum-cash threshold. A runway-by-scenario column chart shows the effect of operating choices.
Burn multiple can sit as a KPI with a 6-month sparkline. A full-sized fourth chart rarely earns the space unless efficiency is the main board discussion.
A chart isn't a control. Keep the cash reconciliation, actual-versus-budget variance, and assumption date visible above or beside it. The polished chart is usually innocent. The hardcoded cell feeding it is the criminal.
Why a 3-month average can still misstate runway
A 3-month rolling net-burn average is better than using one noisy month, but it lags deliberate changes. If January burn was $100,000, February was $120,000, and March was $140,000, the rolling average is $120,000. That makes runway look longer just as the company accelerates hiring.
Use the rolling average for the historical KPI. Use the monthly cash waterfall for projected runway. Label both:
=AVERAGE(Burn_Actuals_Last_3_Months)
=MATCH(TRUE,Projected_Cash_Range<=Minimum_Cash_Threshold,0)
This distinction is the most useful improvement most founders can make. Historical burn answers, “What have we been spending?” Forecast runway answers, “When does this plan force us to raise?”
As of July 2026, that separation also makes tool comparisons cleaner. If you're deciding whether to keep the model in Sheets or move to dedicated software, see the 2026 comparison of runway and burn-rate platforms.
How can AI help without weakening the model?
AI is good at wiring repeated monthly formulas, separating assumptions from calculations, applying number formats, and finding broken references. It isn't a substitute for bank reconciliation or a signed financing document.
A useful prompt is specific: “Create a Summary tab using the existing Actuals and Forecast tabs. Show current cash, 3-month average net burn, forecast cash-out month, burn multiple, and runway under the Base, Slower Hiring, and Faster Hiring cases. Add a cash reconciliation control that must equal zero.”
ModelMonkey can build those formulas and format the output inside Google Sheets or Excel, with proposed sheet changes available for review. The founder still owns the assumptions and signs off on the numbers.