|By David Skok||
|January 19, 2013 09:00 AM EST||
“If you cannot measure it, you cannot improve it” – Lord Kelvin
This article is a comprehensive and detailed look at the key metrics that are needed to understand and optimize a SaaS business. It is a completely updated rewrite of an older post. For this version, I have co-opted two real experts in the field: Ron Gill, (CFO, NetSuite), and Brad Coffey (VP of Strategy, HubSpot), to add expertise, color and commentary from the viewpoint of a public and private SaaS company. My sincere thanks to both of them for their time and input.
SaaS/subscription businesses are more complex than traditional businesses. Traditional business metrics totally fail to capture the key factors that drive SaaS performance. In the SaaS world, there are a few key variables that make a big difference to future results. This post is aimed at helping SaaS executives understand which variables really matter, and how to measure them and act on the results.
The goal of the article is to help you answer the following questions:
- Is my business financially viable?
- What is working well, and what needs to be improved?
- What levers should management focus on to drive the business?
- Should the CEO hit the accelerator, or the brakes?
- What is the impact on cash and profit/loss of hitting the accelerator?
(Note: although I focus on SaaS specifically, the article is applicable to any subscription business.)
What's so different about SaaS?
SaaS, and other recurring revenue businesses are different because the revenue for the service comes over an extended period of time (the customer lifetime). If a customer is happy with the service, they will stick around for a long time, and the profit that can be made from that customer will increase considerably. On the other hand if a customer is unhappy, they will churn quickly, and the business will likely lose money on the investment that they made to acquire that customer. This creates a fundamentally different dynamic to a traditional software business: there are now two sales that have to be accomplished:
- Acquiring the customer
- Keeping the customer (to maximize the lifetime value).
Because of the importance of customer retention, we will see a lot of focus on metrics that help us understand retention and churn. But first let's look at metrics that help you understand if your SaaS business is financially viable.
The SaaS P&L / Cash Flow Trough
SaaS businesses face significant losses in the early years (and often an associated cash flow problem). This is because they have to invest heavily upfront to acquire the customer, but recover the profits from that investment over a long period of time. The faster the business decides to grow, the worse the losses become. Many investors/board members have a problem understanding this, and want to hit the brakes at precisely the moment when they should be hitting the accelerator.
In many SaaS businesses, this also translates into a cash flow problem, as they may only be able to get the customer to pay them month by month. To illustrate the problem, we built a simple Excel model which can be found here. In that model, we are spending $6,000 to acquire the customer, and billing them at the rate of $500 per month. Take a look at these two graphs from that model:
If we experience a cash flow trough for one customer, then what will happen if we start to do really well and acquire many customers at the same time? The model shows that the P&L/cash flow trough gets deeper if we increase the growth rate for the bookings.
But there is light at the end of the tunnel, as eventually there is enough profit/cash from the installed base to cover the investment needed for new customers. At that point the business would turn profitable/cash flow positive - assuming you don't decide to increase spending on sales and marketing. And, as expected, the faster the growth in customer acquisition, the better the curve looks when it becomes positive.
Ron Gill, NetSuite:
If plans go well, you may decide it is time to hit the accelerator (increasing spending on lead generation, hiring additional sales reps, adding data center capacity, etc.) in order to pick-up the pace of customer acquisition. The thing that surprises many investors and boards of directors about the SaaS model is that, even with perfect execution, an acceleration of growth will often be accompanied by a squeeze on profitability and cash flow.
As soon as the product starts to see some significant uptake, investors expect that the losses / cash drain should narrow, right? Instead, this is the perfect time to increase investment in the business. which will cause losses to deepen again. The graph below illustrates the problem:
Notice in the example graph that the five customer per month model ultimately yields a much steeper rate of growth, but you have to go through another deep trough to get there. It is the concept of needing to re-enter that type of trough after just having gotten the curve to turn positive that many managers and investors struggle with.
Of course this a special challenge early-on as you need to explain to investors why you'll require additional cash to fund that next round of acceleration. But it isn't just a startup problem. At NetSuite, even as a public company our revenue growth rate has accelerated in each of the last three years. That means that each annual plan involves a stepping-up of investment in lead generation and sales capacity that will increase spending and cash flow out for some time before it starts yielding incremental revenue and cash flow in. As long as you're accelerating the rate of revenue growth, managing and messaging around this phenomenon is a permanent part of the landscape for any SaaS company.
Why is growth important?
We have suggested that as soon as the business has shown that it can succeed, it should invest aggressively to increase the growth rate. You might ask question: Why?
SaaS is usually a "winner-takes-all" game, and it is therefore important to grab market share as fast as possible to make sure you are the winner in your space. Provided you can tell a story that shows that eventually that growth will lead to profitability, Wall Street, acquiring companies, and venture investors all reward higher growth with higher valuations. There's also a premium for the market leader in a particular space.
However not all investments make sense. In the next section we will look at a tool to help you ensure that your growth initiatives/investments will pay back: Unit Economics.
A Powerful Tool: Unit Economics
Because of the losses in the early days, which get bigger the more successful the company is at acquiring customers, it is much harder for management and investors to figure out whether a SaaS business is financially viable. We need some tools to help us figure this out.
A great way to understand any business model is to answer the following simple question:
Can I make more profit from my customers than it costs me to acquire them?
This is effectively a study of the unit economics of each customer. To answer the question, we need two metrics:
- LTV - the Lifetime Value of a typical customer
- CAC - the Cost to Acquire a typical Customer
(For more on how to calculate LTV and CAC, click here.)
Entrepreneurs are usually overoptimistic about how much it costs to acquire a customer. This probably comes from a belief that customers will be so excited about what they have built, that they will beat a path to their doors to buy the product. The reality is often very different! (I have written more on this topic here: Startup Killer: The Cost of Customer Acquisition, and here: How Sales Complexity impacts CAC.)
Is your SaaS business viable?
In the first version of this article, I introduced two guidelines that could be used to judge quickly whether your SaaS business is viable. The first is a good way to figure out if you will be profitable in the long run, and the second is about measuring the time to profitability (which also greatly impacts capital efficiency).
Over the last two years, I have had the chance to validate these guidelines with many SaaS businesses, and it turns out that these early guesses have held up well. The best SaaS businesses have a LTV to CAC ratio that is higher than 3, sometimes as high as 7 or 8. And many of the best SaaS businesses are able to recover their CAC in 5-7 months. However many healthy SaaS businesses don't meet the guidelines in the early days, but can see how they can improve the business over time to get there.
The second guideline (Months to Recover CAC) is all about time to profitability and cash flow. Larger businesses, such as wireless carriers and credit card companies, can afford to have a longer time to recover CAC, as they have access to tons of cheap capital. Startups, on the other hand, typically find that capital is expensive in the early days. However even if capital is cheap, it turns out that Months to recover CAC is a very good predictor of how well a SaaS business will perform. Take a look at the graph below, which comes from the same model used earlier. It shows how the profitability is anemic if the time to recover CAC extends beyond 12 months.
I should stress that these are only guidelines, there are always situations where it makes sense to break them.
Three uses for the SaaS Guidelines
- One of the key jobs of the CEO is to decide when to hit the accelerator pedal. The value of these two guidelines is that they help you understand when you have a SaaS business that is in good shape, where it makes sense to hit the accelerator pedal. Alternatively if your business doesn't meet the guidelines, it is a good indicator that there is more tweaking needed to fix the business before you should expand.
- Another way to use the two guidelines is for evaluating different lead sources. Different lead sources (e.g. Google AdWords, TV, Radio, etc.) have different costs associated with them. The guidelines help you understand if some of the more expensive lead generation options make financial sense. If they meet these guidelines, it makes sense to hit the accelerator on those sources (assuming you have the cash).Using the second guideline, and working backwards, we can tell that if we are getting paid $500 per month, we can afford to spend up to 12x that amount (i.e. $6,000) on acquiring the customer. If we're spending less than that, you can afford to be more aggressive and spend more in marketing or sales.
- There is another important way to use this type of guideline: segmentation. Early-stage companies are often testing their offering with several different uses/types of customers / pricing models / industry verticals. It is very useful to examine which segments show the quickest return or highest LTV to CAC in order to understand which will be the most profitable to pursue.
Unit Economics in Action: HubSpot Example
HubSpot's unit economics were recently published in an article in Forbes:
You can see from the second row in this table how they have dramatically improved their unit economics (LTV:CAC ratio) over the five quarters shown. The big driver for this was lowering the MRR Churn rate from 3.5% to 1.5%. This drove up the lifetime value of the customer considerably. They were also able to drive up their AVG MRR per customer.
Brad Coffey, HubSpot:
In 2011 and early 2012 we used this chart to guide many of our business decisions at HubSpot. By breaking LTV:CAC down into its components we could examine each metric and understand what levers we could pull to drive overall improvement.
It turned out that the levers we could pull varied by segment. In the SMB market for instance we had the right sales process in place - but had an opportunity to improve LTV by improving the product to lower churn and increasing our average price in the segment. In the VSB (Very Small Business) segment, by contrast, there wasn't as much upside left on the LTV (VSB customers have less money and naturally higher churn) so we focused on lowering CAC by removing friction from our sales process and moving more of our sales to the channel.
Two kinds of SaaS business:
There are two kinds of SaaS business:
- Those with primarily monthly contracts, with some longer term contracts. In this business, the primary focus will be on MRR (Monthly Recurring Revenue)
- Those with primarily annual contracts, with some contracts for multiple years. Here the primary focus is on ARR (Annual Recurring Revenue), and ACV (Annual Contract Value).
Most of the time in this article, I will refer to MRR/ACV. This means use MRR if you are the first kind of business, or ACV if you are the second kind of business. The dashboard shown below assumes monthly contracts (MRR). However in the downloadable spreadsheet, there is a tab that shows the same dashboard for the second kind, focusing on ACV instead of MRR.
SaaS Bookings: Three Contributing Elements
Every month in a SaaS business, there are three elements that contribute to how much MRR will change relative to the previous month:
What happened with new customers added in the month:
- New MRR (or ACV)
What happened in the installed base of customers:
- Churned MRR (or ACV) (from existing customers that cancelled their subscription. This will be a negative number.)
- Expansion MRR (or ACV) (from existing customers who expanded their subscription)
The sum all three of these makes up your Net MRR or ACV Bookings:
I recommend that you track these using a chart similar to the one below:
This chart shows the three components of MRR (or ACV) Bookings, and the Net New MRR (or ACV) Bookings. By breaking out each component, you can track the key elements that are driving your business. The one variation we would recommend making to this chart is to show a dotted line for the plan, so you can track how you are doing against plan for each of the four lines. This is one of the most important charts to help you understand and run your business.
Ron Gill, NetSuite:
This chart is really good. I also like to look at this data in tabular form because I want to know y-o-y growth rates. E.g. "Net new MRR is up 25% over June of last year". The Y-o-Y % is a metric easily compared with increased spending, sales capacity, etc.
The Importance of Customer Retention (Churn)
In the early days of a SaaS business, churn really doesn't matter that much. Let's say that you lose 3% of your customers every month. When you only have a hundred customers, losing 3 of them is not that terrible. You can easily go and find another 3 to replace them. However as your business grows in size, the problem becomes different. Imagine that you have become really big, and now have a million customers. 3% churn means that you are losing 30,000 customers every month! That turns out to be a much harder number to replace. Companies like Constant Contact have run into this problem, and it has made it very hard for them to keep up their growth rate.
Ron Gill, NetSuite:
One oft-overlooked aspect of churn is that the churn rate, combined with the rate of new ARR adds, not only defines how fast you can grow the business, it also defines the maximum size the business can reach (see graph below).
It is an enlightening exercise to build a simple model like this for your business and plot where your current revenue run rate sits on the blue line defined by your present rate of ARR adds and churn. Are you near the left-hand side, where the growth is still steep and the ceiling is still far above? Or, are you further to the right where revenue growth will level off and there is limited room left to grow? How much benefit will you get from small improvements in churn or the pace of new business sign-up?
At NetSuite, we've had great success shifting the line in the last few years by both dramatically decreasing churn and by increasing average deal size and volume, thus increasing ARR adds. The result was both to steadily move the limit upward and to steepen the growth curve at the current ARR run rate, creating room for increasingly rapid expansion.
The Power of Negative Churn
The ultimate solution to the churn problem is to get to Negative Churn.
There are two ways to get this expansion revenue:
- Use a pricing scheme that has a variable axis, such as the number of seats used, the number of leads tracked, etc. That way, as your customers expand their usage of your product, they pay you more.
- Upsell/Cross-sell them to more powerful versions of your product, or additional modules.
To help illustrate the power of negative churn, take a look at the following two graphs that show how cohorts behave with 3% churn, and then with 3% negative churn. (Since this is the first time I have used the word Cohort, let me explain what it means. A cohort is simply a fancy word for a group of customers. In the SaaS world, it is used typically to describe the group that joined in a particular month. So there would be the January cohort, February cohort, etc. In our graphs below, a different color is used for each month's cohort, so we can see how they decline or grow, based on the churn rate.)
In the top graph, we are losing 3% of our revenue every month, and you can see that with a constant bookings rate of $6k per month, the revenue reaches $140k after 40 months, and growth is flattening out. In the bottom graph, we may be losing some customers, but the remaining customers are more than making up for that with increased revenue. With a negative churn rate of 3%, we reach $450k in revenue (more then 3x greater), and the growth in revenues is increasing, not flattening.
For more on this topic, you may wish to refer to these two blog posts of mine:
- Why Churn is SO critical to success in SaaS
- Multi-axis Pricing: a key tool for increasing SaaS revenue
The rise of containers and microservices has skyrocketed the rate at which new applications are moved into production environments today. While developers have been deploying containers to speed up the development processes for some time, there still remain challenges with running microservices efficiently. Most existing IT monitoring tools don’t actually maintain visibility into the containers that make up microservices. As those container applications move into production, some IT operations t...
Feb. 27, 2017 10:30 PM EST Reads: 1,546
We call it DevOps but much of the time there’s a lot more discussion about the needs and concerns of developers than there is about other groups. There’s a focus on improved and less isolated developer workflows. There are many discussions around collaboration, continuous integration and delivery, issue tracking, source code control, code review, IDEs, and xPaaS – and all the tools that enable those things. Changes in developer practices may come up – such as developers taking ownership of code ...
Feb. 27, 2017 09:45 PM EST Reads: 2,996
For organizations that have amassed large sums of software complexity, taking a microservices approach is the first step toward DevOps and continuous improvement / development. Integrating system-level analysis with microservices makes it easier to change and add functionality to applications at any time without the increase of risk. Before you start big transformation projects or a cloud migration, make sure these changes won’t take down your entire organization.
Feb. 27, 2017 07:45 PM EST Reads: 1,631
As Enterprise business moves from Monoliths to Microservices, adoption and successful implementations of Microservices become more evident. The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Documenting hurdles and problems for the use of Microservices will help consultants, architects and specialists to avoid repeating the same mistakes and learn how and when to use (or not use) Microservices at the enterprise level. The circumstance w...
Feb. 27, 2017 06:45 PM EST Reads: 1,983
SYS-CON Events announced today that Catchpoint Systems, Inc., a provider of innovative web and infrastructure monitoring solutions, has been named “Silver Sponsor” of SYS-CON's DevOps Summit at 18th Cloud Expo New York, which will take place June 7-9, 2016, at the Javits Center in New York City, NY. Catchpoint is a leading Digital Performance Analytics company that provides unparalleled insight into customer-critical services to help consistently deliver an amazing customer experience. Designed ...
Feb. 27, 2017 05:45 PM EST Reads: 718
@DevOpsSummit at Cloud taking place June 6-8, 2017, at Javits Center, New York City, is co-located with the 20th International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. The widespread success of cloud computing is driving the DevOps revolution in enterprise IT. Now as never before, development teams must communicate and collaborate in a dynamic, 24/7/365 environment. There is no time to wait for long developm...
Feb. 27, 2017 12:45 PM EST Reads: 2,146
SYS-CON Events announced today that Outlyer, a monitoring service for DevOps and operations teams, has been named “Bronze Sponsor” of SYS-CON's 20th International Cloud Expo®, which will take place on June 6-8, 2017, at the Javits Center in New York City, NY. Outlyer is a monitoring service for DevOps and Operations teams running Cloud, SaaS, Microservices and IoT deployments. Designed for today's dynamic environments that need beyond cloud-scale monitoring, we make monitoring effortless so you...
Feb. 27, 2017 11:45 AM EST Reads: 2,579
Cloud Expo, Inc. has announced today that Andi Mann and Aruna Ravichandran have been named Co-Chairs of @DevOpsSummit at Cloud Expo 2017. The @DevOpsSummit at Cloud Expo New York will take place on June 6-8, 2017, at the Javits Center in New York City, New York, and @DevOpsSummit at Cloud Expo Silicon Valley will take place Oct. 31-Nov. 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Feb. 27, 2017 11:30 AM EST Reads: 2,597
SYS-CON Events announced today that CA Technologies has been named “Platinum Sponsor” of SYS-CON's 20th International Cloud Expo®, which will take place on June 6-8, 2017, at the Javits Center in New York City, NY, and the 21st International Cloud Expo®, which will take place October 31-November 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. CA Technologies helps customers succeed in a future where every business – from apparel to energy – is being rewritten by software. From ...
Feb. 27, 2017 11:15 AM EST Reads: 2,894
DevOps and microservices are permeating software engineering teams broadly, whether these teams are in pure software shops but happen to run a business, such Uber and Airbnb, or in companies that rely heavily on software to run more traditional business, such as financial firms or high-end manufacturers. Microservices and DevOps have created software development and therefore business speed and agility benefits, but they have also created problems; specifically, they have created software securi...
Feb. 27, 2017 11:00 AM EST Reads: 4,301
The emerging Internet of Everything creates tremendous new opportunities for customer engagement and business model innovation. However, enterprises must overcome a number of critical challenges to bring these new solutions to market. In his session at @ThingsExpo, Michael Martin, CTO/CIO at nfrastructure, outlined these key challenges and recommended approaches for overcoming them to achieve speed and agility in the design, development and implementation of Internet of Everything solutions with...
Feb. 27, 2017 10:00 AM EST Reads: 8,074
DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm. In his general session at 20th Cloud Expo, Chris Brown, a Solutions Marketing Manager at Nutanix, will explore...
Feb. 27, 2017 09:45 AM EST Reads: 1,933
This week's news brings us further reminders that if you're betting on cloud, you're headed in the right direction. The cloud is growing seven times faster than the rest of IT, according to IDC, with a 25% spending increase just from 2016 to 2017. SaaS still leads the pack, with an estimated two-thirds of public cloud spending going that way. Large enterprises, with more than 1,000 employees, are predicted to account for more than half of cloud spending and have the fastest annual growth rate.
Feb. 27, 2017 09:30 AM EST Reads: 1,261
All clouds are not equal. To succeed in a DevOps context, organizations should plan to develop/deploy apps across a choice of on-premise and public clouds simultaneously depending on the business needs. This is where the concept of the Lean Cloud comes in - resting on the idea that you often need to relocate your app modules over their life cycles for both innovation and operational efficiency in the cloud. In his session at @DevOpsSummit at19th Cloud Expo, Valentin (Val) Bercovici, CTO of Soli...
Feb. 27, 2017 09:15 AM EST Reads: 1,558
Microservices are a very exciting architectural approach that many organizations are looking to as a way to accelerate innovation. Microservices promise to allow teams to move away from monolithic "ball of mud" systems, but the reality is that, in the vast majority of organizations, different projects and technologies will continue to be developed at different speeds. How to handle the dependencies between these disparate systems with different iteration cycles? Consider the "canoncial problem" ...
Feb. 27, 2017 06:00 AM EST Reads: 6,228
After more than five years of DevOps, definitions are evolving, boundaries are expanding, ‘unicorns’ are no longer rare, enterprises are on board, and pundits are moving on. Can we now look at an evolution of DevOps? Should we? Is the foundation of DevOps ‘done’, or is there still too much left to do? What is mature, and what is still missing? What does the next 5 years of DevOps look like? In this Power Panel at DevOps Summit, moderated by DevOps Summit Conference Chair Andi Mann, panelists l...
Feb. 27, 2017 05:00 AM EST Reads: 7,498
When building DevOps or continuous delivery practices you can learn a great deal from others. What choices did they make, what practices did they put in place, and how did they connect the dots? At Sonatype, we pulled together a set of 21 reference architectures for folks building continuous delivery and DevOps practices using Docker. Why? After 3,000 DevOps professionals attended our webinar on "Continuous Integration using Docker" discussing just one reference architecture example, we recogn...
Feb. 27, 2017 04:00 AM EST Reads: 2,840
Hardware virtualization and cloud computing allowed us to increase resource utilization and increase our flexibility to respond to business demand. Docker Containers are the next quantum leap - Are they?! Databases always represented an additional set of challenges unique to running workloads requiring a maximum of I/O, network, CPU resources combined with data locality.
Feb. 27, 2017 03:00 AM EST Reads: 2,400
Thanks to Docker and the DevOps revolution, microservices have emerged as the new way to build and deploy applications — and there are plenty of great reasons to embrace the microservices trend. If you are going to adopt microservices, you also have to understand that microservice architectures have many moving parts. When it comes to incident management, this presents an important difference between microservices and monolithic architectures. More moving parts mean more complexity to monitor an...
Feb. 27, 2017 02:00 AM EST Reads: 1,904
In recent years, containers have taken the world by storm. Companies of all sizes and industries have realized the massive benefits of containers, such as unprecedented mobility, higher hardware utilization, and increased flexibility and agility; however, many containers today are non-persistent. Containers without persistence miss out on many benefits, and in many cases simply pass the responsibility of persistence onto other infrastructure, adding additional complexity.
Feb. 27, 2017 01:15 AM EST Reads: 1,788