Latest / SaaS Business with Fexingo: Software-as-a-Service Companies, ARR, and Recurring Revenue / How SaaS Companies Survive The Expansion Trap
Transcript
- Lucas: The thing that keeps me up at night regarding SaaS economics right now isn't acquisition cost or even initial conversion. It's what happens after the first year. We are seeing a structural shift in how enterprise software companies measure success, moving away from pure seat counts toward outcome-based billing. Look at Adobe. They stopped counting licenses years ago and started measuring active users and specific feature adoption. That change didn't just stabilize their revenue; it fundamentally altered the relationship with their customers. Luna: Right, because when you charge per seat, the customer’s instinct is to hoard seats they don’t use. Shifting to value metrics forces them to actually engage with the product, which naturally reduces churn. Lucas: Exactly. And let’s be clear about the scale here. For a large enterprise SaaS company, a one percent drop in gross retention can wipe out half of your annual growth targets. In the current quarter, ending October eighth twenty twenty-six, the average gross retention for mature SaaS firms is hovering around ninety-three percent. That sounds good until you realize that to hit hyper-growth, you need net revenue retention above one hundred thirty percent. You cannot get there if your existing base is quietly bleeding out. Luna: So the pressure is on to expand the wallet share of those who stay, rather than just finding new logos. Is it true that usage-based pricing is becoming the default for new launches? Lucas: It’s becoming the standard for developer tools and infrastructure, yes. But for broader enterprise applications, we’re seeing hybrid models. Take Salesforce. They have long relied on tiered seating, but recently introduced more flexible consumption metrics for their AI modules. The data shows that customers who adopt these hybrid models report higher satisfaction scores during renewals. Why? Because the bill feels tied to actual work done, not just headcount. Luna: That makes sense. If I’m paying for API calls or storage used, I know exactly what I’m getting. Seat licenses feel arbitrary when my team structure changes. Lucas: Precisely. And this brings us to the 'expansion trap.' Many companies assume that adding features will automatically drive expansion revenue. But our analysis of recent earnings calls suggests that feature bloat without clear utility leads to confusion, not upsells. The most successful firms are those that bundle high-value outcomes into predictable tiers. Think about how Netflix moved away from DVD rental tiers to streaming-only bands. It simplified the choice architecture for the consumer. Luna: But B2B is different. Decisions involve procurement, legal, and finance. Simplifying the menu doesn't necessarily simplify the negotiation process. Lucas: True, but complexity kills deal velocity. When a procurement officer sees five different pricing structures for the same core product, they delay. The trend we’re seeing among top-quartile SaaS companies is radical simplicity. One core platform, three distinct tiers, and add-ons only for truly isolated needs. This clarity allows sales teams to focus on value demonstration rather than explaining why Tier Two costs less than Tier Three. Luna: I’ve seen deals stall over exactly that kind of confusion. Customers feel like they’re being tricked by the math. Transparency builds trust, even if the price is higher. Lucas: Trust is the currency of renewal. Let’s talk about the metric that matters most: Net Revenue Retention. NRR. If you are below one hundred ten percent, you are likely growing through acquisitions alone, which is expensive and unsustainable. The magic number for public SaaS companies trading at premium multiples is often cited as one hundred fifteen to one hundred twenty percent. It means you are growing faster than you are losing customers, purely from within the existing book of business. Luna: So, how do you drive that expansion without annoying the customer? Pushing upgrades too hard feels aggressive. Lucas: It has to be predictive. Leading SaaS providers now use product usage data to trigger expansion conversations. If a user hits eighty percent of their plan limits, the system should automatically suggest an upgrade path before they hit the wall. This turns a potential friction point into a seamless experience. It’s not sales pushing; it’s the product facilitating the next logical step. Luna: That requires really tight integration between the product team and the customer success team. Most companies keep those silos separate. Lucas: And that separation is why many fail. Customer Success shouldn't just be about solving tickets. It should be about identifying usage patterns that signal readiness to expand. At companies like Datadog, CS reps are trained to look at dashboard engagement, not just support volume. They spot the expansion opportunity weeks before the renewal date. Luna: So the renewal conversation shifts from 'will you stay?' to 'how can we help you scale further?' That’s a much stronger position to be in. Lucas: Absolutely. It flips the power dynamic. Instead of begging for a signature, you are offering a solution to their growing pains. This is particularly relevant today given the economic uncertainty. CFOs are scrutinizing every dollar spent. They want proof of ROI. If your pricing model aligns with their operational efficiency gains, you become indispensable. Luna: Do you think smaller SaaS startups can afford to build these sophisticated measurement systems, or is this an advantage reserved for the giants? Lucas: Good question. Startups actually have an advantage here because they aren't burdened by legacy pricing structures. They can design their billing engine from day one around value metrics. However, they lack the data history to calibrate those metrics accurately. The key is starting simple. Don't try to invent complex consumption models immediately. Stick to clear seat or volume tiers, but ensure every tier maps directly to a specific business outcome. Luna: Mapping to outcomes... so instead of charging for storage GBs, you charge for enabled workflows? That sounds much easier for a buyer to justify. Lucas: Exactly. Workflows are outcomes. Storage is a resource. Buyers buy resources to achieve outcomes. When you price against the resource, you compete on commodity terms. When you price against the outcome, you compete on value. And value is harder to compare. That’s where the margin lives. Luna: It also protects you from competitors who might offer cheaper raw capacity. If my competitor offers cheaper storage, but I’m selling guaranteed workflow completion, their price doesn't matter as much. Lucas: Spot on. You escape the race to the bottom. Now, let’s touch on a risk factor. Usage-based pricing can create volatility in revenue. If a customer’s usage drops seasonally, your ARR fluctuates. This scares investors who prefer predictability. How do companies manage that volatility? Luna: They probably smooth it out with minimum commitments or monthly averages. Otherwise, the cash flow could get messy. Lucas: Most do introduce a minimum floor. It’s essentially an insurance policy for both parties. The customer gets the flexibility of usage pricing, but the vendor gets a baseline guarantee. It’s a pragmatic compromise. We see this heavily in the cybersecurity space, where traffic spikes are common but unpredictable. Luna: It’s interesting how these financial constraints shape product design. The billing model dictates how the product is built. Lucas: Always. You can’t bolt on a complex pricing engine to a poorly architected product later. It has to be baked in. This is why we see so many SaaS IPOs delayed or underperforming. Their unit economics were flawed from the start. Investors are smarter now. They dig into the cohort analysis. They want to see if LTV/CAC ratios hold up over time. Luna: LTV over CAC. That old standby. Is it still the north star metric for investors? Lucas: It’s necessary, but not sufficient. A three-to-one ratio is the baseline. But investors are looking at payback periods now. If it takes eighteen months to recover the cost of acquiring a customer, that’s a problem in a rising interest rate environment. You want payback under twelve months, ideally nine. This forces discipline on the sales cycle and marketing efficiency. Luna: Nine months is tight. That means your sales team can’t drag their feet. Every interaction has to move the needle. Lucas: It does. And it highlights the importance of self-serve motion. Self-serve customers have shorter payback periods because you remove the human friction of a sales call. But self-serve scales differently. It requires exceptional product-led growth mechanics. You need onboarding to be intuitive enough that users find value without talking to anyone. Luna: Which brings us back to the product itself. If the product isn’t delightful, self-serve fails, and then you’re stuck with expensive enterprise sales. Lucas: Correct. Product-Led Growth is not a sales strategy. It’s a product strategy. Your interface must do the selling. This is why we see heavy investment in UX research for SaaS companies. They are optimizing for activation, not just sign-up. Sign-ups are vanity. Activation is sanity. Luna: Activation meaning they complete the key action that proves value. For Slack, it was sending a certain number of messages. For Zoom, it was hosting a meeting. Lucas: Those are the magic moments. Once a user experiences that moment, retention skyrockets. Your job is to reduce the time to value. Every click, every form field, every tutorial adds friction. Reduce that friction, and you lower churn. It’s basic physics applied to software. Luna: So, if I’m running a SaaS company today, what’s the one thing I should audit this week? Lucas: Look at your churn reasons. Not the generic 'budget cuts,' but the specific product-related reasons. Are people leaving because they couldn’t figure out how to use it? Or because it didn’t solve their problem? Fix the product gaps, and your pricing power improves automatically. You don’t negotiate price down; you deliver value up. Luna: Value up, not price down. Simple advice, but hard to execute when you’re chasing quarterly numbers. Lucas: That’s the tension. But long-term compounding favors patience. The companies that win in twenty-thirty will be the ones that mastered this early. They built products that people actually wanted to use, and priced them in a way that grew with the customer. Luna: It feels like a return to basics. Good product, fair price, happy customer. Hard to beat that logic. Lucas: Hard to beat, easy to forget. We got distracted by growth hacks and viral loops. But the fundamentals of recurring revenue remain unchanged. Trust, utility, and alignment. Master those, and the numbers take care of themselves. Luna: Well said. If these deep dives into the mechanics of building and scaling tech businesses are helpful for your own ventures, please consider supporting the show directly. Lucas: Listener support is what keeps this network ad-free and allows us to dig into these details without rushing. If you find value in the analysis, buy me a coffee dot com slash fexingo helps keep the lights on and the research going. Luna: It really does make a difference in the quality of the coverage we can provide. Thanks for listening, and thanks for supporting independent business journalism. Lucas: Back to the topic at hand. As we wrap up, I’m curious if you’ve noticed any vendors making this shift to outcome-based pricing in your own workflow. Did it make the purchase decision easier or harder? Luna: I’d love to hear your stories. Did transparent, value-aligned pricing help you stick with a tool, or did the complexity of usage metrics scare you off? Lucas: Let us know. What worked for you, and what felt like a game of hide and seek with the bill. Until next time, keep building smart.