Churn is dead. Long live Net Dollar Retention Rate with Dave Kellogg

A short webinar-style YouTube session introduced by Jason M. Lemkin featuring Dave Kellogg discussing the shift from focusing on churn to emphasizing Net Dollar Retention Rate (NDR). The chunk contains only the session handoff and introduction to the topic.
Okay, you ready to rock?
Yep.
All right, I'm going to broadcast and I will introduce you and then pass it over.
Super.
Thank you for joining our session. We are here to talk about Churn is Long live Net Dollar Retention Rate with Dave Kellogg. Dave, thanks so much for joining us. Take it away.
Thank you. Well, good morning everybody. Thanks for being here bright and early. I'm Dave Kellogg and today we're going to talk really about understanding SaaS businesses in general, how to think about them, how to value them, how to. We're going to do that through the lens of SaaS metrics and today with a particular focus on understanding the healthiness of the install base of a SaaS company. That's going to quickly bring us to talking about Churn, a topic about which I've blogged a lot and to Net dollar Retention, which I think is actually a more effective way to get at what Churn is trying to measure. Let's jump in. Quick introduction about me first, who is this guy? I've been a CEO of SaaS startups for over 10 years at two different companies. I took Host analytics from 8 million in ARR to 50 million and MarkLogic from 0 to 80 million. In addition to that, I have 10 years as a CMO at two different companies. One Versant where we went from 1 to 15 and BusinessObjects where we had kind of an epic run from 30 million to over a billion in revenue. Not valuation revenue, the old fashioned thing. And then 10 combined years on five different boards, Astrodata and Granular and three other boards today, Elation, Nuxio and Prophecy. I'm also an advisor and angel investor, work with a lot of companies and that's just a sample. And I'm also a blogger, which we'll talk more about in a minute. So that's who I am. Why do I care about this topic? Well, it's a two line proof, which is metrics are key to fundraising and fundraising is key to success. Right. Any further questions? And certainly now in today's Silicon Valley, and this has changed over the last 20 years, in today's Silicon Valley, now more than ever, the ability to raise money is what separates the winners from the runners up and the losers in the formula. This is not a race. VC backed SaaS is not a race or a strong kick at the finish. Like a quarter mile wins the race. In my opinion. It's a race where you get in first early by driving high growth with the right unit economics. And if you've done that, if you're a leader with good growth at the right unit economics, you can then raise lots of capital and you set up a virtuous cycle. The more capital you raise, the faster you grow. The faster you grow with the right unit economics, the more capital you can raise. That's the name of the game. That's why this matters so much. The other reasons I care about it are one, it's a big impact on valuation and ergo dilution. Second, I'm a huge believer in really trying to understand the guts or the drivers of a SaaS business. And looking at SaaS metrics helps you do that. I think every CEO should have a driver based model where you play with sales productivity, sales turnover, sales ramp time, marketing is a percent of sales cost per sale. You put these various drivers in and you can see what happens to your business, see their impact. And to understand driver based models, you want to understand SaaS metrics. And finally, the last point is more of a pet peeve. I loathe the general lack of rigor. I see when some people discuss SAS metrics, where they talk about metrics without defining them or without knowing what they're counting. And there's a lot of that that happens. We get down to churn. So part of this is if we're going to look at these metrics, let's make sure we understand how you're supposed to calculate them, how people game them and how they're supposed to work. So onward. So that's kind of the intro. I do blog a lot about this stuff. My blog's@calblog.com and some of the topics I cover are SaaS businesses in general, kind of all aspects of SaaS businesses. Particular emphasis on SaaS metrics, strategy, sales and marketing, which is my background and more. So if you have a chance, if you like the material today, swing on over to Cal Blog and take a look. Among other things, I'll be posting the slides to this presentation there. So we have three topics today. The first is understanding a SaaS business and we're going to talk about why it's hard to understand the SaaS business. We're going to talk about how to think about a SaaS business and then we're going to talk about kind of basic unit economics. Second section, we're talking about the trouble with churn because it turns out, much as I love churn, I increasingly am kind of skeptical when companies talk about churn rates. And we'll talk about the three problems I see with churn rates that kind of undermine it as a good metric. And by the way, churn rates are used in other calculations. So if CHURN gets polluted, so do the downstream metrics from churn, which is another problem we'll talk about. And by the way, even the concept of churn itself can be a little bit elusive. So we'll talk about that in that second section. The trouble with churn. And then finally, long live King is dead. Long live the king. Long live net dollar retention. We'll talk about this. This is actually more of a public company SaaS metric than a private company SaaS metric. And this is kind of, in my mind, the rare case where the public company SaaS metric is better than the private company SaaS metric. So for those of us who have spent all our time in world, I'll introduce you to what net dollar retention is, then we'll talk about it as a valuation driver. We'll talk about how to calculate it, we'll talk about how to game it. It too is gameable. And then we'll talk about kind of a new twist on it, which is how to manage it. And then as kind of a preview, we'll end by talking about the metric I see coming after it. There's a request in the chat for defining Churn, which I'll get to. I'm going to try and keep one eye in the chat. It's hard, to be honest. I got three monitors up. I'll define CHURN in. In short, it's ARR that leaks out of your bucket and that will mean more in just a minute than it did right now. So that's what we're going to talk about. But first, let's just go look at the profit and loss statement. We'll start here. And this they say the average American family has 2.5 children, right? Like there is no actual average American family. This is the average SaaS company. For each of these lines, I took the median off Meritech and they have a great kind of public comparables website on their website, microsite on their website. And I took the median company. So this is the median revenue, the median cogs, the medium gross profit. And I just laid it out into a P and L. So this is many ways kind of the typical public SaaS company. By the way, it actually looks a fair bit like Alteryx. Not in all respects. Alteryx has better gross margins and other things. But if you had to say who was closest to this kind of just eyeballing it in the data set, it's not miles away from Alteryx. But in any case, this is not Alteryx. This is the typical medium SaaS company. And the answer of where customer success fits into the P and L is sales and marketing. By the way, good question. So trying to keep one eye on that. But in any case, the reason it's hard to understand a SaaS business, when you look at the P and L, there's kind of. There's actually two different reasons. There's what I'll call the usual suspects here. And then in the next slide we'll talk about the more conceptual reason. But the usual suspects are. First, the public companies don't disclose ARR annual recurring revenue. Right? They don't disclose it. An ARR is your subscription base. How many people are signed up, if you will. Revenue is basically a math problem. If you know ARR, then revenue is simply a calculation and it is a lagging indicator, not a leading indicator. Which is why financial analysts don't really look at revenue as much. They look at billings. And billings is a public company SaaS metric. It's revenue plus change in deferred revenue. And it's a way to try and impute what bookings are, but they aren't released, that is new sales don't get released. So you have to kind of triangulate on it. ARR needs to be implied in the same way churn is typically not disclosed. So you really as a public company investor are getting fairly limited visibility into the core engine driving a SaaS business. Now if you think about it, it's kind of a one way transformation which is given ARR, I can in a deterministic way calculate a plot given a P and L, it's non deterministic. To get ARR, I can come up with an infinite number of solutions that will generate that P and L. Maybe not infinite, but I can come up with a lot of different solutions that will generate the same pl. So it is tricky to interpret public company SAS metrics. In fact, I once met, ironically, a public company SAS CFO who didn't actually understand SAS unit economics because public company investors can't see them. So crazy stuff. The other problem with trying to understand a SaaS business is it's actually two businesses. You have this overall business that has $465 million in revenue and it's composed of two very different businesses. One, the recurring business, all those existing customers who hopefully renew every year, right? And every year give you revenue. We'll call that the recurring business. And next to that is a other business called a customer acquisition business, which is out getting customers. And look, I'll walk down the P and L. Let's just assume it costs the same to serve either type of customer. So 23% cost of goods sold. So each business has a 77% gross margin. Now, that's where the similarity kind of ends. If we look, you could argue that 100% of sales and marketing in a SaaS company is to get new customers. It's not entirely true. Somewhere typically around 10% might be the cost of customer success to keep those existing customers. But just to make the math simple, I put all of sales and marketing into this business that's out getting new customers and none into the business that's recurring, right? Keep the math simple. I split R and D. I just said half of R and D is to keep existing customers happy and renewing half is to put in shiny new features that attract new customers. I split GNA on a similar basis. Probably should have prorated it by revenue. Didn't do it, but I just put GNA5050. When you do this exercise, what pops out is you see that a SaaS business is awaited average of this incredibly profitable recurring business with 55% operating margins and this incredibly unprofitable customer acquisition business. Now, the good news about the business on the right is that it is feeding people to the business on the left, right? In many ways, in order to make things simple, I tend to be very black and white and kind of do dichotomies, just like putting all of sales and marketing into the new business business. The other way to think about this is private equity cares a lot about the middle column, the recurring business. And lenders who lend to private equity care a lot about that because that's the annuity portion of a SaaS business. And venture capitalists care a lot about the right side, right? Because they want to know how fast you can grow this thing and how efficiently you can add new customers. Now, in the dark recesses of virtually every board member's mind, at one point or another, somebody thought, look at what happens when you turn off sales and marketing. Gosh, I have this incredibly profitable recurring business, right? And obviously you can't do that. As mentioned, you need some sales and marketing to keep the recurring business going. And then you'll, well, in effect, you'll stop growing. But will you? Right? That's what net dollar retention is actually measuring what happens to this business if you kind of just leave it alone, right? And the fantasy, and it is a fantasy, is what if it grew all by itself, right? That recurring business if it could just grow, if I could get rid of that other business, how much is that recurring business worth? And the answer is, of course, as mentioned twice already, it doesn't grow all by itself. I'm oversimplifying to make the point clear, but by the way, it does grow at 40% of the cost of new log customer acquisition. If you look at the customer acquisition cost ratio, for example, in the KeyBank survey that I'm citing down below, you'll see that the expansion CAC or the customer acquisition cost of expansion ARR is about 40%. That is less than half of the cost of new logo ARR. So this thing doesn't grow all by itself, but gosh, it certainly does grow a lot cheaper than that very expensive new customer acquisition business. Now let's go back to private company land, because I started us in public company land with the kind of average public SaaS company. But look in private company land, which is where most of the people I think on this call come from. We get to see the underlying SAS engine. And now for the person who asked about the definition, here's what I call the SaaS Leaky Bucket, which is I think of a SaaS company as a leaky bucket full of ARR every quarter. Sales dumps more water in every quarter. Customer success tries to minimize the leakage out. We start with a certain amount of ARR, 3.9 million. In this case, in 2Q of 19 we added 525k of new ARR, of which 400 was new logo, 125 was expansion. So new ARR comes in two basic flavors. From new customers or from existing customers. And then despite their valiant efforts, 100 units of ARR leaked out of the bucket, therefore leaving us with 4.3 million in ending ARR. You could just keep running that thing every quarter. Obviously ending ARR in one quarter is starting ARR the next. And you could get some good metrics just off this. How fast is your ending ARR growing? Year over year. In fact, if you only had two numbers to give you the value of a SaaS company, it would be ending ARR and growth rate. I could then tell you roughly what that company is worth. Kind of a first order valuation. Another interesting metric is net new ARR. So if you subtract the churn from all of the new ARR, how much did the water level in the bucket change? There's a lot of ways to look at expansion. One simple way is just expansion as a percent of new ARR. People don't Talk about this enough. I think it's a real simple to understand metric to me. When it's less than 20%, maybe you're not exploiting your expansion opportunity much as much as you should be. When it's over 40%, maybe you're not getting as much new logo as you should be. Right. So I personally like it running in the 20s and 30s. And then there's net expansion, which is kind of all in. If we not all in. If we take new ARR. Sorry, if we take expansion ARR minus churn ARR, what do you have left? So that's kind of your net expansion of the pool. And you can see this company is not doing particularly well on that metric. It went up 25k, that is expansion offset churn by 25k in 219, but then it immediately went negative and offset the increase 3q19. So this company is actually struggling with that metric. But anyway, once you're looking inside a SaaS company's kind of leaky bucket and you can see the ARR engine, as I might call it, you can then calculate these kind of core SaaS unit economics metrics. So yeah, new logo to me is a lot of different terms for it. Some people call it net new, which I don't like. To me, when you get ARR, you either get it from a new logo, that is someone who's not an existing customer, or you get it from an existing customer. So new ARR from somebody you're not doing business with is what I'll call new logo ARR, some people call it new biz ARR, some people call it net new ARR, but I think it's misleading. And when you get ARR, like if you were an existing customer paying me 100 units and you expanded your contract to 120, that would be expansion ARR, sometimes called upsell. And there are fine distinctions between those terms. But grosso moto, that's a good set of definitions. So probably my favorite SaaS metric is the customer acquisition cost ratio, which is how much are you spending to put a dollar of ARR in that bucket? Right. So it's last period sales and marketing expense divided by this period's new ARR for SAS metrics. Nuts, that's actually the inverse of the magic number which Skale Ventures came up with. I prefer it in this form because it's more intuitive to me to say how much did a dollar of ARR cost me? So I like the CAC ratio. Very important SAS metric, you know, typically runs around 1.3, you know, below 1.3 is getting to be quite good. Below 1 is really good. Best I've ever seen was 0.4. Anything between 1.5 and 2, people start to scratch their eyebrows. Above 2 people get nervous. Above 3 people won't talk to you. Roughly. So lifetime value is one over the churn rate. And this is actually customer lifetime. I made a mistake on the slides. It's a little confusing, but. But the lifetime value is basically the ARR per year times lifetime and the lifetime is 1 over the churn rate. So if you have a 10% churn rate, we would say your average Customer lifetime is 10 years. Now this is where it gets interesting because there's this notion of, well, wait a minute, is a CAC of 2 too high? Right? If I'm spending $2 to get a dollar of ARR, is that really too much? It's on the high side compared to averages. But for my business, is it too high? And to answer that question, the best way to do so is say, wait a minute, you paid $2 for something, what's it worth? Right? If you have a very high churn rate, just say you have 50% churn rate. It's a terrible deal, right? Because you paid $2 to get a dollar and a half, right? Because they went one year and half of them churn, you only got a dollar and a half back. So that's not good. But say you have a 10 year LTV. Well, gosh, if I have a CAC ratio of two at a 10 year LTV, then my LTV to CAC is five and that's pretty good. I'm getting back five times what I paid, which helps pay for all those other expenses like R and D and G and A and everything else. So LTV to CAC for me for a long time was ultimate SaaS metric. Like this is it, this is the one that kind of explains everything. It's kind of a balanced scale between how much you're paying for CAC versus how much you're getting back in ltv, right? And conversely, by the way, if you have a really low cac, great. But if you have a very high churn, well, great, you can acquire customers, you churn after a year very cheaply. Who cares, right? It's not a great business. So another metric which is very popular, and I mentioned it here because VCs look at it a lot, is CAC payback period. And this is kind of my unique way of calculating it, it produces the same answer. But if you Just take your CAC ratio and divide it by subscription gross margin you get in years. The CAC payback period. What does that mean? If your CAC is 2, that is you're spending $2 to acquire. Let's say your CAC is 1.5. Make the math easy. You're spending 1.5 dollars to acquire a dollar of ARR and your subscription gross margins are 75.75, 75%. Then that means you get paid back your CAC in two years. Right? 1.5 divided by 0.75 is 2. So how many years of gross profit does it take to pay back the sales and marketing costs of acquisition? A lot of people love this metric. You know, VCs in general, kind of like all in one metrics because they're trying to make an investment decision. I always feel like operators don't love these metrics as much because if it's too high, I don't know which side of it is broken. Right? If my CAC payback period is too long, is it because my CAC too higher, my subscription margin is too low and as an operator I want to go fix it it. So in some ways operators look at SAS metrics a little bit differently than investors. So you think we're good? Hey, we just did SaaS unit economics 101. We looked at the public company view of a SaaS company. We looked at the private company view. We examined really what are the core key metrics? The leaky bucket CAC LTV to cac Churn. We're good, right? Well, no, not so fast. Increasingly over the last several years, I personally and I've blogged a lot about churn. I've become increasingly skeptical about churn rates. And I, I almost entitled this section kind of tongue in cheek, why private equity firms recalculate all your metrics. Because people play games sometimes with their SaaS metrics. And the VC side, frankly, I don't see as much recalculation. But when you meet PE people, they will literally take all your financials and just recalculate everything. You're going to say your churn is only 10%. They're like, well, we'll figure out what your churn rate is. Just give us the data and we'll calculate all the metrics. And the reasons we're going to talk about in here are some of the reasons why. So churn in my mind has kind of of three fatal flaws or not fatal, but you know, in reality, look, the title of the speech is somewhat Dramatized I wouldn't say churn is quite dead. I would say churn is wounded. And the problems with churn are threefold. First, there's too many darn ways to calculate churn, and that makes it ambiguous. Which one are you talking about when you tell me a churn rate? And by the way, you know, it could easily double the number and any number that, if you don't know how it's defined, is off by a factor of two. It's kind of a big deal. So it's a little bit too gamable, It's a little bit too misunderstood. Second, churn is used in downstream metrics like LTV to cac. It's implicitly in there. And unfortunately, if you pollute churn, you pollute everything downstream of churn. So in my mind, churn inflicts kind of collateral damage on LTV. There's a question of, in a SaaS company, what goes into COGS to compute gross margin? On the last slide, the answer of COGS in a subscription COGS to the SaaS company is the cost of running the service. So in the old days, if, if you had a data center, you'd have all your data center costs and your tech ops cost in there. In a modern days, it'll be the check you write to Amazon in all likelihood, and the people you have, and the check to Amazon for running your SaaS service. Let me just see. There's a couple other questions up here. There's a lot of questions about new logo. I think we got that one covered, right? New logo is somebody you haven't done business with before. Do I recommend a reporting system? We'll come back to that. So in any case, back here to the content off the Q and A, Churn inflects collateral damage on downstream metrics. And finally, Churn, if you get into the details, there is kind of a dark rabbit hole of offsets and timing that even makes Churn ARR that one number. Forget rates, just Churn ARR itself a tad ambiguous. And let's jump in. I'll explain what I mean by each of these. So problem one, number one is there's actually at least four ways to calculate churn rates. You can either say before expansion or after exposure. So if I had 100 units of ARR in my bucket and 10 units leaked out from people who didn't renew and 15 units of expansion happened, did I have 10 units of churn or did I have negative 5 units of churn? Am I looking at churn before expansion or after gross? Churn is before expansion, net churn is after. And sometimes people reverse those two terms. It's not that uncommon. So another confusion factor in churn, what does net mean? Is it net of or net? But in any case, by definition, gross is what leaked out of the bucket. Net is what leaked out of the bucket offset by expansion. Right. So you have which one are we talking about? So that's the numerator. And then in the denominator we have. Well, what are we dividing this by churn as compared to what? Either the two most common flavors are one, the entire ARR base. Right. My whole subscription base or my available to renew base. Now how could those be different, you might ask. Well, the answer is multi year contracts. Just say you do only 2 year contracts. If you have a ARR base of 100 units, only 50 comes up for renewal every year. If you do 3 year contracts, only a third of it comes up every year. If you do a blended average, as I did at my last company, of 1, 2, 3 and the occasional 5 year contract, some blended average of those contract durations come up every year for renewal. So this is a huge swing factor on churn. And it's, and it's hard to argue which is right or which is wrong if you're trying to value the annuity as a financial person, I guess you should get the benefit of those multi year contracts. So let's divide by 100 instead of dividing by 50 because mathematically they can't get out of those contracts. And if you have a history of renewing them and people not breaking out, then in reality that's kind of the true churn rate. But on the other hand, if you're trying to understand the health of your business, if 10 units leaked out against 100, that's 10%, not bad. If 10 units leaked out against 50 because only half the base is up for renewal 20%, I'm getting pretty nervous. I don't know about you. So the issue is you make the matrix. You have four different ways of calculating this metric. And to me it's a huge problem. And people often try to dress up one as the other. They'll kind of deliberately confuse net and gross. They'll deliberately confuse ARR with atr. And you know, obviously the most favorable metric is net is number four, the one. By the way, I've ranked them in order of if I could only see 1, I'd want to see gross ATR. If I could only see 2, I'd want to see gross and net ATR. If I could see 3. I'd want to see the same order on ARR based churn rates. So my kind of quip on this is other than not knowing what the numerator is and not knowing what the denominator is, it's a great ratio, right? So there's a problem to me with churn rates. You can argue this is not a lethal problem. PE firms will just go recalculate this for you. A rigorous VC will kind of grill you to make sure you're actually telling them what they understand, which box they're in when you answer. But that's only the first problem. Let's talk about the second problem. The second problem, as we alluded to, and there's really kind of two problems in here, is that churn blows up stuff downstream. So to the extent that churn is now less meaningful than we'd like it to be, now LTV is less meaningful or lifetime, really? This is where I made that same mistake again. This is really the customer lifetime which affects LTV is now blown up as well, right? So if your churn rate is 10%, 1 over 10 is 10 year lifetime. Oops, just kidding. It was actually 20. Oh, now it's a five year lifetime time. So this metric is now polluted by the pollution inherent in churn. So four different churn rates means you effectively have four different LTVs. So that's the first problem. The second problem is that very low churn rates break a lot of these ratios. If you have negative churn, that is, you know, net churn, that's negative, that is you expand more than you shrink, then you have infinite ltv. Well, I don't like that. I mean, I don't like a key metric that breaks when you're in a desirable condition because you want to have negative churn. So I don't want to know how negative. And now the metric's broken because I can't measure it. That's not very encouraging. The other problem is more of a math problem, is when churn rates are very low, a lot of it ends up heavily in the future. You get a very high, very long lifetime and a very high lifetime value. But like half the lifetime values after year 10, right? Or after year 25. And look, a four year old company talking about a 25 year customer lifetime does make me at least uncomfortable, right? Like how credible is that? So you say your customer lifetime is six times longer than you've existed. So that's a little dubious. The other problem with these very low churn rates is you get these very long lifetimes. So either you have the heavily future weighted problem or you have the arbitrary cap problem. So one time I was working with a banker to sell my last company and I saw them calculating LTV and I saw that formula in the spreadsheet and I'm like, what are you doing? And the answer is, well, because of the long lifetime problem, if the churn gets too low, the lifetimes get too high. So I'm going to cap it at 10 years. So we're going to calculate it and we'll take the minimum of 10 years and the calculated value. And as soon as I see that kind of stuff around a SAS metric, it just makes me super uncomfortable, right? Because now I have four different churn rates. I have the low churn problem and the super long LTV problem. And now I'm inserting an arbitrary cap kind of silently and it's just making me very skeptical. And by the way, as mentioned, if we've blown up lifetime value, we've then blown up lifetime value to cac. So the metric that I once blogged as being the ultimate SaaS metric is now kind of polluted as well, because all these downstream problems coming from churn. Now let me just take a quick. So problem number three. Churn ARR itself can be non obvious. And this is really in the detail, so I'm not going to spend too much time here. But there are timing issues on calculating churn. I'll just give you a couple examples. Say somebody at renewal time drops 30 units of product A and adds 40 units of product product B. Do we count that as 30 units of churn and 40 of upsell? Right. Which is going to drive up my churn rate and my expansion rates. Potentially not net expansion, but my upsell is percent of new ARR will go up, right? Do I look at it that way or do I look at it as just 10 units of upsell? I wouldn't agonize over this one too much because as it turns out, most people, most finance and ops people, this is not a hard question. They just go, that's 10 units of upsell. Now, if I'm a product manager, I sure as heck would like to know which products are losing customers and which are gaining customers. So the product management perspective on this might be different, but the finance perspective is what I call account level churn. Hey, we care about this customer. They went up by 10. This counts as 10 units of expansion. And effectively that 30 units of what some people call product churn is effectively Invisible because it's been completely offset. So in any case, that, that's one problem, which is at renewal time, how do we offset shrinkage and expansion? Not that hard. But it makes CHURN ARR a little ambiguous. The other problem is what I call upsell along the way way, which is somebody starts out at 100 units, six months later they expand to 140 and they renew at 130. And the question is, gosh, is this 30 units of expansion or is this 40 units of expansion and 10 units of churn? How do I count that? And look, the company itself, I'm going to argue is schizophrenic because when you're making the fundraising deck, right, you want to call this 30 units of upsell or expansion. But when you're doing CSM comp plans, you want to set, darn it, Mr. And Mrs. CSM, you lost 10 units on that contract. You couldn't renew it at full value. So I'd argue the company itself even gets a little bit confused and then finally we'll talk about this more at the end. But built in expansion. So just say you sign a deal where it's a three year contract, 100 in year one, 120 year two, 140 in year three. If you're going to think about like LTV to CAC calculations, this is more of a CAC thing than a churn thing. But what's the CAC? How much ARR did we acquire for that sales and marketing cost did we acquire, Some might argue 360 units? Well that's not ARR, we got 360 units of revenue, but of ARR, we got 100 units, the initial ARR and then we counted as 20 units of expansion in year two and year three. Or do we flatten it out and say it's 120 across three years? Or if you want to be aggressive, do you say no, we acquired 140 units of ARR. We just haven't realized that year yet. So which is it? Do a terminal ARR average ARR initial ARR. If I'm doing LTV to cac, I need to know the answer to that. So look, as was once said about cash and profit, there's a semi famous quote that cash is a fact, profit is an opinion. I feel the same way about ARR and churn. That ARR is a fact, Churn and churn rates are an opinion. And that's what makes me uncomfortable with churn. And that's why I was kind of thinking how can we solve this problem? Because it's just so detailed, few people really want to talk about the four ways to calculate it. The four different LTVs, the timing and offsets with all that stuff kind of just, you know, bores people, confuses people. So how do we try and answer the question that we're trying to answer, which is how healthy is your installed base without just getting kind of sucked into the weeds? And the answer is to zoom out, not in, right? And I have one word for you cohorts, right? So let's talk about net dollar retention. So net dollar retention. Actually, I'm going to just take a quick look at the Q and A here. So how does uncontrollable churn versus controllable churn fit into this? I mean, first, that's a great question. Those terms are super undefined in my mind, right? And even then I think, what's the example? The example at my last company would be that, oh, they got a new CFO and they churned. Or worse yet, they got acquired and then churned. So we're going to call that uncontrollable. We couldn't control that, so we shouldn't really count that kind of churn. But the issue is it's not that simple, right? Because let's just say the reality was they bought the solution, they were not super happy with it, got acquired and then churned. Oh, that's quite different now, isn't it? Because if they were super happy with it, maybe they would have fought to the death to keep the system rather than just use the system the parent company told them to use. And maybe that would have worked or maybe it wouldn't have. So to me, controllable versus uncontrollable churn. It is a concept people talk a lot about, but I get super uncomfortable because I think it could easily be a cop out, right? You know what? Like my last company, they got a new CFO and they didn't renew. We can blame the new cfo. But if the new CFO asked the head of finance how they like the solution and that person was only lukewarm, the new CFO would say, gosh, just use my system, then I've got a great one, right? So I'm skeptical on the notion of uncontrollable churn. Do I care more about logo churn or ARR churn? I tend to look at SaaS businesses through an ARR lens. And I do that because. Because partially because the last SaaS business I ran was bimodal. We had A corporate sales channel that had a 25k ARR ASP and we had a field sales that had a 75k ARRASP. And therefore if you looked at things like customer counts, they weren't that meaningful because we actually had almost no average customers. Right. There were no 50k ARR customers. So because in my mind, the more your customers all look the same, the more you can just look at counts. Right. Just counting the number of people as opposed to looking at the ARR that churned. The more your business is two, three different businesses all in one. Right. The more to me you need to net it all out and just look at ARR. So I don't do a lot of count based metrics, but a lot of people do. They'll define churn as we had 100 customers, 90 renewed, therefore churn is 10%. I greatly prefer to look at ARR churn. So thank you for asking that. Yeah, usage based pricing and SaaS with seasonality. That's a tough question. If we have time, we'll come back to it at the end. Where do you put the cost of retention, support, customer success, etc. So you're right, I left customer support out of COGS. They do belong in cogs. Customer success in my opinion does not belong in cogs. It belongs in sales. And most companies will put customer success in sales. I have seen on occasion people put customer success into cogs. And the argument for that is if it's really a set of services to kind of keep you and get you up and running, it's a cost of running the service. If it's really about renewing contracts, it should be in sales. In my mind, some might argue gna and if it's about trying to drive upsell and expansion, that it definitely belongs in sales, which. Well, I won't go to the next level on that. So let me just go back to Q and A. Do I see anything else here? Oh darn. I was looking only at the top of the Q and A. I'm sorry. What about customer support? We got that one long term contract. What goes into acquisition versus recurring? Yeah. So the question, let me answer that one. If you do a five year contract for 100 units of ARR and I had that split SaaS business, where does the revenue go? And the answer is in year one it would go in the right hand column and in years 2, 3, 4, 5 it would go into the center column, the recurring business. That's where the revenue goes. The more interesting question, Randy, is where's The CAC go. Especially if that contract's expanding. If I take that sales marketing cost to acquire that ARR, am I dividing it by the tcv, Am I dividing it by the starting ARR, the average ARR, the terminal ARR. By the way, the sales comp plan, what do you want to incent your sales force to do? Is all tied up in that. So let me just go down here, Sorry, the Q and A, I've been at the top of it. So. Good, good, good. How do you factor mid contract churn versus contract renewal? Yeah. Oh wow, you have mid contract. Well at first that's not a good sign in my line. I've seen very little of it frankly. I've always surprised that you don't see more cancellations of multi year contracts. Like you sign a three year contract and people, they kind of just assume it's going to renew every year and I'm like, well just because they signed the contract, if they're really unhappy with the system, you may not get that. You know, it's not a renewal, it's a payment. But you may not get that payment in year two. And maybe in fact if you want to optimize getting that payment, you might be better off treating it like a renewal, even though it isn't. So now mid contract churn means somebody's pretty unhappy. And the question is, look, if, let me pick the. I think that's what you're hitting on. Say it was a three year contract and they decided to stop paying in years two and three first. You could sue them if you want to. Right. A contract is a contract. I don't recommend. Suing customers is a great strategy, but technically speaking a contract is a contract and if you're seeing a lot of that, to me there's a big problem because frankly I've seen very little of it and I've worked with some companies where there are kind of serious product issues, are not that happy, but they're still paying. But the short answer is it's not churn, it's actually what is it? Let me think about that. So somebody refuses to renew. It wasn't up for. It's a great question. Right? Because it's not in the ATR base. Right. So it won't show up in ATR because you're going to have 100 units of churn that was. It's in the numerator, but it's not in the denominator. Technically speaking it's actually bad debt. Debt. Right. But you should take it out of The ARR pool. So personally I would probably put it in adjustments. I mean just to be clear, this is now the advanced level. But in that leaky bucket I have one other row called adjustments and I would put that into an adjustment. It's. I might put it into churn. I need to think more about that. I'd probably just put that one in Churn. What goes through adjustments is like currency. Like just say you have some of your euros and some of it's in dollars and the size of the pool change due to the currency rate changing, that would definitely be an adjustment in the leaky bucket, I guess convinced yours would actually be churn. And I would count it in the period in which it occurred. And if I had much of it, I'd be very concerned quite frankly, because to a certain extent I'd also stop doing multi year deals because if you're giving someone a price lock for multi year deal and they're not renewing, you gave something and got nothing. So anyway, let's come off the Q and A back to the, back to our regularly scheduled content here. So look, this problem trying to figure out how healthy the install base is. It's a great problem for cohort analysis where we just step back rather than stepping in. Because when you step in, it's quicksand. We step back and say let's just grab a cohort. Typically all customers, what were they worth one time period ago? Let's just say a year ago. And now. What are they worth today? Now that's net dollar retention, today's value of their ARR. Right. In ARR, there's some questions of that. It's just annual recurring revenue. If you agree to pay me 100 units a year to use my service, your ARR value is 100. So what were they worth a year ago? What are they worth now? And the beauty of this metric is three things. One, it's easy to calculate, it's easy to understand, and it's hard to game. And that's my biggest problem with Churn, ultimately is it's easy to game. I got four different ways, plus some other things I could do to fudge it. So now there are a few bad apples who survive or bias this. Unbelievably public companies actually do this and what they're effectively saying is, well, excluding the customers who aren't doing business with us anymore, the cohort almost definitionally expanded by end by percent. Right? So instead of taking a set of customers a year ago and looking at what they're worth today, they do it backwards. They take a set of customers today and look at what they were worth a year ago. And that's survivor bias, because we've excluded everybody who's not a customer today. So the only way to gain that dollar retention rate is to survive or bias it. And sadly, some people do, but most people do not. So look, the idea of cohorts is not new. Virtually every S1, this is Datadogs, will show by year the value of cohorts. So the purple is all the customers acquired in 2013 and how they've evolved over time and value, et cetera, et cetera. So look, the idea of looking at cohorts and SAS is not new. The idea of making this kind of chart is not new. And this kind of chart is my mind. Not only is it not new, it's quite standard, but what is newer is netting this out to a single number. Because if you get a single number, you can benchmark it, right? It's hard to benchmark this chart. I can't readily compare it to other charts. I mean, I can look at it, but benchmarks I can do off data. So. And by the way, net dollar retention is actually a very popular metric, right? So there's Martin Casado and Andreessen in a tweet stream about what metrics he likes to see. It's either in a board deck or investor back, I can't remember. But you've got net and gross dollar retention. And by the way, remember I said some people define them inverse of how I do. He's one of them, right? So you can see he's saying that gross includes churn and downsell and that does not. But in any case, a real example of where people use those terms backwards relative to each other. But in any case, both metrics are important in his mind and in mine as well. You have Alex Clayton, a great SaaS blogger who has done blog posts about net dollar retention rate and IPOs. Recently this guy Zach Kukoff, put a tweet up showing the net retention of IPOs of SAS tools selling to developers. And you can see SnowFL 158, Twilio 155. Those are really epic numbers, by the way. Elastic 142. And then finally, John Ma, who I think writes public comps, I think is the name of his newsletter. You can see, here's what it takes to go public. In 2020, the average 1 had 330 million in ARR, 49% revenue growth and 120% net dollar retention. So this is a popular metric and I think it is popular for the reasons we cite it. It's easy to understand, it's easy to calculate, and it's hard to get game. So what is a good net dollar retention rate? About 115, right? I think below 100 people start to get scared. Right, because it's saying that your ARR pool kind of decays by itself. It doesn't expand. It kind of, if left alone, it shrinks. And that's not good. Not for lenders or not for private equity people, or not even for VC people. Nobody wants to see the ARR pool shrinking. So I'd say 100 is a practical minimum. I think between 100 and 105 it's kind of considered very meh. 110 is, I think, kind of the minimum good. And 116 is median. And I think 120 starts to be very good. And anything much above 125, 130 is getting into the epic category. I'm going to keep going here. So net dollar retention. This was kind of an unpleasant surprise, which is I did some linear regressions and I said, hey, how much does net dollar retention drive SAS multiples? If it's so important, I bet it's a big driver of SAS multiples. And the answer is, oops, it's not. The R squared is only 0.06 between debt dollar retention and enterprise value the next 12 months revenue. So it's not a valuation driver. I now think of it as a financing enabler. Okay, so a higher one isn't necessarily by itself going to drive a higher valuation. But I could tell you if you don't have a high enough one, you're not going to be able to raise money. It's still a super important metric. It just doesn't happen to be a good driver of valuation like ARR growth is. So the R squared between ARR growth and enterprise value multiple is 0.5. And then rule of 40, which is the balance of revenue growth and operating profit, in effect, it's revenue growth minus free cash flow or plus free cash flow is the rule of 40. And ironically you can see here that the rule of 40 at one point in time better explained multiples than growth than just revenue growth. And now in these kind of frothy times, the better predictor of your multiple is just simply how fast you you're growing, not how well you're balancing growth and profit. So that's kind of an interesting comment on the Times because for a Long time. The rule of 40 was a better predictor of your multiple, right? How well you balance growth and profit mattered more to your valuation simply than just how much you're growing. But right now it's kind of just. What is it? Just a full speed ahead. Grow as fast as you can and that's a better predictor of valuation. Now to move forward, let's start to wrap this up. Three pithy quotes to ponder. They're all basically saying, you know what, what gets measured gets managed, and various correlations. And when I was younger I viewed that less skeptically. I was like, oh, if you want to manage something, you should measure it. And now I kind of have a negative connotation on the word manage, which is like. And this is expressed by the economist Justin Wolfers down there with Goodhart's law. When a measure becomes a target, it ceases to be a good measure. I've actually blogged about this on pipeline coverage. I call it the self fulfilling 3x pipeline coverage fallacy or prophecy. The self fulfilling prophecy kind of ruined the metric by making it a target because now everyone's managing the metric and it kind of loses its predictive value. It's kind of what Goodhart's law is saying. But to flip that over and to play the operator side of this, hey, if I'm running a SaaS business and I know that NDR matters a lot to my ability to raise funding, if not my valuation, why don't I just build it in? Why don't I, when I make a contract with a customer, say, hey, we think you're going to expand your usage over time. We think you're going to have 100 units of usage in year one, 120 in year two and 140 in year. And how about I give you a price lock on those three numbers and I'll give you a 10% cushion if we estimate it wrong and you're going to pay me those three numbers over the next three years. And wouldn't that be nice? You get price protection, you get some cushion on expansion and I get built in ndr. So right there I have just locked in a near 20% net dollar expansion rate. Right? I've traded away potentially some ARR now but in my example I actually didn't because the usage was naturally expensive expanding. So I didn't really trade away anything other than the price lock and it creates this notion of pre sold expansion. The first time I saw this I was at a board meeting and there was a row in the spreadsheet called pre sold ARR. And I was like, what the heck is that? And the answer was it was this. It was the 20k of expansion in year two and the 40k of expansion in year three. I did a tweet a while ago about what do you call this? And the consensus average was initially ARR kind of average ARR in this case and then terminal arrangement. So look, this complicates as we talked about earlier calculations and sales comp compilations. But the good news is you're locking an expansion up front and that's great. If you're going to get measured on this metric, why not build it in? There is a very similar thing that is bad in my opinion, which is price ramping. And the difference between the left column and the right column is in the right column. The usage and value is not changing over time. All we're doing is tilting the price. We're actually in effect saying you really owe me 120k a year. But it's kind of a financing strategy. I'm going to tip that line. And it will drive on an ARR basis epic net dollar retention. But on a revenue basis, ASC606 will flatten it out. It will see right through this trick and you will just end up with 120k per year in GAAP revenue. And this also has all the downsides of the left hand column. And in my mind it's playing accounting game. So there's a real shade of gray here guys between what I think is good and what I think is bad. But the fact of the matter is if the usage is actually exposed banding and you lock it in, that's smart. If you're just tilting the price and it's really a financing game, it's probably not good. So to finish this up, the next frontier is I think the next metric we're going to see private companies start to look at is now kind of second billing in public companies. Rpo. Remaining performance obligation. It's the amount of contracted ARR you have under contract that is not kind of currently either been billed which is revenue, or been paid in advance which is deferred revenue. So if you're not releasing rpo, there is no other way to see it. The only way a company can you can know a company's RPO is if they tell you because it does not appear in the balance sheet. People sometimes confuse deferred revenue with RPO and they're not the same thing because it only ends up as deferred revenue if they've paid you, in which case it ends up in your balance sheet as liability. So this is not tracked much by private SaaS companies, but I think it's the next public company metric the private companies are starting to look at either as they get bigger and start to think about going public or just because investors private company investors are going to want to know because a SaaS company that has booked a bunch of three year contracts that largely get paid is arguably worth more than one that hasn't. So that's remaining performance obligation. Let's wrap this up here with takeaways. Look, a SaaS company is really the sum of two businesses, a recurring business and a non recurring business unit. Economics are great, but churn can be problematic. Problematic. When this churn gets polluted, it pollutes downstream metrics. The solution to all this is to zoom out, do a court based analysis to say how big was the base a year ago? How big is it today? That's called net dollar retention. A good rate is around 115%. Hey, if this matters so much, why don't we just build it in so we don't have to make it kind of a guessing game and then going forward, little preview for the future. I think startups are increasingly going to look not only at any ndr which is effective public company metric, but now rpo. So let me cut over. I think we're just about out of time. I may have time for one question and yeah, okay. They're hard. Yeah, I think we're going to wrap this up here. We're at time at 8:49. Thank you all for coming. I will post the slides and you can reach me at my blog or on Twitter elblog if you have further questions. Again, thanks for coming, good luck and happy expansion.










