Default Alive or Default Dead: How to Tell Which You Are

"Default alive or default dead?" is the single most useful question Paul Graham ever put to founders — and most can't answer it, which is the whole problem. It asks whether your startup, on its current growth and spending path, will reach profitability before the cash runs out. Not whether you could survive if you raised again. Whether you survive if you don't.

This page is the test, the trajectory math that separates it from a plain runway number, the named diagnostic for when default dead is actually fine, and three real 2026 cases that land on three different verdicts.

Want to run the numbers on your phone? Framework for iPhone & iPad ships a finance worksheet — drop in cash, burn, and growth rate and see your profitability-vs-runway crossover. Or start with the Cash Runway Formula and Burn Rate explainers.

What default alive and default dead mean

Paul Graham coined the terms in a 2015 essay. The definitions are deceptively simple:

State	Definition	The honest reading
Default alive	On current growth and burn, you reach profitability before cash runs out	You control your own survival; a raise is an accelerator, not a lifeline
Default dead	On current growth and burn, cash runs out before you reach profitability	Your survival depends on someone else saying yes — to a raise, an acquisition, or a backer's injection

The word that does all the work is default. It means "if nothing changes." Founders constantly answer the wrong question — "could we survive?" — to which the answer is always yes, because you can always imagine a raise. Graham's question strips out the imagined rescue and asks what happens on the path you're actually on.

Why this is not the same as runway

Runway is a snapshot: cash ÷ net burn, holding everything constant. Default alive is a trajectory: it asks whether your growth curve crosses your cost curve before the runway snapshot expires.

The difference is decisive, and a single example shows why. Take two startups, each with $2M in the bank and each burning $200K net per month. Both have an identical 10-month runway.

	Startup A	Startup B
Cash	$2M	$2M
Net burn (now)	$200K/mo	$200K/mo
Runway (static)	10 months	10 months
Monthly revenue growth	+15%	~0%
Net burn in 6 months	shrinking toward zero	still $200K
Verdict	Default alive	Default dead

Same runway, opposite fates. Startup A's revenue is climbing fast enough that net burn shrinks every month — it crosses into profit around month 8, before the cash is gone. Startup B's flat revenue means the 10-month runway is the whole story, and month 11 is a wall. Runway tells you how long you have; default alive tells you whether that's long enough. Reading runway without the growth rate is the most common way founders fool themselves into feeling safe.

How to tell which you are (5 steps)

1. Take current monthly revenue and its growth rate. Use the trailing 3-month average growth, not a single hot month.
2. Project revenue forward, month by month. Compound the growth rate. Be honest that growth rates decay as you get bigger.
3. Project expenses forward, including planned hires. A hire you've committed to is a cost even before they start. This is where optimistic founders cheat.
4. Find the crossover month — the first month projected revenue exceeds projected expenses. That's your profitability date.
5. Compare it to your runway. If profitability lands before cash hits zero, you're default alive. If runway runs out first, you're default dead — and now you know by how much, which tells you how much to cut or raise.

Graham's essay ships a calculator that does exactly this with a growth-rate slider. The output that matters isn't the date — it's the gap. A default-dead company that's two months short is a different problem from one that's two years short.

The Default-Dead-by-Design Test

Here's the synthesis Graham's original essay gestures at but never names: being default dead is not automatically a death sentence. The world's most valuable private companies are default dead on purpose. What separates a legitimate strategy from a slow-motion failure is intentionality plus a funded bridge. Run any default-dead company through three yes/no questions:

#	Question	Why it matters
1	Did you choose to be default dead to capture a market faster than profitability allows?	An accident you haven't noticed is the most dangerous state of all
2	Is the bridge funded — do you have committed capital or a backer who will fund the gap to profitability?	Intent without capital is just hope; the gap has to be someone's commitment
3	Is the trajectory real — is revenue actually growing fast enough that profitability is a date, not a someday?	A funded bridge to nowhere still ends at nowhere

Three yeses: default dead by design — a defensible strategy. Two or fewer: you are default dead by accident, and the gap between you and the giants isn't ambition, it's that you skipped one of these and didn't notice. The test works because it isolates the only thing that makes outspending revenue survivable — a deliberate choice backed by committed capital and a real growth curve — from the thing that looks identical from the outside but kills you: drift.

Three real cases, three verdicts

Figma — default alive

