Seat-to-Usage Migration: NRR Dipped 9% Before It Hit 128%

Derek Simmons: Welcome to ARR Autopsy. I'm Derek. Elena Reyes: And I'm Elena. And Derek, I'm still not over the number you sent me last night. Derek Simmons: NRR cratered to 84% the month this company flipped to usage-based pricing. Elena Reyes: 84. That's the kind of number that gets a CFO fired. Derek Simmons: And then six months later? Fully rebounded. Higher than where they started. Elena Reyes: Wait, higher than before the migration? Derek Simmons: Yeah, yeah, that's the swing we're autopsying today. Elena Reyes: Okay, so my job, as always, I'm auditing the numbers, poking holes, asking for the receipts. Derek Simmons: And I'm reconstructing the story. Twelve-person team, seat count that just... stalled. Elena Reyes: Flat for straight two quarters. Painful. Derek Simmons: We'll walk through the actual build sequence. Dashboards, shadow billing. A grandfathering window that mattered more than anyone expected. Elena Reyes: And there's a guardrail they built after watching the industry favorite "Bill Shock Horror Story" play out elsewhere. Derek Simmons: You mean the one every founder in SaaS group chats about? Elena Reyes: That one. It quietly saved two enterprise accounts during the transition. Plus, the month expansion revenue actually overtook new logo ARR, which helped me translate this for the client conversation. That's not a small shift. Derek Simmons: Not small at all. Though it came with a support ticket surge nobody planned for. Elena Reyes: Of course it did. Nothing's free. Derek Simmons: Nothing ever is. All right, Elena, where do we start? Elena Reyes: Same place we always do. The number before the fix. Derek Simmons: Let's get into the wreckage. So six weeks after this founder flipped the switch on usage-based pricing, their NRR cratered to 84%. Elena Reyes: Wait, wait, wait, 84? From where? Derek Simmons: They'd been sitting comfortably north of 110% before the migration, then cliff. So the fix broke the thing it was supposed to fix? For about six months, yeah. And then it came back. Not just back, it landed higher than where they started. Okay, but I want the number before I get excited. Higher. Elena Reyes: How? Derek Simmons: We'll get there. That's the whole arc of this episode. The dip is real, the recovery is real, and there's a very specific, very boring sequence of decisions in between. Elena Reyes: Right, and this is exactly the environment that's making that dip so common right now. Derek Simmons: Oh, you're going to love this part. Elena Reyes: Hit me. Derek Simmons: Gartner's forecast shows at least 40% of enterprise SaaS spend is projected to shift to usage, agent, or outcome-based pricing by 2030. Speaker 3: Hmm? Derek Simmons: With seat-based revenue share sliding from 21% down to 15%. That's not a niche experiment anymore. That's a third of the enterprise SaaS market rewriting its own contracts. Every founder who's still charging per seat is watching that number and sweating a little. Sweating's a generous. I'd call it mild panic. Speaker 3: Fair. Derek Simmons: So here's how I want to split this. You reconstruct the story, what they tried, what... what they build, what broke. And you sit there with a calculator and tell me I'm lying. Basically, yes, I'm auditing every number that comes out of your mouth today. Which is fair, because the founder version of the story is we just committed to the model and it worked out. Elena Reyes: Hmm. Derek Simmons: That's not a strategy, that's a horoscope. Exactly why we're doing it the hard way. Elena Reyes: So before that 84% number even existed, before the migration, before the dip, what did the business... this actually look like what was the ARR, the team, the thing that was already broken? Derek Simmons: Oh, that's a good rewind, because it wasn't some scrappy startup flailing around. This was a company that had already hit real revenue and then just stalled. Stalled how? Flat renewals, flat seats. Wait for it. Derek, patience. That's the next step. Ugh. Elena Reyes: Twice six months before any of that net dollar retention chaos, this company sitting at 1.8 million ARR, seat-based only, 12 people on the team. Derek Simmons: Twelve. Okay, and where's growth actually sitting at that point? Elena Reyes: Flat. Dead flat for two straight quarters. New logos were fine, but expansion revenue basically stopped moving. Derek Simmons: Help me understand flat, though. Like, what does that look like on the actual dashboard? Elena Reyes: Seat counts barely budging quarter over quarter. Same accounts. Same headcount, no growth in licenses purchased. Derek Simmons: So the sales team's pulling every lever they've got. Elena Reyes: And getting nothing. They tried sales-led upsell pushes first, just hammering existing accounts to buy more seats. Derek Simmons: Classic move. Didn't work. Elena Reyes: Barely moved the needle. So then they built feature-gated tiers, locked the good stuff behind a higher-seat tier. Derek Simmons: I've seen this movie before. That usually just trains customers. customers to negotiate harder. Elena Reyes: Exactly what happened. And when tiers didn't convert, they discounted to close deals. Derek Simmons: Oh no, discount creep. Elena Reyes: Discount creep. Rep started shaving 15-20% off list just to hit quota. Derek Simmons: So what does this mean for the person listening right now, your seat model's dying and your bleeding margin trying to keep it alive? Elena Reyes: That's the picture. Seats had hit a ceiling because the product's value wasn't scaling with headcount anymore. Derek Simmons: usage was, which is the whole problem with per seat, right? You cap out on humans way before you cap out on what the product can actually do. Elena Reyes: Right. And here's where the industry data gets interesting for them specifically. DigitalApplied published a piece on this in May, and their read was that hybrid models of fixed base plus variable usage are the dominant way companies actually make this transition, not pure usage-based. Not a clean rip the Band-Aid off jump to consumption pricing. Amazing. No, keep the predictable floor; add the variable layer on top. That's apparently the shape most of the market's converging on mid migration. Derek Simmons: So this wasn't some wild bet they were following a pattern that's already showing up elsewhere? Elena Reyes: That's the argument anyway. Whether it actually worked for them is a separate question. Derek Simmons: Which is exactly where I want to go next, because we decided to add usage is the story version. I want the build sequence: what got shipped first. Just what didn't touch billing yet. Speaker 4: Six months start to finish and the first thing they built wasn't pricing at all. Derek Simmons: Wait, what was it? With the seat ceiling set, here's the build order nobody skips: the dashboard came before a single pricing email went out. Elena Reyes: Wait, before they even told customers what the new model would be? Derek Simmons: Before. Months one and two, engineering ships a usage dashboard. No new invoice, no new plan, just visibility. Elena Reyes: So on a Tuesday morning in month one, what's actually happening? Is someone in a stand-up saying ship the meter, not the price? Derek Simmons: It's basically, yeah, you instrument every account's usage first. So when the pricing conversation starts, you're not guessing. Elena Reyes: Okay, but two months of dashboard work with zero revenue conversation? That's a long runway for a company already stuck at that ARR ceiling. Derek Simmons: Which is exactly why month three is where it gets real. That's when shadow billing starts. Elena Reyes: Explain that like I'm the CFO who just heard the word shadow and got- And got nervous. Derek Simmons: Digital Applied lays out the shadow billing play like this: meter usage on the new model for sixty to ninety days before you touch a single invoice. So customers are seeing a fake bill, a preview? A projected bill running parallel to their real one. Nobody pays it; it just surfaces who's about to freak out. And that's the point: you find the objections before they cost you a renewal. Exactly. Low usage accounts see they'd pay more, high usage accounts see they'd pay less. You know the fight before it happens. OK, so what's the grandfathering window? Give me the actual months. DigitalApplied's playbook says grandfather the existing base for twelve to eighteen months, and this team landed toward the middle of that middle-legacy pricing honored while the shadow numbers ran. That's a real runway, not a fake one. And here's the part I actually like. Every renewal call was anchored to that specific account's usage data, not some theoretical average customer. So the rep isn't saying most customers pay X. They're saying, here's your last 90 days and here's what you'd pay. Right, you can't argue with your own numbers the way you can argue with a benchmark. I'll give you that. That's harder to churn on if the pitch is literally your own dashboard. But six months of dashboard first, Shadow Bill second. Second discipline still didn't stop one thing from almost blowing up the whole migration: Oh no, what broke? One account, one uncapped month. We'll get to the invoice that scared everybody straight. Shifting gears, the near-disaster part: one account, uncapped month, and the invoice basically exploded. Elena Reyes: Okay, let's stress test that assumption before you tell the story. What would that invoice actually have hit, dollar-wise, if nobody caught it? Derek Simmons: So the industry version of this? DigitalApplied wrote about it back in May: a single cursor developer racked up a $7,200 invoice in one day. One user. Elena Reyes: In a day? Derek Simmons: One day, annually-billed plan, 500 requests, nobody flagged it until the bill landed. Elena Reyes: And that post blew up online, right? Derek Simmons: Reached the digital Twitter masses within a week, according to that same analysis, and here's the part that should scare every founder listening, the root cause wasn't the customer's behavior, it was the architecture. Exactly. Digitalapplied called it a design failure, not a customer education failure. Flat out, that's the penalty flag, right? Except nobody threw it until the ball's already in the end zone. Sports guy strikes again. But yeah, That's the scenario our founders were staring at mid-migration. So what'd they actually build? A spend cap, configurable per user, per team, not just slapped on the whole account. Why does that granularity matter so much? Because if it's account-wide only, one rogue user in a f***ing The 50-seat enterprise account can still torch the whole invoice before finance even notices. Right, so walk me through the actual save. Two enterprise accounts. What would have happened without the cap? One account had a team lead running batch jobs nobody else knew about. Usage spiked mid-cycle, the cap throttled it automatically, alert fired, customer success called before the invoice even generated. So the customer never saw this scary number at all. At all. Never saw it. Same on account two: different trigger, same outcome. Cap kicks in, CS gets a heads up, conversation happens before the surprise, not after. I mean, without that cap, are we talking real churn risk or just an awkward call? Real churn risk. Digitalapplied framing is blunt. Spend caps and alert thresholds aren't optional UX, they're engineering requirements. Skip them and you're one bad billing cycle from losing the account. account. Elena Reyes: Right. Configurable, multi-level, built before the invoice ever prints. That's the Guardrail. Derek Simmons: That's the guardrail, and it held through the exact stretch where usage revenue started doing something new to the top line. Elena Reyes: Which is where we need to go next because that crossover point didn't come free. Derek Simmons: No, it did not. Shifting to the crossover, the month expansion revenue finally passed new logo ARR. Elena Reyes: Which month exactly? Because that's the number I care about. Derek Simmons: Month seven post-migration, NRR climbs to one hundred eighteen percent up from the dip we flagged earlier. Elena Reyes: 118. Okay, that's not a rebound. That's a full reversal. Derek Simmons: And it tracks with what the industry data shows broadly. GetMonetizely's piece on NRR strategy cites OpenView's benchmark. Remark. Companies with usage-based pricing components report 28% higher NRR than pure subscription models. Elena Reyes: I'll give you the direction, but 28% higher than what baseline? That's a wide range depending on segment. Derek Simmons: Fair. It's a benchmark, not this company's exact delta. But it's the same mechanism. Usage lets expansion happen without a sales call. Okay, operator hat on. What broke when this thing actually scaled? Invoices. Support tickets on invoices went vertical. Customers didn't understand line items that moved month to month. Of course they didn't. Nobody reads a metered bill for fun. Finance felt it too. Forecasting monthly revenue got genuinely hard when usage swings 20, 30% between customers. Right, because you can't build a clean model off a number that moves under your feet every cycle. So what does this mean for the team living through it in real time? They had to build fast what they actually do. Two things: First, a tier two support role just for billing questions because tier one was drowning. Elena Reyes: And the finance- Derek Simmons: Inside? Elena Reyes: They build a rolling forecast model off trailing 90 day usage instead of point-in-time snapshots smooths the noise. Derek Simmons: That's the fix I'd have pushed for too. You can't forecast off one bad week. Elena Reyes: Exactly. And a proactive invoice explainer email sent before the bill, not after the confused ticket comes in. Derek Simmons: Getting ahead of the confusion instead of cleaning it up. Smart. Elena Reyes: So here's the real question, the one I'd want answered if I were sitting across from this team. Go ahead. What's the one thing they'd change at month one, knowing everything we've walked through? Derek Simmons: My guess is hire the billing support role before launch, not four months after the tickets pile up. Elena Reyes: That's my read, too. Staff the mess before it exists, not once it's already on fire. Derek Simmons: Because the guardrail, the dashboard, the shadow billing, all of that protected revenue. But nobody protected the support queue. And that's the gap. Build the person into the plan at month one, not month seven. One hire, three months earlier. That's the whole difference between scrambling and being ready. Elena Reyes: So if you're taking one thing from this episode, it's that the dip isn't the failure, it's the plan working. Right, that crossover month, expansion revenue passing new logo ARR, that's the whole payoff for surviving the Eighty-four scare. And staffing support before the billing questions hit, that's the fix they'd move up to month one. Knock on wood, every founder listening writes that down before they migrate. Please save yourself the ticket surge. If this saved you from a bad pricing bet, send it to one founder who needs it. Derek Simmons: Subscribe on YouTube or wherever you listen and leave a review. It helps us get more founders to open up their real numbers. Elena Reyes: Thanks for spending this one with us. Derek Simmons: We'll see you next time with the next set of books to open up. Elena Reyes: Autopsy's never done. Derek Simmons: Never.