Latest / SaaS Business with Fexingo: Software-as-a-Service Companies, ARR, and Recurring Revenue / The SaaS Pricing Trap That Kills Margins
Transcript
- Lucas: We need to talk about the silent killer of SaaS margins, and it isn't churn in the traditional sense. It's what I call the 'access trap.' Most operators think they're growing fast because their average revenue per user is climbing, but if you look at the underlying contract structures, those customers are paying more just to unlock features that should have been included in the base tier. Luna: So you're saying the price increase is actually a mask for poor product segmentation? Because if I'm paying extra to do my actual job, I'm not happy, I'm just trapped. Lucas: Exactly. And the trap is sprung because sales teams are incentivized to close deals today, not protect the product roadmap for tomorrow. Let's look at a typical mid-market platform scenario we've seen repeatedly this quarter. A company sells a core analytics tool at fifty thousand dollars annually. It works great. Then they release a new AI reporting module. Luna: Which sounds valuable, so why is it a trap? Isn't that just standard versioning? Lucas: It becomes a trap when the sales rep, trying to hit quota on November third twenty twenty-six, offers the AI module as a free add-on for the first year to secure the renewal. The customer gets the value. The rep hits their number. But now the baseline expectation shifts. Next year, that feature is expected to be included in the base price. Luna: Right, because once you give it away, you can't take it back without causing friction. So you've effectively lowered the floor for everyone else. Lucas: Precisely. And it compounds. If you have ten percent of your cohort getting these free upgrades, and then another five percent asking for the same deal to match them, your gross margin on that segment drops instantly. You're subsidizing your own growth. Luna: But isn't that just competitive pressure? If your competitor bundles it, you have to too. Lucas: That's the lazy exit. The real issue is that the sales team doesn't see the long-term CAC payback impact. They see a closed loop. But for the finance team, that free upgrade is a permanent drag on unit economics. We're seeing this specifically in the CRM and marketing automation spaces right now. Luna: Let's drill into that. What does the contract actually look like when this goes wrong? Are we talking about explicit discounts or something more subtle? Lucas: It's almost never an explicit line item called 'free AI module.' It's bundled into the 'enterprise agreement' as part of the premium support package. The legal language says you get access to all future beta features. So when you ship something significant, you're already under contract to give it to them. You lose all leverage. Luna: So the 'future beta' clause is basically a gift card to the customer, paid for by your future margins. That's a clever way to bleed cash without anyone noticing in the quarterly report. Lucas: And it's invisible until you try to raise prices. When you go to increase the ARR by eight percent next year, the customer says, 'I already have all the advanced features in my base contract, so I don't see why I should pay more.' You've boxed yourself in. Luna: It feels like the sales team is winning the battle but losing the war. They close the deal, but they hand over the keys to the pricing engine. Lucas: Right. And here's the kicker: the product team builds these features anyway because they want to ship cool stuff. So you have a misalignment across three departments. Sales wants the signature, Product wants the shipment, and Finance wants the margin. Usually, Finance loses. Luna: Is there a structural fix for this? Or do companies just have to accept lower margins in exchange for faster adoption? Lucas: There is a fix, but it requires killing the 'free trial of enterprise' habit. Some forward-thinking platforms are moving to a usage-based overlay. Instead of giving away the AI module, they charge per query or per report generated. This keeps the base price clean and makes the expansion revenue truly incremental. Luna: So instead of a flat fee for a feature, you monetize the consumption of that feature. That aligns cost with value better. Lucas: Exactly. And it protects the baseline. If the customer uses the AI module ten times, they pay ten units. If they use it ten thousand times, they pay ten thousand units. You don't have to fear adoption anymore. Adoption drives revenue, not churn. Luna: That seems much healthier for the P&L. But does it complicate the buying process for the customer? Enterprise buyers love predictable flat fees. Lucas: They hate variable costs until they realize the alternative is being locked out of innovation. If you have a predictable cap, say one hundred thousand dollars a year for unlimited AI usage, it solves the predictability issue while still capturing the upside. It's a hybrid model. Luna: A usage cap with unlimited access above that threshold. That's smart. It removes the fear of bill shock while ensuring high-volume users pay for their share of the compute costs. Lucas: Yes. And it forces the sales team to sell the value of the usage, not just the existence of the feature. They have to qualify the account differently. Are you going to use this heavily? Good, here's the tier. If you won't use it, stick to the base plan. Luna: So it acts as a filter. It weeds out the low-value takers and highlights the high-value partners. That changes the entire dynamic of the renewal conversation. Lucas: It absolutely does. Now the conversation is about optimization, not just maintenance. The customer success manager can say, 'You're using eighty percent of your allocated queries. Do you want to expand your tier?' That's a positive, growth-oriented dialogue. Luna: Versus the old way where they just check if you're renewing or leaving. One feels like a partnership, the other feels like a transaction. Lucas: Spot on. And let's be clear, this isn't just about AI. It applies to storage, API calls, seat counts—anything that scales. If your marginal cost is near zero, you still need to price it to signal value and cover infrastructure. Luna: Because even if the code is free, the server hosting it isn't. Charging for it keeps the business honest about what people actually use versus what they hoard. Lucas: Exactly. Hoarding is a bug in the old model. Usage is a feature in the new one. But shifting to this model requires strong internal governance. You can't let sales override the pricing architecture again. Luna: So the CEO or CFO needs to have veto power over custom contracts that deviate from the published pricing tiers? Lucas: Veto power or strict guardrails. No more 'one-off' exceptions. Every exception sets a precedent. If you make an exception for the whale client, the mid-market client will ask for the same thing. You create a race to the bottom. Luna: And once that precedent is set, you can't unilaterally remove it later without triggering massive churn. You're hostage to your own past generosity. Lucas: That's the definition of the access trap. You're trading long-term stability for short-term vanity metrics. And in this market environment, stability wins. Luna: It really does. Growth without margin is just a bigger burn rate. I think a lot of founders are realizing that lesson the hard way right now. Lucas: They are. And the ones who survive will be the ones who enforce discipline in their pricing architecture. It's unsexy work, but it's the only way to build durable equity. Luna: If today was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo — that's F. E. X. I. N. G. O. Lucas: Thanks for keeping the lights on. It helps us keep digging into these structural details rather than just skimming the surface. Back to the pricing architecture—what happens when you finally break the cycle? Luna: Do customers resist the change initially, or do they adapt quickly once they see the clarity of the new model? Lucas: There is always initial resistance. Sales teams complain that it's harder to close. Customers complain that it's more complex. But within six months, the clarity pays off. Everyone knows where they stand. Luna: And the expansion becomes organic rather than negotiated. You stop fighting over features and start scaling with usage. Lucas: Exactly. You move from a transactional relationship to a scalable utility. That's the difference between a commodity vendor and a strategic partner. Luna: It also frees up the product team to build what's actually valuable, not just what's easiest to bundle into a discount. Lucas: Precisely. Innovation becomes the driver of revenue, not a liability on the balance sheet. It's a fundamental shift in how you view your own asset. Luna: So the question for operators listening is whether they're building a moat or just handing out keys. Which one feels more accurate for most SaaS companies today? Lucas: Most are still handing out keys. But the ones who stop will be the ones defining the next decade of software economics. Luna: A powerful distinction. I hope more of them start locking the doors soon. Lucas: Let's hope so. Because the margin recovery is coming, and it's going to be brutal for those who didn't prepare.