Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why SaaS Buyers Now Demand Usage-Based Pricing
Transcript
- Lucas: The spreadsheet on my desk has three columns: seats, features, and a total number that doesn't move when you actually use the product. For twenty years, that was the entire game. You sold a license per user, they paid a flat fee, and everyone went home happy. But as we sit here in late September of twenty twenty six, that model is effectively dead in the enterprise. Luna: It feels like we hit a wall with it. Buyers are looking at their bills and realizing they are paying for people who never log in. It is not just about headcount anymore; it is about actual consumption. Lucas: Exactly. And the pressure is coming from the bottom up, but also from the top down. The CFOs are the ones demanding it now because flat-seat pricing creates massive volatility in operational expenditure. If your software cost goes up simply because you hired more people, but those people don't generate proportional revenue, you have a margin problem. So procurement teams are rewriting their standard contracts to require usage-based or consumption-based billing. Luna: I saw a report last month from a major consulting firm showing that over sixty percent of new enterprise deals signed this quarter included some form of metered usage clause. That is a huge shift from five years ago. Lucas: That number tracks with what I am hearing from sales leaders. They are frustrated because their old playbooks don't work. You can no longer just upsell more seats to increase ARR without delivering more actual value. The definition of value has shifted from access to outcome. If I am using a customer success platform, I do not care if ten thousand people have accounts. I care if my retention rate goes up by two percent. And if the software helps me do that, I will pay for the compute, the API calls, the storage—whatever drives that result. Luna: But isn't that scary for the vendor? You used to know exactly what your revenue was going to be next year. Now it depends on how much the customer uses it. Lucas: It is terrifying for unmanaged growth, yes. But let us be clear about the alternative. Under the old model, you had shelfware. You sold licenses, people got them, and then nothing happened. The vendor counted the money, but the customer got zero return on investment. That is a toxic relationship. With usage-based pricing, you only get paid when the customer gets value. It aligns incentives perfectly. If the customer stops using the tool, your revenue drops. So you are forced to make sure they love the product and keep using it. Luna: So it forces better product quality and customer success. But how do you handle the budgeting side? My finance team hates unpredictable bills. Lucas: This is the real friction point. Procurement wants predictability, but engineering wants flexibility. To solve this, most modern contracts are introducing a hybrid approach. You have a base subscription fee that covers the platform overhead and guarantees minimum revenue for the vendor. Then you have a variable component based on usage above a certain threshold. This gives the buyer a floor for their budget and the seller a baseline for their operations. Luna: Right, so it is not all or nothing. It is a guardrail. I think I have seen terms like true-up clauses becoming standard in these negotiations. Lucas: Yes, the true-up is critical. At the end of the quarter or the year, you reconcile actual usage against the estimated volume. If you used less, you might get a credit or roll it over. If you used more, you pay the difference. It keeps both parties honest. But it requires robust metering infrastructure. You cannot fake this. The data has to be transparent, accurate, and auditable. Luna: Which brings us to the technology itself. How hard is it for a legacy software company to switch to this? Lucas: For a company built in the early two thousands, it is a nightmare. Their billing systems were designed to process a static invoice every twelve months. Now they need real-time event tracking, complex aggregation logic, and granular reporting for the client. Many of them are essentially rebuilding their financial stack from scratch. It is a massive operational burden. Luna: So there is a barrier to entry here. Newer, cloud-native companies probably have an advantage because their architecture was always built for this kind of flexibility. Lucas: Absolutely. Startups today are born usage-based. They think in APIs and events. Established players are playing catch-up. And this is where we see the market consolidation happening. Companies that cannot adapt their pricing to match modern buyer expectations are losing deal velocity. They are getting stuck in procurement black holes because their contract terms are too rigid. Luna: It reminds me of the utility industry. You pay a connection fee, plus what you use. Does software naturally evolve into that model? Lucas: In many ways, yes. Think about cloud infrastructure providers. They set the precedent for this. When a major cloud vendor adjusted its tiered structure earlier this year, it wasn't just about changing numbers; it was about signaling that the era of bloated, fixed-fee enterprise contracts is over. Buyers want to pay for capacity when they need it, not reserve it forever. Luna: That makes sense for compute resources. But does it work for everything? What about a project management tool? Is usage even measurable there? Lucas: It is harder, but possible. You might charge per active project, or per integration triggered, or even per data point stored. The key is finding a metric that correlates with value. If the tool saves a manager five hours a week, charging by hour saved or by task completed makes more sense than charging by seat. It turns the software from a cost center into a performance multiplier. Luna: I can see why a CFO would prefer that. It ties expense directly to productivity gains. But what about the sales team? How do they forecast revenue if it fluctuates? Lucas: That is the big question for the business. Forecasting becomes less about signing deals and more about predicting adoption curves. Sales reps have to focus on onboarding and activation, not just closing. If the customer doesn't start using the tool heavily in the first thirty days, your recurring revenue will plummet. The sales motion shifts from transactional to consultative. Luna: So the definition of a successful sale changes completely. It is not done at the signature; it is done when the customer is hooked. Lucas: Precisely. And that changes the compensation structure too. You cannot just commission on the initial contract size. You have to incentivize long-term engagement. Many companies are now tying rep bonuses to net revenue retention, which includes expansion from increased usage. It aligns the whole organization around keeping the customer happy and active. Luna: This sounds like a lot of work for everyone involved. Is there any downside to this shift besides the technical complexity? Lucas: There is a risk of churn acceleration. If a customer reduces their usage because of a slowdown in business, your revenue drops instantly. Under a flat contract, you might have kept that revenue for another year even if they stopped using it. Here, the market dictates your income in real time. It exposes you to economic cycles faster. Luna: That is a valid concern. Volatility is bad for stability. But I guess the trade-off is higher overall satisfaction and lower friction in buying decisions. Lucas: Exactly. Lower friction wins the war. Buyers are tired of negotiating over unused seats. They want to deploy quickly, scale up or down as needed, and only pay for what works. If you offer that, you win the deal. If you force them into a rigid box, you lose to someone who won't. Luna: We should pause for a moment to talk about how this show stays running. We deliberately do not run ads on these episodes. If you want to support that choice and help us keep producing this deep-dive content, the link is buy me a coffee dot com slash fexingo. Lucas: It really is just listener support that allows us to take the time to research these specific angles without chasing clicks or sponsors. Every bit helps keep the signal clean. Luna: Thanks for being part of the network. It makes a huge difference for us to have this direct line to you. Lucas: Back to the economics. One final thought on the future of this. As artificial intelligence becomes embedded in more enterprise tools, usage-based pricing is going to become even more dominant. AI consumes compute. It processes tokens. It generates insights. These are inherently variable costs. Luna: Right. You cannot put a flat price tag on a neural network that might process ten queries one day and ten thousand the next. The metering has to be granular. Lucas: So we are moving toward a world where software is not a product you buy, but a service you consume. The boundary between capital expenditure and operational expenditure is blurring. Everything becomes OpEx, scaled by usage. It is a fundamental rewrite of the corporate balance sheet. Luna: It is fascinating to watch. The tools themselves are changing how we account for them. Do you think legacy software giants will survive this transition, or will they be displaced? Lucas: Some will survive by pivoting hard, but many will struggle. The inertia is real. Changing your billing system is like changing the engine of a plane while flying it. Those who succeed will be the ones who view pricing not as a administrative task, but as a core product feature. Because in this new model, the price IS the product. Luna: A powerful way to put it. The price isn't just a number on a contract; it is the mechanism that proves value exists. Lucas: Exactly. And as we look ahead to the rest of the quarter, I wonder which other industries will be forced to adopt this model next. Healthcare? Logistics? Luna: Probably. Anywhere there is heavy inventory or variable resource usage, the flat-rate model is starting to feel outdated. The market is pushing for efficiency everywhere.