Default Alive vs Default Dead: The Startup Survival Test

Default alive and default dead describe whether a startup will reach profitability on its current growth rate and spending before its cash runs out. A company is default alive if it gets to breakeven with the money it has, and default dead if, on the present trajectory, it runs out first.

The framing comes from Paul Graham, and its power is that it collapses a founder's whole financial situation into a single yes-or-no question. It is not a vanity metric or a slide for investors; it is the fastest way to know whether you are building on solid ground or quietly heading for a wall. Knowing your status changes what you do this quarter - and most founders discover it far too late.

What Does Default Alive vs Default Dead Actually Mean?

Default alive means that if your growth rate and your expenses stay exactly as they are today, your revenue crosses your costs - you become profitable - before the money in the bank is gone. You do not need to raise again to survive. Default dead means the opposite: on the current trajectory, you run out of cash first, so survival depends on either raising more money or changing the trajectory.

The word "default" is load-bearing. It describes the outcome you drift toward if nothing changes - not your best case, not the plan on the deck, but the path you are actually on. A default dead company can absolutely become default alive; it just will not happen by accident. The label is a starting position, not a verdict.

• Default alive: current growth + current burn -> profitable before cash zero. You control your own fate.
• Default dead: current growth + current burn -> cash hits zero first. You are dependent on a raise or a change.

Crucially this is a question about your present numbers, not your projections. Anyone can be default alive in a spreadsheet where growth accelerates and costs hold flat. The honest calculation uses the growth rate you have actually posted for the last few months and the spending you are actually doing now.

How Do You Calculate Whether You Are Default Alive?

You need four inputs: current cash in the bank, current monthly revenue, current monthly expenses, and your recent monthly revenue growth rate. The mechanic is simple to state and slightly fiddly to compute: project revenue forward at your current growth rate, hold expenses roughly flat (or grow them the way you realistically will), and check whether cumulative revenue overtakes cumulative spend before the cash balance crosses zero.

If revenue reaches your expense line while you still have money left, you are default alive. If the bank account empties first, you are default dead. Graham built a graph for exactly this - it plots your projected path and shows whether the profitability line arrives before the cash-out line.

Two things make the calculation more truthful:

• Use a real, recent growth rate. Average the last three to six months, not your best month or your board-deck forecast. Growth that has decayed for two straight months is your real rate.
• Model expense creep honestly. If you plan to hire, the flat-expense assumption is a fantasy. A more useful version holds hiring flat and asks whether you are default alive without adding headcount - because that is the version you can actually control.

This is a close cousin of the work in how much runway you need before fundraising and of efficiency measures like the burn multiple. Runway tells you how long you last at a fixed burn; default alive asks the harder question of whether growth outruns burn before that runway expires.

What Is the Fatal Pinch, and Why Is It So Dangerous?

The fatal pinch is Graham's name for the specific trap that kills default dead companies: you are default dead, you have a few months of runway left, and you have not yet raised more money. Founders in this state almost always believe they will be saved by a fundraise. Usually they are wrong, because the very situation - low growth, dwindling cash - is what makes investors decline.

The danger is that the pinch feels survivable from the inside. Revenue is still coming in, the team is shipping, and next month always looks like the month growth reaccelerates. Meanwhile each week that passes shortens the runway that a new investor would need to see, which makes the raise harder, which shortens the runway further. It is a doom loop disguised as a rough patch.

Graham's blunt prescription for the fatal pinch: the only reliable escape is to reach ramen profitability, and the fastest lever is usually cutting costs, not hoping for a raise. A company that convinces itself the next round is imminent tends to keep spending at the exact moment it should be extending its life.

Default Alive vs Default Dead: What Changes for the Founder?

The two states demand different behavior. Treating a default dead company as if it were default alive - spending freely, hiring ahead of revenue, assuming the next round - is how startups walk off a cliff while feeling fine.

The most important consequence is negotiating leverage. A default alive company raises because it wants to; a default dead company raises because it has to, and investors can smell the difference. If you must raise, do it while the numbers still let you tell a story of strength - the guide on how to show traction to investors covers what that story needs to contain.

What Do You Do If You Are Default Dead?

You have exactly two levers, and they are not equally reliable. You can grow revenue faster, or you can cut expenses. Founders instinctively reach for the first because it is the happier story, but growth is slow and uncertain, while cost cuts are fast and fully within your control.

1. Cut costs to buy time. The quickest way to move toward default alive is to lower the expense line - it extends runway immediately and pushes your breakeven point closer. This is the lever Graham points to for the fatal pinch precisely because it does not depend on anyone else's behavior.
2. Grow faster, if you credibly can. If you have a channel that is genuinely working and more spend or focus would accelerate it, growth can flip you to default alive without shrinking. But be honest about whether the growth is real and repeatable or a hope.
3. Raise - but from as much strength as you can manufacture. If you raise, treat it as a bridge to profitability, not a lifestyle. Raise enough to reach default alive, then get there, so you never have to raise from the fatal pinch again.

