|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
Data center models are changing. A variety of technical trends and business demands are forcing that change, most of them centered on the explosive growth of applications. That means, in turn, that the requirements for application delivery are changing. Certainly application delivery needs to be agile, not waterfall. It needs to deliver services in hours, not weeks or months. It needs to be more cost efficient. And more than anything else, it needs to be really, dc infra axisreally, super focus...
Jun. 29, 2015 04:45 PM EDT Reads: 1,749
Cloud Migration Management (CMM) refers to the best practices for planning and managing migration of IT systems from a legacy platform to a Cloud Provider through a combination professional services consulting and software tools. A Cloud migration project can be a relatively simple exercise, where applications are migrated ‘as is’, to gain benefits such as elastic capacity and utility pricing, but without making any changes to the application architecture, software development methods or busine...
Jun. 29, 2015 04:15 PM EDT Reads: 1,733
"Plutora provides release and testing environment capabilities to the enterprise," explained Dalibor Siroky, Director and Co-founder of Plutora, in this SYS-CON.tv interview at @DevOpsSummit, held June 9-11, 2015, at the Javits Center in New York City.
Jun. 29, 2015 03:34 PM EDT Reads: 476
Discussions about cloud computing are evolving into discussions about enterprise IT in general. As enterprises increasingly migrate toward their own unique clouds, new issues such as the use of containers and microservices emerge to keep things interesting. In this Power Panel at 16th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists addressed the state of cloud computing today, and what enterprise IT professionals need to know about how the latest topics and trends affect t...
Jun. 29, 2015 01:19 PM EDT Reads: 724
Many people recognize DevOps as an enormous benefit – faster application deployment, automated toolchains, support of more granular updates, better cooperation across groups. However, less appreciated is the journey enterprise IT groups need to make to achieve this outcome. The plain fact is that established IT processes reflect a very different set of goals: stability, infrequent change, hands-on administration, and alignment with ITIL. So how does an enterprise IT organization implement change...
Jun. 29, 2015 12:45 PM EDT Reads: 2,683
DevOps tends to focus on the relationship between Dev and Ops, putting an emphasis on the ops and application infrastructure. But that’s changing with microservices architectures. In her session at DevOps Summit, Lori MacVittie, Evangelist for F5 Networks, will focus on how microservices are changing the underlying architectures needed to scale, secure and deliver applications based on highly distributed (micro) services and why that means an expansion into “the network” for DevOps.
Jun. 29, 2015 11:00 AM EDT Reads: 2,228
Conferences agendas. Event navigation. Specific tasks, like buying a house or getting a car loan. If you've installed an app for any of these things you've installed what's known as a "disposable mobile app" or DMA. Apps designed for a single use-case and with the expectation they'll be "thrown away" like brochures. Deleted until needed again. These apps are necessarily small, agile and highly volatile. Sometimes existing only for a short time - say to support an event like an election, the Wor...
Jun. 29, 2015 11:00 AM EDT Reads: 1,361
Containers have changed the mind of IT in DevOps. They enable developers to work with dev, test, stage and production environments identically. Containers provide the right abstraction for microservices and many cloud platforms have integrated them into deployment pipelines. DevOps and Containers together help companies to achieve their business goals faster and more effectively. In his session at DevOps Summit, Ruslan Synytsky, CEO and Co-founder of Jelastic, reviewed the current landscape of...
Jun. 29, 2015 10:00 AM EDT Reads: 1,949
The cloud has transformed how we think about software quality. Instead of preventing failures, we must focus on automatic recovery from failure. In other words, resilience trumps traditional quality measures. Continuous delivery models further squeeze traditional notions of quality. Remember the venerable project management Iron Triangle? Among time, scope, and cost, you can only fix two or quality will suffer. Only in today's DevOps world, continuous testing, integration, and deployment upend...
Jun. 29, 2015 10:00 AM EDT Reads: 1,693
Sharding has become a popular means of achieving scalability in application architectures in which read/write data separation is not only possible, but desirable to achieve new heights of concurrency. The premise is that by splitting up read and write duties, it is possible to get better overall performance at the cost of a slight delay in consistency. That is, it takes a bit of time to replicate changes initiated by a "write" to the read-only master database. It's eventually consistent, and it'...
Jun. 29, 2015 08:00 AM EDT Reads: 1,521
While DevOps most critically and famously fosters collaboration, communication, and integration through cultural change, culture is more of an output than an input. In order to actively drive cultural evolution, organizations must make substantial organizational and process changes, and adopt new technologies, to encourage a DevOps culture. Moderated by Andi Mann, panelists discussed how to balance these three pillars of DevOps, where to focus attention (and resources), where organizations migh...
Jun. 28, 2015 05:00 PM EDT Reads: 1,936
At DevOps Summit NY there’s been a whole lot of talk about not just DevOps, but containers, IoT, and microservices. Sessions focused not just on the cultural shift needed to grow at scale with a DevOps approach, but also made sure to include the network ”plumbing” needed to ensure success as applications decompose into the microservice architectures enabling rapid growth and support for the Internet of (Every)Things.
Jun. 28, 2015 01:00 PM EDT Reads: 1,844
Mashape is bringing real-time analytics to microservices with the release of Mashape Analytics. First built internally to analyze the performance of more than 13,000 APIs served by the mashape.com marketplace, this new tool provides developers with robust visibility into their APIs and how they function within microservices. A purpose-built, open analytics platform designed specifically for APIs and microservices architectures, Mashape Analytics also lets developers and DevOps teams understand w...
Jun. 27, 2015 11:00 AM EDT Reads: 1,861
Sumo Logic has announced comprehensive analytics capabilities for organizations embracing DevOps practices, microservices architectures and containers to build applications. As application architectures evolve toward microservices, containers continue to gain traction for providing the ideal environment to build, deploy and operate these applications across distributed systems. The volume and complexity of data generated by these environments make monitoring and troubleshooting an enormous chall...
Jun. 26, 2015 12:00 PM EDT Reads: 1,500
Buzzword alert: Microservices and IoT at a DevOps conference? What could possibly go wrong? In this Power Panel at DevOps Summit, moderated by Jason Bloomberg, the leading expert on architecting agility for the enterprise and president of Intellyx, panelists peeled away the buzz and discuss the important architectural principles behind implementing IoT solutions for the enterprise. As remote IoT devices and sensors become increasingly intelligent, they become part of our distributed cloud envir...
Jun. 26, 2015 12:00 PM EDT Reads: 2,154
Containers and Docker are all the rage these days. In fact, containers — with Docker as the leading container implementation — have changed how we deploy systems, especially those comprised of microservices. Despite all the buzz, however, Docker and other containers are still relatively new and not yet mainstream. That being said, even early Docker adopters need a good monitoring tool, so last month we added Docker monitoring to SPM. We built it on top of spm-agent – the extensible framework f...
Jun. 26, 2015 09:00 AM EDT Reads: 1,564
Jun. 25, 2015 01:00 PM EDT Reads: 1,859
Jun. 25, 2015 03:01 AM EDT Reads: 333
SYS-CON Events announced today that the "Second Containers & Microservices Conference" will take place November 3-5, 2015, at the Santa Clara Convention Center, Santa Clara, CA, and the “Third Containers & Microservices Conference” will take place June 7-9, 2016, at Javits Center in New York City. Containers and microservices have become topics of intense interest throughout the cloud developer and enterprise IT communities.
Jun. 22, 2015 02:15 PM EDT Reads: 2,634
The causality question behind Conway’s Law is less about how changing software organizations can lead to better software, but rather how companies can best leverage changing technology in order to transform their organizations. Hints at how to answer this question surprisingly come from the world of devops – surprising because the focus of devops is ostensibly on building and deploying better software more quickly. Be that as it may, there’s no question that technology change is a primary fac...
Jun. 22, 2015 01:05 PM EDT Reads: 949