By its 2025 IPO S-1, Figma was unambiguously default alive: FY2025 revenue of roughly $1.06B (growing ~40% year over year), non-GAAP operating income of $129.5M (a 12% margin), and adjusted free cash flow of $242.7M — a 23% margin. It held $1.7B in cash it did not need to touch, and posted a Rule of 40 score of 74, the second-highest among public cloud companies. Figma generates more cash than it spends. For a default-alive company, a raise (or in Figma's case, a public listing) is an accelerant, not oxygen — which is exactly why it could go public from a position of strength rather than need.

OpenAI — default dead by design

OpenAI is the textbook case of passing all three Default-Dead-by-Design questions. It is nowhere near profitable: it expects to burn about $8B in 2025, more than doubling to $17B in 2026, on the way to a reported $115B in cumulative burn through 2029. That is default dead by any static reading. But (1) it is deliberate — outspending revenue to win the AI platform race; (2) the bridge is funded by some of the largest capital commitments in private-market history; and (3) the trajectory is real — annualized revenue crossed ~$12B in 2025, roughly doubling inside the year, with cash-flow positivity targeted for 2029 on projected revenue above $125B. Three yeses. OpenAI is default dead and that is the plan, not the problem. The only thing that turns this strategy fatal is if the trajectory stalls before the bridge runs out.

Humane — default dead by accident

Humane is the warning. The AI-hardware startup raised about $230M from backers including Sam Altman and Marc Benioff, shipped the AI Pin to scathing reviews in April 2024, and was sold to HP for $116M in assets in February 2025 with the device discontinued. It had capital — it failed question 3. There was no real trajectory: no retention, no organic pull, no growth curve bending toward profitability. A funded bridge to a market that wasn't there still ends where the market isn't. Money bought runway; it could not manufacture the trajectory that makes default dead survivable.

When the question misleads

• Pre-product-market-fit, the growth rate is noise. Before product-market fit, your revenue growth is too erratic to project — the crossover math is built on a number you don't really have. Get to PMF first; then the default-alive question becomes answerable. See product-market fit examples.
• A committed backer changes the question entirely. For a sovereign-backed or strategically-backed company, the static math is almost beside the point — the real question is "how long until the next injection, and on what terms?" (the Lucid case in our runway guide).
• Decaying growth breaks naive projections. Compounding a 15% monthly growth rate forward for two years produces a fantasy. Growth rates fall as you scale; model the decay or your "default alive" verdict is fiction.

Common default-alive mistakes

Mistake	Why it happens	Fix
Answering "could we survive?" instead of "will we?"	You can always imagine a raise	Strip out the imagined rescue; ask what happens if you don't raise
Using runway without the growth rate	A runway number feels concrete and safe	Always read runway next to monthly growth — they're one question
Compounding today's growth rate forever	Optimism plus a spreadsheet	Decay the rate as revenue scales; sanity-check the 24-month figure
Excluding committed-but-unstarted hires from the burn forecast	They're "not costs yet"	A signed offer is a cost; put it in the projection
Assuming default dead means failing	The label sounds terminal	Run the Default-Dead-by-Design Test — intentional + funded + real trajectory is a strategy

Related reading

Default alive is the trajectory read on the same numbers Framework's finance cluster covers statically:

• Cash Runway Formula — the static calculation, gross vs net burn, and the Runway Triangle
• Runway — the 18 / 12 / 6-month thresholds and what founders do at each
• Burn Rate — gross vs net burn and the Burn Multiple
• Rule of 40 — the growth-plus-profit efficiency read Figma scored 74 on
• Product-Market Fit Examples — why the default-alive question is unanswerable before PMF

When runway tightens and you're default dead by accident, RICE scoring is the standard tool for deciding which bets survive the cut.

---

Run your trajectory: Framework's iOS app keeps cash, burn, growth rate, and the profitability crossover in one finance worksheet. Get it on the App Store.

Sources

• Paul Graham — "Default Alive or Default Dead?" (2015)
• Figma, Inc. — Form S-1, FY2025
• Yahoo Finance — "OpenAI's own forecast predicts $14 billion loss in 2026 but $100 billion revenues by 2029"
• Business Today — "OpenAI Raises Cash Burn Projection To US$115 Billion Through 2029"
• The Verge — "HP buys Humane, will discontinue the AI Pin"