Gross Burn Rate
Definition
Average monthly cash outflow before any inflows are netted off — essentially the company's monthly cost base in cash terms. Tracked alongside net burn because net burn alone can mask a structural problem when revenue is masking high cost. The board reads gross burn to understand the absolute cost commitment (mostly payroll, infra, COGS, sales spend) regardless of revenue mix. Common pitfall: founders often optimize the net burn narrative ("we cut burn 30%") via a one-time inflow without addressing the gross-burn cost base — the next quarter without that inflow re-exposes the underlying spend. Always present gross and net side-by-side.
Why it matters
Strips revenue volatility from the survival picture — shows the cost commitment the company must support each month regardless of bookings outcomes. A widening gap between gross and net burn that depends on a single deal or one-off inflow is a fragility signal.
How it's calculated
gross_burn_rate = total_operational_outflow / months_in_period. Same denominator and averaging convention as net burn (3-month trailing average is standard). Always greater than or equal to net burn. How to interpret it
Compare gross-burn composition (payroll, infra, GTM, COGS) to revenue mix; sustained gross burn growing faster than ARR is a leading deterioration signal even when net burn looks flat. No single published gross-burn threshold exists — interpret relative to ARR and revenue per FTE (`hr.arr_per_fte`). Practitioner consensus (industry folk-wisdom, not citation-grade): payroll typically accounts for 65–80% of gross burn in venture-backed SaaS.
Source
imboard Editorial
Stage relevance
Typically owned by
Related KPIs
Average monthly net cash outflow over the reporting period — total cash spent minus total cash collected, divided by the number of months in the period. The headline survival number for venture-backed startups: it pairs with `finance.total_cash_in_bank` to produce runway, and pairs with revenue growth to produce the Bessemer "burn multiple". Common pitfall: net burn is volatile — large quarterly bills (annual SaaS renewals, employer-tax true-ups), enterprise prepayments, and FX swings can mask the underlying trend. Smoothing over a trailing 3-month average is standard board practice. Equally important: do not silently include one-off cash events (acquisitions, settlements, large prepayments received) without flagging them — boards prefer a "core burn" and "headline burn" pair when the period is noisy.
The single past-period observed burn — gross and net — that anchors the forecast-scenario matrix. The "we just lived through this" baseline against which conservative / most-likely / best-case forecasts are projected. Differs from `finance.gross_burn_rate` and `finance.net_burn_rate` in being explicitly a point-in-time historical anchor with both components paired in one object, rather than the standalone monthly KPI values. Common pitfall: anchoring forecasts off a single month with a known one-off (large bill, prepayment received) bakes a distortion into all scenarios — pick a representative period or document the adjustment.
Sum of cash actually paid for operating activities for the period — payroll and benefits, employer taxes, vendor payments (infra, tooling, contractors), sales and marketing spend, rent, professional services, refunds issued. Excludes financing activities (debt repayment, dividend payments) and investing activities (acquisitions, capex). Direct input to gross burn. Common pitfall: capitalized R&D and long-term capex sometimes get bucketed here; if so they distort gross burn. Keep this strictly operating-cash and surface investing/financing outflows separately so the board can see "ongoing cost base" vs. "discretionary capital deployment".
Estimated number of months the company can operate at the current net burn before unrestricted cash reaches zero, holding everything else constant. The single most consequential survival input for venture-backed companies — it sets the urgency of every fundraising, hiring, and cost decision. Common pitfall: runway is often quoted off `finance.total_cash_in_bank` and a single-month spot-burn instead of operationally-available cash and a 3-month-trailing burn — the result is a runway that looks 2–4 months longer than it actually is when working capital tightens. Boards should ask which cash and which burn went into the calculation.
Annual Recurring Revenue divided by total FTE-equivalent workforce — the canonical SaaS workforce-productivity ratio anchored to the SaaS Capital Annual Survey methodology (revenue per employee benchmarks). A high-signal denominator for "are we over- or under-staffed for our revenue scale?" Common pitfall: choosing different ARR conventions (ending vs average, GAAP-reconciled vs raw) without locking in a board-level standard. Best practice is to pair this with `sales.arr` so the numerator is unambiguous and to disclose whether contractors are included in the FTE denominator.
Annual Recurring Revenue — the value of all recurring subscription revenue normalized to a one-year run-rate as of the period close. The headline operating metric for a subscription business; every growth and efficiency ratio (NRR, GRR, magic number, CAC payback, Rule of 40) is calibrated against it. Excludes one-time fees, professional services, and non-contractual usage. Common pitfall: confusing ARR (contracted recurring) with revenue (recognized) or with CARR (contracted incl. not-yet-live) — the SMSB standard draws sharp lines between them, and boards expect the same discipline. The KpiVarianceTable widget surfaces forecast / actual / variance / status / future-forecast columns against the same field.
Track these KPIs with your board
I'mBoard helps startup CEOs report the metrics that matter, track resolutions, and run better board meetings.