Usage-based pricing models and revenue forecasting featuring Ray Rike
Speakers

Ray Rike, Founder of Benchmarkit

Kirk Kappelhoff, Senior Director of Strategic Finance, Drivetrain
A usage-priced customer with no minimum commitment budgeted $50K for your product. Its bill reached $60K, then climbed toward $120K, and now its CFO has told your account manager, "We have to consider options."
Ray Rike, founder and CEO of Benchmarkit, knows where that conversation leads. At the usage-priced company where he started his career, the largest customers were the most likely to leave. They were spending more than they had planned and didn't feel comfortable raising it with the vendor.
In this webinar, Ray walks Drivetrain’s Kirk Kappelhoff through how finance teams should count and forecast revenue that moves with usage. Watch the full session below, or read on for his working definitions of ARR, expansion, NRR, and CAC for usage pricing, a threshold-based approach to moving large usage-based customers onto commitments, and a customer-by-customer method for forecasting usage.
60:25Why does usage revenue grow faster and fall faster?
Usage-based revenue rises and falls with the billable units your customers run through your product, such as transactions, messages, or API calls. When a customer’s business grows, it sends more of those units through your product, and your revenue grows at the same rate. Ray illustrates this with a vendor that bills Uber per transaction. If Uber’s transactions grow 300%, the vendor’s revenue from Uber grows 300% too.
Usage-based pricing also makes it easier to win new customers. With no minimum commitment, a customer can start paying for what it uses without signing a large upfront contract, and Ray sees pay-as-you-go pricing as one of the fastest ways for an early-stage company to add logos. In the benchmarking research he has reviewed, many early-stage companies use usage as their primary pricing model, mostly with no minimum commitment, and they tend to grow about twice as fast as companies on subscription or seat-based pricing. In strong markets, large companies with usage-based pricing models, such as Snowflake, Datadog, and Twilio have posted net revenue retention of 140% to 150%.
The decline is faster for the same reason. A customer can throttle usage as soon as its budget tightens, while a customer with 100 subscription seats keeps paying until the contract ends. In the billing data Ray has reviewed, growth at usage-priced companies slows sooner and more steeply than at companies with subscription-based pricing when the economy turns. Subscription-based companies feel the slowdown later, when contracts come up for renewal. Companies with usage-based pricing also recover first, so Ray watches their growth as an early signal that the market is turning.
Industry concentration can make the drop steeper. Ray’s example is ZoomInfo. Ray’s example is ZoomInfo, which priced partly on contacts used and drew about 40% of its revenue from early-stage B2B technology companies. No other industry made up more than 6% to 8%, so when those technology companies stopped buying, nothing offset the drop and ZoomInfo’s growth collapsed. Ray’s advice is to track the economic conditions in each industry your revenue depends on.
What counts as ARR when part of the revenue is variable?
Ray recommends reporting annual recurring revenue (ARR) in two ways: ARR from committed subscriptions only, and ARR that also includes variable usage. Prepaid usage counts as committed. A customer that buys a million transactions upfront has signed a minimum commitment, so Ray would count that purchase in both ARR and bookings. A company showing $22M of committed ARR and $28M of variable ARR tells investors how much of its $50M could fall next quarter.
The SaaS Metrics Standards Board, which Ray co-founded, had to work out how usage-based pricing changes standard SaaS metrics, including whether usage revenue counts as ARR at all or only as GAAP revenue recognized as the usage happens. Its recommendation is to start with the chart of accounts, putting committed subscription revenue and variable revenue on separate lines.
Most companies with pricing models that include a usage-based component blend the two. Research Ray cited shows that almost three-quarters of them convert monthly usage revenue into ARR. He considers this a dangerous practice because investors can’t see how much revenue is at risk. It also distorts gross revenue retention.
...if you include variable usage-based revenue in your ARR and the usage goes down, gross revenue retention could go from 85% down to 72%...I didn’t really have churn; I just didn’t have as much usage.
What counts as expansion, and what belongs in NRR?
Ray recommends defining how long a new customer takes to ramp, counting all its revenue during the ramp as new, and counting revenue from growth after the ramp as expansion. In subscription software, the contract draws that line clearly: the first annual contract is new revenue, and any increase from month 13 is expansion. Usage-based pricing has no contract term to mark the line, and almost every company’s new customers ramp up, sometimes to 5, 10, or 20 times the revenue they started at.
The ramp might last one, three, six, or twelve months, depending on the product and the customer base. With a six-month ramp, expansion starts in month seven. Ray recommends using the same number of months for every customer. Where you draw the line also changes NRR. If you start counting expansion before customers finish ramping, their normal ramp-up is counted as expansion, and NRR looks higher than their real growth after onboarding.
NRR must also include downsells and churned customers. As an example, Ray recalled an earnings call where Snowflake reported 160% NRR, meaning its existing customers were spending 60% more than a year earlier. About 20 minutes later, it presented its forecast for total revenue growth as 55% for the next quarter. An analyst asked how existing customers could be growing 60% while the company grew only 55%, and whether Snowflake was “paying new customers to become new customers.” As it turned out, Snowflake’s NRR had left out the customers who churned.
To analyze ramp revenue, Ray suggests using a separately named measure, net expansion rate, which compares a cohort’s ARR or GAAP revenue over the last 12 months with the same customers’ revenue in months 13 to 24. Because net expansion rate leaves churned customers out, so Ray treats it as a complement to GRR, which counts churn and downsells but not expansion. Together, they show both how much revenue you kept and how fast the customers who stayed are growing. Ray has seen several companies use the same calculation, under the name “two-year look-back,” as a proxy for net expansion rate.
How do you measure CAC payback when new revenue isn’t committed?
Ray says to choose the revenue basis for CAC payback and the CAC before you calculate them. CAC payback and CAC usually compare new ARR with sales and marketing expense. Payback is typically calculated after adjusting the new ARR for gross margin. But a small commitment followed by a six-month ramp leaves no settled new-ARR figure. Ray's default is to use the first 12 months of contract value, though three or six months can work if applied consistently.
The expense side can reflect how your deals are sold. Depending on your sales cycle length and average contract value, a company might take marketing expense from the previous quarter and sales expense from the current one, so each cost lines up with the customers it produced. Ray’s rule is to choose a time lag that fits your business and apply it the same way every period.
For land-and-expand deals, Ray offers a different option. Say an automotive customer commits $10K, and customers of its size in the automotive industry typically spend $100K in their first 12 months. Calculate CAC payback on that $100K of annual projected revenue, then recalculate it on actual GAAP revenue 12 months later. A projected 23-month payback might come in at 21 or 28 months, which holds the leadership team accountable for its forecasts. Ray recommends running both calculations by customer segment, because enterprise and SMB customers differ in acquisition cost and projected revenue.
So I strongly recommend you do both a booking/forecast model and an actual GAAP revenue model.
When and how should you move usage-based customers onto commitments?
Ray suggests moving usage-based customers onto commitments once your company has grown to the point where investors want predictable revenue, and once a customer’s spend has passed a threshold your company sets. Even then, the commitment works as a floor. The customer agrees to a minimum, usually in exchange for a lower unit price, and keeps paying for usage above it.
Ray doesn’t treat commitments as the goal for every customer. In his research, few companies charge on usage alone with no subscription or minimum fee. A minimum commitment with usage charges on top is far more common. He also noted that the goal for how many customers to move onto commitments differs from company to company.
The push for commitments usually comes with scale. As a company grows, investors start asking what revenue will look like next quarter and over the next 12 months. That’s when Ray expects the company to start asking its larger customers for commitments. Twilio followed that path, sending enterprise salespeople to offer a lower unit price in exchange for minimum commitments of $100K or $500K.
…History repeats itself. Early days, less friction, less commitment. As you scale, more commitment, lower unit economic cost.
Customers often prefer to skip the commitment at first. Early in Ray’s career, his company’s customers included Dell, Sun, Ford, and Toyota, and they liked not having to commit upfront. Two or three years later, their bills had kept rising, and their CFOs couldn’t budget for them.
Ray suggests that your company set spend thresholds, such as $10K, $25K, and $50K, and have account managers offer each customer a lower unit price in exchange for a minimum commitment as it crosses one. The offer heads off a budget surprise before the customer’s CFO starts weighing options. To make the conversions happen, Ray recommends giving the account management team a compensated goal: convert a share of usage-based customers to minimum commitments worth at least 80% of what each billed over the previous year.
How do you forecast usage you don't control?
To forecast usage-based revenue, Ray recommends starting with each customer. Forecast usage for every customer and every customer cohort, from the bottom up and the top down, for the next three months and for each of the next four quarters. Ray calls the result annual projected revenue.
Earlier in his career, Ray held sales, account management, and finance jointly accountable for the forecast. And today, he recommends naming an owner for each forecast, such as the account manager or an FP&A analyst covering a region.
Investors will ask how accurate those forecasts are. Ray noted that the average company’s new-business forecast is already off by 11% to 15%.
Ray said this kind of forecast accounts for four drivers that vary by segment: industry trends, each customer’s business, seasonality, and how far each customer is into its ramp. If mortgage refinancing is expected to grow 30% next year, that growth belongs in the mortgage segment’s plan and quotas. If you charge retailers a percentage of their sales, your revenue from them will peak in Q4.
If I'm selling to OpenAI right now with a variable-based product, I'm pretty sure it's gonna grow a lot faster than if I'm selling to Salesforce.
Ray distinguishes cohorts, which are grouped by start date, from segments, which are defined based on customer type (e.g., enterprise in the US or mid-market in Europe). He recommends forecasting each cohort at least one or, ideally, two levels lower by both segment and product type, using trends from the last one to eight quarters. He acknowledged that this approach can get difficult to manage in Excel, so he advises building the capability when you first introduce usage-based pricing.
Billing cadence carries the same variability into cash flow forecasting with usage-based pricing. Most companies in Ray's research bill overages monthly, with comparatively few billing quarterly or annually.
How do you build these definitions into your model?
Ray’s definitions only help if your model applies them the same way every period: the ramp length, the revenue basis for CAC payback, the time lag between expense and new customers, and the split between committed and variable ARR. That takes a model that pulls data from your ERP, billing, CRM, and product analytics systems, and lets you change a definition in one place without rebuilding the calculation.
How do you change a metric definition without rebuilding it?
In the demo, Kirk built CAC in Drivetrain from two systems: sales and marketing expense from NetSuite and new customers from Salesforce. Both flowed into Drivetrain and lined up by period without manual matching, and Ray noted that getting that source data is the biggest issue with these metrics.
Kirk then showed how to adjust the definition: shifting expense to the previous month or quarter, limiting it to the sales department, and filtering new customers by vertical or region.
How do you build the cohort forecast?
Kirk called a waterfall cohort analysis the best way he's seen to forecast usage. It takes two inputs: the number of new customers expected in each monthly cohort, usually estimated from history, and a retention curve that defines how each cohort behaves after its first month.
Every new cohort starts the curve over from its first month, so at any point the forecast is the sum of several cohorts, each at a different stage of the same curve. The curve can also rise above 100%, which lets the same model forecast usage revenue from customers who stay and grow.
Kirk noted that the same waterfall can be built in Excel, but it usually takes nested IF and INDEX-MATCH formulas that are hard to update. In Drivetrain’s revenue forecasting tool, the waterfall is a single expression that multiplies each new cohort by the retention curve. To plan conservatively, a scenario can swap in a lower retention curve. If you’d like to see that forecast run on your own customer data, book a demo.
About Ray Rike
Ray Rike is founder and CEO of Benchmarkit, a SaaS benchmarking firm whose database covers 18,000 B2B SaaS companies. He spent the first ten years of his career, in the 1990s, at a provider of mainframe-hosted applications priced on usage. Over the following 25 years, he worked at venture-backed subscription software companies with five exits: two to strategic buyers, two to private equity, and one IPO. He co-founded the SaaS Metrics Standards Board. Ray also joined Drivetrain for a webinar on investor vs. operator metrics.
Summary
- Usage-priced revenue grows faster than subscription revenue while customers’ businesses are growing and falls faster when they cut back because it moves with how much each customer uses your product, and customers can throttle usage at any time.
- To predict revenue with unpredictable usage-based pricing, Ray recommends reporting committed ARR separately from ARR that also includes variable usage, and offering large usage-based customers a lower unit price in exchange for a minimum commitment.
- Ray recommends that companies with usage-based pricing set a ramp period for new customers, count revenue growth during the ramp as new ARR, count growth after the ramp as expansion, and include downsells and churn in NRR.
- CAC payback and the CAC ratio both need a defined basis for new revenue. For land-and-expand deals, Ray suggests calculating CAC payback by segment twice: once on projected revenue at signing and again on actual GAAP revenue 12 months later.
- Ray recommends forecasting usage customer by customer and cohort by cohort, bottom-up and top-down, with an account manager or FP&A analyst owning each forecast, because each customer’s usage depends on its business, industry, its seasonality, and how far into its ramp period it is.
Questions from the webinar
Does usage-based pricing earn a higher valuation multiple than fixed-license pricing?
Ray’s answer is no. Among public SaaS companies, growth has the strongest effect on enterprise-value-to-revenue multiples. Next comes a minimal level of profitability, which Ray tied to the Rule of 40, and then NRR. Rule of X research that Ray attributed to Bessemer and Meritech Capital found growth has 2.3 times the impact of free cash flow margin. A pricing model affects valuation through its effect on those three measures.
How do you decide when usage revenue from customers who are still ramping can be counted as ARR?
Ray ties the decision to the ramp period. If the ramp typically lasts three months and about 90% of customers are 80% to 100% ramped by then, converting their usage revenue to ARR at that point is defensible. Ray’s own preference is to report usage as GAAP revenue and keep it out of committed ARR until the customer signs a minimum commitment.
How do you show new ARR in an ARR bridge while new logos are still ramping?
Ray suggests a separate report for customers in their ramp period, alongside the standard ARR bridge. It shows where each customer is today and where you project it to be over the next one to four quarters, with customers grouped by cohort.
What holds companies back from testing usage-based pricing?
The most common reason is customer pushback, according to Ray. Customers worry they won't be able to budget for usage and that their costs will rise unless the vendor protects them from overruns. Ray's advice is to talk to customers before choosing a usage-based pricing model, then test it with a new customer segment or a new product. Citing Chris Mele of Software Pricing Partners, he warns against starting with existing subscription customers.
How does Drivetrain support usage-based revenue forecasting?
Drivetrain pulls metric inputs from separate systems, such as expenses from NetSuite and new customers from Salesforce, and lets you change a metric's time period or dimension without rebuilding it. Its cohort forecast multiplies each new cohort by a retention curve that restarts with every cohort and can be swapped for a lower curve in a conservative scenario.
Speaker spotlight

