Burn Multiple vs Runway

Most solo founders track runway. A smaller fraction track burn multiple. Almost none track both, and the gap shows up in the decisions they make when growth slows or capital tightens. Runway alone tells you the deadline; burn multiple alone tells you the velocity. Together, they tell you whether to step on the accelerator, ease off, or tap the brakes.

This article walks through both metrics with definitions, the bands that map to founder decisions, the 2x2 matrix that combines them into a single weekly read, a worked example across four quarters, and how investors interpret the pair when evaluating early-stage companies.

1. Burn multiple and runway, defined precisely

Burn multiple was named by David Sacks at Craft Ventures^[1]. The formula:

Burn Multiple = Net Burn / Net New ARR

Net burn is cash out minus cash in over a period (usually monthly or quarterly). Net new ARR is new ARR minus churned and contracted ARR over the same period. The ratio answers: for every dollar of new recurring revenue you added, how many dollars of cash did it cost. Lower is better. A burn multiple of 1.0 means every dollar of new ARR cost a dollar of cash; 0.5 means each new ARR dollar cost fifty cents; 2.0 means it cost two dollars.

Runway is older and more familiar:

Runway (months) = Current cash balance / Average monthly net burn

Both formulas have edge cases. Burn multiple is undefined when net new ARR is zero or negative; in that case, label it explicitly as "infinite" or "negative" rather than computing a misleading ratio. Runway calculations should use trailing 3-month average burn rather than a single month, because single-month burn fluctuates with annual contract billings, tax payments, and one-time spend. The Burn Multiple Calculator handles the period-averaging arithmetic and the Startup Runway Calculator handles the cash-balance projection.

2. The two metrics answer different questions

The two are not substitutes. They answer questions on different time horizons and about different aspects of the business.

Runway is a survival metric. It answers "when does the business die at current burn?" The implicit assumption is that current burn continues. The metric is most useful when burn is stable and revenue is roughly flat.

Burn multiple is an efficiency metric. It answers "is the cash we are spending producing proportional growth?" The implicit assumption is that burn is paying for growth. The metric is most useful when both burn and ARR are moving.

A business with $500k cash, $25k monthly burn, and zero growth has 20 months of runway and an undefined burn multiple. The runway number says "you are fine for 20 months." The undefined burn multiple says "the business is not actually growing, which means the 20 months of runway is the runway, full stop, with nothing on the other side." Two different reads on the same balance sheet.

A second business with $300k cash, $40k monthly burn, and $50k monthly net new ARR has 7.5 months of runway and a burn multiple of 0.8. The runway number says "you are nearly out." The burn multiple says "every dollar of burn is producing $1.25 of new ARR, which is excellent capital efficiency." The right interpretation is "raise capital now while the efficiency story is strong, not in three months when the runway story is desperate."

3. Burn multiple bands and what they mean

Sacks's essay gives two anchors: a 2x burn multiple is "reasonable for an early-stage startup", and needing 3x or more is a sign that product-market fit may not be what it seems^[1]. The bands below are this guide's working reading around those anchors, set for a company that has to fund its own burn:

• Below 1.0 (amazing). Each new ARR dollar costs less than a dollar of burn. Sustainable scale-up territory. Below 0.5 often signals product-led-growth dynamics or an unusually efficient sales motion.
• 1.0 to 1.5 (good). Defensible during normal market conditions. Capital is being deployed productively but the business is not yet self-funding.
• 1.5 to 2.0 (acceptable with funding). Within what Sacks calls reasonable for an early-stage startup, but a bootstrapped business pays for every point of it out of cash. Check channel mix and pricing before scaling.
• 2.0 to 3.0 (watch closely). Capital is producing growth at unfavorable terms. Either burn needs to come down or growth needs to come up materially, and raising money at this level is harder.
• Above 3.0 or undefined (warning). Burn is not producing proportional growth, the level Sacks reads as a sign that product-market fit may not be what it seems^[1]. Restructure the cost base or rethink the business model.

The bands are not bright lines. A 1.6 burn multiple at $30k MRR with 8 months of runway is materially different from 1.6 at $3M ARR with 24 months of runway. Always read burn multiple alongside ARR scale and runway to get the full picture.

4. The runway floor for solo founders

For venture-backed firms, the standard guidance is to raise enough for 18 to 24 months of runway, because the next round takes time to earn and longer still to close when capital is tight.

For bootstrapped solo founders, the runway floor is different. Without a fundraising deadline, the binding constraints are personal cash reserves and the time required to reach revenue self-sufficiency.

Practical floors for bootstrapped solos:

