Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise RFPs Now Ask Vendors About Data Portability
Transcript
- Lucas: So there's a clause that's been showing up in enterprise RFPs lately that I think is worth drilling into, because it sounds boring but it's actually a weapon. It's the data portability requirement. Luna: Data portability. You mean like the right to take your data and leave? That's been around for a while, hasn't it? Lucas: Right, but the way it's being written now is different. It's no longer just a boilerplate line about 'vendor shall provide data upon request'. The new RFPs are specifying the format, the timeline, the API. They're asking for a data migration plan as part of the proposal. Luna: A migration plan? That's a big ask. That's almost like they're planning to fire you before you even start. Lucas: Exactly, and that's the mindset shift. Buyers aren't treating portability as a nice to have anymore. They're treating it as a risk mitigation tool. And I've got a concrete example. I was talking to a sales director at a mid-market SaaS company — they sell a project management tool, about five thousand employees using it. They lost a seven-figure deal because their export feature was literally a button that generated a messy CSV dump. Luna: Ouch. So the buyer walked because the data wasn't cleanly exportable. Lucas: They had a ten-page security appendix, but the portability section was one line. The buyer's procurement team actually tested it. They asked for a sample export of their own data during the pilot, and what they got back was a CSV with broken encoding and columns that didn't match the documentation. Luna: So they called it a dealbreaker. That seems harsh for a format issue, but I guess if you're a big enterprise, you're thinking about the next ten years. Lucas: And that's the thing. The buyer's logic was: if they can't export my data cleanly now, what's it going to be like in five years when I've got three terabytes in there? The cost of switching vendors is huge, and they want to know that they can leave at any time. It's like a prenup for enterprise software. Luna: So what does a modern portability clause actually look like? Is there a standard template or is it all over the place? Lucas: It's still evolving, but there are some common threads. First, they want the export to be in an open, machine-readable format. JSON is the gold standard. Some are even asking for a full database dump in SQL, which is a whole other level. Luna: SQL dump. That's a serious ask. That's like handing over the keys to the entire kingdom. Lucas: And they're also specifying the API. They want a documented, public API that lets them pull their own data in real time, not just a nightly batch file. And they're putting a response-time SLA on it. So if you don't deliver the export within, say, seventy-two hours, there's a financial penalty. Luna: Penalties. Wow. So the cost of not being portable just went up. Is this really a new thing though, or is it just GDPR being translated into procurement language? Lucas: That's a fair challenge. GDPR definitely put the right to data portability on the map. But this is B2B enterprise procurement, so it's not about consumer rights. It's about operational continuity. These buyers are thinking about their own data strategy, and they want to avoid vendor lock-in at all costs. Luna: So it's less about legal compliance, more about business leverage. That makes sense. But what if the vendor is actually good and you never want to leave? Does it still matter? Lucas: It matters because the buyer doesn't know that upfront. And honestly, a vendor that has good portability is usually a vendor that has good engineering. It means they've structured their data model in a sane way. So it's a signal of software quality, not just a contractual checkbox. Luna: I've heard from some sales teams that they're scared to put portability in the contract because they think it'll be used against them. Like, the buyer will just take the data and run. Lucas: And that's the old-school thinking. But in practice, the cost of switching is still high. Even with perfect export, you're going to have to retrain users, integrate with other tools, migrate historical data. So it's not like buyers are going to churn just because they can. Portability actually builds trust, and trust closes deals. Luna: So for a SaaS founder listening, what's the one thing they should do today to get ahead of this? Lucas: I'd say treat portability as a product feature, not a compliance obligation. Build an export tool that's actually good. Test it with real data, make sure the format is clean, document the API. And then put that front and center in your RFP response. It's a differentiator. Luna: And if you're a buyer, what's the key question to ask? Lucas: Ask to see a sample export of your own data. Not a demo with dummy data. Your actual data, in a sandbox, exported to a format you can open in a standard tool. If they hesitate, that's a red flag. Luna: That's a good concrete takeaway. So you're saying the RFP is becoming a test of the vendor's data architecture, not just their sales pitch. Lucas: Exactly. And actually, this connects to something we talk about a lot on this show. If you're building or running a B2B SaaS company, the way you handle data portability says a lot about how you think about your customers. It's an investment in trust. And if these conversations are useful for what you're building, you might consider supporting the show. It's what keeps us ad-free. You can do that at buy me a coffee dot com slash fexingo. No pressure, just if it's helped you. Luna: Yeah, we really appreciate that. And it does help us keep doing deep dives like this. Lucas: So, coming back to the portability clause – one more thing. We're seeing some buyers put a 'data deletion' requirement alongside it. They want to know that when you export the data, you also delete it from your servers. That's a whole other layer. Luna: So it's not just about getting your data out, it's about making sure the vendor can't keep a copy. That's a trust issue too. Lucas: Right. And that ties into the broader trend of buyers wanting more control throughout the lifecycle. The question for vendors is: are you ready for that level of scrutiny? Because the ones that are will win the deals. Luna: So if you're a sales leader, you might want to start talking to your engineering team about that export button. Lucas: And make sure it's not just a CSV dump. Because that seven-figure deal could be on the line.