Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise Software Deals Now Include a Customer Health Score Mandate
Transcript
- Lucas: So there's a new clause creeping into enterprise software contracts that I think is going to reshape how vendors and buyers negotiate renewal terms. It's called a customer health score mandate. Luna: A health score mandate — meaning the buyer requires the vendor to report some kind of standardized health score, and then tie contract terms to it? Lucas: Exactly. And it's not just a nice to have KPI dashboard anymore. I'm seeing procurement teams insert language that says the vendor must calculate and share a health score — using agreed-upon metrics — and that score directly impacts renewal rights, discount tiers, even termination clauses. Luna: That feels like a power shift. Historically, the vendor's customer success team kept health scores internal, used them to prioritize accounts, maybe flag churn risk. Now the buyer wants that data on the table. Lucas: Right. And the catalyst is pretty clear. Over the past three years, enterprise buyers got burned by vendors who promised the moon during the sales cycle but then delivered mediocre onboarding, low adoption, and opaque renewals. So they're saying: prove it with data. Luna: Prove what, specifically? That we're actually using the software, that we're getting value? Lucas: Yes, but with more structure. The typical health score mandate I've seen defines three to five composite metrics. Usually: product usage depth — not just logins, but feature adoption; business outcome attainment — did you hit the KPIs from the joint business case; and support health — ticket volume, response times, satisfaction. Then there's often a fourth: community engagement or training completion. Luna: And the vendor has to report that quarterly, with a score out of 100, and then the contract says if the score stays above 80, renewal pricing is capped at a certain increase, but if it drops below 60, the buyer can renegotiate or even exit without penalty? Lucas: You've seen one. That's almost exactly the structure in a deal I reviewed last month — a mid-market CRM implementation, about 500 seats. The vendor was a well-known player, not a startup. The buyer's procurement team had a dedicated SaaS negotiator who brought this clause from a previous Fortune 500 deal. Luna: So it's spreading from the enterprise down to mid-market. That's significant. What was the vendor's reaction? Lucas: Initially, resistance. The vendor's argument was: health scores are proprietary, they're based on algorithms we've tuned over years, sharing them would expose our customer success methodology. But the buyer held firm. They said, 'If you can't measure our success, how do we know we're successful?' Ultimately, they compromised: the vendor would share a subset of the metrics — the objective ones, like usage stats and support response times — and keep the predictive model internal. Luna: I can see both sides. On one hand, transparency forces the vendor to actually deliver. On the other, if the health score becomes a contractual weapon, it could incentivize vendors to game the metrics — focus on what's measured, neglect what's not. Lucas: That's the risk. And it's already happening. I talked to a customer success leader at a SaaS company — they asked not to be named — who told me their team is now optimizing for the three metrics in the contract, even if it means deprioritizing other value levers that don't get scored. Luna: So the mandate might actually reduce overall customer value, not improve it. That's the classic Goodhart's Law problem. Lucas: Precisely. When a metric becomes a target, it ceases to be a good metric. And that's the tension I want to unpack today — whether these health score mandates genuinely align incentives or just create a new layer of compliance theatre. Luna: Before we go deeper — Lucas, this topic reminds me how much I value shows that cut through the hype and look at real contract dynamics. It's rare to find a podcast that digs into procurement clauses without a sales agenda. Lucas: I feel the same way. And honestly, if today's episode was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. It's the smallest way to keep this ad-free and focused on the real stuff. Luna: Yeah, listener support is what lets us spend hours on research like this. So seriously, if it's useful, that's the place. Lucas: Alright, back to the health score mandate. One of the more interesting design questions is: who defines the metrics? In the early contracts, it was the buyer dictating terms. But I'm now seeing collaborative scorecards where both sides negotiate the components. Luna: That seems healthier. But it also adds complexity to an already long procurement process. How many rounds does that negotiation add? Lucas: From what I've heard, two to three additional meetings, plus legal review. But buyers are willing to invest that time because the payoff is a contract that self-corrects. If adoption dips, the vendor gets an early warning and the buyer has leverage to demand a remediation plan, not just a renewal with a price hike. Luna: Let's talk about a concrete example. You mentioned the mid-market CRM deal. What was the outcome? Lucas: The deal closed, but with a 15% discount off list price — the buyer argued that since the vendor would be held accountable for health, the risk premium should be lower. The vendor also had to agree to a quarterly business review where the health score is presented to the buyer's executive sponsor. And the contract included a 'health trigger' — if the score dropped below 65 for two consecutive quarters, the buyer could terminate without cause. Luna: That's a serious exit clause. So the vendor essentially put skin in the game for ongoing value delivery. That's a big shift from the old model where the vendor got paid upfront and then hoped for renewals. Lucas: Exactly. And it's not just about renewals. Some of these mandates also tie pricing to the health score. For instance, if the score is above 90, the buyer gets a loyalty discount on expansion seats. If it's below 70, the vendor has to offer free onboarding or training to bring it up. Luna: So the health score becomes a dynamic pricing lever. That's clever — it aligns the vendor's financial incentive with customer outcomes. But it also requires a level of data sharing that many vendors are uncomfortable with. Lucas: That's the next frontier: data transparency. The health score mandate effectively forces the vendor to open up their product telemetry. Some vendors are pushing back by offering a third-party audit instead — a neutral party that assesses the health score using vendor data but doesn't share the raw data itself. Luna: Like a SOC 2 type report, but for customer health. That could be a compromise. But it adds cost and complexity. Lucas: It does. And that cost ultimately gets passed to the buyer. So there's a trade-off: more transparency, higher software costs. But buyers seem to be accepting that because the alternative — opaque renewals and potential vendor lock-in — is worse. Luna: I want to step back and ask: is this mandate actually reducing churn? Or is it just shifting the churn conversation earlier? Lucas: There's early data. I spoke with a procurement analyst who tracks SaaS contract terms across about 200 enterprises. She said that in deals with health score mandates, the average renewal rate over the first two years is about 92%, compared to 85% for deals without. But she cautioned that the sample is still small and self-selected — buyers who push for these clauses are probably more sophisticated and more likely to succeed anyway. Luna: So correlation, not necessarily causation. But it's promising. What about the impact on the vendor's side? Are they seeing better customer outcomes? Lucas: Mixed. Some vendors have used the mandate to build better customer success processes. They now have a contractual reason to get executive attention on struggling accounts. But others see it as a burden — they have to build dashboards, train sales teams, and sometimes expose weaknesses they'd rather hide. Luna: I imagine the mandate also affects the sales conversation itself. If the vendor knows the buyer will be tracking health post-sale, they might be more honest about what the software can actually deliver. Lucas: That's a great point. I've heard sales reps say that the health score clause actually helps them sell — because it signals that the vendor is confident enough to be measured. It becomes a trust signal, especially against competitors who refuse to include such terms. Luna: So it's a differentiator. That could accelerate adoption — vendors who offer health score mandates might win deals they otherwise would lose. Lucas: Exactly. And I think that's where we're headed. Within two to three years, a health score mandate could become as standard as a service-level agreement in enterprise SaaS contracts. It's already common in the largest deals — think seven-figure annual contract values — and it's trickling down. Luna: What about the smaller vendors? A startup with 50 employees might not have the resources to build a health score system and report quarterly. Are they being shut out? Lucas: That's a real concern. Some buyers are offering a grace period — smaller vendors get a year to implement the reporting before the clause kicks in. Others accept a simpler scorecard with just three metrics. But if a vendor truly can't provide any health data, they may lose the deal. It's becoming a table-stakes requirement. Luna: So the mandate is also a barrier to entry for new SaaS companies. They need to invest in customer success infrastructure earlier. Lucas: Right. And that changes the capital requirements for a SaaS startup. You can't just build great software and hire a sales team — you need a customer success engine, a data pipeline, and a legal framework to support these clauses. It's part of the maturation of the SaaS industry. Luna: I want to circle back to the gamification risk. If the health score is based on usage, couldn't a buyer just ask employees to log in more often to keep the score high, even if they're not getting value? Lucas: Absolutely. That's why sophisticated clauses include outcome-based metrics, not just activity metrics. For example, instead of just tracking login frequency, they track 'deal velocity' for a CRM or 'time to close' for a project management tool. The vendor has to demonstrate that the software is moving the needle on business outcomes, not just being clicked. Luna: Outcome metrics are harder to game, but also harder to measure and agree upon. That negotiation can get pretty philosophical — what counts as a business outcome? Lucas: Exactly. And that's why these contract negotiations are taking longer. But the buyers I've spoken to say it's worth it. They'd rather spend two extra weeks defining success than two years in a low-value relationship. Luna: Well said. So what's the one takeaway you want listeners to remember about health score mandates? Lucas: If you're buying enterprise software, ask for a health score clause. Start with a simple version: 'Vendor will provide a quarterly health report using, and if the score falls below, the buyer has the right to.' It's a small addition that can transform the vendor relationship from transactional to outcome-oriented. Luna: And if you're selling, embrace it. Use it as a trust signal. Build the infrastructure now, because it's coming to a deal near you. Lucas: Exactly. Thanks for digging into this with me, Luna. I think this is one of those quiet changes that will define the next decade of B2B SaaS. Luna: Agreed. And to our listeners, if this conversation saved you time or gave you an edge, you know where to find the coffee link. Lucas: Buy me a coffee dot com slash fexingo. Until next time.