Burn Rate

The rate at which a startup spends cash, split into gross and net burn: the figure that turns a bank balance into a deadline.

A startup spends money it does not yet earn, and the speed of that spending decides almost everything about its timeline. Burn rate is the name for that speed. It converts a bank balance into a countdown: how long the company has, when it must raise, and whether the spending is buying anything worth the money. A founder who can’t state burn rate from memory is driving without a fuel gauge.

What It Is

Burn rate is how much cash a company consumes in a month. It comes in two forms, and conflating them is the most common way the number lies.

Gross burn is total cash going out the door: payroll, rent, software, cloud bills, everything. Net burn is gross burn minus the cash coming in from revenue. The gap between them is the whole story of a company’s progress toward sustainability.

gross burn = total monthly cash out
net burn   = gross burn − monthly revenue

A company spending $300K a month with $100K of monthly revenue has a gross burn of $300K and a net burn of $200K. Net burn is the number that matters for survival, because revenue extends the company’s life as surely as fresh capital does. It’s also the denominator of runway: cash on hand divided by net burn is the number of months remaining. Gross burn still matters as a worst-case figure, the speed at which the cash would drain if revenue vanished tomorrow. A pre-revenue company watches gross and net burn as the same number until the first dollar of revenue arrives.

Two distinctions separate an honest burn figure from a flattering one. First, burn is rarely flat. A company that just raised and is hiring against the plan will see burn climb month over month, so last month’s number understates where the spending is headed. The useful version projects the burn curve forward rather than freezing today’s number.

Second, burn is a cash concept, not an accrual-accounting one. It tracks money actually leaving the account, not expenses booked on a schedule. A company can post a small accounting loss while burning cash fast, because a large annual software contract paid up front hits the bank balance long before the income statement spreads it across twelve months.

Why It Matters

Burn rate governs the fundraising clock, and the fundraising clock governs the rest. Because runway is just cash divided by net burn, burn is the survival input a founder controls most directly. Cutting burn buys time without raising a dollar. Letting it climb spends time the company may not be able to replace. A team that grows revenue from zero to $80K a month has cut its net burn and lengthened its runway as surely as if it had closed a small round.

The three readers come at the number from different seats. A founder reads burn rate as the throttle: how aggressively can the company spend before the next milestone, and what does each new hire cost in weeks of runway. For an investor, net burn is both a risk gauge and a discipline signal. If burn climbs faster than the metrics that would justify the next round, it is the clearest early sign of premature scaling, and a fund will often size its follow-on reserve against that risk. The talent reader, an engineer or operator weighing an offer, reads burn against the bank balance as the bluntest measure of how long the job is funded before the company must raise, reach profitability, or cut.

What the concept gives a practitioner is the ability to value a spending decision in the currency that actually constrains the company. “We’re hiring two engineers” is an org-chart statement. “We’re adding $60K to monthly net burn, which trims four months off the runway, in exchange for shipping the feature the Series A story needs” is a financial one. Only the second framing lets a founder decide whether the trade is worth it.

How to Recognize a Burn Rate You Can Trust

A burn figure earns trust when it’s net, projected forward, and attached to what the spending is supposed to produce. The signs that a number is real rather than decorative:

• It’s net burn, not gross spend. Quoting gross burn while counting revenue somewhere else is the most common way founders overstate how fast the cash is really leaving.
• It projects the curve, not last month. A burn rate frozen at a single trailing month during a hiring ramp will always understate where the spending is headed.
• It’s paired with what it buys. Burn in isolation says nothing about health. The question is always burn toward what? Name the milestone the spending is meant to reach before the runway closes.
• It separates one-time from recurring. A month that included an annual insurance premium or a conference sponsorship isn’t the company’s true run-rate burn, and treating it as one distorts the runway in both directions.

Benchmarks help only when they’re read against the company’s stage and sector, because burn is not a virtue or a vice on its own. The rough 2025–2026 frame for venture-backed software companies is a starting boundary, not a rule. Pre-seed teams commonly run net burn in the low tens of thousands per month, often under $50K while the team is small and pre-revenue. Seed-stage companies typically run $50K to $150K as the first hires land. A Series A company is frequently in the $200K to $500K range as it builds out a go-to-market motion.

