Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise Software Contracts Now Include Outcome Guarantees
Transcript
- Lucas: If you're selling enterprise software today, you've probably heard a new demand from buyers: guarantee the outcome, not just the feature set. Luna: Right, outcome-based pricing. It's been talked about for years, but I'm seeing real contracts now with actual KPIs tied to revenue. Lucas: Exactly. I've been tracking this for a while, and one mid-market SaaS company I follow — let's call them DataSync Solutions — recently restructured their entire enterprise tier around it. They now tie twenty percent of the annual license fee to three specific outcomes: deployment time under forty-five days, ninety-percent user adoption by month six, and a thirty-percent reduction in manual data entry errors. Luna: That is specific. And risky for the vendor. If the software doesn't deliver, they literally leave money on the table. Lucas: Which is the whole point. Buyers are tired of paying for shelfware. Procurement teams have gotten much smarter about demanding value. And honestly, it aligns incentives. If my software is good, I should be happy to bet on it. If it's not, I shouldn't get paid the same. Luna: But this lengthens the sales cycle, right? I mean, negotiating those terms can't be quick. Lucas: It does. DataSync's average enterprise deal cycle went from about ninety days to around one hundred thirty. That's almost fifty percent longer. And that's after they standardized the outcomes. The first few deals took even longer because the legal team had to figure out how to measure and verify each KPI. Luna: So who defines what 'good' looks like? The vendor? The buyer? Both? Lucas: That's where value engineering teams come in. DataSync has a three-person value engineering group that works with the prospect's operations team to baseline current performance. Then they agree on targets. It's like a consulting engagement before the contract is signed. And that actually adds value for the buyer because they get a free diagnostic. Luna: But doesn't that also create a conflict? The vendor's value engineer is incentivized to set targets they can hit, not necessarily the most ambitious ones. Lucas: That's a real tension. DataSync addresses it by having the outcome metrics audited by a third party — a small analytics firm that specializes in SaaS adoption data. The buyer pays for the audit, but it's a fraction of the contract value. That keeps everyone honest. Luna: And if the vendor misses the target? What happens to that twenty percent? Lucas: It scales down. If they hit all three, they get the full twenty percent premium. If they miss one, they get ten. If they miss two or more, they get zero — and in some cases, the buyer gets a credit toward the following year. So the downside is real. Luna: That's a bold structure. I wonder how CFOs react to that. Most finance teams want predictable revenue, and this introduces variability. Lucas: I spoke with a CFO at a company that's been doing this for two years. She said the first year was nerve-wracking because they didn't know if they'd hit the targets. But after year one, they had enough data to price the outcomes accurately. Now she actually prefers it because it forces the sales team to sell only to accounts where the software is a good fit. It naturally filters out bad deals. Luna: So it's a quality filter for the pipeline. That's a hidden benefit. Lucas: Exactly. And it also changes how customer success operates. They're no longer just about renewals — they're about hitting specific adoption milestones. DataSync actually restructured their customer success team into pods aligned with those three KPIs. Each pod has a clear mission: deployment, adoption, or error reduction. Luna: That's smart. But it also means you need a product that can actually deliver those outcomes. If your software is buggy or hard to use, you're not going to sign those contracts. Lucas: Which is why this trend is forcing product teams to focus on what matters to buyers. At DataSync, the product roadmap is now heavily influenced by the outcome targets. Features that don't contribute to deployment speed or user adoption get deprioritized. It's a direct line from contract terms to engineering sprints. Luna: I've seen some larger vendors experiment with this too. Salesforce has a program called 'Success Guarantee' for their Marketing Cloud, and Workday has outcome-based components in some of their HCM deals. Lucas: Right, but they're usually more limited — maybe a ten percent at-risk component, not twenty. And they often tie to softer metrics like 'time to value' rather than hard numbers. DataSync's approach is more aggressive because they're a smaller company trying to differentiate. But I think we'll see the larger players move in this direction as procurement teams increasingly demand it. Luna: So what's the catch? Why isn't every vendor doing this? Lucas: A few reasons. First, it requires a level of product maturity and data infrastructure that many companies don't have. You need to be able to measure usage accurately, track it over time, and report it transparently. Second, it changes the revenue recognition model — accounting teams have to figure out how to recognize variable consideration. And third, it scares sales reps who are used to getting full commission upfront. DataSync had to redesign their comp plan so that reps get a base commission plus a bonus when outcomes are achieved. Luna: That's a big cultural shift. How did the sales team react? Lucas: Initially, resistance. The top performers who were closing deals easily didn't want to complicate things. But after a few quarters, the data showed that reps using the outcome-based model had higher customer satisfaction scores and lower churn. The deals that closed were stickier. So now some of the skeptics have become advocates. Luna: It also changes the relationship with procurement. Instead of adversarial negotiations over price, you're negotiating over metrics and measurement. Lucas: Exactly. And that's actually a more productive conversation. Procurement gets to feel like they're getting a guarantee, and the vendor gets to differentiate on value rather than price. One procurement director I talked to said she prefers outcome-based contracts because they give her a clear way to justify the investment to her CFO — she can point to a specific ROI target built into the contract. Luna: That's a powerful selling point. But what about vendors who can't offer this? Does it become a competitive disadvantage? Lucas: I think it will, over time. Especially in mature categories like CRM or HR software where buyers have options. If one vendor says 'we'll guarantee a twenty percent productivity improvement' and another says 'here's our feature list', the guaranteed one is more compelling. But it's not a given — some buyers prefer lower upfront costs and are willing to take the risk themselves. So there will be segmentation. Luna: So outcome-based pricing is not for everyone. But for companies that can execute it, it's a genuine competitive moat. Lucas: I think so. And it's still early. DataSync's approach is one data point, but I'm tracking a handful of other companies in vertical SaaS — construction, healthcare, logistics — that are building similar models. If this scales, it could fundamentally change how enterprise software is bought and sold. Luna: We don't run ads on these episodes. That's a deliberate choice — we want the content to be the only thing here. If you find these conversations useful for what you're building or running, you can support the show at buy me a coffee dot com slash fexingo. It's a simple way to keep this ad-free and focused on the signal. No pressure, just an option. Lucas: Yeah, we really believe in that. And we're grateful to everyone who has chipped in — it allows us to dig into topics like this without worrying about sponsor preferences. So thanks. Luna: Okay, back to outcomes. Lucas, you mentioned vertical SaaS — where do you see this catching on fastest? Lucas: I think construction tech is a natural fit. Projects have clear timelines and budgets. If your software helps a contractor finish a project two weeks early, that's a measurable outcome. Same with logistics — if a route optimization tool reduces fuel costs by a certain percentage, you can tie payment to that. These are industries where outcomes are already quantified in the buyer's operations. Luna: And the vendor has to have a way to capture that data. In construction, that might mean integrating with project management tools. In logistics, with fuel card systems. Lucas: Right. So the data integration layer becomes a key part of the product. Some vendors are actually building APIs specifically for outcome measurement. It's becoming a feature in itself. Luna: That's a significant investment. But if it locks in customers for multi-year deals, it could be worth it. Lucas: Exactly. And the renewals are stronger because the customer has seen the value. Churn drops. Expansion revenue goes up because once you prove you can deliver on one outcome, they want to add more. DataSync saw a forty percent increase in upsell revenue from customers on outcome-based contracts compared to their traditional ones. Luna: Forty percent? That's compelling. But I imagine not every outcome is easy to measure. What about something like 'improved employee satisfaction' from an HR tool? Lucas: That's harder. Some vendors are using proxy metrics — like survey response scores or retention rates. But it's less concrete than deployment time. I think the trend will start with the easiest to measure outcomes and then get more sophisticated as data analytics improves. Maybe we'll see ai driven outcome models that predict value and adjust pricing dynamically. Luna: That sounds like a future episode in itself. For now, it's clear that outcome-based pricing is more than a buzzword. It's changing contracts, compensation, and product strategy. Lucas: And it's forcing vendors to put their money where their mouth is. Which, ultimately, is good for buyers. If I'm a CIO, I'd rather have a contract that guarantees results than one that just lists features. Luna: Agreed. And I think we'll look back in five years and wonder why it took so long to get here. Lucas: Probably. But for now, it's a fascinating experiment playing out in real time. I'll keep tracking DataSync and the others, and we'll report back on how it evolves.