The best default dead companies attack costs and growth at once: trim the burn to extend the clock, and pour the saved focus into the one channel that is working. The worst do neither and wait for the market to change.

Why Do Founders Find Out Too Late?

The cruelest feature of default dead is that it is invisible from the cockpit. Revenue is growing, the team is busy, and the bank balance is still positive - every dashboard says things are fine. The problem is that "fine" is a snapshot, and default alive is a question about the trajectory, which no single snapshot reveals.

Graham's observation is that founders often cannot even answer whether they are default alive or default dead when asked - and that not knowing is itself a warning sign. The calculation should be a standing number every founder recomputes monthly, the same way you watch cash. When you only run it during fundraising, you learn your status at the worst possible moment: when it is too late to fix cheaply.

The fix is a ritual, not a tool. Recompute default alive status every month against your real, recent growth and burn. The moment the profitability line drifts past the cash-out line, you are default dead again - and the earlier you see it, the cheaper the correction.

A Worked Example

Take a startup with $600,000 in the bank, $50,000 in monthly revenue, $90,000 in monthly expenses, and revenue growing 10 percent month over month. Today it burns $40,000 a month, so a naive runway reading says 15 months.

But run the default alive question. Revenue grows 10 percent monthly: $50k, $55k, $60.5k, and so on. It crosses the $90k expense line around month 7 (roughly $88.6k in month 7, $97.4k in month 8). By the time revenue overtakes expenses, cumulative burn has consumed a large share of the $600k, but the cash line has not hit zero - so this company is default alive, with a thin margin.

Now change one input: growth is 3 percent, not 10 percent. Revenue reaches only about $62k by month 15, still $28k under expenses, and the $600k is gone before profitability arrives. Same cash, same starting revenue - but at 3 percent growth the company is default dead. The single variable that flips the verdict is the growth rate, which is exactly why "how much runway do I have" is the wrong question and "does growth beat burn before the cash runs out" is the right one.

TL;DR

• Default alive = on current growth and spend, you reach profitability before cash runs out. Default dead = you run out of cash first.
• It is about your trajectory, not a snapshot - use your real recent growth rate and current burn, not projections.
• The fatal pinch is being default dead, low on runway, and not yet raised - the doom loop where waiting on a raise makes the raise harder.
• If default dead, cut costs first (fast, fully in your control), grow faster if the growth is real, and raise only to bridge to default alive.
• Default alive raises from strength; default dead raises from weakness - and investors can tell the difference.
• Recompute monthly. Founders who only check during a raise learn their status too late to fix it cheaply.

FAQ

What Does Default Alive vs Default Dead Mean?

A startup is default alive if, on its current growth rate and current level of spending, it will reach profitability before it runs out of money - meaning it can survive without raising again. It is default dead if, on that same trajectory, its cash runs out before it becomes profitable, so survival depends on raising more money or changing the trajectory. The word "default" is key: it describes the outcome you drift toward if nothing changes, not your best-case plan.

How Do You Calculate Whether a Startup Is Default Alive?

Take four numbers: current cash, current monthly revenue, current monthly expenses, and your recent monthly revenue growth rate. Project revenue forward at that growth rate, hold expenses roughly flat, and check whether revenue overtakes expenses before your cash balance hits zero. If profitability arrives while money is still in the bank, you are default alive; if the cash runs out first, you are default dead. Use a real growth rate averaged over the last three to six months, not a forecast.

What Is the Fatal Pinch?

The fatal pinch is Paul Graham's term for being default dead, having only a few months of runway left, and not having raised more money yet. It is dangerous because founders in it usually assume a fundraise will save them, but their weak growth and shrinking cash are exactly what makes investors decline. Each week that passes shortens the runway and makes the raise harder, creating a doom loop. Graham's advice is to escape by cutting costs to reach profitability rather than betting on a rescue round.

What Should You Do If Your Startup Is Default Dead?

You have two levers: grow revenue faster or cut expenses. Cutting costs is usually the better first move because it is fast and fully within your control, while growth is slow and uncertain. Trim the burn to extend your runway and push breakeven closer, and pour saved focus into the one channel that is genuinely working. If you raise, treat it as a bridge to reach default alive, not a lifestyle - raise enough to become profitable so you never face the fatal pinch again.

How Does Default Alive Relate to Fundraising?

Default alive companies raise from strength: they do not need the money, so they can raise to grow faster on good terms or walk away. Default dead companies raise from weakness, and investors can sense the difference, which produces worse terms or a failed round. The practical rule is to raise while your numbers still tell a story of strength, and to raise enough to reach default alive, so your next raise is a choice rather than a survival requirement.