The Rule of 40 says a healthy SaaS company's revenue growth rate plus its profit margin (usually EBITDA margin, sometimes free cash flow margin) should add up to 40% or more. A company growing 50% year over year with a -15% margin passes (35... actually fails narrowly at 35%); a company growing 20% with a 25% margin passes comfortably at 45%. The appeal is real: it's a single number that captures the fundamental SaaS trade-off between growth and profitability, so investors and boards don't have to argue growth-stage companies down to an arbitrary profit target while they're still supposed to be spending on growth.
Why growth and margin are treated as substitutes
The Rule of 40's core insight is that a fast-growing, unprofitable company and a slower-growing, profitable one can both be executing well, and the metric is trying to say "the specific mix doesn't matter as much as the sum." This is a useful corrective to boards that reflexively demand profitability from an early-stage company still in a land-grab phase of its market, where every dollar spent on growth this year is worth more than the same dollar saved — as long as the growth is actually efficient, not just expensive.
WITH yearly AS (
SELECT
DATE_TRUNC('year', invoice_date) AS yr,
SUM(revenue) AS revenue,
SUM(revenue) - SUM(total_opex) AS ebitda
FROM finance_ledger
GROUP BY 1
)
SELECT
yr,
ROUND((revenue - LAG(revenue) OVER (ORDER BY yr))
/ NULLIF(LAG(revenue) OVER (ORDER BY yr), 0) * 100, 1) AS growth_pct,
ROUND(ebitda / NULLIF(revenue, 0) * 100, 1) AS margin_pct
FROM yearly
ORDER BY yr;
A screening heuristic, not something to optimize for directly
The Rule of 40 was designed as a quick filter for investors comparing many companies, not as an internal target a management team should steer toward directly — because a company can hit 40 in ways that are healthy (efficient growth, genuine margin improvement) or hollow (cutting R&D to hit a margin number this quarter, or juicing growth with unsustainable discounting). Treating the sum itself as the goal invites exactly the kind of gaming that makes any single composite metric eventually stop measuring what it was meant to measure.
Rule of 40 = revenue growth rate % + profit margin %, using consistent definitions of both across any comparison — ARR growth vs. margin as a fraction of ARR, or GAAP revenue growth vs. GAAP margin, but not one metric's ARR-based growth mixed with the other's GAAP-based margin. Mixing definitions produces a number that looks precise and means nothing.
Company stage changes what "40" should mean
A five-year-old company at $2M ARR growing 150% with deeply negative margins is in a completely different situation than a $50M ARR company growing 25% with 15% margins, even if both clear 40 on paper. Early-stage companies should lean almost entirely on the growth side of the equation, since margin at that stage is often more a function of how much has been raised than of underlying business efficiency; later-stage companies are reasonably expected to show the margin side improving as growth naturally decelerates with market size.
What the Rule of 40 doesn't tell you at all
It says nothing about the quality of the growth (net revenue retention, churn, customer concentration), nothing about the cash runway required to sustain the growth-heavy end of the trade-off, and nothing about unit economics at the customer level. A company can pass the Rule of 40 while burning through a fixed amount of cash that runs out before the growth compounds into profitability — the rule is a health screen on the income statement's shape, not a substitute for reading the cash flow statement.
Growth rate mechanically decelerates as ARR scales — doubling from $1M to $2M is a very different operational feat than doubling from $50M to $100M. Comparing two companies' Rule of 40 scores without normalizing for scale conflates "smaller companies grow faster" with "this company is executing better."
Wrapping up
The Rule of 40 is a useful single-number screen for whether a SaaS company's growth-versus-profitability trade-off looks healthy in aggregate, and a poor target to manage toward directly, since the sum can be hit by cutting the wrong things as easily as by genuine efficient growth. Read it alongside net revenue retention, cash runway, and unit economics rather than treating 40 as the whole story.
Independent software engineer in Nairobi specialising in Acumatica customisations, Laravel backends, and tax fiscalisation integrations across East and Southern Africa.