Latest / SaaS Business with Fexingo: Software-as-a-Service Companies, ARR, and Recurring Revenue / How SaaS Companies Survive The Expansion Trap
Transcript
- Lucas: If these conversations are useful for what you're building or running, a couple of dollars a month is genuinely what keeps these going. You can support us at buy me a coffee dot com slash fexingo — that's F. E. X. I. N. G. O. It helps cover the research time so we don't have to sell ads. Luna: Thanks for that, Lucas. And yeah, it really does make a difference for the team. Lucas: Let's jump into today. We've spent the last few episodes dissecting pricing tables, usage tiers, and the subtle art of monetizing data. But there is one structural trap that even the most sophisticated SaaS operators stumble into when they try to scale past a certain point. It's not just about raising prices; it's about the mismatch between how customers consume value and how they actually pay for it. Luna: You mean the classic 'usage spike' problem? Where a customer loves the product but then gets hit with a massive bill they didn't budget for? Lucas: Exactly. That is the surface-level symptom. The deeper issue is what we call the Procurement Friction Loop. When a software company shifts from a flat seat-based license to a usage-based model, they unlock incredible top-line growth. But they also introduce a variable cost center that makes enterprise finance teams nervous. Today, October 26, 2026, we are seeing a distinct pullback on discretionary cloud spend, and this friction is becoming a major bottleneck for mid-market deals. Luna: So the sales team is selling the efficiency, but the procurement team is blocking the variable costs because they can't predict the end-of-year bill. Lucas: Right. And here is the concrete detail that most founders miss. It isn't just about unpredictability. It's about the internal politics of large organizations. If a marketing team uses a SaaS tool that charges per impression or per active user, and that usage spikes by forty percent in Q4, the CMO takes the blame for blowing the budget. Even if the tool generated ROI, the friction of explaining an unexpected overage is high enough that many companies will simply cut the subscription rather than fight for a variance approval. Luna: That sounds like a retention killer. So you lose the customer not because the product failed, but because the billing structure triggered a bureaucratic defense mechanism. Lucas: Precisely. Let's look at a specific case. Consider a major data analytics platform that transitioned fully to usage-based pricing two years ago. Their initial ARR jumped thirty percent as adoption exploded. But within eighteen months, their net retention rate dipped below one hundred percent. Why? Because their largest enterprise clients started hitting hard caps. Once a client exceeded their pre-negotiated volume limit, the overage rates were steep—sometimes double the standard marginal cost. The client didn't stop using the tool entirely, but they froze new project deployments until the next fiscal year. Luna: So they essentially paused their own growth to avoid the penalty. That is a fascinating behavior. Did the platform adjust the pricing to fix this? Lucas: They did, but the adjustment was complex. They introduced a hybrid model. Instead of a hard cap, they offered a 'commitment discount.' The client commits to a minimum annual spend, say five million dollars, and anything above that is billed at a discounted marginal rate. This shifts the risk back to the buyer. They are now incentivized to use the tool aggressively because every extra dollar spent brings them closer to unlocking cheaper future usage. Luna: That's clever. It turns the procurement officer into a champion because they're actively trying to maximize their committed value. But doesn't that require more trust? Enterprise buyers are skeptical of these long-term commitments right now. Lucas: It does require trust, which is why the timing matters. In early 2026, those commitments were tough to sell. But by late 2026, with interest rates stabilizing and corporate balance sheets looking healthier, CFOs are more willing to sign multi-year usage contracts if the unit economics are clear. The key is transparency. The best SaaS companies now provide real-time dashboards that show exactly where a client stands against their commitment, often with alerts when they are approaching ninety percent utilization. Luna: I love that dashboard feature. It changes the dynamic from 'surprise bill' to 'budget management tool.' But what about smaller customers? Do they face the same procurement friction? Lucas: Smaller customers, typically under fifty employees, rarely have a dedicated procurement department. They use corporate cards. For them, the friction is psychological, not bureaucratic. If a small business sees a bill triple overnight because they launched a viral campaign that drove heavy API calls, they panic. They assume the price has changed. They assume they are being gouged. This leads to immediate churn, often without any conversation. Luna: So for the long tail, simplicity wins. They need predictable costs, not complex tiered structures. Lucas: Absolutely. This is why many successful SaaS platforms segment their pricing. They offer a strict, capped plan for SMBs—maybe ten thousand dollars a year max—and a flexible, usage-based plan for enterprises. This protects the small customer from shock while allowing the large customer to scale. It’s a classic segmentation strategy, but it requires disciplined product engineering to enforce those caps without degrading performance. Luna: Enforcing caps can be tricky technically. If you throttle performance once they hit the limit, you punish the good users for the bad usage. Is that a common mistake? Lucas: It is a very common mistake. Throttling is the nuclear option. It damages brand loyalty and creates operational chaos. The better approach is 'soft limits.' When a user hits eighty percent of their cap, you send a notification. At one hundred percent, you might slow down non-critical processes or queue requests, but you never block core functionality. Instead, you prompt an upgrade. You make it easy to expand, not difficult to continue. Luna: That feels much more aligned with the customer success mindset. But let's talk about the metric side. How do you measure if this hybrid model is actually working for the business? Lucas: The primary metric becomes 'Commitment Utilization Rate.' You want to see this hovering around eighty-five to ninety percent across your enterprise book. If it's too low, your pricing is too generous, and you're leaving money on the table. If it's consistently above one hundred percent, your caps are too tight, and you're inducing churn. The sweet spot is where customers feel challenged but not penalized. Luna: And what about gross margin? Does usage-based pricing hurt margins compared to flat licenses? Lucas: It depends on the underlying infrastructure costs. For ai heavy workloads, compute costs are volatile. If you charge a flat fee but your GPU costs spike, your margin collapses. Usage-based pricing passes that volatility risk to the customer, protecting your margin. However, you must be careful not to pass on too much complexity. If the customer struggles to understand their bill, your support costs will skyrocket. Luna: Support costs. That's an invisible expense. A confused customer calls support ten times instead of once. Lucas: Exactly. So the investment in clear documentation and intuitive billing interfaces is not optional. It's part of the product. Companies like Stripe and Twilio set the gold standard here. Their APIs are developer-friendly, and their billing dashboards are transparent. Competitors who lag in UX will lose deals not because their code is worse, but because their accounting is harder. Luna: It seems like the battle is shifting from feature parity to billing clarity. That's a significant change from five years ago. Lucas: It is. And as we move through the rest of 2026, I expect to see more SaaS companies adopting 'predictive billing.' Using machine learning to forecast next month's usage based on current trends and giving the customer a heads-up before the invoice drops. It reduces surprise and builds trust. Luna: Predictive billing sounds like a natural evolution. But does it require access to deep historical data that not all companies have? Lucas: Most mature SaaS firms have enough data to build a simple moving-average model. You don't need a PhD in data science. You just need to show that you're paying attention to their behavior. That signal alone increases renewal rates. Luna: So the lesson is: manage the relationship, not just the resource. The billing is the touchpoint. Lucas: Spot on. If you treat billing as a transactional afterthought, you'll lose enterprise deals. If you treat it as a strategic partnership tool, you unlock expansion revenue. Luna: That's a powerful reframing. Most founders think of pricing as something you set once. You're arguing it's a continuous dialogue. Lucas: It is. And the companies that master that dialogue will dominate the next cycle of SaaS growth. The rest will get stuck in the friction loop. Luna: I wonder if we'll see more consolidation among billing platforms as SaaS companies realize they can't build this internally anymore. Lucas: That's a strong possibility. Specialized billing infrastructure is becoming its own category of enterprise software. We'll likely see more M&A activity in that space over the next twelve months. Luna: Good thing we're tracking these structural shifts. It helps us advise our listeners on where to focus. Lucas: Exactly. Keep an eye on the commitment utilization rates of your favorite vendors. It tells you everything you need to know about their pricing health. Luna: And if you find your own numbers are out of whack, maybe it's time to revisit that hybrid model we discussed. Lucas: Or just call your procurement team and ask them what keeps them up at night. Sometimes the answer is simpler than you think.