Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise RFPs Now Demand Vendor Escrow Agreements
Transcript
- Lucas: So there's a clause that's been quietly sneaking into enterprise software contracts for the last couple of years, and I think it's about to become as standard as a data processing agreement. I'm talking about vendor escrow agreements. Luna: You mean like source code escrow? That's been around forever though, right? I thought that was more of a legacy software thing. Lucas: Right, classic source code escrow is old school — think bank vaults and physical tapes back in the mainframe days. But what's happening now is different. Enterprises are starting to ask for escrow not just for source code, but for data, configurations, even AI model weights and training data. And it's showing up in RFPs at a rate I haven't seen before. Luna: Interesting. What's driving that shift? I mean, SaaS vendors don't exactly love handing over their crown jewels. Lucas: A big part of it is the fear of vendor failure. There have been some high-profile collapses in the last few years — remember that mid-market CRM vendor that shut down in 2024? They had thousands of customers, and when they went under, those customers couldn't get their data out. The vendor's servers just went dark. That really spooked procurement teams. Luna: Yeah, I remember that. It was a nightmare. Some of those companies had years of customer data and sales history locked in that platform. They had to scramble to rebuild from scratch. Lucas: Exactly. And that's the classic use case for escrow — it's a safety net if the vendor goes bust or, you know, just decides to stop supporting the product. But the modern twist is that now the escrow might cover not just the code, but the entire runtime environment, the data schema, even the AI models that the vendor has custom-trained for you. Luna: So what does a typical escrow agreement actually look like in 2026? Is it still a third party holding a deposit box? Lucas: The core structure is similar, but the contents have changed. You've got a neutral escrow agent, like Iron Mountain or NCC Group, holding the deposit. The vendor regularly deposits updates — source code, build scripts, documentation, sometimes a full virtual machine image. The key is the release conditions: when can the customer access that deposit? Luna: And typically that's tied to bankruptcy or failure to provide support, right? Lucas: Right, the classic triggers are insolvency, cessation of business, or a material breach of the support agreement. But now enterprises are pushing for more subjective triggers, like 'if the vendor fails to meet a critical patch deadline' or 'if they're acquired by a competitor and the product is sunset.' Luna: That acquisition one is interesting. A lot of vendors get bought, and the new parent decides to kill the product line. Escrow would help customers keep access to what they've been paying for. Lucas: Precisely. And that's why we're seeing more RFPs include escrow as a mandatory question. I read a recent procurement survey — I think it was from the end of last year — that said nearly 40 percent of enterprise RFPs for SaaS now include a section on escrow, up from maybe 15 percent pre-pandemic. Luna: Wow, that's a big jump. But I bet a lot of vendors don't even know how to respond. What's the typical pushback? Lucas: The biggest pushback is cost and complexity. Setting up a proper escrow arrangement with a reputable agent isn't cheap — it can run tens of thousands of dollars a year, depending on the size of the deposit. And for a small SaaS vendor, that's a significant margin hit. Plus, they're worried about intellectual property leakage — handing over source code to a third party, even under NDA, feels risky. Luna: So how do vendors walk that tightrope? I mean, they need to win deals, but they also don't want to give away the farm. Lucas: The smart ones are offering tiered escrow options. For a lower tier, you might only deposit the source code and schema, no build scripts or data migration tools. For a higher tier, you include the full deployment images and a verification process where the escrow agent actually tests that the code can be restored and run in a test environment. That's something we're seeing a lot more of — verification as a differentiator. Luna: Verification sounds key. Because if you never test the escrow, how do you know it works? There's a term for that, isn't there — like a 'dry run' or something? Lucas: Exactly, escrow verification, sometimes called a 'verification release' or 'test deposit.' The escrow agent takes the deposit and tries to build the software or spin up the VM in a sandbox. If it fails, the vendor has to fix their deposit. But here's the catch — verification adds cost, and not every vendor wants to pay for it. So it becomes a differentiator in the RFP process. Luna: So a vendor that offers verified escrow is basically saying, 'we're so confident in our continuity plan that we'll prove it works.' That's a strong signal for an enterprise buyer. Lucas: It is. And it ties into a broader trend we've been covering — enterprises are demanding more proof of viability, whether that's financial stability or operational resilience. Escrow is another tool in that toolbox. Luna: Let's talk about the AI angle. You mentioned model weights and training data. How does that work in practice? Lucas: So imagine you've contracted with a vendor to build a custom AI model for fraud detection, and they've trained it on your data. If that vendor goes under, you lose not just the code, but the model itself — which could be your competitive advantage. So enterprises are now asking for the model weights, the training pipeline, even the hyperparameters to be placed in escrow. Luna: That feels like a much harder thing to escrow than regular source code. I mean, models are complex, they require specific hardware to run, and they might depend on external APIs. Lucas: Exactly, and that's the frontier. A lot of vendors are pushing back on AI escrow, saying it's technically infeasible or that the models are proprietary. But some creative solutions are emerging. For example, some escrow agents now offer 'model escrow' where they hold a snapshot of the model and the training environment, and they verify it can be loaded and makes predictions on test data — not necessarily run a full production service. It's a compromise. Luna: So it's more about ensuring you have the assets to rebuild, rather than a turnkey replacement. Lucas: Right, that's the realistic expectation. An escrow agreement isn't a guarantee of uninterrupted service — it's a guarantee that you, the customer, can get the keys to the kingdom if the vendor goes away. And then you have to figure out how to use those keys, whether that's self-hosting or hiring a third party to maintain it. Luna: Speaking of keys, who actually holds the keys in these agreements? The escrow agent, obviously, but how do they stay neutral? I've seen cases where the agent is more aligned with the vendor. Lucas: That's a real concern. The escrow agent is typically appointed by the vendor, and they pay the agent's fees. So there's an inherent conflict of interest. That's why more enterprises are now asking to co-manage the escrow, or at least have a say in choosing the agent. Some procurement teams are even insisting on using their own preferred escrow provider, to level the playing field. Luna: That's a smart move. And I bet the vendor's willingness to accept that is a signal of how confident they are in their own stability. Lucas: It is. And that's the thing — the escrow clause is becoming a proxy for trust. If a vendor pushes back too hard on escrow, it raises red flags. They might be hiding something — like they're on the verge of bankruptcy and can't afford the escrow fees, or they're planning to pivot away from the product line. Luna: So for vendors listening, what's the practical advice? How should they approach this in their next RFP? Lucas: First, don't dismiss it. Treat escrow as a standard part of your offering, especially for enterprise deals. Second, be transparent about what you can and can't escrow. If you can't escrow your AI model, say so upfront, and offer an alternative, like a data export and model documentation package. Third, consider getting a standard escrow agreement pre-negotiated with a reputable agent, so you can respond quickly to RFP questions without a legal battle. Luna: And for buyers, what should they watch out for? Lucas: Don't just check the box. Make sure the escrow deposit includes everything you'd need to recover, not just the source code. You want data schemas, migration tools, API documentation, and any custom configurations. And push for verification — without it, the escrow is just a false sense of security. Also, review the release conditions carefully. They should align with your business continuity triggers, not just the vendor's legal definitions. Luna: And I guess it's worth saying that escrow isn't just for startups or small vendors. Even big tech companies can have product line discontinuations or divestitures. Lucas: Absolutely. We've seen major vendors kill off products after an acquisition, leaving customers high and dry. Escrow is a safety net for any software dependency, regardless of vendor size. It's the kind of thing you hope you never need, but when you need it, you really need it. Luna: That's a good point. And honestly, the fact that we're talking about this on a show about enterprise software shows how much procurement thinking has evolved. It's not just about features and price anymore — it's about resilience and exit strategies. Lucas: Yeah, and that's a healthy shift. But look, we're able to dig into these nuances because of our listeners — a small group of you already chip in monthly via buy me a coffee dot com slash fexingo, and that support literally funds making all of these deep dives. It keeps the show independent and ad-free, which is how we want it to stay. Luna: That's right, and we're grateful for every one of you. It lets us spend the time on the details that matter. Lucas: But back to escrow — I think the next frontier is going to be escrow for AI agents. You know, autonomous agents that are acting on behalf of a business. If that agent goes away, you don't just lose code, you lose a business process. I wouldn't be surprised if we see 'agent escrow' in RFPs within the next two years. Luna: That's a wild thought, and probably a little scary. But I can see it coming. For now, I'd say the takeaway is this: if you're a buyer, make sure escrow is on your checklist. If you're a vendor, make it a selling point, not a burden. Lucas: Well said. Escrow might not be the most exciting topic, but it's one of those quiet clauses that can save your business when things go wrong. And in the world of enterprise software, that's worth paying attention to.