Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Enterprise Buyers Now Demand a Vendor Cyber Insurance Floor
Transcript
- Lucas: So I was on the phone last week with a CPO at a mid-market manufacturing company — about four thousand employees — and she told me something that stopped me cold. Luna: Okay, now I have to know. Lucas: She said her procurement team now automatically disqualifies any software vendor that can't show a cyber insurance policy with at least a five-million-dollar per-occurrence floor. No exception, no negotiation. Luna: Wait — a minimum insurance amount as a vendor gate? I've heard of requiring proof of cyber insurance, but a specific dollar floor? Lucas: Exactly. And she's not alone. I've now talked to three procurement leaders in the past month who've adopted the same rule. One at a financial services firm requires ten million per occurrence. The logic is straightforward: if a vendor suffers a breach that takes down the buyer's operations, the buyer wants to know there's a real payout pool behind the vendor, not just a token policy. Luna: But isn't cyber insurance already common? I thought most SaaS companies carry it as a matter of course. Lucas: Most do. But 'most' isn't 'all.' And the policies vary wildly. I looked at a data point from a 2025 survey by the Cyber Insurance Association — roughly 15 percent of SaaS companies with under fifty million in revenue either have no cyber insurance or carry a policy under two million. That's a non-trivial slice of the vendor pool that's suddenly un-hirable for large enterprises. Luna: So this is really a small-to-mid-size vendor problem, not a Salesforce or Workday issue. Lucas: Exactly. The big players already carry hundred million dollar towers. But the emerging vendor — the one with killer product but thirty employees — that's who gets caught. And here's the concrete case that made this real for me. Luna: I'm ready. Lucas: A B2B SaaS company I'll call 'DataFlow' — about two hundred million in ARR, so not tiny — had a deal with a Fortune 500 retailer. Procurement sends the standard insurance questionnaire. DataFlow's CFO signs off, saying they have a ten million dollar cyber policy. Two weeks later, the retailer's risk team does a deeper check and discovers the policy had lapsed for two weeks during a renewal gap. DataFlow's broker had missed the renewal date. Luna: Ouch. A gap of two weeks nearly killed a deal that size? Lucas: Nearly. The retailer put the deal on hold and demanded a signed affidavit from DataFlow's carrier confirming continuous coverage for the past twelve months, plus a rider that any future lapse would be reported within 48 hours. It took DataFlow's legal team three weeks to get that paperwork sorted. The deal closed, but the CEO told me it added six figures in legal and broker fees. Luna: And I bet the procurement template changed after that. So what exactly are buyers looking for in the policy language? Lucas: Three specific coverage areas. First, business interruption — if the vendor's systems go down, the policy needs to cover the buyer's lost revenue during the outage, not just the vendor's own losses. Second, data recovery, which includes forensic investigation, restoration, and notification costs. Third, third-party liability — that's the big one — covering damages the buyer incurs if the vendor's breach exposes the buyer's customers. Luna: So it's not just 'do you have insurance?' It's 'does your insurance actually protect me?' Lucas: Right. And the floor is just the starting point. Some buyers are now also requiring that the vendor's policy be 'primary and non-contributory' — meaning the vendor's insurance pays first before the buyer's policy kicks in. That's a huge shift. Historically, enterprise buyers would self-insure and treat vendor insurance as a backstop. Luna: I imagine that changes the premium calculation for a SaaS company. If you know a Fortune 500 buyer is going to demand primary coverage, your underwriter might charge more because the likelihood of a claim hitting your policy goes up. Lucas: Exactly. And the cyber insurance market has hardened significantly since the big ransomware wave of 2023 and 2024. Premiums for a five-million-dollar policy can run anywhere from fifty thousand to two hundred thousand dollars annually for a mid-size SaaS company, depending on their security posture. That's not nothing for a startup burning cash. Luna: Which raises the question: how is a bootstrapped SaaS company supposed to meet this requirement without blowing up their unit economics? Lucas: That's the tension. And honestly, the market is starting to adapt. A few specialized brokers have emerged — InsureTech Risk, CyberPlace — that focus exclusively on SaaS vendors. They bundle policies with lower premiums if the vendor demonstrates strong security controls like SOC 2 Type II, penetration testing, and incident response plans. One broker told me a company with robust controls can get a five-million-dollar policy for as low as thirty-five thousand a year. Luna: So it's becoming another dimension of the security maturity conversation. SOC 2 used to be the table stakes. Now it's SOC 2 plus a five-million-dollar insurance floor. Lucas: Right. And I think we're still early. I've seen procurement playbooks from two large financial institutions that are piloting a requirement for a ten million dollar floor, with a planned increase to twenty million by 2028. If that becomes standard, the insurance requirement becomes a real barrier to entry for small vendors. Luna: That would effectively shrink the addressable market for early-stage B2B SaaS. If you can't afford the insurance, you can't sell to large enterprises. Lucas: Which might actually be a good thing, in a way — it forces vendors to take security seriously from day one. But it also means procurement teams need to be thoughtful about not locking out innovative small vendors that just need a bit of runway to get their security program in place. Luna: Speaking of things that need support to keep going — I think we're talking about something that's genuinely useful for anyone building or running a B2B SaaS company. Lucas: Absolutely. And if today's episode helped you think about your own vendor stack or your own insurance posture, the way these stay ad-free and independent is listener support. People can find that at buy me a coffee dot com slash fexingo. Luna: Yeah, it's a small way to make sure we keep digging into the details that actually matter for operators. Appreciate anyone who chips in. Lucas: Alright — back to the insurance floor. One other development I'm watching: some buyers are now asking for the vendor's insurance carrier's financial strength rating. If your carrier is rated below A-minus by A.M. Best, they might reject the policy as insufficient. Luna: So it's not just the policy amount — it's the quality of the insurer behind it. That's a pretty sophisticated procurement requirement. Lucas: It is. And it's driven by a few high-profile cases where carriers became insolvent after a major cyber event. In 2024, a mid-tier carrier called CyberGuard collapsed after a wave of claims from a ransomware attack on a healthcare software vendor. Policyholders got pennies on the dollar. Luna: So buyers learned the hard way that a policy is only as good as the carrier's balance sheet. That's a lesson that's now baked into procurement templates. Lucas: Exactly. And I think we'll see this requirement trickle down to smaller buyers over the next two years. Right now, it's mostly Fortune 500 and regulated industries — finance, healthcare, energy. But as more mid-market companies adopt enterprise-grade procurement practices, they'll start asking the same questions. Luna: So what's your advice for a SaaS founder listening right now who's at, say, ten million in ARR and hasn't thought about cyber insurance? Lucas: First, don't wait until a deal requires it. Get a policy now, even if it's a smaller one. The underwriting process can take six to eight weeks, and you don't want to be scrambling when a buyer asks. Second, work with a broker who specializes in tech companies — they'll know what language enterprises expect. Third, bundle your insurance with a security audit; many carriers offer discounts for SOC 2 or ISO 27001 certified companies. Luna: And if you're a buyer, what's the one thing you should add to your procurement checklist besides the dollar floor? Lucas: Ask for the policy's sub-limits. Some policies have a five-million-dollar aggregate but only a one-million-dollar sub-limit for data recovery or notification costs. If the sub-limit is too low, the policy might not cover the actual expense of a breach. Also ask for a 'waiver of subrogation' — that means the vendor's insurer can't come after the buyer to recover costs. Luna: That's the kind of detail that separates a good procurement process from a checkbox exercise. I think we've covered a lot here — any final thought? Lucas: Just that insurance is becoming a proxy for trust. A vendor that can show a clean, well-structured policy with adequate limits sends a signal that they're run by people who think about risk. And in a world where breaches are inevitable, that signal matters more than ever. Luna: Well said. Thanks, Lucas. Lucas: Thanks, Luna. See everyone next time.