Burn Multiple Calculator
The formula
What the burn multiple tells you
David Sacks' efficiency-era metric: dollars burned per dollar of new ARR. Under 1 the growth funds itself; over 3 the company is renting a trajectory.
Calculation: Burn multiple = net burn rate ÷ net new ARR added (annualized). Enter your inputs and every substitution is shown below the result.
Reading the result
Stage matters — seed companies legitimately burn 4–6×; the bar tightens as ARR compounds.
Rules of thumb: 2020-era norms: <1.5 good, 1.5–2.5 acceptable, >4 flag
Limitations and best practice
Netting revenue against burn hides margin structure; a company can post a fine burn multiple on loss-making revenue.
This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Frequently asked questions
Is 1× the goal?
Does it work pre-ARR?
Source & methodology
Sacks, "Burn Multiple: A Better SaaS Metric" (2020).
Burn Multiple: what this tool answers
You are here because you need a specific number, and you want to see how it was produced before you rely on it. Searchers land on a Burn Multiple page for three reasons — to plan, to compare options, and to check that somebody else’s arithmetic is honest. This tool serves all three, and everything after the calculator explains the model instead of hiding it.
There is a habit that separates people who get useful answers from Startup Metrics numbers: they decide what question the figure answers before they compute it. Burn Multiple answers “Burn multiple?” — and nothing else, which is precisely why the result is trustworthy.
Like most useful measures, Burn Multiple is a summary, and summaries hide as much as they reveal. The companion outputs and the input table are here to reopen what the headline compressed.
What makes a calculation page trustworthy is that its copy is derived from its own arithmetic: here burn multiple = 0.54, recomputed every time a field changes, and the sensitivity section ranks the inputs that move the result — Current ARR first, at ≈143.2 % of the headline for a ten-percent error either way in that input — which is the thread the rest of this guide pulls on.
Inside the Burn Multiple calculation: formula and every input
The engine implements a single stated model: Burn multiple = net burn rate ÷ net new ARR added (annualized). There is no hidden coefficient and no login-gated precision — the formula printed is the formula executed, which is also what makes the result citable.
Monthly net burn ($) (example value 287,500) is a measured number in the unit named by the label; the formula does not convert for you. If you are unsure what belongs in this field, look at the printed steps: the substitution shows exactly how the engine uses it.
Current ARR ($) (example value 9,433,340) is a plain measured quantity — the unit shown in the label is the unit the formula expects. Replace the example with the figure from your own records — the tool recomputes instantly and the printed steps follow your numbers.
ARR three months ago ($) (example value 7,831,301) is a numeric input whose unit is fixed by the label; a wrong unit is a wrong answer wearing a plausible disguise. Use the value as of today, not as of the last time you looked — time fields drift silently.
Burn Multiple with real numbers, step by step
Rather than describe the calculation, here it is end to end — every substitution in order, starting from the inputs above. Starting figures: Monthly net burn ($), Current ARR ($), ARR three months ago ($). The endpoint of that chain is 0.54 of burn multiple, sitting in the “Excellent — growth costs less than it returns” band.
- ΔARR × 4 = $6,408,156 annualized new ARR
- Burn multiple = $3,450,000 ÷ $6,408,156 = 0.54
Net new ARR (annualized) — $6,408,156. Compare it against the main result of 0.54 before drawing conclusions.
Annualized net burn — $3,450,000. If your inputs change, this is usually the first companion figure to move.
Burn multiple if growth +20% — 0.45. This is the number experienced users quote when the headline alone would mislead.
Overwrite any input above and every line of this example updates with it — the substitution is live, not a screenshot of somebody else’s numbers.
Scenario table: Burn Multiple at ±10 % and ±20 % of the key input
Read this table as the practical error bar on the headline figure. It answers the question people actually have after seeing a single number: how wrong could this be if the main input is off by ten or twenty percent?
| Current ARR setting | Burn multiple |
|---|---|
| 80 % of the example value | 3,450,000.00 |
| 90 % of the example value | 1.31 |
| example inputs | 0.54 |
| 110 % of the example value | 0.34 |
| 120 % of the example value | 0.25 |
Across 5 settings of Current ARR, the result spans 0.25 to 3,450,000.00. A decision that only works at one row of this table is a decision waiting for an input to move. Reproduce it in the form above by editing Current ARR alone; the substitution steps will follow your figures exactly.
What actually moves your Burn Multiple
Generic advice says “it depends on your inputs”; this section says exactly how much. Each field was perturbed by ±10 % in isolation and the burn multiple recomputed, so the ranking below is measured rather than asserted. Read it as a map of where Burn Multiple is fragile — drawn for the example inputs, which is the map you want when deciding what to measure carefully.
- Current ARR: ten percent up gives 0.34, ten percent down gives 1.31 — ≈143.2 % of the burn multiple either way
- ARR three months ago +10 % → Burn Multiple = 1.05 · −10 % → 0.36 (the burn multiple shifts ≈95.6 %)
- Monthly net burn +10 % → Burn Multiple = 0.59 · −10 % → 0.48 (the burn multiple shifts ≈10.0 %)
Current ARR is the dominant lever here: ten percent either way moves the result by about 143.2 %, from 0.34 to 1.31. Spend your verification effort there first, and treat ARR three months ago as the second priority (≈95.6 % per ten percent). Everything below that can stay approximate, which is a licence to stop chasing data that would not change the decision.
Reading the result: bands, zones and thresholds
Nobody acts on a bare figure — they act on a figure with a comparison attached. On the example inputs the band reads “Excellent — growth costs less than it returns”; your own figures place you on a different rung of the same ladder. Before treating the band as fact, note its width: ten percent either way on Current ARR already spans 0.34 to 1.31. The practical reading rules: ask what would have to change to move you one band. If the answer is “a small, plausible input difference”, the band itself is not the finding — the uncertainty is.
In Business & Entrepreneurship, Burn Multiple is one instrument in an orchestra: on its own it is a number, next to Net new ARR (annualized) and Annualized net burn it becomes a diagnosis. The tools linked above exist so the headline never has to carry that weight alone.
The errors that quietly break a Burn Multiple figure
Netting revenue against burn hides margin structure; a company can post a fine burn multiple on loss-making revenue. This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Chasing precision in Current ARR ($) while Monthly net burn ($) is still a guess. The sensitivity ranking above shows exactly where the accuracy budget should go.
One mistake is specific to this engine: assuming every input matters equally. The computation above shows Current ARR dominating — a careful figure there beats false precision everywhere else.
The subtlest error is answering the wrong question precisely. Confirm that burn multiple is actually the quantity your decision needs — the arithmetic is flawless either way, which is what makes the mistake invisible.
A quick check for any Burn Multiple figure
- Recompute once with the dominant input deliberately set low, and see whether the decision changes.
- Record the date and the inputs alongside the number so future-you knows what was assumed.
- Check Current ARR before anything else: it is the measured dominant input, ≈143.2 % of Burn Multiple per ten percent.
- Compare the output against one published benchmark or a colleague’s independent estimate.
- State, in one sentence, which convention each rate, unit or period in the form is using.
- Run the ±10 % stress on the top two levers and check that your conclusion survives both.
Step by step: getting a trustworthy Burn Multiple out of this tool
Using a calculator well sounds trivial, but the difference between a decision-grade figure and a throwaway one lives entirely in the routine. The routine for Burn Multiple takes a minute to learn and applies to every input above.
Step 1 — gather before you type. Burn Multiple depends on monthly net burn ($), current arr ($), arr three months ago ($). Collect them from a source document — a statement, a report, an invoice, a log — rather than from memory, because recalled inputs are the single largest cause of wrong results. Comparisons are cheap: run the identical calculation for the alternative and look at the gap.
Step 2 — baseline before exploration. Get one defensible Burn multiple on screen before you start nudging numbers. Without a baseline, every variation looks interesting and none of them means anything. The point of transparency is that a reader can disagree with a specific line rather than with you.
Step 3 — play with the inputs on purpose. Ten percent up, ten percent down, one field at a time. Within a few minutes you will know this calculation better than most people who quote its results. Write the figure down before moving on; memory flatters whichever number you saw last.
Step 4 — stress before you commit. A decision that survives a ten-percent squeeze on its two biggest inputs needs no luck to be sound. One that does not survive is a decision about hope, not about arithmetic. Compare the calculation to the rough guess you arrived with, and ask why they differ.
Step 5 — record the context, not just the number. Note today’s date and the inputs alongside the 0.54 output. Six months from now the context is what turns this figure into a trend. A result worth acting on survives having its two shakiest inputs halved.
From calculation to decision: where Burn Multiple earns its keep
Most Startup Metrics disagreements are arithmetic disagreements in disguise. When Burn multiple of 0.54 sits on the table with its working shown, the conversation stops being about who sounds more confident and starts being about which input is wrong. Numbers are cheap to produce and expensive to retract; the extra minute is the cheapest insurance available.
Used properly this is a five-minute filter that saves weeks. Compute Burn Multiple, reject what fails, and only then bring in the expensive analysis for the survivors. A figure with a date beside it becomes evidence; without one it stays an anecdote.
Nothing here is stored or transmitted, so the habit of checking is free: open the page, re-enter current figures, compare with the number you saved last time. Precision is a promise you make about your data; make sure your inputs can keep it.
People also ask about Burn Multiple
What affects Burn Multiple the most?
Measured on this engine, Current ARR is the dominant lever: moving it ±10 % shifts the burn multiple across 0.34 to 1.31 — about 143.2 % of the headline, with ARR three months ago next at ≈95.6 %. The ranked list in the sensitivity section is computed live, not asserted from a template.
Which matters more: arr three months ago or current arr?
By the numbers, Current ARR: a ten-percent change in it moves the result ≈143.2 %, versus ≈95.6 % for ARR three months ago. Spend your measuring effort in that order — precision on the weaker lever buys almost nothing.
What is a typical Burn Multiple?
With the example inputs on this page the result is 0.54, labelled “Excellent — growth costs less than it returns”. “Typical” varies with situation, which is why every result here ships with its verdict band and its sensitivity list: they turn one figure into a range you can locate yourself inside.
How do I calculate Burn Multiple by hand?
Use the stated model — Burn multiple = net burn rate ÷ net new ARR added (annualized) — and substitute in the order the tool prints (it starts from ΔARR × 4 = $6,408,156 annualized new ARR). On the example inputs the hand route lands on 0.54, exactly what the calculator shows. A spreadsheet reproduces it in two or three cells; doing it once by hand is what makes the automated answer trustworthy.
What happens to Burn Multiple if current arr changes by 10 %?
On these inputs a ±10 % change in current arr takes Burn Multiple to 0.34 against the 0.54 example — around 143.2 % of the headline. The same test on every other field is in the sensitivity section.
Is the Burn Multiple result of 0.54 good or bad?
Neither, on its own — the label “Excellent — growth costs less than it returns” is the band this figure falls in for the example inputs, and your own inputs will place you elsewhere on the same ladder. Judge the number against your history and your alternatives, and remember that a ten-percent error in Current ARR alone moves it by ≈143.2 %.
Should I use Burn Multiple before launching?
Yes — a Burn Multiple run on honest inputs before spending is the cheapest consulting an entrepreneur can buy. Re-run at every pricing change; the number moves more often than founders expect.
Is Burn Multiple accurate?
The arithmetic is exact: Burn multiple = net burn rate ÷ net new ARR added (annualized) is evaluated with full floating-point precision and every substitution is printed in the worked example. What limits accuracy is input quality and the model’s assumptions, so treat the 0.54 result as the correct answer to the question you typed — and check the assumptions section before acting on it.
Is 1× the goal?
By Series B most durable companies run 1–2×; sub-1 at scale is a flag for underinvestment, not virtue.
Does it work pre-ARR?
No — pre-revenue teams use runway and milestones; burn multiple needs a ΔARR.
Is my data private on this page?
Yes — computation happens locally in your browser, with no account, no tracking of your inputs and nothing sent to a server. The printed formula is the whole story of what happens to your figures.
The vocabulary of Burn Multiple
- Net new ARR (annualized)
- $6,408,156 in the default Burn Multiple calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- Annualized net burn
- $3,450,000 on the example inputs — a companion figure printed beside the headline of Burn Multiple so that no result is read in isolation.
- Burn multiple if growth +20%
- 0.45 on the example inputs — a companion figure printed beside the headline of Burn Multiple so that no result is read in isolation.
- Burn multiple
- The primary output of this tool: 0.54 for the default inputs, computed exactly from Burn multiple = net burn rate ÷ net new ARR added (annualized).
- Worked example
- The calculation written out in full so that nothing on this page has to be taken on trust.
- Verdict band
- The interpretation attached to a result (“Excellent — growth costs less than it returns” on these inputs), which turns a bare number into a position on a scale.
- Sensitivity (±10 %)
- How far the Burn Multiple moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.
Method, sources and what this tool cannot tell you
There is no black box on this page — the engine evaluates Burn multiple = net burn rate ÷ net new ARR added (annualized). Source of record: Sacks, "Burn Multiple: A Better SaaS Metric" (2020). Where a professional version of this calculation differs, it differs in inputs and jurisdiction-specific coefficients, not in the algebra — which is why re-checking your inputs beats hunting for a second calculator.
Nothing here replaces a qualified professional, and nothing here is approximate either — the arithmetic is exact, and the honesty is in the inputs you supply. The promise to the reader is narrow and testable: same inputs, same output, no silent rounding, and no figure presented without the formula that produced it.
What to do with your Burn Multiple next
Re-run the calculation with your own figures, stress the two most sensitive inputs by ±10 %, and only then act on the result.
The audience here is people who need one trustworthy number before their next decision. Everything you need to defend the result — formula, substitution, sensitivity, source — is printed above, so the only remaining variable is the honesty of your inputs.