Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise RFPs Now Ask About Vendor Incident Response Staffing
Transcript
- Lucas: So Luna, I was prepping for a conversation with a procurement lead at a financial services firm, and she told me about a deal that almost didn't close. A forty-million-dollar, three-year contract with a SaaS vendor, and it nearly fell apart over a single question in the RFP. Luna: Okay, I have to ask: what was the question? Lucas: It wasn't about data residency or AI governance or any of the things we've covered in recent episodes. It was this: 'How many people are on your incident response team, and what's their on-call rotation?' The vendor's answer was basically, 'We have a guy.' Luna: A guy. That's terrifying. And I'm guessing it didn't go over well. Lucas: It didn't. The buyer's security team flagged it as a material weakness in resilience. They'd had a recent incident with another vendor where response times were measured in hours, not minutes, and they weren't going to repeat that. The deal only closed after the vendor agreed to a documented staffing plan and a third-party audit of their response process. Luna: So this is becoming a standard part of enterprise RFPs now. We've talked a lot about technical controls, but this is about the human side of security operations. Why the shift? Lucas: Partly it's the post-SolarWinds mindset. That breach was a wake-up call about how dependent enterprises are on the resilience of their vendors. But more recently, I've seen a 2026 industry survey that says 68 percent of enterprises now require vendors to document their incident response staffing as part of the RFP process, up from 34 percent just three years ago. Luna: Sixty-eight percent is huge. And it makes sense—if your vendor goes down for a day, it's not just their problem, it's yours. You need to know they can actually respond. Lucas: Exactly. And the interesting thing is how detailed these questions have become. It's not just 'do you have an incident response plan?' It's 'who's the incident commander, what's the escalation path, and how do you handle the first fifteen minutes of a critical alert?' Luna: The first fifteen minutes—that's where the difference between a minor blip and a full-blown outage is made. I read a case study about a vendor who lost a deal because their on-call engineer was a single person, and that person had a wedding the week of the presentation. Lucas: Ouch. That's the kind of thing that's really hard to quantify in a security questionnaire, but it's exactly why these staffing questions are showing up. Buyers want to know that the response capability is robust enough to handle real life—holidays, sick days, the occasional wedding. Luna: And you know, it's not just about having a warm body on call. It's about the structure around it. I've seen RFPs that ask for the average response time, but also the median, and the worst-case scenario in the last twelve months. Lucas: Right, they're looking for outliers, not just averages. An average response time of fifteen minutes sounds great until you find out that half the time it's actually six hours, and the average is skewed by a few good weeks. Luna: So what should a SaaS vendor actually have in place to answer these convincingly? I'm thinking about smaller startups that might not have a full 24/7 SOC. Lucas: That's a fair question, and I think the answer is that you don't necessarily need a huge team, but you do need a documented, tested process. A lot of vendors are now designating an incident commander role even if it's part-time, and they're using third-party services to fill after-hours coverage. Luna: So it's about showing a structure that can scale, not just a promise that someone will pick up the phone. Lucas: Exactly. And one of the things that buyers are probing is how you handle the post-incident review. It's not enough to say 'we fixed the issue.' They want to know that you have a process for figuring out what went wrong, how you'll prevent it from happening again, and how you'll communicate that to customers. Luna: That's where the real learning happens. But it's also something that can be hard to prove in an RFP. How do you show that your post-incident reviews are actually effective? Lucas: Some vendors are starting to include anonymized case studies in their RFP responses. They'll say, 'Here's an incident from last year, here's what we did, here's the root cause, and here's the change we implemented.' It's a powerful way to demonstrate capability. Luna: That's smart. It also shows a level of transparency that can really set a vendor apart. I've heard from procurement folks that they love seeing that kind of concrete evidence. Lucas: And it's not just about the RFP—this kind of transparency builds trust throughout the relationship. I was talking to a CISO the other day, and she said she'd rather have a vendor who admits to a minor incident but showed a strong response, than one who claims perfect uptime with nothing to back it up. Luna: Before we go further—and I know we're in the middle of this—I've been thinking about how much of our own work here depends on listener support. It's genuinely what keeps this show going. If you've gotten something out of these episodes, a couple of dollars a month makes a real difference. Lucas: Yeah, it's true. We keep everything ad-free, and the only reason we can do that is because people who find value in the show chip in a little something. If you're one of them, you can find us at buy me a coffee dot com slash fexingo. Luna: Even just covering a coffee for us helps keep the lights on. But back to incident response—you were talking about how this is changing the vendor evaluation landscape. Lucas: Right. So what we're seeing is that incident response staffing is becoming a tier-one criterion in enterprise procurement. It used to be buried in the security appendix, now it's often a deciding factor between two otherwise similar vendors. I've even seen a few RFPs that include a scenario-based question: 'Describe how you would handle a critical vulnerability with an active exploit.' Luna: Wow, that's a whole different level. They're asking vendors to demonstrate their thinking, not just check a box. Lucas: And it's forcing vendors to be more deliberate about their staffing. I know of a mid-size SaaS company that completely reworked their on-call rotation after losing a deal to a larger competitor. They had two engineers covering weekends, and the buyer's security team saw that as a single point of failure. Luna: So it's not just about having enough people, it's about showing that you've thought through the failure modes of your own staffing model. Lucas: Exactly. And that's a good lesson for any vendor, regardless of size. You don't have to be a giant security operation, but you do need to demonstrate a methodology. Even a small team can document its escalation paths, its on-call schedule, and its incident review process. Luna: I also wonder how this is affecting the internal security teams at enterprises themselves. If they're asking these questions, they must be confident in their own incident response. Lucas: That's a great point. There's a kind of mirror effect. Enterprises are holding their vendors to a standard that they're also trying to meet internally. The same survey I mentioned earlier found that 61 percent of enterprises are increasing their own incident response staffing this year, partly because they want to lead by example. Luna: So it's a win-win in some ways. Better staffing on both sides, which ultimately means more resilience across the board. Lucas: And I think it's also changing the conversation during the sales cycle. Instead of just talking about features and pricing, vendors are now having real discussions about security operations with their buyers. It builds a more collaborative relationship from the start. Luna: That's a nice way to think about it. The RFP isn't just a hurdle to overcome, it's an opportunity to align on what matters. Lucas: Right. And for those vendors who aren't prepared for these questions, the message is clear: it's time to invest in your incident response team and make sure you can articulate your process. Because the buyers are definitely asking. Luna: And they're going to keep asking. I think we'll see even more scenario-based questions in the future, maybe even live simulations. Lucas: Actually, I've heard about a couple of enterprises that are experimenting with tabletop exercises as part of the vendor evaluation. They bring in the vendor's incident response lead and run through a hypothetical breach together. It's intense, but it's a powerful way to assess capability. Luna: Wow, that's taking it to the next level. I can imagine that a lot of vendors would be nervous about that, but it also gives them a chance to shine. Lucas: Exactly. And the ones who are confident in their processes are welcoming it. It's a differentiator. So, as we wrap up, I'd say the message for this episode is: if you're a vendor, start documenting your incident response staffing today, not when the RFP arrives. Luna: And if you're a buyer, ask the hard questions. The first fifteen minutes matter. Thanks for joining us, and we'll see you next time.