Ray Rike
Founder of Benchmarkit
Ray Rike is the founder & CEO of Benchmarkit and one of the most respected voices in SaaS metrics. With 20+ years in B2B SaaS, Ray has worked across operating and investment roles, and now leads Benchmarkit’s data-driven insights for SaaS leaders. His research has been featured by OpenView, TechCrunch, and SaaStr.

Kirk Kappelhoff
Senior Director of Strategic Finance, Drivetrain
Kirk Kappelhoff is a financial modeling expert with a BBA in Finance & Accounting and nearly a decade of experience at Deloitte, EY, and KPMG, where he built models for pre-IPO companies, M&A transactions, and strategic planning initiatives. At KPMG, he led the Business Modeling Services team, specializing in equity stories and financial forecasts that help high-growth companies communicate their value to investors. At Drivetrain, Kirk writes about strategic planning, granular reporting, and modern FP&A best practices for rapidly scaling finance teams.
- 00:00
Kirk Kappelhoff
Ray, how are you doing today, my friend?
- 00:04
Ray Rike
Doing great, Kirk. Thank you so much for inviting me to join you on this webinar.
- 00:08
Kirk Kappelhoff
No. It is an absolute pleasure to have you. We've been looking forward to speaking with you for quite some time now. We know you are a metrics master, and you've got all the industry benchmarks to prove it. And so we'll wait here for maybe one more minute, as people join — maybe meetings are going over, maybe they're grabbing their lunch, whatever the case may be. But high level, thanks for coming. Where are you today?
- 00:33
Ray Rike
I'm in New York City. I hop around quite a bit between New York City, San Francisco, Southern California, Los Angeles, and a weekend house in Pennsylvania. So I'm never in one place more than about three days, Kirk.
- 00:50
Kirk Kappelhoff
Sounds like a true consulting lifestyle, but you're not a consultant.
- 00:55
Ray Rike
Exactly.
- 00:56
Kirk Kappelhoff
Good stuff. Well, I too am in New York. Hello to everybody joining from around the state and around the world. We normally have a pretty global audience. Feel free to check in the chat where you are. If not, no problem. Today, we're talking about usage-based pricing models, and we're here with Ray. If you have ever joined our webinars before, you know that I'm Kirk, the director of strategic finance here at Drivetrain. I have the privilege of interviewing great minds like Ray. You both still might have seen me in some of our demos or online, talking about the different features that we're gonna be releasing. Ray, I'd love if you could give everybody an overview about who you are, who's Benchmarkit, and what's your guys' mission in the SaaS world, or metrics world, today?
- 01:46
Ray Rike
Yeah. Happy to do that, Kirk. And whenever I join a webinar, it's like, why am I willing to invest forty-five minutes, sixty minutes of my time to listen to someone? So what most people don't know about me is my first ten years out of undergrad, I worked at the world's largest provider of hosted applications on a mainframe accessible via a global private network, and our pricing model was usage-based. So I did this for the first ten years of my career. This was back in the nineteen-nineties. So I have a long history here. I grew up in a usage-based pricing model. And over the last twenty-five years, I've been involved in multiple VC-backed software subscription model companies, five exits, two strategic, two private equity, and one IPO. And then about three years ago, I took on this mission to build the b2b SaaS and cloud industry's largest and most contextualized benchmarking database. And over the last three and a half years, we've collected performance metrics data from eighteen thousand unique b2b SaaS companies across twenty-two different metrics categories, with over a million unique data points making up over five hundred different benchmarks. So that's what I do. So in other words, we can trust the data. Sounds like it's pretty well seasoned. Yeah, there's a lot of data there, but you can tell any story you want. I just give the objective — here's what the data says, and you interpret it for yourself.
- 03:19
Kirk Kappelhoff
Love to hear it. Well, let's take a look at what we'll be covering today in terms of an agenda. We're gonna go through four items at a high level. We're gonna take a look at the current state of usage-based pricing, see how calculating SaaS metrics with usage-based pricing can be done, and then how that turns into forecasting. Right? We'll have a bit of time at the end for Q&A. There's a variety of things in here, and I'm really excited to let Ray present a couple of these findings that he has. And then we'll have a little bit more discussion in two and three before four comes and you guys have the floor in terms of questions for Ray or myself. So let's jump into this really quickly. We're gonna start off with a poll. How many of you today are currently using usage-based pricing? You can just respond right there. Once you do, that'll disappear, and then we're ready to move on. While they're doing that, perhaps, Ray, you can take a look at this slide and give us a little overview of the state of usage-based pricing today and some of these leading companies we see on the screen.
- 04:17
Ray Rike
Yeah. And we're gonna talk about our latest research on what percentage of b2b SaaS and cloud companies are using usage-based pricing, but it's not that new of a concept. In fact, back two or three years ago, pre what I call the SaaS-acre — when enterprise valuations of SaaS companies went down dramatically since the second half of '22 — companies like Snowflake and Datadog were talking about a hundred and fifty, hundred and sixty percent NRR. And that was the case because of their usage-based pricing models. And I always like to segment this — and by the way, so does OpenView and Kyle Poyar, who is one of the best thought leaders on usage-based pricing — into infrastructure, middleware, applications, and then vertical apps and vertical marketplaces. So it's very common. But let's get into the data, and we're gonna show the benchmarking research about what percentage of b2b SaaS companies are actually using some level of usage-based pricing. So on the left-hand side with the green bars, this was research we conducted about twelve months ago — so it is twelve months old. Are you using any consumption or usage-based pricing attributes? Fifty-two percent of companies said yes, they were using some type of usage-based, not user-based. Twenty-one percent said no, and twelve percent said they were planning on introducing some level of usage-based pricing in the next twelve months. On the right-hand side, almost at the same time, was the OpenView benchmark, and you could see where in twenty twenty-two it was forty-six percent, so pretty close to our fifty-two percent. And then last year, there was a slight retreat. Now there's always selection bias in any type of benchmarking, so it wasn't exactly the same companies. But on a directional basis, you can see that about fifty to sixty percent of companies are using or plan on using some type of usage-based pricing. Well, what's interesting is — oh, sorry, go ahead. Sorry about that, Kirk?
- 06:25
Kirk Kappelhoff
I was just gonna say that in our poll, we've just come back, and it looks like forty-three percent said they've either implemented or plan to implement, thirty-four percent said, and then only twenty-three percent said no. So I'd say the data here matches up pretty decently with what we're showing on the screen as well.
- 06:41
Ray Rike
Yeah. And the populations of both of these were over five hundred companies. So it wasn't small — a lot of times you'll see VCs say, here's the benchmarks in my portfolio, but it's an n of forty or n of fifty. These are n's of four hundred, five hundred, six hundred companies. So, let's look at the components, Kirk. This is another question we ask before we get into what usage-based variables are being used. What's your primary pricing model? Right? So what you see here is that twenty-two percent had just a pure subscription, flat fee, not based upon any lever or value lever such as users or usage. Thirty percent was still primarily using a user-based, the old seat-based pricing. Eighteen percent had a minimum commitment subscription that included x number of usage variables. Right? We can think about HubSpot and their marketing platform for that. Right? They have number of contacts as their primary usage-based variable. And then you had a hybrid model. And, by the way, you could say, well, HubSpot's really hybrid. Right? Because in their entry level, you can have three users and a thousand contacts. Right? But then there's the volume of emails. So that would be kind of a hybrid model. But only one percent in our research had purely usage-only, no subscription, no minimum fees. And all the research I've reviewed over the last twelve to eighteen months, it ranges between one and two percent. So very few b2b SaaS companies are going a hundred percent usage-based, no subscription.
- 08:30
Kirk Kappelhoff
And so, Ray, I know you're not meant to have opinions on these sorts of things, since we're only looking at the numbers, but would you say strategically most companies will expect to see that one percent increase? Or would you say it's about where it should be in today's technological age?
- 08:46
Ray Rike
Well, I'm gonna give a lot of data today, Kirk. So, some other recent benchmarking research showed for companies under a million, about sixty percent were using usage-based as their primary model. Wow. And they were growing about twice as fast as pure subscription/user-based companies. Right? Wow. And a majority of them were using no minimum commitment. They wanted to reduce friction during this cautious capital environment and just say pay-as-you-use-it, pay-as-you-go. That's a great way in the early days, Kirk, to accelerate customer acquisition velocity as measured by logos. However, as you start getting into the predictability of your forecast, and investors wanna know what you're gonna be doing next quarter, over the next twelve months, you're gonna see the same thing happen as with companies like Slack, Twilio, etc. They're gonna quickly get their enterprise salespeople to go get a minimum commitment. And in return, give the customer a per-unit cost reduction, but I want that hundred-thousand, five-hundred-thousand-dollar commitment. So nothing's going to change. History repeats itself. Early days, less friction, less commitment. As you scale, more commitment, lower unit economic cost.
- 10:09
Kirk Kappelhoff
Makes sense.
- 10:11
Ray Rike
Now this was surprising. We talk about — and we do a lot of work with companies when they're introducing new pricing models — mostly around how it impacts metrics and how they report those metrics. But you wanna keep it simple. When you first introduce new pricing, keep it simple. And, by the way, it's better to introduce it to a new customer segment than to go back and try to retrofit existing customers. That's one big piece of practical advice. When you start testing and experimenting with usage-based pricing, do it on a new customer segment, not the existing one. One usage variable is most common — thirty-five percent. This might be, in some AI companies right now, the number of prompts or the number of transactions. Two usage variables — I'll use HubSpot because it's such a common example. Right? Two usage variables: number of contacts and number of users. Right? There's two things there. Now you could say, but there are add-ons like number of APIs or number of emails sent — so that could get into three or three-plus usage variables. But the most common and safest way to start your usage-based pricing model is a single-value pricing variable. And so on this, Ray, would you say there's one that you've seen that is most common in the SaaS world? Is it maybe API calls, number of seats, whatever the case may be? Is there one that sticks out above the rest in terms of ranking, order of operations? Kirk, it's almost like you looked at my slides. Why don't we move forward? Right? So it all depends on the category the software serves — middleware, infrastructure, application. Transactions — now loosely defined, but a lot of infrastructure companies are doing a lot of transaction movements. You could even say Twilio. Is it a message or is it a transaction? But transaction was number one, thirty-two percent. Messages — even like an email message or a text — was at eight percent. For your middleware/API solutions, it was API calls. Database size was pretty low. It was only five percent of participants in our research, about five hundred companies. Then database and record count. Now, we position record count based upon the category you're in — that might be contact count in the marketing automation space, document count in content management, etc. — but it's some type of record count. So transactional and message-oriented systems were the early adopters of usage-based pricing, Kirk. Makes sense. Now, one of the biggest decisions companies have to make — and by the way, we invite questions, if you're going through this, if you've got a different experience, if you're thinking about A versus B, please throw those questions in the chat or Q&A, we'd love to take them during the webinar — one of the considerations is, I'm just introducing usage-based pricing, do I cap it? And if I do cap it, what type of cap? Some people will put a hard cap. Okay, it's a thousand messages, and you can't do a thousand and one until you upgrade to the next level. That's a small percentage, only five percent have that. The second, especially for new customers and new usage-based pricing model introductions, is a soft cap. Okay, it's a thousand, but for the first quarter or the first year, we're gonna let you go over that and not charge you for overage. Now that's not very common, it's twenty-one percent. I'm gonna go all the way to the bottom option. That's where there's no cap, but we're gonna charge you for every overage transaction, message, or record, etc., during the term of the agreement. So let's say it's an annual agreement, there's no cap, you projected a thousand, we gave you pricing for a thousand, you do ten thousand — that nine thousand overage will be charged. And then there's a consideration on the right-hand side: how often do you charge for that overage? You'll see the most common is monthly. You had a thousand transactions projected, you did ten thousand this month, we're gonna charge you for those nine thousand this month. Nine percent do that true-up quarterly, and ten percent do it annually. So most companies, because they're looking at cash flow, are doing that overage charge on a monthly basis, Kirk.
- 15:10
Kirk Kappelhoff
So how does someone go about determining a cap? Is there a good rule of thumb for a company operating in any space? Is there a rule of thumb, like it's this much plus that, or a multiple of this? Is there a way, Ray, or is it truly up to the business to decide strategically what works best for them?
- 15:32
Ray Rike
In the pricing that you put on your pricing page? Right? Because if you're doing product-led growth and/or usage-based pricing, I highly recommend you put your pricing on the pricing page — that's becoming the de facto standard for usage-based pricing companies. It all depends on the category you're in, Kirk. Right? So, say I'm in marketing automation, and I go after SMB, mid-market, and enterprise. Right? I might have my basic or starter package for the SMB customer. They're typically gonna have somewhere between, let's say, if it's contacts, a minimum of a thousand, a maximum of ten thousand contacts, and one to two users. So they often do it based on the target customer segment. But there's no best practice — if you look at Twilio, they have multiple different products, and they basically say, okay, what's the minimum we want from the initial customer acquisition? Right? Okay, we want at least a thousand dollars a month. So how many variable transactions do you get for that? So it's also based on your own internal economics and what you want as that minimum revenue per month, per quarter, per year. Gotcha. Now, the first big lesson in usage-based pricing — I mentioned earlier Snowflake, Datadog, and Twilio with NRR of a hundred and forty, hundred and fifty percent, growth rates of seventy, eighty, ninety percent. So during the good times, when the economy is growing, or your target customers are growing — think about customers who sold to Uber ten years ago, and sold on a transaction basis. Right? Uber grows three hundred percent, we're growing three hundred percent, right, because every message is using us. So during the good times, usage-based pricing will grow quicker — and I'll show an example of that across fifteen hundred companies next. But at the same time, when markets start to have headwinds, like we've seen the last two years in the cloud industry, the market correction velocity and slope of that decreasing curve is much faster with usage-based, because it's easy to govern and throttle down usage, unlike a subscription model — I signed up for a hundred users, and there's still nine months left on that contract. Right? So in the middle, that green line — subscription growth — kind of maintains, while usage-based goes down. But as soon as the economy or the industry or the customer base starts to accelerate, usage-based pricing starts to grow much faster again. And if we go to the next slide, you actually see this — this is a report from Maxio Growth Institute, around fifteen hundred companies that use their software for subscription billing. The blue line is the usage-based or consumption-based pricing companies. Look what happened starting in Q1 of '22. They were at a thirty-five percent growth rate in Q1, Q2 down to thirty-one percent, Q3 down to twenty-five percent, Q4 of '22 down to twenty percent growth, down to nineteen percent in Q1 '23. So you see the decrease in growth rate was much faster. But look at the subscription, the green line — there was some decrease in Q3, but it went back up in Q4. It wasn't until Q1 of '23. Why? A lot of customers bought in Q4 of the prior year, so they didn't renew. Right? So that really impacted the growth rate, and subscription-based companies had lower growth rates a bit later. We're now in the last two quarters — I call this my canary in the coal mine — usage-based pricing companies are growing faster again. They were at twenty-two percent in Q3 of '23, but in Q4 they started to grow, and in Q1 of '24, they grew even faster. So usage-based pricing is great during positive economic times and more challenging during difficult times. I'll give an example: ZoomInfo. ZoomInfo's largest customer segment was early-stage b2b technology companies. They were subscription-based, but also priced on number of contacts used. Right? Their growth fell off a cliff for two reasons. Number one, that industry segment, which was forty percent of their revenue, stopped buying. Other b2b tech companies said, we're gonna stop buying all this stuff. And at the same time, they didn't have another industry segment that represented more than six to eight percent of their business. So you have to be really careful about external macroeconomic variables that impact your growth. Well, that's super insightful. I've also heard you say this is one of the best leading indicators for the economy — the fact that usage-based pricing can decrease so aggressively, almost anticipating what might happen to the rest of the world. And then when it increases, we can expect that good times are coming. Yeah. I'll go back to something as simple as b2c, because b2b software companies today — when I say software, I'm talking about cloud and SaaS — we're taking a lot of lessons from b2c companies. Think about usage-based pricing — I'm a little older than some of the people here, and I remember paying for long-distance calls on a per-minute basis. Right? That was usage-based pricing. So right now, if you did usage-based pricing and were selling middleware to mortgage companies, you'd be pretty happy, because mortgage refinancing went up about thirty-five percent just in the last two weeks. If you're doing that on a transaction or new-mortgage-initiation basis, you're really happy right now. But you weren't happy six months ago.
- 22:00
Kirk Kappelhoff
So let's take a change of pace here. Let's take a look at the impact on the metrics. We all know there are various SaaS metrics, everything from something as common as ARR to CAC, LTV, and so on. But when we're taking a look at usage-based, it might not be the traditional subscription-times-number-of-users calculation. Let's take a look at the impact on these. Right? I'd be super interested in your thoughts at a high level on ARR — new ARR versus expansion, these sorts of concepts from a UBP level.
- 22:27
Ray Rike
Yeah. And the reason this one is so important to me, Kirk, is one of the good fortunes I've had over the last couple of years is being co-founder of the SaaS Metrics Standards Board, along with other great thought leaders like David Spitz, who started KeyBanc Capital Markets Research, Todd Gardner, who launched the first credit-based revenue facility for recurring revenue at SaaS Capital, and Ben Murray, the SaaS CFO. We had to deal not only with standard definitions and formulas for calculating SaaS metrics in the traditional subscription world, but also start wrangling with how consumption-based pricing and usage was going to impact SaaS metrics. So one of the questions we went over: ARR, annual recurring revenue — is that variable revenue from usage-based pricing? Is that just GAAP revenue, recognized as it happens? Or is it truly annual recurring revenue? Some people in the digital ecosphere said, well, it's "reoccurring," not "recurring." It's like, what's the difference between reoccurring and recurring? But one of the standard best practices we recommend starts at your chart of accounts. You should have your subscription-based revenue, which is the firm subscription, and then we recommend a separate line item for variable revenue. Variable revenue on your income statement shows your usage-based pricing revenue — hey, it was three million this quarter, but next quarter it's three point eight, and the following quarter we're down to three point four. So, first, we truly recommend you have usage-based-pricing-driven revenue as a separate chart-of-accounts line item. And then you need to decide whether to include usage-based revenue in your MRR and thus ARR calculations. The latest research, from about four months ago, says seventy-two percent of companies using usage-based pricing will convert that monthly revenue into ARR. Seventy-two percent. Now, honestly, I think that's very dangerous. So our recommendation to all our clients is: show your ARR from firm subscription commitments only, and then show ARR plus variable ARR, and show both. That way your investors are aware — oh, you have twenty-two million of firm committed ARR and another twenty-eight million that's variable, that could go down next quarter and subsequent quarters. So that's what we recommend on ARR. And we'll go into some of these in more detail, Kirk. New ARR versus expansion. Historic wisdom said that if you're a recurring-revenue technology company, seventy percent of your growth should come from new-logo ARR, and thirty percent should come from existing-customer expansion. But it starts with, how do you define when new-logo ARR ends and existing-customer expansion ARR begins? In the old world, we did a one-year annual subscription as a first contract, and we knew that was new revenue. Some people also called it a booking, but most people put that into new ARR. And then on month thirteen, if there was an increase, that was expansion ARR — which is how you calculate net revenue retention, your gross revenue retention plus expansion. But you really have to define, in your usage-based environment, what is new and what is expansion. I'll show a chart on that next. Same with gross revenue retention — what's your starting point for ARR in that existing-customer cohort this period? Then how do you calculate it in twelve months? What's the ending point? Because if you include variable usage-based revenue in your ARR and the usage goes down, gross revenue retention could go from eighty-five percent down to seventy-two percent. Right? Well, no, no, no, no — I didn't really have churn, I just didn't have as much usage. So there's no right answer here, Kirk, but these are the things you need to think about, and how usage-based pricing models are going to impact your SaaS metrics. Same with net revenue retention — you start with how you're defining GRR, then you have to define what's ramp revenue versus expansion. By the way, let's go to the next slide, because I think it's really important, if it's okay, Kirk — to really think about this: what's my business model, how long does it take a new customer to ramp on my usage-based-priced product? Almost all companies are gonna have a ramp-up. Right? Maybe it's API-driven — in the first month we're gonna do one or two integrations, and then once we prove the product works, the transactions are flowing, we might go to integration three, four, and five. So every company should define what their ramp-up period is. For some it may be one month, for some three months, for some six or twelve months. Right? That's your ramp-up period — that's not expansion revenue, that's just your new customer revenue ramping up. And once you've defined, on average, what your ramp-up period is — let's say it's six months — then from month seven on, that's considered expansion ARR. Now, as you can see from my description here, Kirk, one model does not fit all, because it's based on your product, your customer base, etc. So what we recommend is including ramp-up growth as part of your new ARR. Once you define when your ramp period is over, then you determine your expansion ARR timeframe and associated revenue. And now you have to think about — well, now that I've defined ramp versus expansion, how does that impact my metrics calculations? Net revenue retention is an easy one, because that's looking at all your expansion from that customer cohort. So if you start expansion earlier, your NRR might look better. CAC — well, CAC, in things like CAC payback period and CAC ratio, you're typically looking at how much new ARR you brought in, divided into sales and marketing expense, CAC payback period on a gross-margin-adjusted basis. So now, if you have no commitment or a low commitment, and you know customers ramp over six months, how do you determine your customer acquisition cost ratio, since you don't know exactly what the committed ARR is? Right? So all of your CAC-efficiency metrics need to be defined for a usage-based pricing model. Now, I could say that should be your first twelve months — the value of the contract, to make it easy — but some companies may say no, it's the first three months, or the next six, or the next twelve. So you have to define it for yourself. Was that clear enough, Kirk? That was great. I can very clearly see how they're all interwoven, and how each company needs to define for itself what that ramp period is — here's the ramp, here's the expansion. It allows for some sort of measurability, and if you're not measuring it, what insights can you really pull from it? I think that — here's where I've seen — oh, go ahead, Kirk.
- 30:49
Kirk Kappelhoff
I think there's a question here from Chris. How do you think about usage-based variable pricing versus traditional SaaS fixed-license pricing in terms of corporate value? Does one receive a higher multiple than the other in an exit? I can see where you have the ability to grow revenue faster in good periods with UBP, but does an acquiring company place more value on guaranteed revenue streams?
- 31:14
Ray Rike
Well, the best way to evaluate that is to look at publicly traded SaaS companies. And if you go back and look at even the last twelve months, the highest correlation, or cause and effect, on enterprise-value-to-revenue multiples is still growth. Sure. So whatever model drives the highest growth rate is number one. Number two is some minimal level of profitability — rule of forty, right, growth rate plus free cash flow margin. And if you look at the rule of x research by Bessemer and Meritech Capital, growth has a two-point-three-times higher impact on enterprise-value-to-revenue multiples than profitability, free cash flow margin. Wow. If you look at this in a matrix manner, companies with twenty-seven percent-plus growth and a ten-to-twenty-percent free cash flow margin have the highest multiples. So I'd answer your question with: it's not the pricing model, it's the pricing model's effect on your growth rate, your profitability, and then third, NRR. NRR is still the number-three causal factor in enterprise-value-to-revenue multiples. Did I answer your question okay?
- 32:40
Kirk Kappelhoff
Yeah, I think — you'll have to ask Chris — but I think Chris would be pleased with that. Let's jump on here. Anything else on this slide, Ray, before we jump to the next one?
- 32:50
Ray Rike
Yeah. So if you're doing usage-based pricing and you have kind of a hyper land-and-expand model — hey, I want some type of minimal commitment, skin in the game, let's say it's ten thousand, but I know for a customer in this industry or segment, they're gonna be doing a hundred thousand in twelve months — an option for your metrics is you can do things like CAC payback period on the forecasted revenue or ARR for those accounts in that category. Hey, they're in the automotive industry, I know their company profile, they're gonna do a hundred thousand in the next twelve months. So you can do your efficiency metrics on the forecasted, call it annual projected revenue — we'll talk about that in a minute. And then after twelve months, redo those calculations on actual GAAP revenue. That really holds you, as an executive leadership team, accountable for your forecasting in a usage-based pricing model. You said your CAC payback period was projected to be twenty-three months, and now when you do a twelve-month look-back, it was twenty-one months (better) or twenty-eight months (worse). So I strongly recommend you do both a booking/forecast model and an actual GAAP revenue model. Now, the other thing is on your CAC efficiency metrics — you should really look at it by customer segment, because that way you can say, my cost to acquire an enterprise customer was this, and the projected revenue in this usage-based pricing model is a hundred thousand, versus my cost to acquire an SMB customer, but the projected usage-based revenue is only that much. So it's really misleading to do it across the entire customer base — you should do it by segment.
- 34:41
Kirk Kappelhoff
What about NRR and ramp-up revenue? Give us the overview. Right?
- 34:45
Ray Rike
Okay, why don't you go ahead and show the bullet points here. So we just showed you want to isolate the ramp-up revenue, because that ramp-up revenue, based on how you do it, may increase five, ten, twenty x from the beginning of the ramp-up period to the end. So, number one, define and isolate your ramp-up revenue, and make sure it's consistently defined by number of months. One of the things you can do is use something called the net expansion rate to analyze the ramp-up revenue. You take a cohort of customers, maybe by industry, region of the world, customer segment, company size, etc., and you compare the ARR or GAAP revenue of those customers for this most recent period, say the current fiscal year, versus the same customers for the previous twelve months — so this most recent twelve months versus the preceding thirteen-to-twenty-four months. Now you know your net expansion rate. It's a nice complement to GRR, gross revenue retention, but it does not factor in churn — whereas GRR does. What we want to see here is, for the customers who stay with us, what is that average net expansion rate? So hopefully that helped, Kirk.
- 36:16
Kirk Kappelhoff
Definitely, no doubt about it. It's something like a two-year look-back. This has been talked about a lot — we've got Snowflake listed here. I'd love if you could give the overview of that story; I think those of us who don't know it will find it super interesting.
- 36:32
Ray Rike
So, I still remember this — about three years ago, you'd read Snowflake's 10-Qs or 10-Ks, and you saw a hundred and fifty-eight, then a hundred and sixty-four, then almost a hundred and sixty-eight percent net revenue retention. And you're like, oh my god, this really is a unicorn snowflake. Right? Because it was so incredible. But one of the things they did — I think it was about ten to eleven quarters ago — they were on an earnings call and said, we have a net revenue retention of a hundred and sixty percent, which is incredible, meaning our existing customers are growing sixty percent year over year. Then, about twenty minutes later, someone asked, what's your guidance for projected growth rate next quarter? And they said, fifty-five percent. And an analyst said, whoa, whoa, whoa, wait — I don't understand. How can your existing customers be growing sixty percent, but as a company you're only growing fifty-five percent? That doesn't make sense — are you paying new customers to become new customers? And what we found was that the way they were calculating NRR was they took the customers at a current point in time and compared that to the revenue that set of customers was generating twelve months ago, excluding any churned customers — but you cannot calculate NRR without including downsells and churn. So one of the things they came out with was their two-year look-back methodology. The two-year look-back takes the revenue over the last twelve months for a cohort of customers and compares it to the revenue from the previous twelve-month period — so, months thirteen to twenty-four earlier — for that same cohort. So the two-year look-back still kind of eliminates the impact of churn, but they don't call it NRR — they just call it NRR using a two-year look-back. Do we see other companies adopting a similar approach? Pardon me? Do we see other companies adopting a similar approach, now that the sort of dilemma between growth and NRR was made public with Snowflake? I've seen several companies use a two-year look-back, because it's almost another proxy for net expansion rate — I just want to see, for the customers who stick with me, how fast are they growing? So the answer is yes, but as far as public companies actually using this on a standard basis, it's non-GAAP, and the answer is no, it's a minority, not a majority, Kirk.
- 39:20
Kirk Kappelhoff
Sure.
- 39:24
Ray Rike
Now, I mentioned this earlier — Kyle Poyar, a good professional friend, and OpenView, from twenty-nineteen to twenty twenty-three (early twenty-three), were the best organization for research on both usage-based pricing and product-led growth. This is their framework, not mine, but I like to learn from the best, and Kyle's one of the best in this. It's just a framework for deciding whether usage-based pricing is meant for you or not. Number one: are your competitors doing it? Right? Yes or no. And if they are, you need to at least seriously consider it, because that might be a competitive advantage. Do their customers like it? Now, often you'll find customers love it at the beginning. In my experience from the beginning of my career, we had customers like Dell, Sun, Ford, and Toyota, and they loved this variable usage-based pricing because they didn't have to commit a lot upfront — they didn't have to deal with an aggressive salesperson trying to get them to commit to a hundred-thousand-dollar contract. Right? But then, after two or three years, if their cost kept going up and they couldn't budget for it accurately, the CFO comes and says, you told me you'd spend a hundred thousand dollars, we've got three hundred and twenty-three thousand dollars of invoices from this vendor — what's going on? I can't run a budget and a plan like that. So find out if your customers like it. If they do, you need to understand what your costs are tied to. If your costs are tied to usage — like AI companies, native AI companies today — they have a lot of costs because they're paying ChatGPT, or Anthropic, or other providers, etc. So you might need to tie your pricing variable model to your cost infrastructure, because AI is very CPU- and resource-intensive. On the other side, if customers don't like it, you have to figure out whether you can reduce friction by offering usage-based pricing with low-to-no commitment upfront, or unlimited usage. This is a really good — I know we're gonna be sharing these slides, Kirk, this is just a good framework — Software Pricing Partners has done pricing engagements for about five hundred different enterprise software companies, and Chris Mele gives this advice, from doing it five hundred times: do not introduce usage-based pricing to your subscription customer base as step one. Do it with a new customer segment. Maybe do it with a new product, if you're introducing a new product that lends itself to usage-based pricing. Do it that way, but don't start with a beautiful Excel model saying, well, if I converted all my existing customers from subscription to usage, we'd see twelve percent inherent growth, and then factor in some attrition of four or five percent — that's a nice Excel model, but you're gonna spend a lot of your customer success and sales organization's time on dissatisfied customers. So start with a new product or a new customer segment.
- 42:55
Kirk Kappelhoff
What a great visual, as a decision framework for UBP. Let's quickly take a look at this — a great four-step framework for setting up these metrics. It's pretty logical: step one, you want to accumulate the data needed for your metrics in one place. This comes from a variety of tools — ERP, billing system, invoicing. If you're doing something involving more usage, product analytics tools are super important. But once you've got them together, stitching them together somehow is step two — essentially ensuring you've got an apples-to-apples comparison between your data sources, where you're able to see how one item from one dataset affects one item from another dataset. Using the metrics standards boards Ray mentioned before, you'll be able to actually calculate those SaaS metrics. And if you ever want resources on that, please visit Ray's materials — he's got great guidance on SaaS metrics and the SaaS Metrics Board's work. And then, number four, once you've done one through three fairly often, is automating this process. Once you've figured out how to create the SaaS metrics specific to your company, defined your ramp, defined your cohorting analysis — how can we automate this to make it a little easier? We can always arrive at the answer, but it's nice to arrive at it a little quicker. So here's an overview from one of the modules within Drivetrain. What you're seeing here is a couple of SaaS metrics listed on the left. In the next column, the forecast formula column, is where you write the formulas to define it. But amongst all of this, you're seeing some nuance — a lot of the time, we don't want all of sales and marketing included in our metric, we just want the sales department, which is what you're seeing in the formula bar at the bottom. Maybe it's not from this quarter, maybe it's from last quarter. Regardless, we usually want some nuance to it. So let me jump over to something like this here in Drivetrain. I'm gonna go over to our metrics section, where we can actually build those metrics. And if I take a look at something like CAC, which is one thing we brought up a couple of times today, Ray, I may want to do something like this — I'll name it, I'll categorize it under my SaaS metrics. But when it comes to actually developing this, I have two options. One, maybe it's all in one data source, in which case I could go into that source and pull whatever I need. But normally it's from multiple systems — the numerator might come from one system, the denominator from another. So here I could bring up the sales and marketing expense, which in this case is coming from NetSuite, and divide it by my new customers, which in this case is coming from Salesforce. If I apply this, both of those will be aligned across their timeframe. Let's take a look at twenty twenty-three, which is when this data is coming in, and I could see this flowing into Drivetrain quite seamlessly. Now, the thing about this — and you've probably experienced this a lot, Ray — is a lot of the time I get feedback where people say, well, the sales and marketing expense from my current period isn't what's feeding my new customers in the current period. It's not the sales and marketing expense from January that's feeding the new customers in January — it's actually from a previous time period. In that case, you should have the ability to set your time period, whether it's previous month, previous quarter. And maybe there's some nuance to your customers too — perhaps it's not all new customers, perhaps we're looking at a particular vertical or region, some dimensionality we want to consider. And when I apply that through, I should be able to get to those answers pretty seamlessly as well. So here's a little bit about the metrics setup. While I jump back to the slides, I'm interested — have you seen some sort of nuance or variability when it comes to metrics like CAC and other SaaS metrics?
- 46:51
Ray Rike
In the interest of time — I know we've only got about thirteen minutes left, but I'll answer it — based on your sales cycle length, your ACV, you may say, I want to take my marketing expense from the previous quarter and my sales expense from the current quarter, and that's how I calculate my CAC ratio. So there's all kinds of nuance. Having the ability to define those and be consistent about them — and the biggest issue is where you get the source data from — is huge value. But, Kirk, if you don't mind, I want to get to the last thing, because this is where I have a lot of experience and a lot of pain. With usage-based pricing, a lot of times we focus on modeling it, reducing friction, how it impacts growth rate. But as you scale, what your investors are gonna ask — especially public investors — is how do you forecast it accurately? Think about how you forecast new business today: the average company has a plus-or-minus error rate of eleven to fifteen percent on new business forecasting. So how are you gonna be better at forecasting customers' actual usage and the associated revenue? Number one, you have to develop the muscle, the capability and competency, to project usage and associated revenue. I learned this a long time ago — the concept of annual projected revenue. We held both the sales organization/account management and finance responsible for this: for every customer, and every cohort of customers, they had to forecast usage for the upcoming three months, one, two, three, four quarters out. You have to do that bottoms-up and top-down. You have to assign responsibility — who owns that forecasting? Is it the account manager? Is it an FP&A person assigned to a region or country? You have to think about how you're gonna forecast the variability of usage-based revenue. Then you also have to think about quotas — if I know this industry is growing thirty percent next year (say it's mortgage refinancing), how do I set my plan for that segment or subsegment? So you have to consider granular variability like vertical industry trends, the customer's business climate. If I'm selling to OpenAI right now with a variable-based product, I'm pretty sure it's gonna grow a lot faster than if I'm selling to Salesforce. Right? Seasonality — if I'm selling to retailers, and I'm doing value-based pricing, like percent of GMV (which is technically value-based pricing, not usage-based pricing, but we haven't talked about that yet), you know that's gonna go up in Q4 compared to Q2 and Q3 if you're selling to retailers. And you also have to do forecasting based on the stage of adoption ramp. So if you're considering usage-based pricing, you have to start thinking about the infrastructure and ability to forecast down the road. Let's move on.
- 49:55
Kirk Kappelhoff
That's great. That's a great overview. By far, the most common way of doing usage-based forecasting is via cohort modeling, something like this, and I'd be interested in your thoughts.
- 50:06
Ray Rike
Whenever we've done cohort modeling, whether in Excel or in Drivetrain, there are always two elements I see as necessary. One is this customer cohort number you see just under the dates at the top — ten, thirteen, sixty, and so forth. That's the assumption for your new cohorts coming in — usually a best guess based on historicals. You'll see where January on the x-axis meets January on the y-axis, that ten repeats, the thirteen repeats, the sixty repeats — those are the new cohort numbers. The behavior of those customers after that first month is defined by the retention curve — it starts at a hundred, goes to ninety, eighty, fifty, and so on. So that ten from January becomes a nine — obviously, ten times ninety percent. But then the retention curve resets for February — a hundred percent of thirteen is thirteen, but if we're rounding in March, that ninety percent is twelve. And so on. So this waterfall cohort analysis is the best way I've seen to forecast it.
- 51:13
Kirk Kappelhoff
High level, Ray, any thoughts on that, or other ways you've seen the cohort or usage-based pricing being forecast?
- 51:23
Ray Rike
I think the only thing I'd comment on — and it can get complex and hard to do in Excel — is I'm gonna use "segment" differently. Often cohort refers to a time basis, versus segment, which is customer type — like enterprise in the US versus mid-market in Europe. You have to have the infrastructure and do the forecasting at least one, if not two, levels of granularity lower, by customer segment and by product type. That's the thing I'd say, and it gets really complicated, Kirk.
- 51:55
Kirk Kappelhoff
It really does. One way we've tried to simplify it in Drivetrain — typically, when you're building these cohort models in Excel, there are multiple IF statements, multiple INDEX-MATCHes, to create this waterfall effect. If I jump back to a similar screenshot, but this time live within Drivetrain, those two items I mentioned — the new cohorts and the retention curve — are listed right here. Each of these new cohorts is the starting amount for each line item, and the behavior, the retention curve of those new cohorts, is defined right here. Each item grows based on that retention curve as it pushes through. If I change any one of these — just hard-code them — I'll see that filter through to the appropriate cohort month, and then a retention curve of, in this case, a hundred and one point five percent on top of the original hundred percent is what I'm seeing here. The way we've simplified that is to make the expression like this — these two items being multiplied together instead of the complex IF/INDEX-MATCH formulas, which work once you get the hang of them, but are complex to update. Now it's a multiplication of two items: the new cohorts at time equals cohort, meaning January always matches up with January, February with February, and so on. And then we take the retention curve at t-minus-cohort, essentially restarting that retention curve with each new cohort. Scenario-based planning can modify that — if you think a higher retention curve might occur, versus a lower one you want to be conservative against, you're welcome to do that too. But it's a bit more simplified than the traditional methods we've used before. Let me jump back to this now, Ray, really quickly — we've got one more poll here. If we could check the poll on the screen, that'd be super helpful. I'd be interested, Ray, in any other high-level comments we've missed from the forecasting piece, while people answer this poll.
- 53:55
Ray Rike
No, there's a few questions here, so I wanna get to those as soon as we can, Kirk, because we only have about seven minutes left.
- 54:00
Kirk Kappelhoff
Let's do it. So high level here — I'll just call out, while we're looking at this poll, this directly relates to it: here's a couple of our customers. We are the leader right now on G2 as the FP&A finance tool, so if you'd like a demo, I'd be happy to give anybody here one. And here's a variety of other resources regarding SaaS metrics, if you want to take a look. Like Ray mentioned, we'll be sending these out, so you'll have access to all of that. Let's jump into the Q&A here. Anything jumping out — oh, I see a variety, we've got several different Q&A items right here. Ray, did you — yeah, go ahead. Jump out at me — the first one was, what would you consider committed usage in the calculations? Customer buys a million transactions upfront.
- 54:50
Ray Rike
Hey, that's committed revenue, that's a subscription, that's ARR. I would definitely factor that into bookings and ARR, because of the minimum commitment. And someone says, we track the overage charge in a separate GL — remember, I said, okay, you should have subscription, which is committed revenue, and then variable usage revenue — exactly the way you should do it.
- 55:14
Kirk Kappelhoff
I see one here, Ray, that intrigues me: any suggestions on converting UBP into the standard renewal process? The goal is turning non-recurring UBP revenue into ARR at renewal.
- 55:28
Ray Rike
It's different for every company, but the answer is yes — you should say, okay, what are my thresholds? Say it's ten thousand, twenty-five thousand, fifty thousand — you should proactively go to those customers and offer a lower per-unit cost for a minimum commitment. Your investors over time are gonna love it, and it eliminates surprises where people come to you and say, hey, Ray, I budgeted fifty thousand, it was sixty thousand, now it's a hundred and twenty thousand, and my CFO says we have to consider options. Because what we found, when I did this a long time ago, was the largest customers were the most likely to attrite. Why? Because they were spending more than they thought and didn't feel comfortable talking to us about it. So have your account management/AE team know what those thresholds are and proactively recommend a lower per-unit cost for commitment.
- 56:24
Kirk Kappelhoff
Beautiful. I got one from Jim here, a simple one: how do you convert usage-based pricing into ARR, three-month average? How do you do it?
- 56:38
Ray Rike
Well, again, this is where you define what your ramp period is — if it's typically three months, and you know that ninety percent of customers will be eighty-to-a-hundred-percent ramped, then you could say, okay, now I'm comfortable converting that to ARR. But, for me, I'd rather just have that as verbal usage on a GAAP revenue basis, and not convert it to ARR until it's a firm commitment. Okay, so it really comes down to that ramp.
- 57:07
Kirk Kappelhoff
Here's another one, from Aaron: if you have a ramp-up period, what are the ways to get comfortable with the delayed ability to report new consumption from new accounts? For example, if the ramp-up period is six months, it's tough to show a traditional ARR bridge with new ARR, etc., since those logos aren't yet mature.
- 57:29
Ray Rike
One of the things I've seen is you have a different ARR report for customers in ramp, and you can show and project that out over the next one, two, three, four quarters, where they are and where you project them to be, customer by customer, and then categorize or cohort that. But you're gonna need a new report — your forecasted ARR for usage-based pricing customers.
- 58:01
Kirk Kappelhoff
Lovely. Another one, from Ryan — we've got two minutes left, so maybe two more questions. Any suggestions on converting UBP into the standard renewal process, goal of turning non-recurring UBP revenue into ARR at renewal?
- 58:15
Ray Rike
Yeah, one of the things you can do is have comp plans — for your account management team, you expect them to convert x percent of your usage-based pricing customers to a minimum commitment of at least eighty percent of what they billed over the last year. I won't give you the number because it can differ, but there should be a goal, compensated for your renewal team, on what that transition to fixed contracts looks like.
- 58:45
Kirk Kappelhoff
Lovely. Now let's end on this one — a very unique question from Chris: what are the top two reasons people delay testing a UBP approach, and are there valid reasons?
- 59:00
Ray Rike
Number one: I've gone out and surveyed and talked to a number of customers, and the overall feedback has been very negative — I couldn't budget this way, I'm afraid my cost will go up, unless you can guarantee me the flexibility that if I use less, my upside isn't as expensive and I won't go over budget. So talk to your customers, number one. And number two: experiment, experiment, experiment. Right? When you do introduce usage-based pricing, don't do a big bang, and don't do it with your current customers — try it with a new customer cohort. And the last thing on forecasting, since I saw a question here — you're gonna have to be really good at looking at your trends over the last one to four, six, eight quarters to make the forecast by customer segment, industry, region of the world, etc.
- 59:56
Kirk Kappelhoff
Beautiful. Well, Ray, absolute pleasure — this has been intense, lots of good questions, incredible material. Thanks so much for joining us, and we look forward to having you back. Everyone, if you want to get in touch with us, you can do so using the emails or websites you see below. We'll send out this material and have it available for you, and be sure to follow up. If nothing else, have a great day. Thanks again, Ray.
- 1:00:20
Ray Rike
Thanks, Kirk. It was a blast. Bye bye now.






