Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / How Enterprise SaaS Pricing Models Are Breaking Down
Transcript
- Lucas: So we used to talk about enterprise software pricing like it was a simple subscription box, right? You pay a fixed fee per user, you get access, life is good. But if you look at what’s happening in the enterprise sector today, that model is completely fracturing. Vendors are moving toward consumption-based billing, where you pay for exactly what you use, which sounds fair until your bill doubles overnight because someone ran a big analytics job. Luna: Exactly, and the scary part is that most buyers don’t realize they’re being charged by the query or the gigabyte until they see the invoice at the end of the quarter. It’s like buying electricity without a meter. Lucas: Right, and this shift didn’t happen by accident. It started with companies like Snowflake and Datadog, who built their entire go to market strategy around usage. They convinced enterprises that flexibility was worth a premium, even if it meant less predictability in spending. Now, legacy vendors are scrambling to copy that model, but they’re doing it wrong because their infrastructure costs are fixed, not variable. Luna: I saw a case study last week where a mid-sized fintech company spent forty thousand dollars on a single day because a developer accidentally triggered a recursive loop in a logging service. That’s the kind of shock no CFO can explain to the board. Lucas: That’s the classic example of why procurement teams are suddenly demanding more granular controls over these contracts. They aren’t just looking at the price per seat anymore; they’re asking for caps, thresholds, and real-time dashboards so they can see usage before it becomes a crisis. It’s a fundamental change in how we negotiate software deals. Luna: It feels like the power dynamic has shifted back to the buyer, but only if they have the technical literacy to understand what they’re actually consuming. Lucas: Yeah, and here’s the thing: most procurement teams don’t have that literacy. They’re still negotiating based on headcount and years of tenure, while the vendor is tracking every API call. So you end up with these bizarre hybrid contracts where the base fee covers the license, but then there’s an add-on for usage that’s basically a blank check with a cap. Luna: Blank checks with caps are just fancy ways of saying we’ll let you bleed us slowly instead of all at once. Smart move for the vendor, terrible for the budget planner. Lucas: Well, it’s smart for the vendor’s valuation because it creates a long-tail revenue stream that investors love. But for the buyer, it introduces what I call 'bill shock anxiety.' Every time someone in the organization clicks a button, there’s a tiny fear that they’re burning cash. And that fear changes behavior. People stop experimenting. They stop innovating. They start hoarding licenses they don’t need just to stay within a safe baseline. Luna: That’s ironic because the whole point of cloud software was supposed to be agility. Now we’re creating bureaucratic walls around innovation because of fear of the meter. Lucas: Absolutely. And it’s not just about the technology; it’s about the cultural shift in how companies manage risk. In the old world, risk was capped by the contract value. In the new world, risk is uncapped unless you explicitly define it. And defining it requires engineering insight that most finance departments simply don’t have. Luna: So who bridges that gap? Is it FinOps becoming a standard role in every enterprise, or are we just going to keep seeing surprises? Lucas: FinOps is definitely growing, but it’s still niche. Most companies are relying on third-party tools that aggregate cloud spend across multiple vendors. But here’s the problem: those tools are often too late. By the time you see the spike in your dashboard, the damage is done. You need predictive modeling, not just reporting. You need to know how much a new feature will cost before you ship it. Luna: Predictive costing sounds great in theory, but does any vendor actually provide that level of transparency right now? Or is it just another buzzword? Lucas: A few are starting to do it well. For example, some database providers now offer sandbox environments where you can test queries and get an instant estimate of the compute cost before you run them in production. It’s a small step, but it’s huge for changing behavior. If developers know that a specific query will cost five dollars versus fifty cents, they’ll write better code. Luna: That’s fascinating. It turns cost awareness into a development metric, almost like code quality or security standards. Suddenly, efficiency is part of the job description. Lucas: Precisely. And that’s where the real tension lies. Developers want speed and flexibility. Finance wants control and predictability. The consumption model sits right in the middle, forcing both sides to communicate more than ever before. If they can’t align, the project stalls. If they do align, you get incredible value. Luna: But let’s be honest, most organizations are terrible at cross-functional alignment. How often does the dev team actually talk to the finance team about tool usage? Lucas: Rarely. Usually, it’s siloed. The devs buy the tools, the finance team pays the bills, and nobody talks until renewal time. And when renewal comes, the vendor knows they have leverage because the buyer is locked in. Switching costs are high, data migration is painful, and everyone just accepts the price hike. Luna: So the consumption model doesn’t solve the lock-in problem; it just makes it more expensive to leave. You’re paying for convenience until you’re trapped by complexity. Lucas: That’s a really sharp point. Lock-in used to be about proprietary formats or difficult migrations. Now it’s about embedded workflows and historical data patterns. The more you use the platform, the harder it is to leave, regardless of whether you’re paying per seat or per query. Luna: So procurement needs to start thinking about exit strategies before they sign the entry strategy. That’s a massive shift in mindset. Lucas: Exactly. You need to ask: what happens if we double our usage next year? What happens if we need to migrate this data to a competitor? Those questions should be in the RFP, not after the fact. And yet, I rarely see them addressed. Luna: Because nobody wants to think about failure when they’re excited about a new tool. It’s human nature to focus on the gain, not the loss. Lucas: Right, but in B2B software, the loss can be millions of dollars. So we have to train people to think about the worst-case scenario. It’s not pessimism; it’s prudence. And frankly, it’s the only way to survive in a market where vendors are constantly tweaking their pricing algorithms to squeeze out more margin. Luna: It feels like we’re entering a era of hyper-transparent pricing, but also hyper-volatile costs. Stability is gone, and in its place is constant negotiation. Lucas: I think stability is coming back, but in a different form. We’re seeing the rise of 'commit and grow' contracts, where you agree to a minimum spend in exchange for significant discounts on usage above that threshold. It gives the vendor predictability and the buyer a clear path to savings if they scale efficiently. Luna: commit and grow sounds like a compromise, but it still requires accurate forecasting. If you guess wrong, you either pay for unused capacity or get hit with overage fees. Lucas: True, but it’s better than the binary choice of flat fee versus unlimited risk. It encourages collaboration between sales and finance to set realistic targets. And if you miss the target, most vendors will work with you rather than penalize you, because they want the long-term relationship. Luna: That’s interesting. It suggests that trust is becoming a currency in itself, alongside the actual dollars being exchanged. Lucas: I’d argue it’s always been there, but now it’s visible. When you share your usage data openly, you signal confidence. When you hide it, you signal fear. And vendors are rewarding the confident ones with better terms. Luna: So the lesson here is: be transparent, forecast carefully, and never assume the default pricing model is the best one for your specific use case. Lucas: Spot on. And if you’re listening to this and you’re responsible for software spend, start auditing your current contracts today. Look for those hidden usage clauses. Ask your vendors for granular breakdowns. And please, talk to your developers about what they’re actually building, not just what they’re buying. Luna: Before we wrap up, I want to mention something real quick. A handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that's literally what funds making this many of these. Lucas: Yeah, it’s amazing how much support keeps this independent and ad-free. If that resonates with you, feel free to check it out. No pressure, just gratitude. Luna: Thanks for keeping us going. Anyway, back to the topic. Lucas: So, here’s the question for you: as you look at your own tech stack, do you see consumption-based pricing as a opportunity for efficiency, or a liability you’re trying to minimize? Where do you stand on that spectrum?