Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / How SaaS Vendors Manage Customer Churn Risk
Transcript
- Lucas: The way we used to measure success in enterprise SaaS was pretty straightforward: did they sign the contract, and did they pay the invoice? But if you look at the current landscape as of September nineteen twenty-six, that model is completely broken for anything above five hundred thousand dollars in annual contract value. Luna: Right, because the sale is just the entry fee now. The real work starts after the pen hits the paper, and most vendors are still treating it like an afterthought. Lucas: Exactly. And I think the biggest shift has been the move from reactive fire-fighting to predictive health monitoring. You see this clearly with companies like Salesforce or Adobe, where customer success managers are no longer just waiting for a complaint. They are building algorithms that flag risk based on login frequency, feature adoption rates, and even internal email sentiment analysis from public data sources. Luna: It feels less like support and more like intelligence gathering. Do buyers actually know how much data their vendors are tracking on them? Lucas: Most don't, but procurement teams certainly do. That is why our last few episodes touched on algorithmic transparency, but today I want to focus on something slightly different: the structural incentive problem. Why would a vendor care about your churn if their sales team gets paid on day one, but the success team only gets bonuses if you stay for three years? Luna: That misalignment is exactly why so many implementations fail in the first six months. The seller walks away, and the successor is left holding the bag. Lucas: Precisely. And the solution isn't just 'hire better people.' It's about tying compensation directly to net revenue retention rather than gross bookings. When you look at the top quartile performers in the sector, their customer success leaders have equity stakes that vest based on multi-year retention, not just quarterly upsells. Luna: So the money follows the relationship, not just the transaction. That changes the entire dynamic of the renewal conversation. Lucas: It does. And here is the concrete detail that matters for listeners who might be negotiating contracts right now: look at the definition of 'active user' in your SLA. A lot of legacy contracts define active users as anyone who logs in once a month. Modern vendors are pushing for 'meaningful engagement,' which often requires daily or weekly interaction with core modules. Luna: That sounds like a trap. If I can't get my team to log in daily, am I automatically flagged as high risk? Lucas: Not necessarily, but it forces a conversation about change management. The vendors who are winning now are the ones providing embedded enablement resources, not just training videos. They are essentially acting as consultants to ensure your team actually uses the tool effectively. Luna: Which means the vendor becomes part of your internal operating system. That makes switching costs incredibly high, both technically and culturally. Lucas: It absolutely does. And that brings us to the donation segment, because keeping this network running relies on exactly that kind of sustained engagement from you, the listener. Luna: If these conversations help you navigate the complexities of enterprise tech, consider supporting the show directly. Lucas: A small monthly contribution really helps us keep producing independent, ad-free analysis like this. You can find us at buy me a coffee dot com slash fexingo. Luna: It makes a huge difference in our ability to dig into these operational details without relying on sponsorships. Thanks for listening. Lucas: Let's get back to the mechanics of those health scores. Because once a vendor flags you as 'at risk,' what actually happens? Is there a standard playbook, or does every company handle it differently? Luna: I imagine there is some panic behind the scenes. Do they call you immediately, or do they try to fix it quietly first? Lucas: In well-run organizations, it triggers a structured intervention protocol. Step one is usually a diagnostic call from a senior customer success manager, not the account rep. They aren't trying to sell; they are trying to diagnose. Is it a product issue? A training gap? Or has your champion left the company? Luna: Ah, the champion leaving is a classic one. That always throws the whole project into chaos. Lucas: It is the single biggest predictor of churn in mid-market deals. If your primary contact leaves, and the vendor hasn't built relationships with secondary stakeholders, you are vulnerable. That is why smart procurement teams now require 'key person continuity' clauses in their contracts. Luna: I haven't seen that very often. Does the vendor agree to that, or do they push back? Lucas: They usually push back initially, arguing that personnel changes are normal business operations. But if you frame it as risk mitigation for both parties, it becomes easier to negotiate. The idea is that the vendor must identify a replacement within ten business days who has equivalent authority and knowledge. Luna: That keeps the momentum going even when your own org structure shifts. It protects the implementation timeline. Lucas: Exactly. And another critical metric that buyers should demand visibility into is 'time to value.' How long does it take from contract signature to the first measurable ROI event? If that window is dragging out beyond ninety days, the likelihood of cancellation spikes dramatically. Luna: Because the excitement fades and the budget cycles start closing. People forget why they bought it in the first place. Lucas: Right. And during that fragile period, the vendor needs to be hyper-vigilant. We are seeing a trend where successful vendors assign dedicated onboarding specialists who are separate from the ongoing success team. Their sole job is to get you to that first win, then hand off to the relationship manager. Luna: Specialization seems key here. You don't want someone doing two jobs poorly. You need experts in each phase. Lucas: Agreed. And this specialization extends to the pricing models themselves. We talked about how pricing structures are breaking down, but one specific innovation is outcome-based pricing tiers. Instead of charging per seat, some vendors are starting to charge based on the number of deals closed or the volume of transactions processed. Luna: That aligns incentives perfectly. If I'm not growing, I'm not paying more. It reduces the fear of over-provisioning. Lucas: It does, but it introduces complexity for the vendor. Now they have to trust your data reporting. So you end up with audits and verification steps that weren't necessary in the old flat-rate model. Luna: So we trade simple billing for aligned outcomes, but gain audit overhead. Is that worth it for most companies? Lucas: For large enterprises, yes. The scale makes the efficiency gains significant. For smaller companies, the administrative burden might outweigh the benefits. It depends entirely on your maturity level. Luna: Maturity seems to be the recurring theme here. It's not just about buying software; it's about buying organizational capability. Lucas: Spot on. And that capability includes how you manage the vendor relationship internally. Too many companies silo their software purchases across different departments. Marketing buys one thing, Sales buys another, and IT buys a third, with no coordination. Luna: That creates shadow IT and duplicate spend. It also dilutes the negotiation power you could have as a unified buyer. Lucas: Exactly. The best procurement teams are centralizing their vendor management functions. They create a single source of truth for all software assets, tracking everything from license counts to renewal dates and performance metrics. Luna: Visibility gives you control. If you don't know what you have, you can't manage the risks associated with it. Lucas: Which brings us back to the initial point about predictive health. Centralized data allows procurement to see patterns across all vendors. If three different tools are showing low engagement in the same department, that is a signal of broader cultural resistance to digital transformation. Luna: So the software failure is actually a symptom of a larger organizational issue. The vendor can fix the tool, but they can't fix the culture. Lucas: Correct. And sophisticated vendors know this. They offer change management services precisely because they understand that technology alone rarely solves business problems. They are selling a transformation, not just a license. Luna: That raises the bar for everyone involved. Buyers need to be honest about their readiness, and sellers need to be honest about their capacity to guide that change. Lucas: Transparency is becoming the currency of enterprise sales. When you are looking at these complex contracts, ask yourself: who is accountable for my success? Is it a vague promise, or is it baked into the legal terms and the compensation structure? Luna: If you can't answer that clearly, maybe you shouldn't be signing yet. It's about due diligence, not just technical fit. Lucas: Absolutely. And as we move toward the end of the quarter, I think we will see more buyers leveraging this leverage to demand better retention guarantees. It is a fundamental shift in how B2B relationships are structured. Luna: From transactional to relational. It feels like the industry is finally maturing into that distinction. Lucas: It is, though the pace varies wildly by sector. Financial services and healthcare are leading the way, while retail and media are still catching up. Luna: Interesting divergence. I wonder if the slower sectors are just dealing with tighter margins or if it's purely cultural inertia. Lucas: Probably a mix of both. But the pressure is mounting. As AI integration becomes standard, the cost of poor adoption will become too high to ignore. Luna: Then maybe the market will force the issue. If the technology gets smarter, the expectation for human alignment must rise with it. Lucas: That seems like the inevitable trajectory. The question is whether organizations can adapt fast enough to keep up with the capabilities they are purchasing. Luna: A worthy challenge for any CTO or procurement leader sitting down with their next RFP. Lucas: Indeed. We will see how these dynamics play out in the coming quarters, especially with the upcoming fiscal year planning cycles. Luna: Keep an eye on those health score disclosures. They might tell you more about the vendor's future stability than their past revenue reports. Lucas: A sharp observation. Let's leave it there for now and see what the rest of the year brings.