Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise Software Buyers Now Demand a Vendor Exit Plan
Transcript
- Lucas: So you sign a three-year, seven-figure deal with a SaaS vendor. Year two, the vendor gets acquired, the product roadmap flips, and now you're stuck in software that no longer fits your business. What do you do? Luna: You sue them, or you eat the loss. That's basically the binary choice most companies have today. Lucas: Right, and that's exactly why procurement teams are starting to demand something that was almost unheard of five years ago: a vendor exit plan baked into the contract. Not just a termination clause — an actual playbook for how you get out. Luna: A playbook? Like, step-by-step instructions? Lucas: Exactly. I'm talking about a schedule that specifies data extraction formats, API uptime guarantees during the wind-down period, a non-disparagement clause, and even a 'knowledge transfer' window where the vendor has to train your team on migrating to a competitor. Luna: That sounds like a nightmare for the vendor. I mean, why would they agree to help you leave? Lucas: Because increasingly, buyers are walking away if they don't get it. I spoke with a procurement director at a mid-market manufacturing firm — let's call it Acme Parts — they were evaluating a new CRM platform. The vendor was a well-funded Series B company, trying to unseat Salesforce in the mid-market. The deal was worth about two and a half million over three years. Luna: So not trivial. Lucas: Not trivial at all. And the vendor's standard contract had a thirty-day termination clause — basically, you can cancel with thirty days' notice, but no obligation on the vendor's part to help you extract your data or transition. Acme's CIO said, 'If you can't document how we leave, we're not signing.' That stalled the deal for six months. Luna: Six months? That's a long time to hold up a seven-figure deal over an exit plan. Lucas: It is, but the CIO's logic was pretty sound. He said, 'We've been burned before. We had a logistics platform that got acquired by Oracle, and Oracle killed the product. We spent nine months extracting our data manually. We lost two quarters of shipping data.' So for him, the exit plan was non-negotiable. Luna: So what did the vendor finally agree to? Lucas: After a lot of back and forth, they settled on a ninety-day transition period. During that window, the vendor guaranteed API uptime at 99.5 percent, provided weekly data exports in CSV and JSON formats, and assigned two engineers to help Acme's team migrate. They also included a non-disparagement clause — both sides agreed not to badmouth each other during the transition. Luna: And the vendor didn't see that as giving away the store? Lucas: The CEO told me they actually used it as a competitive advantage. When they pitched against Salesforce, they would say, 'If you want to leave us, we'll help you pack your bags. Salesforce won't.' And that resonated with buyers who had been locked into Salesforce for years and felt trapped. Luna: That's a really smart counter-intuitive move. Make the exit plan a feature. Lucas: Exactly. And it's not just about CRM. We're seeing this across categories — HR platforms, analytics tools, even infrastructure software. The trend is being accelerated by the SEC's new cyber rules, which require companies to disclose material cybersecurity incidents within four days. If you have a breach and you need to migrate off a compromised vendor quickly, you can't afford a six-month extraction process. Luna: So the exit plan becomes part of your cyber resilience posture. Lucas: Exactly. I talked to a CISO at a financial services firm who said they now include a 'cyber exit clause' in every SaaS contract. If the vendor suffers a material breach, the buyer has the right to terminate within fourteen days, and the vendor must provide a complete data dump within five business days. Luna: That's a pretty tight timeline. Can most vendors actually deliver data that fast? Lucas: Most can't, which is why the clause is usually negotiated. The CISO said they rarely enforce the five-day deadline — they just want the right to demand it. It's a leverage point. If the vendor knows they might have to produce all your data in a week, they're incentivised to keep their infrastructure clean and their data export tools well-maintained. Luna: So it's more about hygiene than actual execution. Lucas: Right. But let's be honest — for early-stage SaaS companies, offering a robust exit plan is expensive. You need to build and maintain export APIs, document data schemas, train support engineers on migration handoffs. That's real engineering time. Luna: So what's the minimum viable exit plan for a startup? Lucas: I'd say three things. One: document your data model and provide a schema diagram. Two: build a self-serve data export tool that works even if the customer's subscription is cancelled. Three: define a reasonable transition period — sixty to ninety days — and commit to API stability during that time. You don't need dedicated migration engineers, but you do need a named point of contact. Luna: And what about the legal side? I've seen contracts where the exit plan is buried in a schedule that's 'subject to mutual agreement' — basically, the vendor can refuse. Lucas: That's a red flag. A real exit plan should be a binding schedule that outlines specific deliverables, timelines, and SLAs. 'Subject to mutual agreement' means the vendor can hold you hostage. I've also seen vendors try to limit the exit plan to 'commercially reasonable efforts' — that's too vague. You want concrete commitments: data format, frequency, response times. Luna: Any other deal-breakers to watch for? Lucas: One I've seen recently: vendors insisting that the exit plan only kicks in if the customer is 'current on all payments.' That sounds reasonable, but it's often used to deny exit assistance if there's a billing dispute. So buyers are now pushing for the exit plan to be unconditional — if you cancel, you get the data regardless of payment status, though the vendor can still pursue unpaid invoices separately. Luna: Makes sense. So who's leading the charge on this? Any industries or company sizes that are particularly aggressive? Lucas: Financial services and healthcare are the most aggressive, because they're heavily regulated. But the mid-market is catching up fast. I think the tipping point will come when a major enterprise vendor — say, Workday or ServiceNow — starts proactively offering a standardised exit plan as part of their standard terms. Once one of the giants does it, it becomes table stakes. Luna: Speaking of table stakes — I want to pivot for a second. You know, we do about seventy episodes of this show a year, and we keep it ad-free. That's only possible because a small group of listeners chips in through buy me a coffee dot com slash fexingo. If you find these conversations useful for what you're building or running, that's literally what keeps the lights on. Lucas: Yeah, and it's not about big donations — it's about the signal. Knowing that a handful of you value this enough to contribute. It lets us keep the episodes focused and honest, without any sponsor pressure. So if you're inclined, buy me a coffee dot com slash fexingo. And if not, no worries — the show stays free. Luna: Alright, back to exit plans. Lucas, you mentioned the mid-market catching up. Do you see this becoming a standard clause in all enterprise software contracts within the next two years? Lucas: I do. I think by 2028, any vendor that doesn't offer a reasonable exit plan will lose deals against competitors that do. It's already a differentiator for the smart ones. And for buyers, it's just good hygiene. You wouldn't buy a house without knowing how to sell it. Why sign a seven-figure software contract without knowing how to leave? Luna: So what's the one thing a procurement team should do right now if they're about to sign a big SaaS deal? Lucas: Ask the vendor: 'Show me your standard exit plan. If you don't have one, we need to write one together before we sign.' And if the vendor hesitates, that tells you everything you need to know about how they view the partnership — they see it as a lock-in, not a relationship. Luna: That's a good litmus test. Alright, thanks Lucas. And for our listeners, if you want to dig deeper, we'll link to some sample exit plan language in the show notes. Lucas: And if you've negotiated an exit plan that worked — or one that didn't — we'd love to hear about it. You can reach us at fexingo at gmail dot com. Thanks for listening.