Growth vs Profitability: How Startups Balance the Two
Turn this article into takeaways for your work.
Each assistant summarizes the article only for you and suggests best practices for your work.
Every young company eventually faces the same question. Do you spend money to grow faster, or hold back and make money now? Neither answer is right everywhere. The trade-off is real, it changes with the business and its stage, and most of the useful thinking on it comes down to a few simple tests.
This article explains why venture-backed startups lean toward growth, when that logic breaks, and three tools founders and investors use to judge the balance: Paul Graham's default alive test, the Rule of 40, and the burn multiple. It also covers how the balance shifts as a company matures. If you're new to the early-stage vocabulary, a guide to the stages of a startup is a useful map first.
Why startups often choose growth
A normal small business can sensibly aim to be profitable from the start. A venture-backed startup usually can't, and usually doesn't want to. There are three common reasons.
Unit economics reward scale. If each customer is worth more than they cost to win, then adding customers adds value. When that's true, spending today to acquire customers is an investment, not a loss. The test is unit economics: if the maths works per customer, growing faster just means getting more of a good thing sooner.
Markets get captured. In some categories, the first company to reach a large share gets lasting advantages, such as brand, distribution, or supplier terms. A rival who waits to be profitable may find the good customers already taken.
Network effects favour the biggest. In marketplaces, social products, and platforms, each new user makes the product more valuable to the others. Being slightly ahead can snowball into a lead that's hard to close. The extreme version of this thinking is blitzscaling, which deliberately prioritises speed over efficiency.
All three arguments share a condition: the growth has to be buying something durable. That's also where the logic fails.
When the growth-first logic fails
"Grow now, profit later" is a bet, not a law. It tends to go wrong in a few recognisable ways.
- The unit economics were never good. If every customer costs more to serve and win than they ever pay back, growth deepens the loss. More volume makes a bad model worse.
- There's no real moat. If a competitor can copy the product and the customers aren't sticky, the market isn't "captured." It's rented.
- Growth is being bought, not earned. Paid acquisition can make a growth chart look healthy while the underlying demand is thin. When the spending stops, the growth stops.
- The funding isn't guaranteed. A plan that depends on raising the next round is exposed if the round doesn't come.
That last point is the heart of Paul Graham's framing, covered next. And a related warning sign is whether the company has found real demand at all. If it hasn't, speed isn't the fix; see product-market-fit explained before pouring in money.
Default alive or default dead
In his October 2015 essay Default Alive or Default Dead?, Paul Graham offers a simple test for a startup that hasn't reached profitability. He frames it as a question: assuming expenses stay constant and revenue growth is what it's been over the last several months, does the company reach profitability on the money it has left?
If yes, the company is default alive. If no, it's default dead. The test is useful because it replaces vague optimism with an arithmetic check using numbers the founders already have.
Two other points from the essay are worth keeping. First, Graham notes that if you have steep revenue growth, he gives "over 5x a year" as an example, you can start to count on investors being interested even if you're not profitable. But he adds that investors are so fickle you can never do more than start to count on them. Second, he observes there's surprisingly little connection between how much a startup spends and how fast it grows.
That second observation cuts against the reflex that more spending always means more growth. Graham also argues that the real problem for a default-dead company is usually the product, which is only moderately appealing, and that the answer is often doing things that don't scale or redesigning the product rather than simply cutting costs.
Here's a rough way to run the check yourself:
- Take your current monthly expenses and hold them flat.
- Project revenue forward using your recent growth rate.
- Find the month where revenue first covers expenses.
- Compare the cash you'd burn getting there with the cash you have.
If the cash runs out first, you're default dead on today's numbers. Your runway and burn rate are the two inputs doing the work.
Key Facts: Growth vs Profitability
- Graham's default alive test asks whether a company reaches profitability on its remaining cash if expenses stay constant and revenue grows at its recent rate (source).
- Graham writes that steep revenue growth lets you start to count on investor interest, but that investors are too fickle to count on fully (source).
- Brad Feld's version of the Rule of 40 says growth rate plus profit should add up to 40% (source).
- Feld credits the rule to a late-stage investor who called it the 40% rule, and applies it to SaaS companies at scale (source).
- David Sacks defines burn multiple as net burn divided by net new ARR (source).
The Rule of 40
The Rule of 40 is a shortcut for judging whether a company is balancing growth and profit sensibly. In his February 2015 post The Rule of 40, Brad Feld states it plainly: your growth rate plus your profit should add up to 40%. He credits it to a late-stage investor he met at a board meeting, whose firm called it the 40% rule, rather than claiming it as his own.
The point is that growth and profit are interchangeable up to a limit. Feld's examples: a company growing 20% should be making 20% profit, one growing 40% can break even, and one growing 50% can afford a 10% loss. He suggests using year-over-year MRR growth for the growth side and EBITDA for the profit side, and notes the profit definition can vary. He frames it for SaaS companies at scale, so it's a poor fit for a pre-revenue startup.
Here's a hypothetical worked example, with invented numbers, to show how the arithmetic works.
| Company | Growth rate | Profit margin | Sum | Meets the rule? |
|---|---|---|---|---|
| A | 60% | -15% | 45% | Yes |
| B | 25% | 5% | 30% | No |
| C | 10% | 30% | 40% | Yes |
Company A is losing money but growing fast enough to justify it. Company C grows slowly but is very profitable. Both pass. Company B is in the uncomfortable middle: not growing fast and not earning much, so neither story supports it.
The rule has limits. It's a blunt average of two very different things, and it says nothing about how long the cash lasts. A company can hit 40 with a growth rate that's about to collapse. For the SaaS-specific mechanics, including how to improve each side, see the deep dive on Rule of 40 optimization.
Burn multiple and efficient growth
The Rule of 40 works at scale. Earlier on, many startups have no profit margin worth measuring, so investors look at efficiency instead: how much cash does it cost to add each unit of growth?
David Sacks of Craft Ventures popularised the burn multiple in an April 2020 article, The Burn Multiple. He defines it as net burn divided by net new ARR. As a hypothetical example, if a company burns 2 million and adds 1 million of new annual recurring revenue in the same period, its burn multiple is 2.
Lower is better, because it means less cash consumed per dollar of new revenue. Sacks sets out benchmarks by stage and argues that the number should improve as a company matures, and that a worsening multiple signals trouble even when headline growth looks good. His specific thresholds are worth reading in the original rather than quoting second-hand here.
What the burn multiple captures is the idea of efficient growth: growing quickly without needing ever-larger piles of cash to do it. It also complements default alive. The burn multiple tells you how efficient today's growth is, and the default alive test tells you whether that efficiency is enough to survive.
How the balance shifts with stage
The right mix isn't fixed. It moves as the company and its funding situation change, and the shifts below are general patterns, not rules with numbers attached.
| Stage | Typical emphasis | Why |
|---|---|---|
| Idea and pre-seed | Learning, not growth or profit | The goal is finding a real problem |
| Seed | Early signs of demand and a believable model | Investors fund evidence of traction, not a finished P&L |
| Growth | Scaling what works, watching efficiency | Spending is justified only if unit economics hold |
| Mature | Profit and cash generation | Growth slows, so margin carries more of the weight |
The article on early-stage vs growth-stage covers how the questions change between the two. The common thread is that the cost of being wrong rises with spend. Early on, over-spending on a bad guess is survivable. Later, it can end the company.
Capital markets matter too. When money is easy to raise, burning for growth is cheap to finance, and when it's tight, investors ask harder questions about efficiency. A founder can't control that cycle, which is the practical argument for the default alive habit: know where you'd stand if no new money arrived.
A practical way to decide
Putting the tools together gives a short decision routine.
- Check the unit economics. Is each customer worth more than they cost to win and serve? If not, fix that before spending more.
- Run the default alive test. On current numbers, do you reach profitability before cash runs out?
- Measure efficiency. What's your burn multiple, and is it improving or getting worse?
- Apply the Rule of 40 once you're at scale. Does growth plus margin clear the bar?
- Ask what the spending buys. If it buys a moat, a network effect, or a durable customer base, it's investment. If it only buys a number on a chart, it isn't.
And if the answers disagree, trust the one that's closest to cash. A growth story can survive a lot of arguments. A bank balance of zero can't.
Related reading