• 9 months minimum. Below 9 months, decision-making compresses to short-term cash management. Strategic moves (price increases, channel pivots, product repositioning) require 3 to 6 months to play out. Below 9 months runway, you do not have enough room to execute strategy.
• 12 to 18 months target. The band where strategic experimentation is possible. A failed experiment costs 2 to 3 months of runway; from a 15-month base, that leaves 12 months to recover. From a 9-month base, the same failed experiment leaves 6 months, which is below the floor.
• 24+ months (over-conservative). Sitting on more than 24 months of runway as a bootstrapped founder usually indicates underinvestment in growth. The cash is doing nothing in a checking account; if the business has product-market fit, the right move is to redeploy into acquisition.

Stack a separate personal-finance runway underneath the business runway. Many solo founders forget that the business going to zero and the founder going to zero are not the same event. A six-month personal cash buffer outside the business is the difference between "we shut down the business" and "we lose the house."

5. The 2x2 decision matrix

Combining burn multiple and runway produces four states with four distinct decision-trees. Use these as the weekly check.

                          Runway < 9 months         Runway >= 9 months

Burn multiple <= 1.0    State A: RAISE NOW          State B: SCALE
                        Efficiency is strong but    Both metrics are healthy.
                        cash is short. Use the      Reinvest. The business
                        efficiency story to fund-   has earned the right to
                        raise immediately.          deploy more capital.

Burn multiple > 1.0     State C: CUT BURN           State D: FIX EFFICIENCY
                        Both metrics are bad.       Cash is fine but capital
                        Cost cuts first, growth     is not producing growth.
                        cuts second. Survival       Diagnose channel mix and
                        before strategy.            pricing before more spend.

State A (raise now). Strong efficiency, weak runway. Investors fund efficient businesses; the burn multiple story is the lever. Begin a fundraise immediately and target close before runway drops below 4 months. Do not let runway erode further trying to lift the burn multiple from 0.9 to 0.6; the marginal improvement is not worth the calendar cost, and a founder raising with only a few months of cash negotiates from weakness.

State B (scale). Strong efficiency, healthy runway. The business has earned room to invest. Increase acquisition spend or hire the next role. Watch the burn multiple monthly; if it deteriorates as spend rises, the new spend is not pulling its weight. Stay in this state until either burn multiple drifts above 1.5 or runway drops below 12 months.

State C (cut burn). Weak efficiency, weak runway. Cost cuts are the only intervention that changes both metrics simultaneously. Cut burn first, growth second. Fundraising is unlikely to succeed at these metrics; even if it does, it locks in a low valuation. Most companies that survive State C do so by becoming smaller and more focused, not by raising bridge capital.

State D (fix efficiency). Weak efficiency, healthy runway. The luxury state for diagnosis. Use the runway buffer to investigate why burn is not producing growth. Common causes: wrong channel mix, underpriced product, sales hire who is not productive yet, expensive features serving small user segments. The Burn Multiple Calculator alongside the Startup Runway Calculator handles the recompute as you adjust inputs.

6. Weekly cadence: what to actually look at

Both metrics are best read on monthly granularity with weekly check-ins on the inputs. Daily tracking is noise; quarterly tracking is too slow to catch a deteriorating signal before runway compresses.

Weekly inputs to watch (5 minutes per week):

• Cash balance, current and projected to end of month.
• Net new ARR booked this week (deals closed minus churn and contraction).
• Spend run-rate vs plan (variance over 10% in either direction needs investigation).
• Pipeline coverage for the next 30 days (deals weighted by expected close probability).

Monthly closes (30 minutes per month):

• Compute trailing-3-month average burn.
• Compute trailing-3-month net new ARR.
• Burn multiple and runway, both written down with the prior month for comparison.
• Map current state on the 2x2 matrix.
• Review last month's decisions against the 2x2 prescription. Did you actually do what the matrix said?

The discipline of writing down the state and the prescription monthly is the largest single value of the system. Founders who only compute the metrics in moments of stress make decisions about both growth investment and cost cuts at exactly the wrong times. The monthly cadence forces decisions in the right state of mind.

7. Worked example: the same business across four quarters

One bootstrapped SaaS, four quarters of operation, both metrics tracked together.

Quarter | Cash    | Net burn/mo | Net new ARR/mo | Burn Multiple | Runway   | State
Q1      | $180k   |  $14k       |  $9k           |   1.6         |  12.9 mo | D - Fix efficiency
Q2      | $135k   |  $15k       |  $13k          |   1.2         |   9.0 mo | D - Fix efficiency
Q3      | $90k    |  $15k       |  $18k          |   0.83        |   6.0 mo | A - Raise now
Q4      | $215k   |  $22k       |  $26k          |   0.85        |   9.8 mo | B - Scale

