Latest / Vertical SaaS with Fexingo: Industry-Specific Software for Healthcare, Construction, Legal / Why Vertical SaaS Companies Are Moving to Outcome-Based Pricing
Transcript
- Lucas: So you've probably seen the headline: 'SaaS is dead.' It's not, of course. But a very specific kind of SaaS pricing is under real pressure — the flat, per-seat subscription. Luna: We've talked a lot about how vertical SaaS companies find their niche and grow. But the pricing model itself — that's a whole other layer. Lucas: Exactly. And there's a growing push toward what's called outcome-based pricing. Instead of charging per user or per month, you charge based on the value the software actually delivers. A concrete example: ServiceMax, which makes field-service software for industrial equipment. Luna: That's a GE spin-off, right? Now part of Silver Lake. Lucas: Correct. Traditionally, a factory would pay ServiceMax a subscription for each technician using the app to schedule repairs. But ServiceMax has started piloting deals where they say: 'We'll charge you based on the uptime of your equipment.' If the software helps keep a turbine running 99% of the time instead of 95%, ServiceMax gets a cut of that increased productivity. Luna: That's a fundamentally different risk profile. It aligns incentives completely — but it also means the vendor bears the cost if the product doesn't perform. Lucas: Exactly, and that's the scary part for most SaaS companies. You're basically saying, 'Our software is so good that we'll take the downside.' But if you can make it work, the upside is enormous. The customer sees it as a no-brainer — they only pay when they get value. Luna: And it completely changes the sales conversation. Instead of arguing over seat count, you're talking about business outcomes. That's a much higher-value conversation. Lucas: Right. And it forces the product team to obsess over actual impact, not just feature velocity. Another company doing this: Samsara, which makes IoT sensors and software for trucking fleets. Luna: Samsara — they do cameras and telematics. So what's their outcome-based play? Lucas: They've been experimenting with pricing tied to fuel efficiency. If their route optimization and driver behavior monitoring reduce a fleet's fuel spend by 10%, Samsara takes a percentage of the savings. Not a flat monthly fee per truck. Luna: So the customer sees a direct line between the software and the bottom line. That's powerful. Lucas: It is. But it also introduces complexity. How do you define the baseline? What happens if fuel prices spike? That's not the software's fault. Samsara has to build in guardrails. Luna: And the accounting gets tricky. Revenue recognition under ASC 606 — if your revenue is contingent on customer outcomes, it's variable consideration. You can't recognize it until the outcome is realized. Lucas: That's a huge operational burden. You need systems to track outcomes, audit them, and handle disputes. Most SaaS companies don't have that infrastructure. So why are they moving this direction? Luna: I think it's a response to commoditization. In vertical SaaS, once you've won the initial land grab, competitors copy your features. Pricing becomes a race to the bottom. Outcome-based pricing is a way to differentiate. Lucas: And it's sticky. If you're saving a customer $2 million a year in fuel, they're not going to switch to a competitor that charges $50 per truck per month. The switching cost becomes enormous. Luna: But it also means your revenue is lumpier. A good quarter depends on how well your software performs, not just how many seats you sold. Lucas: That's the trade-off. Public markets hate lumpy revenue. So you see this mostly in private companies or in divisions of larger firms that can absorb the volatility. But I think it's the future for certain verticals where the value is unambiguous. Luna: If this episode is useful to you — if you're thinking about your own pricing model or just trying to understand where the industry is going — the reason we can dive deep on stuff like this is listener support. This show is ad-free, and it stays that way because of people like you. If you want to keep it going, you can toss a few bucks at buy me a coffee dot com slash fexingo. Lucas: Yeah, it genuinely makes a difference. And we don't run ads, so that's how this whole thing works. Anyway — back to the pricing models. Another angle: outcome-based pricing doesn't just change revenue. It changes the product roadmap. Luna: How so? Lucas: When you're paid per outcome, you're incentivized to build features that directly drive that outcome. Not vanity features, not nice to haves. Features that demonstrably improve uptime or fuel efficiency. It's a forcing function for product-market fit. Luna: So you end up with leaner, more focused products. That's actually a good thing for customers too. Lucas: Absolutely. And it changes how you think about customer success. In a subscription model, customer success is about reducing churn — keeping the customer paying. In an outcome-based model, it's about maximizing the outcome. You're literally in the business of making your customers more successful, because your revenue depends on it. Luna: That's a very different incentive structure. It probably changes how you hire customer success managers too. You need people who understand the customer's business deeply, not just the software. Lucas: Right. You need domain experts who can speak the language of uptime, yield, throughput. That's harder to find than a typical CSM. Luna: But it also means you can charge more. The total addressable market might be smaller — not every customer wants this model — but the revenue per customer can be significantly higher. Lucas: Exactly. And that's the thesis for a lot of these vertical SaaS companies going upmarket. The biggest, most sophisticated customers are the ones who can handle the complexity of outcome-based pricing. They have the data to measure the baseline, the legal teams to negotiate the contract, the finance teams to handle the variable billing. Luna: So it's a way to move upmarket without just raising your per-seat price. Lucas: Precisely. And it creates a moat. If you can prove your software delivers a measurable return on investment, competitors can't just undercut you on price per user. They have to match the outcome, which is much harder. Luna: I'm curious about the measurement part. How do companies like ServiceMax actually measure uptime? Are they pulling data from the customer's ERP? Do they need to integrate with the customer's systems? Lucas: Great question. They typically need API access to the customer's systems of record — maintenance logs, sensor data, maybe even financial data on lost production. That's a deep integration. It's not trivial. But once that pipe is in place, it's very hard for a competitor to rip out. Luna: So it's a data moat as well as a pricing moat. Lucas: Exactly. And that's why we're seeing this trend accelerate. The infrastructure for IoT and data sharing is getting cheaper and more standardized. Ten years ago, setting up real-time sensor data feeds was a multi-million dollar project. Now it's a few thousand dollars and a weekend. Luna: That makes outcome-based pricing feasible for more verticals. Not just heavy industry, but maybe property management, healthcare, logistics. Lucas: I think healthcare is the next big frontier. Imagine a software platform that manages patient intake for a hospital. Instead of charging per provider per month, it charges based on reduction in wait times. Or a telemedicine platform that gets paid based on patient outcomes — readmission rates, for example. Luna: That would require a massive shift in how healthcare software is bought and sold. But the potential is enormous. Lucas: It really is. And it aligns with the broader push toward value-based care. The software starts to look less like a cost center and more like a partner in the clinical outcome. Luna: So what's the downside? We've talked about lumpy revenue and operational complexity. But are there any risks for the customer? Lucas: One risk: the vendor might optimize for the measured outcome at the expense of other things. If you're a trucking company and Samsara gets paid on fuel efficiency, they might push you to drive slower, which reduces fuel use but might delay deliveries. The contract needs to define the outcome holistically. Luna: So it's not a panacea. You need really well-designed contracts. Lucas: Absolutely. And you need trust. This only works in long-term relationships where both sides believe the data is accurate and the math is fair. Luna: That's interesting. It almost forces a partnership mindset rather than a vendor-client relationship. Lucas: Exactly. And that's the ultimate takeaway. Outcome-based pricing is not just a pricing change. It's a business model change. It changes who you hire, how you build product, how you measure success, and how you relate to customers. It's a bigger shift than moving from perpetual licenses to subscriptions was. Luna: That's a bold claim. But I think you're right. Subscriptions changed cash flow. Outcome-based pricing changes everything. Lucas: It's early days. Most vertical SaaS companies still use seat-based or usage-based pricing. But the pioneers — ServiceMax, Samsara, a few others — are proving it can work. And if it works, I think we'll see a wave of adoption over the next five years. Luna: It's a fascinating development. Thanks for walking through it. Lucas: Happy to. That's our show for today. We'll be back with another deep dive soon.