Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why SaaS Vendors Are Betting On Usage-Based Pricing
Transcript
- Lucas: The biggest lie in enterprise software right now is that predictability equals safety. We have spent the last decade convincing CFOs that a flat per-seat license fee is the gold standard of budgeting, but that model is cracking under the weight of AI integration. When you add generative tools to your stack, usage spikes unpredictably, and seat-based caps feel increasingly arbitrary. Luna: Exactly, and it creates this weird tension where procurement loves the flat fee but the engineering team hates the cap because they just want the tool to work without hitting a wall mid-project. Lucas: Right, so we are seeing a massive pivot toward usage-based pricing, where you pay for what you actually consume rather than who logs in. It sounds simple on paper, but the operational complexity for the vendor skyrockets when you have to track every API call or compute hour across thousands of clients. This isn't just a billing change; it is a fundamental restructuring of the relationship between buyer and seller. Luna: So does that mean the sales team stops selling seats and starts selling outcomes? Because if I am paying by the gigabyte, my incentive changes completely. Lucas: It does, and that is where the friction lives. In a seat model, the vendor wants you to buy more licenses even if you do not use them. In a usage model, the vendor wants you to use more volume, which aligns their interests with yours much more tightly. But alignment only works if the pricing tiers are transparent and the data is visible in real time. Luna: I remember reading about Adobe making this exact shift years ago, moving away from Creative Suite boxes to Creative Cloud subscriptions based on access rather than individual installs. Lucas: Adobe is the classic example, but look at how far they have pushed it since then. They started with a subscription box, but now they are layering on usage metrics for services like Firefly. The key difference is that Adobe has enough scale to absorb the variance, whereas smaller vendors get crushed by the cash flow gap when a client ramps up usage in month three but pays on net thirty terms. Luna: That cash flow gap is a killer for startups though, isn't it? If you are building the tool and the client goes viral using it, you might not see the revenue for ninety days. Lucas: Precisely. And that leads us to the second major risk: forecasting. If your revenue depends on how much data a client processes, your quarterly guidance becomes a guessing game unless you have incredible visibility into their pipeline. Most public companies hate this uncertainty, which is why many still hide usage fees inside complex tiered packages rather than going fully transparent. Luna: But isn't that just obfuscation? If I am a buyer, I would rather know exactly what a million API calls cost than guess at it through a vague enterprise agreement. Lucas: You would, and modern procurement teams are demanding that transparency. The new standard is clear unit economics. You need to know the price per thousand records, the price per minute of video processing, the price per active user hour. When vendors hide these numbers, buyers assume there is a markup so large it is not worth negotiating. Luna: So the vendor who publishes their pricing page clearly actually wins the deal faster? That feels counterintuitive for traditional sales orgs. Lucas: It is counterintuitive for legacy sales teams, but it accelerates the buying committee. When the legal team can review the contract without needing three rounds of redlines on undefined overage charges, the deal closes faster. Speed is currently the most valuable currency in enterprise software because nobody wants to wait six months for a pilot to turn into a contract. Luna: Okay, but let's talk about the downside for the buyer. What happens when your usage spikes unexpectedly during a campaign launch? Lucas: That is the nightmare scenario known as bill shock. I spoke with a CTO last week whose marketing automation platform charged them an extra two hundred thousand dollars in one month because a botched migration caused a loop in their email sends. They had no alert system, no cap, and no recourse until the invoice arrived. Luna: That is terrifying. So does that mean every usage-based contract needs a hard spend limit built into the code? Lucas: It absolutely does. The best contracts include a soft cap with automatic notifications at eighty percent and a hard stop at one hundred ten percent. This forces the vendor to be honest about their capacity planning too. If they cannot handle your spike without breaking the bank, they should tell you upfront rather than trapping you in a feedback loop of overages. Luna: I love that. It turns the pricing model into a shared responsibility rather than a hidden trap. But how do vendors convince investors that this volatile revenue stream is actually stable? Lucas: They use annualized run rate combined with high retention metrics. If you have ninety-five percent gross retention and your usage grows year-over-year alongside your client's growth, the volatility smooths out. The trick is proving that your product is sticky enough that clients won't leave just because they found a cheaper competitor for a single module. Luna: Sticky products are harder to build though. It usually takes years to earn that kind of trust in an enterprise environment. Lucas: True, which is why we see incumbents like Microsoft and Salesforce leading this charge. They have the moat. A startup trying to sell a niche analytics tool has to offer lower prices or better flexibility to win the switch. The market is bifurcating into platforms that dictate terms and point solutions that beg for inclusion. Luna: So for the listener building a B2B product right now, what is the practical takeaway? Do you go usage-based immediately or stick to seats? Lucas: Start with seats if you are early stage, but design the architecture for usage from day one. Build the telemetry hooks that allow you to measure consumption accurately. When you eventually pivot, you will already have the data infrastructure in place instead of scrambling to retrofit billing logic after you have grown. Luna: That makes sense. It is about future-proofing the backend before the frontend gets too crowded. Before we dive deeper into the contract specifics, I want to take a quick moment to acknowledge the people keeping this network running. Lucas: If these conversations are useful for what you are building or running, consider supporting the show directly. Listener contributions help us maintain the research depth and audio quality that keeps this ad-free. You can find us at buy me a coffee dot com slash fexingo — that's F. E. X. I. N. G. O. Luna: Thanks for the support. It really allows us to dig into these structural shifts without rushing for clicks. Let's get back to the contract mechanics. Lucas: The most critical clause in any usage-based agreement is the definition of the metric. You need to specify exactly what counts as a transaction. Does a failed API call count? Does a cached response count? Ambiguity here is where vendors make their margin and buyers lose their sleep. Luna: So if I am negotiating, I should insist on a glossary that defines every single billable event? Lucas: Yes, and you should also demand a monthly reconciliation report. This gives you a thirty-day window to dispute errors before the invoice locks in. It transforms billing from a punitive event into a collaborative audit process. Vendors who resist this are usually hiding something inefficient in their own delivery chain. Luna: That is a smart power move. It shifts the burden of proof onto the vendor to demonstrate accuracy rather than the buyer to prove innocence. Lucas: Exactly. And it builds trust. When a vendor willingly opens their books to verify your usage, you know they are confident in their product value. You do not need to worry about hidden fees if you can see every line item in real time. Luna: I wonder if this transparency will eventually become a competitive advantage in itself. Like, a badge of honor for ethical pricing. Lucas: It already is for mature buyers. Procurement teams are tired of gaming the system. They want straight deals. As we move through late twenty twenty-six, I expect we will see more vendors advertising their transparent pricing as a core feature alongside security and compliance. Luna: So the trend is moving from secrecy to clarity, driven by buyers who just want to know the final number before they commit. It feels like a maturation of the entire industry. Lucas: It is a maturation, but also a survival tactic. In a tighter economic climate, businesses are cutting waste. If your software pricing is opaque, it looks like waste waiting to happen. Transparency signals discipline, and discipline is what CFOs reward right now. Luna: Do you think this will force smaller players out of the market? Can they compete on transparency if they lack the scale to offer low unit costs? Lucas: Not necessarily. Smaller players can compete on flexibility. They can offer custom bundles or hybrid models that combine fixed seats with variable usage. The rigid giants often struggle to adapt quickly, leaving room for agile entrants to capture niche segments with tailored pricing structures. Luna: Hybrid models seem like the sweet spot. You get the budget predictability of seats plus the fairness of usage for the heavy lifters. Is that becoming the dominant pattern? Lucas: It is certainly the most popular compromise. Most enterprise deals today are some variation of base platform fee plus usage add-ons. It satisfies both the finance department's need for baseline certainty and the engineering team's need for unlimited scalability. Luna: So the war is no longer about who has the cheapest flat rate, but who offers the most balanced hybrid structure. That changes the entire sales dynamic. Lucas: It does. Sales reps now need to understand unit economics deeply. They cannot just sell features anymore; they have to model total cost of ownership based on projected usage. The best vendors provide interactive calculators that help buyers estimate their costs before they even sign the NDA. Luna: Interactive calculators! I have never seen those in enterprise sales. That is a huge shift from sending a PDF quote. Lucas: It is part of the digital transformation of procurement. Buyers want self-service options. They want to play with the numbers themselves before involving their manager. Tools that enable that autonomy tend to convert higher because the buyer feels in control of the decision. Luna: Control seems to be the underlying theme here. Whether it is controlling costs, controlling usage, or controlling the data. The old model stripped that control away from the buyer. Lucas: Spot on. The new model returns agency to the customer. You pay for what you use, you see what you pay for, and you can adjust your consumption instantly. It is a more democratic way to do business software. Luna: I hope we see more of that democratization across other verticals beyond just tech. Healthcare and manufacturing could benefit from this level of pricing clarity too. Lucas: They definitely could. Once the technology stack proves itself in enterprise software, the principles trickle down to every industrial sector. The question is whether legacy industries will embrace the agility or cling to their old contracting habits. Luna: Given the current pressure on margins, I doubt they have a choice. Efficiency will force the change regardless of tradition. Lucas: Efficiency always wins in the end. The question for us as observers is how fast the adoption curve will steepen over the next twelve months. Luna: Fast enough to catch everyone off guard if they are not paying attention to the fine print of their current vendor agreements. Lucas: Agreed. Check your contracts. If you are locked into a rigid seat model, you might be overpaying for idle users while your competitors are optimizing for actual output. The leverage is shifting, and it is happening right now.