Updated 9 Jul 2026 • 5 mins read
The Rule of 40 Explained
The Rule of 40 says a healthy software company's revenue growth rate plus profit margin should total at least 40 percent. This guide covers the formula and margin variants, worked examples, how to improve each side, the criticisms worth knowing, and the lever finance often ignores: infrastructure and AI costs inside gross margin.
Software companies live under a permanent tension: grow fast, which burns money, or run profitably, which usually means growing slower, and the Rule of 40 is the industry's one-line answer to how much of each is enough. Add your revenue growth rate to your profit margin; if the sum clears 40 percent, the balance is considered healthy, whether you got there as a rocket losing money or a steady compounder printing it. Investors use it to compare wildly different companies on one axis, boards use it to frame strategy debates, and operators, increasingly, use it to justify the unglamorous work this blog cares about: the score has two halves, and infrastructure efficiency sits squarely inside one of them.
This guide covers the rule properly: the formula and its margin variants, worked examples, what moves each side, the criticisms that keep it honest, and the cloud-and-AI cost lever that finance teams too often leave off the table.
Key takeaway Rule of 40 = revenue growth rate (percent, year over year) + profit margin (percent), with free cash flow margin and EBITDA margin as the most common profitability choices, healthy at 40 or above. A company growing 60 percent while burning 20 percent of revenue scores 40; so does one growing 15 percent at a 25 percent margin: the rule prices the growth-profit trade explicitly. To improve it, work both sides, but do not overlook the operational half: for software companies, cloud and AI infrastructure is a major COGS line, so every point of infrastructure efficiency flows into gross margin and, from there, into the score, which makes FinOps a Rule-of-40 instrument, not just a cost hygiene program. Use the rule as a conversation, not a law: it is stage-dependent, gameable by short-term cuts, and silent about durability.
The Formula, and the Margin Question
The arithmetic is one line: Rule of 40 score = revenue growth rate + profit margin, both as percentages over the same period, typically trailing or forward twelve months. The nuance hides in which margin. Free cash flow margin is the investor favorite, cash is hard to flatter, and it credits the up-front-collection dynamics of good SaaS businesses; EBITDA margin is common in board reporting and comparable across capital structures; operating margin appears where consistency with public reporting matters. The honest rules: pick one definition, state it, and never switch mid-story, because a company can clear 40 on EBITDA and miss it on free cash flow, and the difference is exactly the kind of thing diligence exists to find. Growth, similarly, should be organic recurecurring revenue where possible, acquired revenue flatters the score without proving the machine.
Worked Examples
| Company profile | Growth rate | Profit margin | Score | Reading |
|---|---|---|---|---|
| Early rocket | 80% | -35% | 45 | Healthy: burn is buying growth efficiently |
| Scaling burner | 45% | -20% | 25 | Below bar: burn not converting to enough growth |
| Balanced grower | 25% | 18% | 43 | Healthy: the classic durable profile |
| Mature compounder | 12% | 30% | 42 | Healthy: profitability carrying the score |
| Stalled cutter | 5% | 20% | 25 | Below bar: efficiency alone cannot rescue growth |
Two readings worth internalizing from the table: the rule is deliberately indifferent to the mix, the rocket and the compounder both pass, and it fails companies in both directions, burning without commensurate growth and cutting into stagnation score identically. That symmetry is the rule's real teaching: neither growth nor efficiency is a strategy alone; the sum is the strategy.
Improving the Growth Side
The growth half responds to the classic machinery, pipeline, win rates, expansion revenue, retention, pricing, and one increasingly infrastructure-flavored input: product velocity, since shipping is upstream of every growth motion. Two connections back to this blog's territory: net revenue retention is the highest-leverage growth input for most SaaS companies at scale, and it depends on product investment that a bloated infrastructure line quietly crowds out; and AI features are the current growth bet across the industry, which makes their unit economics (the cost side of the same features) a growth-side concern too, growth bought with negative-margin AI features shows up on the other half of the score with interest.
Improving the Margin Side, and the Lever Finance Forgets
Margin work usually starts with the visible lines, sales efficiency, headcount discipline, pricing, and too often stops before the one engineering controls: cost of goods sold. For a software company, COGS is substantially infrastructure, cloud, data platforms, and now AI inference, and it is enormous and moving: 76 percent of large enterprises exceed 5 million dollars a month in cloud spend, the industry self-estimates 29 percent of cloud spend as waste, and AI adds a fast-compounding meter on top. The implication is direct: infrastructure efficiency is gross margin improvement, and gross margin flows point-for-point into the Rule of 40 score. A company spending 20 percent of revenue on infrastructure that eliminates a quarter of it as waste adds roughly five points of margin, five points of Rule of 40, from work that touches no salesperson, no price list, and no roadmap. That is the FinOps case stated in the board's own currency, and the mechanics are the usual ones: unit economics per customer and feature, waste elimination, commitment discipline, and AI cost control, all reported through the CFO's dashboard in margin terms.
The Criticisms That Keep the Rule Honest
- It is a heuristic, not a law: 40 is a convention that became a benchmark, directionally meaningful, not physics, and sector, scale, and rate environments all shift what good looks like.
- It is stage-dependent: very early companies are legitimately all growth, and applying the rule before revenue is meaningful punishes exactly the right behavior.
- It is gameable in the short term: slashing R&D and infrastructure investment lifts this year's margin and this year's score while quietly selling next year's growth, which is why durable margin work (waste out, efficiency in) beats cut-everything margin work.
- It says nothing about quality of revenue: retention, concentration, and durability live outside the formula, and diligence rightly reads them alongside it.
- Definitional drift is the practical trap: comparing your FCF-based 42 to a peer's EBITDA-based 42 is comparing different numbers wearing the same name.
Using the rule as an operator Track it quarterly with one stated margin definition; decompose every move into its growth and margin components so the narrative is causal, not cosmetic; set the strategy debate as which side has cheaper points this year, and notice that infrastructure waste is usually the cheapest margin point on the table; and pair the score with durability metrics, retention, unit costs, forecast accuracy, so a rising number means a healthier machine rather than a starved one. The rule's best use is not judgment but allocation: it prices the growth-versus-efficiency trade explicitly, every quarter, in one number everyone already respects.
Conclusion
The Rule of 40 endures because it compresses the industry's central trade, growth versus profitability, into one comparable, arguable number: growth rate plus margin, 40 as the bar, indifferent to the mix and unforgiving of imbalance. Use it with its caveats, one margin definition, stage awareness, durability checks, and use both of its sides: the growth machinery everyone already funds, and the margin lever engineering actually controls, where infrastructure and AI efficiency convert directly into score. That second lever is Opslyft's territory: waste eliminated across clouds, Kubernetes, warehouses, and AI, unit economics per customer and feature, commitment governance, and margin-ready reporting for the finance partnership, so the next point of Rule of 40 comes from the line item nobody had to fight sales for.
FAQs
A software-industry benchmark: revenue growth rate plus profit margin should total at least 40 percent, letting investors and boards evaluate the growth-versus-profitability balance in one number, a company can pass while burning cash fast-growing or while compounding profitably.
Add year-over-year revenue growth (percent) to profit margin (percent) over the same period: 25 percent growth with an 18 percent margin scores 43. State which margin you use, free cash flow and EBITDA are the common choices, and keep the definition constant.
Free cash flow margin is the investor favorite (hardest to flatter, credits SaaS cash dynamics); EBITDA margin is common in board reporting; operating margin where public-reporting consistency matters. Any is defensible if stated and held constant, switching definitions mid-story is the red flag.
No, it is a convention that became a benchmark: directionally meaningful, stage-dependent, and shifted by sector and rate environments. Early-stage companies legitimately run all-growth profiles, and mature ones are judged more on the margin half; the number frames the debate rather than ending it.