Latest / SaaS Business with Fexingo: Software-as-a-Service Companies, ARR, and Recurring Revenue / How SaaS Companies Turn Usage Data Into Pricing Power
Transcript
- Lucas: Let’s talk about the biggest lie in software sales right now: the idea that a flat monthly fee is the only way to guarantee predictable revenue. Look at what’s happening with Adobe and their Creative Cloud transition back in twenty nineteen. They moved away from perpetual licenses into a subscription model, but the real shift wasn’t just recurring payments—it was tying those payments to active usage tiers. Today, in September of twenty twenty six, we’re seeing that same logic spreading to enterprise tools where seat-based pricing is suddenly looking like a liability. Luna: It feels counterintuitive when you think about cash flow stability, doesn’t it? If I’m a CFO, I want to know exactly what my bill is going to be next quarter. Lucas: Exactly. And that’s why so many legacy vendors are still clinging to per-seat models even as their customers scream for flexibility. The problem is that seat-based pricing creates artificial friction. You sell a license to fifty engineers, but only ten are actually using the advanced features. The other forty are sitting on dormant accounts, and eventually, they churn because they aren’t getting value. Usage-based pricing forces the vendor to prove worth every single month. Luna: But isn’t that scary for the buyer? When my cloud bill spikes because someone ran a big query or stored too much data, I panic. Lucas: It is scary until you realize that predictable billing often masks inefficiency. Let’s look at a concrete example from the database management space. Companies like Snowflake built their entire moat on this. Instead of paying for a server rack that sits idle half the time, you pay for the bytes scanned. It sounds risky, but the data shows that customers who adopt consumption models tend to have higher net revenue retention because they scale up organically as their business grows. They don’t hit a hard ceiling where they stop buying because they’ve maxed out their seats. Luna: So the risk shifts from the vendor losing a renewal to the customer potentially facing a surprise invoice. That’s a psychological hurdle, not just a technical one. Lucas: It’s a massive hurdle. And this is where most companies fail. They try to bolt usage metrics onto a traditional contract without changing the underlying financial architecture. I spoke with a founder last week who tried to launch a hybrid model for his HR platform. He kept the base seat fee but added overage charges for extra API calls. The result? His support ticket volume doubled because users were terrified of hitting the limit. They stopped innovating with the tool because they didn’t want to trigger a penalty. Luna: That’s the opposite of product-led growth. You’re basically punishing people for using the product more effectively. Lucas: Precisely. To make usage-based pricing work, you need transparency and guardrails. The best-in-class operators build in soft caps or gradual tier jumps rather than hard cliffs. Think about how Spotify handles its premium tiers. You know what you’re getting, and if you go slightly over, it doesn’t feel like a punishment—it feels like natural expansion. In the B2B world, this means giving customers a dashboard that shows their projected spend in real time. If they can see the curve before the invoice drops, the anxiety disappears. Luna: Do most companies actually have the data infrastructure to track that level of granularity? Or is that just a startup luxury? Lucas: It used to be a luxury, but cloud-native architectures have made it cheap. The challenge isn’t capturing the data; it’s mapping it to something meaningful. Just counting clicks is useless. You need to count actions that correlate with business outcomes. For a logistics software company, counting logins tells you nothing. Counting routes optimized tells you everything. If you tie the price to the route optimization, the customer sees immediate ROI. They aren’t paying for software; they’re paying for fuel savings. Luna: That’s a much stronger value proposition. But does that complicate your own sales cycle? Negotiating variable rates must be messier than signing a standard annual contract. Lucas: It does, but it also shortens the time to close for mid-market deals. Sales teams spend less time arguing about how many seats they need to buy for a pilot program. Instead, they focus on integration. The buyer says, let’s start with five hundred dollars a month in usage credits. If it works, they’ll naturally expand. This lowers the barrier to entry significantly. We’re seeing a lot of SMB adoption of this model because it removes the upfront capital expenditure. You don’t need a budget approval for fifty thousand dollars; you just need a credit card for five hundred. Luna: I can see why marketing loves that. Lower friction, faster conversion. But what about the finance team trying to forecast revenue? Variable ARR is a nightmare for planning. Lucas: This is the real pain point. Investors love the top-line growth potential of usage-based models, but they hate the volatility. In the current market environment of twenty twenty six, capital efficiency is king. A company with lumpy revenue gets valued lower than one with smooth, predictable growth. So the smart operators are introducing minimum commitments or floor guarantees. You might have a usage rate, but you promise to spend at least ten thousand a month. It gives the vendor a baseline while keeping the upside open for the customer. Luna: So it becomes a hybrid again. Is there any way to keep it purely variable and still satisfy the investors? Lucas: Only if your growth rate is explosive enough to mask the variance. Look at early-stage AI tool providers. Their user bases are expanding so fast that the fluctuations average out quickly. But for mature companies, pure variable models are dangerous. You need a floor. The trick is communicating that floor not as a penalty, but as a commitment to partnership. It signals that the customer is serious about deriving value, which builds trust. Luna: Trust is huge. If I’m a large enterprise client, I want to know you won’t change the pricing formula halfway through the year to squeeze me. Lucas: That’s why contract clarity is critical. You have to define the unit of measure precisely. What counts as a transaction? Is it a successful one? Does it include retries? These details get litigated in renewals if they aren’t baked into the initial agreement. I worked with a payment processor who lost a major deal because they couldn’t agree on whether 'failed attempts' should be billed. The customer thought they were testing the system; the vendor thought they were processing load. It was a ten million dollar fight over semantics. Luna: Ouch. So the legal team has to be involved way earlier in the process now? Lucas: Absolutely. In the old seat-based world, legal just checked the indemnification clauses. Now, they’re reviewing the data definitions and the billing logic. It’s a heavier lift for the backend, but it pays off in fewer disputes later. And honestly, it forces the product team to be more disciplined about what they’re measuring. You can’t just track everything; you have to track the things that matter to the customer’s bottom line. Luna: That discipline seems like a good thing, even if it’s painful to implement. Do you think this will replace seat-based pricing entirely? Lucas: Not entirely. Some tools are inherently binary. If you need access to the admin panel, you need a seat. There’s no usage metric for that. The future is likely a mix. Core access is seated; advanced capabilities are consumed. Think of it like a gym membership. You pay a base fee for the door, but if you want personal training or specialized classes, you pay per session. Most modern platforms are moving toward this layered approach because it captures value across the entire organization, not just the power users. Luna: That makes sense. It stops the situation where the CEO buys the software but nobody uses it except the IT department. Lucas: Right. It democratizes the usage. When everyone feels like they’re contributing to the cost, they become more invested in making it work. It creates a internal accountability loop that seat-based pricing never could. Plus, it helps with cross-selling. Once a customer is comfortable paying for API calls or storage, adding a new feature is just another line item. It’s easier to upsell than it is to renegotiate the whole contract. Luna: Speaking of contracts, how do you handle the billing cycles? Monthly invoicing for variable usage must be administratively heavy. Lucas: That’s why automation is non-negotiable. If you’re sending PDF invoices for variable usage, you’re burning money. The best systems generate invoices automatically based on the metered data. They integrate directly with the procurement portals of large enterprises. SAP and Oracle buyers want to see the line items match their purchase orders. If you can’t feed that data into their systems seamlessly, you lose the deal regardless of how good your pricing model is. Luna: Integration depth really is the hidden battleground here. It’s not just about the price tag anymore. Lucas: It never was, but it’s becoming more explicit. The price is just the entry ticket. The experience of paying—the visibility, the ease, the fairness—is what keeps them. If I can look at my dashboard and understand exactly why I owe four thousand dollars instead of three thousand, I’m happy to pay it. If I have to call an account manager to figure it out, I’m already thinking about switching vendors. Luna: Transparency builds loyalty. It’s almost simpler than the complex negotiations we’re used to. Lucas: It is, once you build the infrastructure. The hard part is the first six months. You’re debugging the meters, refining the units, and educating your sales team on how to explain the math. But after that, it scales beautifully. You stop worrying about churn because the price moves with the value. If the customer grows, you grow. If they shrink, you shrink. It aligns incentives perfectly. Luna: Aligning incentives is what everyone talks about, but rarely achieves. This feels like a genuine step forward. Lucas: It is. And for listeners running these businesses, the takeaway is clear. Stop treating pricing as a static number. Treat it as a dynamic reflection of the relationship. If your product delivers more value, your revenue should reflect that naturally, not through a negotiated raise, but through organic usage. Luna: If these conversations are useful for what you're building or running, the way these stay ad-free is listener support—buy me a coffee dot com slash fexingo. Lucas: Yeah, we appreciate it. It lets us dig into these structural shifts without rushing. Thanks for keeping the signal strong. Luna: Back to the data side, though. How do you prevent gaming? If users can game the meter, the model collapses. Lucas: Gaming is always a risk with any metric-driven system. In usage-based models, the temptation is to create dummy transactions or abuse free tiers to test limits. You have to implement anti-fraud measures similar to what payment processors use. Rate limiting, anomaly detection, and distinct user verification. If you see one IP address generating ten thousand requests in a minute, that’s not a user; that’s a bot or a mistake. You need automated triggers to pause billing or flag the account for review. Luna: So the finance team needs to work with engineering to set those thresholds? Lucas: They absolutely do. Silos kill usage-based models. If Engineering builds the meter but Finance sets the prices without understanding the data quirks, you get mismatches. Regular audits of the metering logic are essential. I recommend quarterly reviews where finance, product, and engineering sit down to compare the raw data against the actual customer behavior. It catches drift before it becomes a scandal. Luna: Proactive governance. That sounds like a lot of work, but probably cheaper than a PR crisis. Lucas: Much cheaper. And it builds credibility. When customers see that you’re monitoring your own systems to ensure accuracy, they trust you more. It shows you’re partners, not just vendors collecting checks. That trust is the ultimate moat in a crowded market. Luna: It really shifts the power dynamic from adversarial to collaborative. Lucas: Exactly. And that’s where the real long-term growth happens. Not in squeezing every dollar out of a stagnant contract, but in growing together as the customer’s needs evolve. It’s harder to build, but it’s infinitely more sustainable. Luna: So the question for founders today is less about how to price your software and more about how to measure your customer's success. Lucas: Spot on. If you can’t measure success, you can’t price for it. And if you can’t price for it, you’re leaving money on the table while risking churn. Start measuring what matters, then let the price follow the value. Luna: I wonder if the next wave of AI agents will completely break our current understanding of usage metrics. Lucas: That’s a terrifying thought. Imagine billing for autonomous decision-making. We’ll need new vocabularies for value. But for now, mastering the basics of usage transparency is the winning move.