Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise Software Reps Are Now Selling to the CISO
Transcript
- Lucas: There's a quiet power shift happening inside enterprise software deals. The person who can kill a seven-figure contract before it even gets to a demo is increasingly not the CFO — it's the CISO. Luna: The chief information security officer. I've seen that in a few deal post-mortems. But is this really new, or is it just security getting a seat at the table they've always wanted? Lucas: It's new in the sense that it's now structural. A Gartner survey from late 2025 found that 62 percent of enterprise software purchases above $250,000 now require a formal security review before a demo is even scheduled. Not before signature — before the first conversation with a sales rep. Luna: So security is gatekeeping the demo, not just the contract. That changes the whole sales motion. Lucas: Exactly. For years, the security review was a late-stage hurdle. You'd get verbal commitment from the VP of Sales, then legal would pass the contract to InfoSec, and they'd send a 200-question spreadsheet. The deal would stall or die there. Now that review happens before the rep ever gets a room with the economic buyer. Luna: What's driving that shift? Is it just more ransomware headlines, or is there something structural in how companies buy software? Lucas: I think it's a combination. The ransomware attacks on MGM and Caesars in 2023 were a wake-up call — those were casino operators, but the attack vector was a single compromised Okta tenant. Boards saw that a third-party SaaS tool could bring down the entire company. And then you have regulatory pressure: the SEC's new cybersecurity disclosure rules mean that a data breach from a vendor has to be reported publicly. That puts the CISO's job on the line. Luna: So the CISO now has a personal incentive to veto risky vendors. And a lot of them are using that leverage. Lucas: Right. And it's not just veto power — they're shaping the evaluation criteria. I spoke with a CISO at a mid-cap SaaS company last month — he told me that for any deal over $500,000, he now insists on a pre-demo security questionnaire. If the vendor can't answer basic questions about data residency, encryption at rest, and incident response SLAs within 48 hours, the demo is cancelled. Luna: That's a brutal timeline for a sales team. Most SaaS companies don't have a security person in the room during the sales cycle. Lucas: And that's the problem. The best enterprise reps are now recruiting a security champion inside the buyer org — someone who can vouch for the vendor's security posture before the formal review. It's a parallel to the executive sponsor, but this person is usually in the SOC, not the C-suite. Luna: I've seen that too. The security champion is often a senior engineer who's evaluated the product technically. They can answer the hard questions the CISO will ask. But they need to be cultivated early. Lucas: Cultivated is the right word. A common mistake I see is sales teams waiting until the security review is triggered — then they scramble to find someone at the vendor who knows the SOC 2 Type II report. By then, the buyer's CISO has already formed an impression. Luna: What about the vendor side? Are we seeing more SaaS companies hiring sales engineers who specialize in security? Lucas: Yes, and it's becoming a job title: Security Sales Engineer or sometimes Solutions Architect with a security focus. I've seen job postings at mid-stage startups specifically asking for someone who can handle a ciso led evaluation. They need to speak the language of zero trust architecture, SIEM integration, and API security. Luna: So the sales rep doesn't have to be a security expert, but they need a wingman who is. That's not unlike the technical co-seller trend we covered, but now it's specifically security. Lucas: Exactly. And it changes the demo itself. A typical demo might show the UI, the dashboard, the workflow. A security-conscious demo starts with a one-pager on architecture, data flow, and compliance certs. The CISO wants to see that the product is built on a secure foundation before they care about features. Luna: That's a complete reversal of the old sales playbook. For so long, the demo was about the 'wow' moment. Now the first impression might be a boring set of architecture diagrams. Lucas: And the best vendors are getting good at making those diagrams compelling. They frame security as a competitive advantage. I saw one pitch where the very first slide was a comparison of their SOC 2 Type II report against the industry average for time to patch critical vulnerabilities. That's a CISO talking to another CISO. Luna: What about smaller vendors who don't have the resources for a full-time security engineer? How do they survive this gatekeeping? Lucas: They have to be strategic. A lot of early-stage companies use a third-party security questionnaire platform like Vanta or Drata to automate the compliance evidence. That buys them credibility. But the real hack is to focus on a vertical where the security requirements are well-understood. If you sell to mid-market healthcare, you need HIPAA readiness. If you sell to defense, you need ITAR. Pick one vertical, nail the certification, and use that as a wedge. Luna: So it's not about having the best security — it's about having the right security for the buyer's industry. That makes sense. Lucas: And it's worth noting that this trend creates a new kind of buyer friction. We've talked about procurement defense budgets and legal teams getting involved. The CISO is now another layer of scrutiny. But I'd argue it's a healthy one — it forces vendors to build better products. Luna: Speaking of building better products — we try to do that here, too. One thing we're proud of is that these conversations stay free of sponsors and ads. If you find them useful for what you're building or running, the simplest way to keep that going is at buy me a coffee dot com slash fexingo. Lucas: Yeah, that's right. No paywall, no ad breaks. Just the two of us digging into a topic each week. If the show adds value to your work, that's the place to support it. Luna: Appreciate everyone who does. Alright — back to the CISO. I'm curious about the data. Are there any stats on how often a CISO actually vetoes a deal that the business wants? Lucas: There's a 2025 survey from Cloud Security Alliance that found 28 percent of organizations had a CISO veto a deal that the business sponsor had already approved. That's nearly one in three. And those are just the cases where the veto is formal — there are plenty of soft vetoes where the CISO just drags the review so long that the deal loses momentum. Luna: So the CISO doesn't even have to say no — they can just slow-walk the questionnaire. That's a harder problem for the sales team to solve. Lucas: Exactly. And the fix isn't sales technique — it's organizational alignment. The best companies now have a sales enablement function that creates a 'security playbook' for each deal size. For deals under $100K, a standard one-pager. For $100K to $500K, a shared repository of answers to common questions. Above $500K, a dedicated security engineer assigned to the deal. Luna: That's a big investment for a company that's only doing a few enterprise deals a year. But if the ACV is high enough, it pays for itself. Lucas: It does. And the ROI isn't just in closing deals — it's in accelerating them. A security review that takes two weeks instead of eight can be the difference between a Q2 close and a Q4 close. And in a tight capital market, cash flow timing matters. Luna: One last thought: what about the buyer's perspective? Are CISOs becoming too powerful? Could they start blocking innovative tools because they don't fit legacy security models? Lucas: That's a real risk. I've heard CISOs say they prefer vendors that use the same cloud provider as their own infrastructure because it simplifies compliance. That could lock out startups that use a different stack. But I think the market self-corrects — if a vendor brings enough business value, the CISO will find a way to get comfortable. The question for founders is: are you building the kind of product that makes a CISO want to say yes? Luna: And that's a question worth sitting with. Thanks, Lucas. Lucas: Thanks, Luna.