Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise RFPs Now Demand Incident Response Playbooks
Transcript
- Lucas: Something shifted in enterprise RFP rooms this year. Buyers are no longer satisfied with a vendor saying 'we take security seriously.' They want to see the actual incident response playbook. Luna: The playbook? The internal document that describes how you'd respond to a breach? Lucas: Exactly. And it's not just for financial services or defense. We're seeing this demand across healthcare, retail, even manufacturing. I spoke to a CISO at a Fortune 500 retailer last month who said they now require the playbook as part of the security review before they'll even schedule a demo. Luna: That's a big shift. So what changed? Lucas: The MOVEit breach in 2023 was a watershed moment. Hackers exploited a zero-day in Progress Software's managed file transfer tool, and it took days for the company to even acknowledge they had a problem. Customers were left in the dark. That kind of delay costs enterprises millions in operational downtime and reputational damage. Luna: So buyers realized they couldn't rely on a vendor's word anymore. They needed to see the plan. Lucas: Right. A SOC 2 Type II report tells you that controls exist, but it doesn't tell you how the team will actually react at 3 a.m. on a Saturday. Now procurement teams are asking: show us your playbook, and show us evidence of drills and tabletop exercises. Luna: But aren't those documents highly sensitive? Wouldn't sharing them expose a vendor to more risk? Lucas: That's where the negotiation gets interesting. Most vendors now share a sanitized version — redacted contact names and specific IP addresses — under a mutual NDA. It's a willingness to be transparent that builds trust. If these conversations about enterprise procurement are useful to you building or running a SaaS company, consider supporting the show. It's listener-supported at buy me a coffee dot com slash fexingo, and that's what keeps it ad-free. Luna: Yeah, a small way to help us keep digging into the details that matter. So what does a good playbook actually look like from a buyer's perspective? Lucas: Great question. A strong playbook typically includes four things: an incident classification system — severity levels with clear criteria; a communication plan that designates who talks to customers, who talks to regulators, who talks to the board; an escalation tree with actual names and backups; and predefined runbooks for common scenarios like a ransomware outbreak or a data leak. Luna: I read a report from Gartner that said by 2027, 60 percent of enterprise RFPs will include a request for the vendor's incident response playbook. Are you seeing that already? Lucas: Absolutely. We're tracking RFPs in our podcast network's audience — more than half of the deals over five million dollars now include this request. One SaaS vendor we work with has a 40-page playbook with specific runbooks for each incident type. They share a sanitized version with prospects, password-protected NDA. That's becoming table stakes. Luna: So buyers are essentially auditing your operational readiness before they commit. And it's about more than security — it's about business continuity. Lucas: Exactly. That's why we're also seeing clauses in contracts that tie SLAs to incident response timeframes: 'If you don't notify us within one hour of a confirmed incident, you pay a penalty.' The playbook is the proof that you can meet those SLAs. Luna: For early-stage SaaS companies, that's daunting. They might not have a polished playbook. What should they do? Lucas: Start with a template from a framework like NIST or SANS. Document your current process — even if it's rough. Then run a tabletop exercise with your team and iterate. Buyers don't expect perfection from a startup, but they do expect a thoughtful plan and a willingness to improve it over time. Luna: And if a vendor refuses to share anything at all, that's almost a dealbreaker now, right? Lucas: It's becoming one. I recently heard of a procurement team that walked away from a ten million dollar deal because the vendor wouldn't even discuss the playbook. The buyer's reasoning was simple: if you can't be transparent about how you'd handle a crisis, why should we trust you with our data? Luna: Makes sense. So the playbook is the new line item in the security appendix. Let's talk next about how vendors are using this as a competitive differentiator — we're seeing some put a summary in their public trust center. Lucas: That's smart. One company I know publishes a high-level incident response framework on their website: 'See how we respond.' It doesn't reveal secrets, but it shows they've thought it through. In a crowded market, that kind of transparency can close deals. Luna: It's also a signal to existing customers that you're ready. Are you seeing any pushback from vendors on this trend? Lucas: A little. Some legal teams worry about creating a litigation risk if they don't follow the playbook perfectly. But the market is moving fast. If you're a vendor, getting comfortable with this level of openness is now a competitive necessity. The cost of losing a deal to someone who does share the playbook is higher than the risk of sharing it. Luna: Alright, so the new must-have in enterprise procurement: a well-documented, practiced, and sharable incident response plan. Thanks Lucas, that was a great deep dive.