Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Enterprise Buyers Now Demand a Vendor Incident Response Plan
Transcript
- Lucas: So there's this moment in enterprise software sales that used to be rare, and is now becoming routine: the buyer's security team pulls out a twenty-page questionnaire, and question seven is always the same — 'Show us your incident response plan.' Luna: And if you can't produce it on the spot, you're out. Lucas: Exactly. I've been tracking this, and a mid-market SaaS vendor I know — let's call them DataNest — lost a twelve million dollar deal last quarter because their IR plan was a PDF from 2022 that literally still had the previous CISO's name on it. Luna: Oof. That's embarrassing, but also… it's becoming table stakes now. Lucas: It is. And look — if these deep dives into what actually kills enterprise deals are useful for what you're building or running, that's the whole point of this show. Luna: Totally. And if today's episode was worth a coffee to you, honestly, there's a link — buy me a coffee dot com slash fexingo. No pressure, just helps keep this thing ad-free. Lucas: Right. So back to DataNest. The buyer — a Fortune 500 logistics firm — gave them seventy-two hours to produce a current, testable incident response plan. DataNest couldn't do it. Not because they were incompetent, but because their IR plan was tied to their cloud provider's shared responsibility model, and they'd never documented their own piece. Luna: So the buyer walked. Lucas: Walked. And that's becoming the norm. I've now seen this clause in about sixty percent of enterprise SaaS contracts over a certain value — usually anything north of five hundred thousand dollars in annual recurring revenue. The buyer demands a written incident response plan that's been reviewed and pre-approved by their own security team. Luna: So it's not just 'do you have a plan?' — it's 'will our team sign off on your plan before we sign the deal?' Lucas: Exactly. And the plan has to include four specific elements. First, a notification timeline — usually within twenty-four hours of detection, sometimes as fast as four hours for critical incidents. Luna: That's tight. Especially for smaller vendors who might not have a 24/7 security operations center. Lucas: It's brutal. But the second element is an escalation chain — named individuals, with backups, and the buyer gets those names. So they know exactly who to call if something goes wrong at 2 a.m. on a Sunday. Luna: And the third? Lucas: A documented response procedure that's been tested within the past twelve months. Not just a plan on paper — evidence of a tabletop exercise or a live drill. The buyer wants to see that the vendor has actually practiced the response. Luna: So if you haven't run a simulation, you might as well not have a plan at all. Lucas: Right. And the fourth element is a post-incident root-cause analysis report, due within thirty days of the incident being closed. That report has to include what happened, what was done to contain it, and what permanent fixes are being put in place. Luna: That's actually smart from a buyer perspective — you're not just trusting the vendor to fix it; you're getting a written commitment to learn from it. Lucas: Exactly. And some buyers are going further. I've seen contracts that require the vendor to maintain a certain level of cyber insurance that explicitly covers incident response costs — like forensic investigation, legal counsel, notification expenses. Luna: Which, by the way, can run into the millions for a mid-size breach. Lucas: Absolutely. So the insurance requirement is basically a backstop. If the vendor's IR plan fails, the insurance covers the cost of making it right. But here's the thing — this is creating a real divide in the SaaS market. Luna: Between who? Lucas: Between vendors who own their infrastructure and those who are fully built on top of a platform like AWS or Azure. If you're a SaaS vendor and your entire product runs on a single cloud provider, your incident response plan is essentially that provider's incident response plan — which you don't control. Luna: So the buyer is asking you to guarantee something you can't actually guarantee. Lucas: Exactly. And that's causing some enterprise buyers to demand that the vendor have a multi-cloud architecture — or at least a documented fallback plan if their primary cloud provider goes down. Luna: So we're not just talking about security incidents now, we're talking about availability incidents too. Lucas: Right. The line is blurring. A ransomware attack that encrypts your data and a cloud provider outage that makes your app unavailable — from the buyer's perspective, both are 'incidents' that require a response. Luna: I was reading about a healthcare SaaS company that had to disclose a breach in 2025 — it turned out the breach was in their cloud provider's infrastructure, not their own code. But the buyer contract held the SaaS vendor responsible anyway. Lucas: That's the new reality. The vendor is on the hook for the entire stack, whether they control it or not. So smart vendors are now writing their IR plans to explicitly cover dependencies — they map out every third-party service they use and document what happens if that service is compromised. Luna: And that goes into the contract as an appendix, I assume? Lucas: Exactly. I've seen contracts where the vendor attaches a 'dependency incident response matrix' — a table that lists each third-party service, the potential failure scenarios, the notification mechanism, and the expected recovery time. Luna: That's a lot of work for a small SaaS company. Lucas: It is. But the alternative is losing deals. And here's the really interesting part — some buyers are now asking for the vendor's incident response plan to be tested jointly. They want to run a simulated incident with the vendor's team, to see how they actually respond. Luna: Like a fire drill. Lucas: Exactly. I talked to a CISO at a financial services firm who told me they ran a joint tabletop exercise with a potential vendor before signing the contract. The vendor's team froze during the simulation — they didn't know who to call, they didn't have a script for notifying customers. The deal almost fell through. Luna: So the vendor had to go back and rebuild their entire IR program just to close the deal. Lucas: They did. And it worked — they eventually signed, but it added three months to the sales cycle. That's a real cost. Luna: I wonder if we're going to see a standard emerge here — like a SOC 2 type certification specifically for incident response readiness. Lucas: There are already a few frameworks. The National Institute of Standards and Technology — NIST — has a pretty detailed incident response guide. Some vendors are getting certified against that. But the challenge is that enterprise buyers don't all use the same framework. Luna: So you could be certified against NIST, but a buyer who uses the ISO 27035 standard won't care. Lucas: Right. And that's why the contract clause is becoming the unifying mechanism. Instead of asking 'are you certified against X?', buyers are saying 'here's the specific plan we require — meet it or we walk.' Luna: And that's harder for vendors, because they have to customize their IR plan for every big deal. Lucas: It is. But I think the vendors who get ahead of this — who build a really solid, testable IR plan and treat it as a competitive differentiator — are going to close deals faster. Luna: So the takeaway for our listeners — especially the ones selling B2B SaaS — is that you need to treat your incident response plan like a product feature. It needs to be documented, tested, and ready to demo. Lucas: Exactly. Don't wait for the buyer's security team to ask. Have it ready. And if you're a buyer, add that question to your procurement checklist — ask for the incident response plan before you even schedule the first demo. Luna: Because by the time you need it, it's too late to ask. Lucas: Right. And that's the episode. See you next time.