What is the Rule of 40?

What is the Rule of 40?

4 min read

Managing a software team or a tech-based venture often feels like being pulled in two directions at once. You are told to capture the market as fast as humanly possible. At the same time, you are told to keep the lights on and ensure the business is actually making money. This creates a specific kind of anxiety for a leader who cares about longevity. You want to build something that lasts, not a house of cards that collapses the moment the external funding stops. You want to de-stress by knowing that your decisions are backed by a solid framework rather than just gut feelings or the latest trend from a thought leader.

Defining the Rule of 40

The Rule of 40 is a high level health metric specifically designed for software companies. It provides a single number to help you judge if your current trajectory is sustainable. It is not a get-rich-quick formula. Instead, it is a way to measure the trade-off between how much you are expanding and how much cash you are generating.

  • You add your revenue growth percentage to your profit margin percentage.
  • If the total is 40 or higher, the business is generally considered healthy.
  • If the total is below 40, you might be sacrificing too much profit for too little growth, or vice-versa.

Calculating Growth and Profit

To use this metric, you look at your year-over-year revenue growth. If your revenue grew by 30 percent, that is your first number. Then you look at your profit margin. This is often calculated using EBITDA, which stands for earnings before interest, taxes, depreciation, and amortization. For some managers, using free cash flow is a more honest way to look at the bank account.

If your profit margin is 15 percent, your score is 45. You are in the green. However, if you are growing at 50 percent but losing 20 percent in margin, your score is 30. This suggests the growth might be too expensive to maintain over the long term. This simple math helps you strip away the complexity of your financial statements to see the core truth of your operations.

Growth at All Costs vs Sustainable Scaling

Many managers feel pressured by the growth at all costs narrative that is common in some investment circles. This mindset often ignores the emotional and financial toll of burning through cash without a plan. The Rule of 40 serves as a guardrail against reckless spending.

  • It acknowledges that a profitable slow-grower can be just as valuable as a money-losing fast-grower.
  • It rewards balance rather than extremes.
  • It provides a sense of confidence when you have to tell your team why you are not expanding as fast as the competition.

Practical Scenarios for the Rule of 40

You might find yourself using this calculation when you are deciding on the next years budget. If you want to hire five more employees, you can see how that impact on your profit margin affects your overall score. It allows you to make decisions based on data rather than fear. During a market downturn, you might shift from high growth to higher profitability to keep your score above 40. During a product launch, you might accept a lower profit margin because you expect a massive spike in growth later. This gives you a clear language to use with your staff and stakeholders.

The Unknowns and Strategic Trade-offs

While the math is simple, the implementation leads to questions that data cannot always answer. Is 40 still the magic number in a high interest rate environment? How does the stage of your business change the expectation? A startup with five people might have different needs than a firm with fifty. You must also consider the human element. Forcing a team to hit 40 by cutting essential resources can lead to burnout. Every manager must decide which version of the calculation reflects the reality of their specific team. It is a starting point for a conversation about the kind of legacy you want to build.

Join our newsletter.

We care about your data. Read our privacy policy.

Build Expertise. Unleash potential.

World-class capability isn't found it’s built, confirmed, and maintained.