TL;DR: The Rule of 40 states that a SaaS company's revenue growth rate plus its profit margin should equal or exceed 40%. It gives investors and operators a single number to evaluate whether a business grows efficiently. This guide covers the formula, margin variations, stage-based benchmarks, and how FinOps teams can move the metric through better cost governance.
In the early days of SaaS investing, growth was the only number that mattered. Investors rewarded top-line expansion and tolerated almost any level of burn. That era ended. Capital markets repriced, interest rates climbed, and the companies that survived the correction shared a common trait: they could articulate a credible path from growth to profitability without abandoning one for the other.
The Rule of 40 emerged from that shift as the operating standard for measuring SaaS efficiency. It's not a guarantee of business health, and it won't replace unit economics or cohort analysis. But it gives anyone looking at a SaaS business, from a board member to a FinOps lead, a fast, comparable signal for whether the company grows in a way that's worth sustaining.
This guide covers what the Rule of 40 is, how to calculate it accurately, what scores mean at different company stages, and how FinOps teams can use it as a practical framework for cost governance decisions.
What is the Rule of 40?
The Rule of 40 defines a threshold of combined efficiency for software businesses: a company's revenue growth rate plus its profit margin should sum to at least 40. A company growing at 50% annually with a negative 15% margin scores 35, below threshold. A company growing at 25% with a 20% margin scores 45, above it. The metric captures the trade-off between investing in growth and generating returns, reflecting the idea that a high-growth company can tolerate losses as long as the growth rate compensates.
The metric originated in venture capital as a quick filter for SaaS portfolio health, but it's spread into operator conversations because it creates shared language between finance and engineering. Both sides can agree on what moves the number, even if they disagree on which lever to pull.
For FinOps teams specifically, the Rule of 40 matters because cloud infrastructure sits at the intersection of both components. Infrastructure costs affect profit margin directly, and infrastructure decisions affect how fast a company can scale, which affects revenue growth. A FinOps team that frames cost optimization in Rule of 40 terms connects their work to a metric the CFO and board already care about.
Which profit margin should you use?
This is where Rule of 40 calculations diverge across companies and reports, which makes benchmarking unreliable unless everyone uses the same definition. The three most common margin types each produce different results.
| Margin type | What it includes | Best used when |
|---|---|---|
| EBITDA margin | Operating profit before interest, taxes, depreciation, and amortization | Comparing capital-intensive companies; strips out financing decisions |
| Operating margin (EBIT) | Revenue minus operating expenses including D&A | Standard GAAP reporting; easier to audit; most common in public company filings |
| Free cash flow margin | Operating cash flow minus capex, divided by revenue | Investor-preferred for mature companies; reflects actual cash generation |
Most public SaaS companies report Rule of 40 using free cash flow margin because investors treat it as the cleanest signal of operational health. Earlier-stage companies often use EBITDA because it's easier to calculate from internal financials. The important thing isn't which margin you choose. Apply it consistently across every reporting period so trends stay comparable.
Revenue growth rate: trailing vs. forward-looking
The growth rate component also carries a methodology choice. Trailing twelve months (TTM) growth uses actual reported revenue, which makes it auditable and consistent. Forward-looking ARR growth projects the next twelve months based on current ARR and net revenue retention, giving a more current picture of business momentum but introducing forecast assumptions.
For internal FinOps planning, TTM works well because it uses verified numbers and removes the noise of optimistic projections. For investor-facing reporting, many SaaS CFOs present both: TTM for accountability, forward ARR for narrative. Pick one for your baseline tracking and document it.
How do you calculate the Rule of 40?
The formula is straightforward. The discipline is in defining your inputs before you run the calculation.
Rule of 40 Score = Revenue Growth Rate (%) + Profit Margin (%)
Example: Revenue growth rate (TTM): 35% Free cash flow margin: -8% Rule of 40 score: 35 + (-8) = 27To calculate revenue growth rate, take the difference between current period revenue and the same period a year ago, divide by the prior period, and multiply by 100. For a company with $40M TTM revenue today vs. $28M a year ago: ($40M - $28M) / $28M = 42.9%.
To calculate the margin, divide your chosen profit figure by total revenue for the same period. If FCF was -$3M on $40M revenue, that's -7.5%.
Rule of 40 score: 42.9 + (-7.5) = 35.4. Below threshold, but trending in the right direction if margins are improving.
Before you lock in a calculation methodology, document three decisions: which margin type you'll use, which revenue growth basis (TTM or ARR), and how you'll treat one-time items. Document those decisions once and don't revisit them mid-year unless you restate historical periods alongside any changes.
What do Rule of 40 benchmarks actually look like by company stage?
A score of 40 is the threshold, not a universal standard of excellence. Context changes what "good" means considerably, and comparing an early-stage company to a scaled SaaS business using the same benchmark misses the structural differences in how each generates and deploys capital.
Early-stage companies (under $10M ARR)
Companies in this range typically show strong growth rates, often 80% to 150% year over year, and deeply negative margins as they invest in product, go-to-market, and infrastructure. A Rule of 40 score in the 20 to 35 range is common and reasonable at this stage. The margin deficit reflects deliberate investment, not operational dysfunction.
For FinOps teams at early-stage companies, the priority isn't margin improvement in absolute terms. It's building the cost attribution and tagging infrastructure that lets the company scale without losing visibility. The cost of fixing bad tagging practices later vastly exceeds the cost of doing it right at $5M ARR.
Growth-stage companies ($10M to $100M ARR)
This range is where Rule of 40 performance starts to differentiate strong operators from companies running on runway without a plan. Companies in this band typically target scores of 30 to 50. Growth rates moderate from hypergrowth toward 40% to 80%, and gross margin improvement becomes a visible priority as infrastructure costs, customer support, and sales efficiency draw more scrutiny.
According to the FinOps Foundation's 2024 State of FinOps report, cloud cost optimization ranks as a top-three priority for engineering and finance leadership at growth-stage SaaS companies, reflecting how directly cloud spend affects margin at this stage.
FinOps teams here play an active role in Rule of 40 performance. Eliminating idle resources, rightsizing compute, and implementing commitment-based pricing (reserved instances, committed use discounts) can shift cloud costs meaningfully as a percentage of revenue.
Scaled companies ($100M+ ARR)
At scale, the growth rate naturally compresses. A company at $300M ARR growing 25% year over year adds $75M in new revenue, exceptional business performance even as the percentage looks modest compared to earlier years. At this stage, investors and boards expect Rule of 40 scores of 40 to 60 or higher, with the margin component carrying more weight.
McKinsey research on SaaS company performance found that top-quartile performers at scale generate Rule of 40 scores above 50, typically through a combination of disciplined gross margin expansion and efficient go-to-market spend. Cloud infrastructure efficiency contributes directly to gross margin at this stage, particularly for product-led growth companies where infrastructure costs sit inside cost of goods sold.
How do FinOps teams improve Rule of 40 performance in practice?
Rule of 40 improvement for FinOps teams concentrates in the margin component, since engineering and finance rarely control revenue growth directly. But margin improvement through cloud cost governance is more tractable than most teams realize, because cloud spend tends to grow faster than revenue at companies without active cost management.
The practical levers break into three categories.
Cost visibility and allocation. You can't optimize what you can't see. Many companies at the $10M to $100M ARR stage still lack consistent cost allocation by product line, team, or customer segment. Without that attribution, you can't calculate cloud cost as a percentage of revenue per customer, which means you can't tell whether your infrastructure scales efficiently as the business grows. Building a tagging taxonomy and enforcing it across engineering teams turns cloud spend from a blended overhead line into actionable unit economics data. The article on seven cloud bill red flags covers the most common places FinOps teams find unattributed waste.
Commitment-based pricing. On-demand pricing is the most expensive way to run production workloads for predictable traffic patterns. AWS Savings Plans, GCP committed use discounts, and Azure reservations typically reduce compute costs 30% to 60% compared to on-demand rates. For a company spending $2M annually on cloud compute, a well-structured commitment program could recover $600K to $1.2M, flowing directly to margin.
Cross-functional accountability. Cost optimization initiatives that live inside the FinOps team alone rarely sustain their gains. Engineering teams respond to cost feedback when it arrives inside their existing workflows, sprint reviews, and on-call runbooks, not when it arrives as a monthly report from finance. Shared dashboards, per-team cost budgets, and anomaly alerts routed to engineering owners convert cost visibility into behavior change.
What calculation errors and data quality problems undermine Rule of 40 tracking?
The most common Rule of 40 problems aren't conceptual. They're methodological. Companies calculate the metric inconsistently across quarters, include one-time items without flagging them, or use different margin definitions in different reports. The result is a number that looks like a KPI but behaves like noise.
Stock-based compensation and one-time items
Stock-based compensation (SBC) is a significant expense for most SaaS companies, and its treatment in Rule of 40 calculations varies widely. Some companies exclude SBC on the grounds that it's non-cash. Others include it because it represents real economic dilution. Neither approach is wrong, but you need to pick one and disclose it consistently.
The same logic applies to one-time items: restructuring charges, acquisition costs, and litigation settlements. Exclude them if you'd exclude them every time a similar item appeared. Don't exclude them selectively when they hurt your score and include them when they help.
Revenue recognition and acquisition adjustments
ASC 606 revenue recognition rules require SaaS companies to recognize revenue as they deliver service, not when they collect cash. For companies with large upfront contracts or multi-year deals, this creates timing differences between billings and recognized revenue that can affect the growth rate component in any given quarter.
Acquisitions introduce additional complexity. When you acquire a company mid-year, the acquired revenue appears in your results from the close date forward, inflating the current year base and potentially distorting next year's organic growth rate comparison. Reporting organic growth separately from total growth, and explaining the difference, keeps your Rule of 40 trend readable.
Establishing consistent reporting standards
Before a company calculates its first official Rule of 40 score, CFO and FinOps leadership should document a reporting standard that answers five questions: Which margin type? Which revenue basis? How do we handle SBC? How do we handle one-time items? How do we handle acquisition revenue? That document becomes the source of truth for every future calculation. Without it, each new analyst or finance hire recalculates the metric slightly differently and the trend data loses coherence.
How do you build Rule of 40 performance that lasts?
One-time cost reduction projects don't move Rule of 40 in a durable way. A team that rightsizes its EC2 fleet in Q2 and then stops monitoring will find that new workloads, new engineers, and new features gradually re-inflate the cost base by Q4. Sustainable Rule of 40 improvement requires ongoing optimization built into how teams work, not bolt-on audits run once a year.
The companies that maintain strong Rule of 40 performance over multiple years share a few structural characteristics. Engineering and finance share cost accountability, not just visibility. Cost targets exist at the team or product level, not just as a company-wide budget line. FinOps practices sit inside engineering workflows rather than running parallel to them. And leadership treats cloud cost efficiency as a product quality concern, because infrastructure that scales inefficiently creates both margin drag and reliability risk.
For FinOps teams building toward this model, the path starts with attribution, moves to commitment-based savings, and matures into shared accountability structures. The Rule of 40 gives you a board-level metric to attach that work to, which makes it easier to justify the investment and easier to show impact when it works.
DoiT works with 4,000+ cloud-native companies to turn cost visibility into the margin improvements that move Rule of 40 performance. Talk to a DoiT cloud cost expert to see how teams at your stage approach cloud financial management, or explore DoiT DataHub for a closer look at how commitment coverage and cost attribution work in practice.
Frequently asked questions about the Rule of 40
What is a good Rule of 40 score for a SaaS company?
A score at or above 40 is the conventional threshold for efficient SaaS performance. Top-quartile public SaaS companies often score 50 to 60 or higher. Early-stage companies growing very quickly may score well above 40 on growth alone even with negative margins, while mature companies with slower growth compensate through stronger profitability.
Can a company have a negative Rule of 40 score?
Yes. If a company's revenue growth rate plus its profit margin sums to less than zero, the score turns negative. This typically signals that growth is too slow to justify the current level of investment, or that the company burns cash without proportional revenue momentum. Sustained negative Rule of 40 scores draw significant scrutiny from investors and boards.
Does the Rule of 40 apply to non-SaaS companies?
The Rule of 40 originated in SaaS because recurring revenue makes the growth and margin components predictable and comparable. It's less meaningful for transactional businesses or hardware companies where the margin structure differs significantly. Some analysts apply a version of it to cloud infrastructure businesses and marketplace models, but the benchmark thresholds don't translate directly.
What's the difference between Rule of 40 and the burn multiple?
The burn multiple measures how much cash a company burns to generate each dollar of new ARR. Rule of 40 combines growth and profitability into a single efficiency score. Both metrics help evaluate capital efficiency in SaaS, but the burn multiple focuses specifically on the cost of acquiring new revenue, while Rule of 40 captures overall business health across growth and margin together.
How often should a company calculate its Rule of 40 score?
Most SaaS companies track Rule of 40 quarterly to align with financial reporting cadence, and review it annually against public benchmarks. FinOps teams may track the margin component monthly to catch cloud cost trends before they compound into quarterly results.