Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise Deals Now Require a Security Review Before Procurement
Transcript
- Lucas: If these conversations are useful for what you're building or running, we want to keep them free—no ads, no sponsorships, no nonsense. Luna: Yeah. And that only works if the people who get value from them chip in. It's not a big thing—just a coffee. Lucas: Exactly. So if you're up for it, the link is buy me a coffee dot com slash fexingo. No pressure, just the option. Now, let's talk about why your enterprise deal just died in security review. Luna: Oh, that's a fresh wound for a lot of reps. I've been hearing more and more that security questionnaires are the new procurement gatekeeper. Lucas: Right. And it's not just a checkbox anymore. We're seeing deals worth seven figures get stuck in a security review loop for months. The average enterprise software deal now requires filling out a security questionnaire that can be 100 to 300 items long. And that's before procurement even sees the contract. Luna: So the rep isn't selling to just the IT buyer or the CFO anymore. They're selling to a security team that has veto power. Lucas: Exactly. And that security team doesn't care about ROI or feature lists. They care about encryption standards, data residency, audit logs, and vulnerability disclosure policies. I talked to a VP of sales at a data infrastructure company—let's call them 'DataStream'—who lost a $1.2 million deal because their SOC 2 Type II report was three months old. The buyer's security policy required a report issued within 90 days. Luna: Three months old and the deal dies? That's brutal. So how do reps even prepare for that? Lucas: Well, the smartest ones are becoming 'security-fluent.' They learn the basics of SOC 2, ISO 27001, and now even FedRAMP if they sell into government-adjacent industries. But more importantly, they're pre-positioning security materials before the buyer asks. Instead of waiting for the questionnaire, they attach a one-page security overview to the initial proposal. Luna: That's proactive. But what about the companies that don't have those certifications yet? A lot of early-stage B2B SaaS startups might only have a SOC 2 Type I, not Type II. Lucas: Yeah, that's a real gap. And what we're seeing is that buyers increasingly treat SOC 2 Type II as table stakes. If you only have Type I, you're basically saying 'we had a good day once.' But there are workarounds. Some vendors use a third-party security assessment like a HITRUST or a SIG Light questionnaire to bridge the trust gap. Others offer a shared-responsibility model document that clarifies what the vendor handles versus the customer. Luna: So the rep needs to know which framework the buyer's security team actually cares about. Because a healthcare company might require HITRUST, while a financial services firm might want ISO 27001 plus a penetration test report. Lucas: Precisely. And the best reps I've seen actually ask the security team — early in the cycle — 'What's your security requirements framework? Can you share your standard questionnaire upfront?' That way they can pre-fill it and have the technical team review it before it's formally submitted. Luna: That's smart because once it's submitted, any delay looks like a red flag. But let's talk about the role of value engineering here. How do VE teams help with security reviews? Lucas: Great question. Value engineering teams are increasingly getting pulled into security reviews, not just ROI discussions. They help translate technical security controls into business impact. For example, instead of just saying 'we have AES-256 encryption,' the VE team can say 'our encryption meets your regulatory requirements, which reduces your compliance audit burden by an estimated 200 hours a year.' That speaks the CFO's language while satisfying the security team. Luna: So they're bridging the gap between security speak and business speak. I love that. But what about the 'security-qualified lead' concept you mentioned earlier? Can you unpack that? Lucas: Sure. Just like we have a marketing-qualified lead and a sales-qualified lead, some vendors now have a 'security-qualified lead' stage. It means the deal has passed an initial security fit check. That might include checking that the vendor's data center region matches the buyer's data residency requirement, or that the vendor's uptime SLA meets the buyer's criticality threshold. It's a way to avoid wasting time on deals that will inevitably die in security review. Luna: That's a really practical filter. And it forces the sales team to collaborate with security early. So what's the biggest mistake reps make when faced with a security review? Lucas: The biggest mistake is treating it as a clerical task. They pass the questionnaire to a junior engineer or a solutions architect who fills it out in isolation. But the buyer's security team will compare the answers to the vendor's public documentation. If there's any inconsistency, trust is broken. Luna: Oh, that's a nightmare. So the rep needs to own the process and coordinate internally. Lucas: Exactly. The best practice is to have a security review playbook. That includes a cross-functional team: the rep, a security engineer, the product manager, and sometimes legal. They review the questionnaire together, assign ownership for each section, and check for consistency with the contract terms. One company I know — a cloud security startup — even runs mock security reviews with their own internal security team before they send anything to a prospect. Luna: That's like a fire drill for the deal. And it probably surfaces gaps in their own readiness. So what's the one concrete change you'd recommend for a SaaS company selling into enterprises? Lucas: I'd say: create a 'security one-pager' that sits alongside your product one-pager. Include your certifications, your data encryption standards, your uptime SLA, your data center regions, and your compliance frameworks. Distribute it to every rep. And train them on the top five security questions they'll face — things like 'Where is my data stored?' 'Do you support single sign-on?' 'What is your incident response time?' If a rep can't answer those off the top of their head, they're not ready to sell. Luna: That's a very concrete takeaway. And it shifts the mindset from 'security is a blocker' to 'security is a qualification criterion.' Lucas: Exactly. And I think we'll see more vendors hiring security-focused sales engineers specifically to handle this layer. It's already happening in cybersecurity, but I expect it to spread to general SaaS. Luna: So the question becomes: when does a vendor know they need a dedicated security sales role? Lucas: I'd say when more than 30 percent of your deals are getting stuck in security review for longer than four weeks. That's a signal that the friction is systemic, not just a few picky buyers. At that point, a specialist can reduce the cycle time by preemptively addressing concerns. Luna: That's a good rule of thumb. And it's also a sign that the market is maturing — security isn't just a feature, it's a pillar of the sales process. Lucas: Yeah, and I think we'll look back at this era as the time when security reviews became the new procurement gatekeeper — and the vendors that adapted fastest pulled ahead.