What's the difference between gross burn rate and net burn rate?

Gross burn rate is your total cash out per month — all expenses, no offsets. Net burn rate subtracts revenue from that figure. A startup spending $200,000/month with $50,000 in revenue has a gross burn of $200,000 and a net burn of $150,000. Runway calculations should always use net burn, not gross.

How do I calculate startup runway in Google Sheets?

Divide your current cash balance by your monthly net burn: `=cash_balance / net_burn`. For a more accurate figure, use a 3-month rolling average of net burn as the denominator rather than the most recent month alone. Wrap the formula in an `IF` to handle months where net burn is zero or negative.

What is burn multiple and why does it matter?

Burn multiple is net burn divided by net new ARR added in the same period. A burn multiple of 1.5x means you're burning $1.50 for every $1.00 of new ARR — an efficiency metric popularized by David Sacks at Craft Ventures in 2022. Below 1.0x is considered efficient. Above 2.0x typically signals that go-to-market spend isn't converting to durable revenue.

How often should I update a burn rate dashboard?

Monthly is the minimum. Most finance teams update it at month-end close, roughly 5-7 business days after month-end when all invoices and payroll figures are confirmed. If you're in a high-burn phase approaching a raise, weekly updates using estimates are better than waiting for actuals.

Should my burn dashboard live in the same spreadsheet as my financial model?

It depends on your model's complexity. For early-stage companies with a single P&L sheet, embedding the dashboard makes sense. For companies with a full three-statement model across multiple tabs, keep the burn dashboard as a separate file that pulls from the main model via `IMPORTRANGE`. This prevents accidental edits to source data and keeps the dashboard load time fast.

Startup Burn Rate Dashboard in Google Sheets

This article covers what a startup burn rate dashboard should contain, how to structure it in Google Sheets, and what most founders get wrong when they build one.

What Goes Into a Startup Burn Rate Dashboard

A complete startup burn rate dashboard tracks 4 metrics minimum: gross burn, net burn, runway, and burn multiple. Everything else — headcount cost breakdown, department-level spend, MoM variance — is useful context, not the core.

Gross burn is total cash out per month. No offsets. If you spent $180,000 in March across payroll, infrastructure, and marketing, gross burn is $180,000.

Net burn subtracts revenue. If you brought in $40,000 in March, net burn is $140,000. Net burn is what actually drains your bank account.

Runway is cash on hand divided by net burn. $1.4M in the bank at $140K/month net burn = 10 months. That's the number you're watching.

Burn multiple is net burn divided by net new ARR. David Sacks at Craft Ventures popularized this metric in 2022 as a more honest efficiency measure than gross margin alone. A burn multiple under 1.0x means you're generating more ARR than you're burning — rare at early stage, but that's the target. Above 2.0x is a warning sign.

How to Structure the Dashboard in Google Sheets

Google Sheets caps at 10 million cells per spreadsheet, per Google Workspace documentation — more than enough for a burn dashboard, but structure still matters. A dashboard that works is one where the inputs, calculations, and outputs live in separate places.

Use 3 sheets:

Inputs: Raw monthly expense data by category, cash balance, ARR figures
Calcs: Gross burn, net burn, runway, burn multiple — all derived from Inputs
Dashboard: Charts and summary KPIs that reference Calcs, nothing else

Never put hardcoded numbers in your Dashboard sheet. When you update February's payroll in Inputs, the Dashboard should update automatically. If you're editing numbers directly in a chart's data source, the model is already broken.

The Core Formulas

Assume your Inputs sheet has months in row 1 (B1:M1 = Jan through Dec) and expense rows below. Cash balance sits in a named range cash_balance. ARR data lives in a separate row.

// Gross Burn (sum all expense rows for the month)
=SUMIF(Inputs!A:A,"<>Revenue",Inputs!B:B)

// Net Burn
=Gross_Burn - Inputs!Revenue_Row

// Runway (in months)
=cash_balance / Net_Burn

// Burn Multiple
=Net_Burn / (New_ARR_This_Month)

Wrap runway in an IFERROR — if net burn ever goes negative (you're cash-flow positive), the division will return a negative number that means nothing. Flag it explicitly:

=IF(Net_Burn<=0,"Cash Flow Positive",ROUND(cash_balance/Net_Burn,1))

Headcount Is Usually 60-75% of Burn

Andreessen Horowitz operating benchmarks consistently show that headcount-related costs (salary, benefits, equity comp, contractor fees) account for 60-75% of total burn for early-stage software companies. If your dashboard doesn't break out headcount separately, you're flying blind on the one lever that actually moves the number.

Add a dedicated headcount section to your Inputs sheet with rows for:

Category	Jan	Feb	Mar
Full-time salaries
Employer taxes & benefits
Contractors / freelancers
Recruiting fees
Headcount Total

The Headcount Total row feeds into gross burn automatically. When you're in a board meeting and someone asks "what happens if we cut 2 engineers," you pull from this row, not from memory.

Burn Rate vs. Runway: What Changes and What Doesn't

A common mistake: founders optimize for burn rate and forget to update runway when they raise. Runway is a function of both spend and cash, and cash changes when you close a round, receive a customer payment, or pay a large one-time vendor invoice.

Build a cash waterfall into your Calcs sheet:

// Cash balance this month
=Cash_Balance_Prior_Month - Net_Burn + Capital_Raised + One_Time_Items

This means your runway figure auto-updates whenever you log a wire. No manual edits to a "current cash" cell somewhere.

For more on how to model the funding side of the equation, the article on runway forecasting with funding integration covers how to wire investor tranches into a rolling model.

The Charts That Actually Matter

Three charts belong on a startup burn rate dashboard. Everything else is noise.

1. Monthly burn trend — a simple line chart with gross burn and net burn as two series, months on the x-axis. This tells you immediately whether the gap between gross and net is widening (revenue growing) or narrowing (revenue slowing relative to spend).

2. Runway over time — a bar chart showing projected runway in months at the end of each month. As burn increases, bars shorten. You want this on the dashboard as a visual alarm, not a number buried in a cell.

3. Burn multiple trend — line chart of burn multiple by month. A startup that raised a seed round in 2023 might have had a burn multiple of 4.0x early on. If it's not moving toward 2.0x and then toward 1.0x, the chart will show you the stagnation before the spreadsheet will.

If you're building this in Google Sheets for the first time, the article on startup metrics dashboards covers the setup mechanics including chart anchoring and dynamic range references.

The One Calculation Most Dashboards Get Wrong

Most startup burn rate dashboards calculate runway using the current month's net burn as a static denominator. That's fine for a snapshot, but it lies to you about trajectory.

A better approach: use a 3-month rolling average for net burn in your runway calculation. If January was $100K, February was $120K, and March was $140K, your point-in-time runway calculation uses $140K. A 3-month rolling average uses $120K — more accurate if costs are ramping, less accurate if you just made a big hire. The point is to make the averaging method explicit, not invisible.

// 3-month rolling average net burn
=AVERAGE(Net_Burn_Row[-2]:Net_Burn_Row[0])

// Runway using rolling average
=cash_balance / Rolling_Avg_Net_Burn

Label it. Your board and investors will ask which method you're using. Have an answer.

If you're using ModelMonkey in Google Sheets, you can describe this calculation in plain language — "calculate a 3-month rolling average of net burn and use it for runway" — and it will write the formula into your model, including the correct relative references across your monthly columns.