The figures travel poorly across business models. A hardware or biotech company burns far more for far longer before revenue than a SaaS company at the same stage, and a deep-tech team with heavy compute or wet-lab costs sets its own baseline. Treat any single benchmark as a prompt to ask why this company sits where it does, not as a target to hit.

The 2025–2026 shift worth dating runs through the team-size line. Because payroll is the largest component of burn for most early-stage software companies, the AI-driven move toward smaller teams reaching the same milestones shows up first as lower burn at a given stage. As lean team economics argues, some AI-native teams now reach revenue milestones at a fraction of the headcount, and therefore a fraction of the burn, that the 2020-era playbook assumed. The countervailing force is that AI infrastructure cost is itself a fast-growing burn line, so a lean team can trade salary burn for compute burn rather than eliminate it. The directional signal is real; the magnitude is still moving, and the figure to watch is total net burn at a milestone, not headcount alone.

How It Plays Out

The failure is quiet and common. A seed-stage team raises $2M, feels flush, and hires against the eighteen-month plan the round was sized for. Gross burn climbs from $90K a month to $180K within two quarters as the engineers, a head of sales, and an office come online. Revenue is real but small, so net burn lands near $160K. The founders are still anchored to the runway they computed the day the money landed, but the runway recomputed on the new burn is closer to twelve months, then nine. By month nine they have neither the metrics to raise a Series A nor the time to raise anything before the cash is gone. Nothing dramatic happened. The spending simply outran the burn figure the founders were still quoting from memory.

The disciplined version looks different in a way investors notice. A founder closes the same $2M and treats net burn as the binding constraint from the first hire. Each new role is costed in months of runway before the offer goes out, the burn curve is modeled three ways against the milestone it has to reach, and spend increases are gated behind evidence. The company can begin raising its Series A while a year of runway remains. When the funding market tightens, this founder is raising from evidence and time rather than scrambling, because the burn rate was managed as a deliberate throttle rather than discovered as a surprise. The cash balance was identical. The outcome wasn’t, and the difference was entirely in whether the burn was decided or merely observed.

Consequences

Treating burn rate as a managed throttle rather than a monthly readout changes which spending a company is willing to commit to and when.

Benefits. A team that watches net burn in real time converts every spending decision into a runway decision, which makes hiring and budgeting legible instead of intuitive. It can answer the question every board and prospective investor eventually asks: how fast are you burning, and toward what? Arithmetic reads better than optimism. And because burn is the input a founder controls most directly, a team that manages it can extend its own life under pressure without waiting on anyone else to act.

Liabilities. Burn is only as honest as the assumptions beneath it, and the assumptions are easy to flatter. Typical distortions include a flat-burn projection during a hiring ramp, a gross figure quoted while revenue is netted elsewhere, or a one-time cost smoothed into the run-rate or out of it depending on which tells the better story. The number can also become a fetish in the other direction. A team that drives burn toward zero by starving the hiring or marketing that would compound has bought months at the cost of the milestone those months were meant to reach. A low burn rate next to a flat growth curve reads to an investor as under-investment, not discipline. Low burn is survival, not progress. A company can hold its burn admirably low and still be building something nobody wants. Burn rate measures how fast the cash leaves, never whether it’s buying anything worth having.

Related Articles

Sources

• Paul Graham, “Default Alive or Default Dead?” (2015) — the essay that tied burn and revenue growth together into the sharper question of whether a company’s own trajectory reaches profitability before the cash runs out.
• David Sacks, “The Burn Multiple” (2020) — the essay that took the net-burn figure and turned it into the working measure of how efficiently that burn buys new revenue.
• The 2025–2026 net-burn ranges by stage and the sector caveats (hardware, biotech, and deep tech setting their own baselines) reflect the venture-finance benchmarks reported across the period; read the figures as a directional 2025–2026 frame rather than fixed standards, since they move with the cost of capital and with the AI-driven shift in team size.