Reading the table.

Q1: 12.9 months runway looks healthy. Burn multiple of 1.6 says the business is in State D, fix efficiency. The founder has runway to diagnose. Investigation shows two underperforming channels (paid LinkedIn at $1,200 CAC, paid Google with poor landing-page conversion) consuming $5k/month with thin contribution.

Q2: Cuts on the underperforming channels and a small pricing change move burn multiple from 1.6 to 1.2. Runway has compressed to 9.0 months because cash kept falling while the changes took effect. State remains D but improving.

Q3: Pricing change has flowed through to net new ARR. Burn multiple drops to 0.83 (efficient). Runway has compressed to 6 months because cash continued depleting during the lag period. State is now A, raise now. Founder begins fundraising on a clean efficiency story; the burn multiple trend is the pitch.

Q4: A $170k seed extension closed at the end of Q3, so Q4 opens with $215k (the $90k Q3 balance, less $45k of Q3 burn, plus $170k). Burn multiple holds at 0.85 because the new capital is being deployed proportionally with new ARR. Runway returns to 9.8 months. State is now B, scale. The founder can hire the next role or expand into a second channel.

The same business looking at runway alone would have read Q1 (12.9 months) as fine, missed the inefficient burn signal, and arrived at Q3 (6 months) in panic. The same business looking at burn multiple alone would have read Q3 (0.83) as healthy, missed the cash compression, and entered fundraising weak. Together, the metrics produce three distinct correct decisions across the four quarters.

8. How investors read the two together

For seed and Series A diligence, expect to be asked for both metrics: runway says how long the company can wait for a deal, and burn multiple says whether more capital would produce growth.

What investors look for, paired:

• Burn multiple trending down over the last four quarters. The trend matters more than the absolute level. A burn multiple moving from 2.5 to 1.2 over four quarters is more attractive than a flat 1.2.
• Runway above 6 months at conversation start. Below 6 months, the founder is operating from weakness. Investors price the desperation into the round.
• Net new ARR not concentrated in single deals. Burn multiples that look healthy because of a single annual contract get heavily discounted. Investors normalize for deal-size variance.
• Clear story for what the next dollar of capital does to burn multiple. "We will hire two more AEs and burn multiple will hold at 1.0" is a defensible plan. "We will hire and figure it out" is not.

9. Mistakes founders make tracking either metric alone

• Tracking runway only and scaling spend right up to the wall. Runway compresses linearly until it does not. Sudden churn events, lost deals, or category downturns can chop 4 months off a 12-month runway in a single quarter. The burn multiple metric catches this earlier because it measures whether burn is producing growth, not just whether cash exists.
• Tracking burn multiple only and missing cash-survival pressure. A 0.6 burn multiple feels excellent, but if runway is 4 months and a fundraise will take 5 months, the business runs out before it can capitalize on the efficiency story. Burn multiple without runway is competence on a path to insolvency.
• Single-month readings on either metric. Both metrics are meaningful only on rolling 3-month bases. A single-month spike in churn produces a misleading burn multiple; a single month of high billings (annual contracts arriving) produces a misleading runway. Trailing-3-month averages stabilize both.
• Ignoring negative net new ARR. When churn and contraction exceed gross adds, net new ARR is negative and burn multiple is undefined. Founders sometimes report it as "infinite" or "n/a" and move on. The right response is to flag it explicitly as a churn problem and stop computing burn multiple until net new ARR is positive again.
• Treating burn multiple bands as universal. A 1.5 burn multiple is fine at $50k MRR and a problem at $5M ARR. The bands are starting points; calibrate to your stage, category and funding.
• Cost cuts that destroy efficiency. Cutting marketing spend lowers burn but often raises burn multiple if revenue growth slows more than burn falls. Always re-run both metrics after a cost cut; if burn multiple worsens, the cut was in the wrong place.
• Personal-runway not stacked underneath business runway. The business going to zero and the founder going to zero are not the same event. A 12-month business runway with 0 personal cash buffer behind it is materially riskier than a 6-month business runway with 12 months of personal reserves. Track both, separately.

Runway alone tells you a deadline. Burn multiple alone tells you a velocity. The combination tells you which decisions to make and in which order. The discipline of computing both monthly, mapping to the 2x2, and writing down the prescribed action turns weekly cash anxiety into a structured operating cadence. Most cash-flow surprises in early-stage companies are foreseeable from the prior two quarters of these metrics; the surprise is usually that no one was reading them.