Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / How Enterprises Now Audit Vendor Security Roadmaps
Transcript
- Lucas: So Luna, we've spent the last twenty episodes talking about all the new things enterprise buyers are demanding from SaaS vendors. And today I want to zero in on a request that's quietly become a dealbreaker in 2026: the security roadmap. Luna: A security roadmap? You mean like, where they want to see your future security plans? That's not just a checkbox anymore? Lucas: Exactly. We're not talking about a SOC 2 report or a pen test from last quarter. Buyers are now asking: what are you doing to improve your security posture over the next eighteen to twenty-four months? And they want it in writing, with milestones. Luna: So they want a forward-looking document, not just a snapshot. That's a big shift from the old days of 'we take security seriously'. Lucas: Right. And the data backs it up. In a recent survey of enterprise procurement leaders, over sixty percent said they now require a security roadmap as part of the RFP process. That's up from about twenty percent just two years ago. Luna: Wow. So if you're a vendor and you don't have a roadmap ready, you're probably not getting to the demo stage. Lucas: Exactly. And it's not just about having a document. The roadmap needs to be credible. It needs to show that you understand the evolving threat landscape and that you have a plan to address it. Luna: So what does a credible security roadmap actually look like? Give me some specifics. Lucas: Well, the best ones I've seen are aligned to frameworks like NIST. They break down into three horizons: the next six months, twelve months, and eighteen to twenty-four months. Each horizon has concrete initiatives, like implementing zero-trust architecture, or achieving ISO 27001 certification, or rolling out hardware security keys for all employees. Luna: So it's not just a wish list. It's got milestones and owners. That makes sense. Lucas: And that's the key. A roadmap without ownership is just a slide deck. Buyers are now asking who's responsible for each initiative, what the success criteria are, and how they'll track progress. Luna: I can see why that would resonate. It shows you're not just checking boxes for the RFP, you're actually committed to improving. Lucas: And it's a way to differentiate. Some vendors are even productizing their security roadmap—turning it into a living document that they update quarterly and share with prospects and customers. Luna: That's a smart move. It builds trust before you've even signed the contract. Lucas: But here's the risk. If you put a roadmap out there and you don't deliver on it, that's a bigger problem than not having one at all. Buyers are checking. They might even ask for evidence of past roadmap achievements. Luna: So you need to be careful not to overpromise. But if you underpromise, you might lose the deal to someone who's more confident. Lucas: That's the tension. And I've seen vendors handle it well by being realistic and specific. For example, one company I spoke with said, 'We're aiming to reduce our average patch time from seven days to forty-eight hours by Q2 next year.' That's concrete and measurable. Luna: That's a great example. It shows you're thinking about operational security, not just compliance. Lucas: Exactly. And that's the kind of detail that resonates with enterprise buyers who have seen too many security theater presentations. Luna: So, for sales teams out there, what's the practical advice? How do you prepare for this question? Lucas: First, make sure you have a security roadmap document that's approved by your CISO or equivalent. It should be shared with sales, not hidden in the security team's files. Luna: And it should probably be tailored to the prospect's industry, right? A healthcare buyer wants to see hipaa related projects, while a financial services buyer cares about SOC 2 and maybe even FedRAMP. Lucas: Yes, customization matters. A generic roadmap is better than nothing, but you'll score points if you can show you've thought about their specific regulatory environment. Luna: Now, let's take a quick step back. We've been talking a lot about what buyers demand, but why is this happening now? What's driving it? Lucas: I think it's a combination of factors. The cyber insurance market has tightened significantly, so insurers are pushing companies to do more due diligence on their vendors. Also, there have been some high-profile supply chain attacks that made boards realize they can't just rely on their own security—they need to understand their vendors' plans. Luna: That makes sense. It's a risk management move, not just a compliance checkbox. Lucas: And that's why we're seeing it in RFPs more and more. It's a way to filter out vendors who aren't thinking long-term about security. Luna: So, what's the future? Is this going to become as standard as SOC 2? Lucas: I think so. In fact, I wouldn't be surprised if, in a few years, we see third-party audits of security roadmaps, kind of like SOC 2 but for future plans. Luna: Interesting. So, before we wrap up, I have to say, this kind of conversation is exactly why we keep this show ad-free. It's a niche topic, but it's so valuable for people building and selling B2B software. Lucas: Absolutely. And if you find value in these deep dives, you can support the show by buying us a coffee at buy me a coffee dot com slash fexingo. It keeps us going without ads, so we can keep digging into these procurement trends. Luna: Yeah, it's a small way to say thanks. But no pressure, we're just happy you're listening. Lucas: And we're back. So, thinking about the future, how do you see security roadmaps evolving? Will they become more standardized? Luna: I think they'll have to. Buyers don't want to compare apples to oranges. A standard format would make it easier to evaluate vendors side by side. Lucas: Maybe we'll see industry working groups develop a common framework, similar to what happened with SOC 2 and the AICPA. Luna: But until then, it's on each vendor to make their roadmap clear and compelling. And for now, the ones who do it well are going to win deals. Lucas: That's the bottom line. It's not just about having a roadmap—it's about having a credible, specific, and honest one. That's what separates the vendors who see security as a competitive advantage from those who see it as a burden. Luna: Well said. And that's a good note to end on. For our listeners, if you're a vendor, start working on your security roadmap today. You might not get asked for it, but if you are, you'll be glad you prepared. Lucas: And if you're a buyer, ask for it. You deserve to know what your vendors are planning. Until next time, keep building.