Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / How SaaS Vendors Handle Security Reviews
Transcript
- Lucas: The average enterprise software sale now takes four months longer than it did three years ago. And it is not because buyers have less money or because features are worse. The delay is almost entirely concentrated in the final thirty days, right before signature. We call that the security and legal review phase, but really it is just the procurement black hole wearing a different mask. Luna: Right, and it feels like every vendor thinks they can just throw a PDF at the buyer’s general counsel and expect them to wave goodbye. But GCs are under pressure too, so they just push back harder. Lucas: Exactly. The old playbook was to get the verbal yes, then hand over the SOC 2 Type II report during the legal review stage. You assume the buyer’s security team will glance at it, see the blue ribbon, and sign off. That worked when your target customer was a mid-market company with five hundred employees. Today, if you are selling into Fortune five hundred accounts, that approach guarantees a two-month stall. Luna: Because the security team at a large enterprise doesn't care about your certificate. They care about whether your incident response plan actually works when someone tries to breach your database on a Tuesday night. Lucas: Precisely. And here is the specific number that keeps me up at night: roughly forty percent of all stalled enterprise deals in Q three of this year were attributed to unresolved security questions rather than pricing or feature gaps. That is a massive opportunity cost for any vendor growing through new logo acquisition. Luna: So if we know security reviews are killing our close rates, why do so many SaaS companies still treat their security posture as an internal ops problem rather than a sales enablement tool? Lucas: Because it is deeply uncomfortable to expose your infrastructure to strangers before you have a signed contract. Vendors fear that a prospective buyer’s penetration test or detailed questionnaire might reveal a vulnerability they haven't patched yet. So they hide behind vague assurances until it is too late. Luna: But hiding creates distrust. If I am buying a platform that handles my client data, I want to know exactly what happens if things go wrong, not just read a marketing slide about zero-trust architecture. Lucas: That is where the concept of trust engineering comes in. Leading vendors are no longer waiting for the RFP to ask for security docs. They are building a public trust center that is accessible even before a demo is booked. This includes real-time status pages, past audit summaries, and clear data retention policies. Luna: I remember reading about a fintech startup that did something similar. They put their entire data flow diagram on their website. It was terrifyingly transparent, but it made procurement move twice as fast. Lucas: That is the key insight. Transparency reduces cognitive load for the buyer’s risk manager. When a vendor proactively answers the hard questions, it signals confidence. It tells the procurement team that there is nothing to hide. And that accelerates the internal approval chain significantly. Luna: But transparency cuts both ways. If you publish everything, you also give competitors a blueprint of your architecture. How do you balance openness with competitive advantage? Lucas: You do not publish source code or proprietary algorithms. You publish governance frameworks. You show how you manage access controls, how you encrypt data at rest and in transit, and who has administrative privileges. That level of detail satisfies auditors without giving away your secret sauce. Luna: So it is about demonstrating process maturity rather than technical novelty. Which makes sense, because enterprises buy reliability, not novelty. Lucas: Absolutely. And this brings us to the second major bottleneck: the indemnification clause. This is where deals die more often than any other legal term. Buyers demand unlimited liability for IP infringement or data breaches. Vendors refuse to sign anything above their annual contract value. Luna: It is a standoff. The buyer wants protection against catastrophic loss. The vendor knows that a single bug could wipe out their entire runway if they agree to uncapped damages. Lucas: And neither side moves. The deal sits in limbo for weeks while legal teams send back redlined documents that make no progress. We saw this play out repeatedly last quarter with several high-profile AI platforms trying to enter the healthcare sector. Luna: Healthcare is particularly strict because of HIPAA. But isn't this issue broader than just regulated industries? Almost every enterprise now has some kind of data sensitivity. Lucas: It is universal. The solution is not to capitulate to unlimited liability, nor is it to flatly refuse. It is to offer insurance-backed indemnification. Many mature SaaS vendors now carry cyber liability insurance that covers claims up to ten million dollars or more. Luna: So instead of betting their own equity on the line, they bet their policy limits. That shifts the risk profile dramatically for the buyer. Lucas: It does. And it allows the vendor to cap their exposure while still providing meaningful protection to the client. The trick is getting your sales reps to understand this nuance so they don't just say no to every indemnity request. Luna: Which means your revenue operations team needs to be involved in legal training. Salespeople usually hate talking about liability. They just want to sign the check. Lucas: They do. But treating legal terms as obstacles rather than tools is a strategic error. A well-negotiated indemnification clause can actually reassure a buyer that you take your responsibilities seriously. Luna: So let's talk about the actual workflow. Once a buyer starts asking these questions, how long should it realistically take to resolve them? Two weeks? A month? Lucas: If you have done your homework, two weeks. If you have to scramble for documents, two months. The difference is preparation. Vendors who win these deals have a dedicated trust and security liaison who responds to procurement queries within twenty-four hours. Luna: A dedicated liaison? That sounds expensive for a smaller SaaS company. Do you really need a full-time employee just to answer security questionnaires? Lucas: Not necessarily a full-time employee initially, but a dedicated function. Some founders handle it themselves until they hit a certain revenue threshold. After that point, the cost of lost deals far exceeds the salary of a security program manager. Luna: That is a fair calculation. The cost of delay is real money. Every week a deal stalls is revenue sitting on the table, compounding interest that you never collect. Lucas: Exactly. And there is another subtle factor: standardization. The best vendors provide their own master services agreement that aligns closely with industry standards. They do not force the buyer to use their own legal team's template, which is usually biased toward the seller. Luna: So you meet them halfway. You use a recognized framework, maybe something based on standard tech industry agreements, and you make minor edits rather than rewriting the whole thing from scratch. Lucas: Yes. It shows good faith. It signals that you respect their governance processes. And it drastically reduces the time their lawyers spend reviewing your contract. Time is money for everyone in that room. Luna: I think the biggest mistake vendors make is thinking security is a checkbox. It is not. It is a continuous relationship that starts before the first dollar changes hands. Lucas: It is a sales channel in itself. A strong security posture opens doors that a weaker one simply cannot reach. It is the gatekeeper to the largest budgets in the market. Luna: Before we dive deeper into the mechanics of setting up a trust center, I want to pause for a moment. If today was actually useful to you, the way these stay ad-free is listener support — buy me a coffee dot com slash fexingo. That is F. E. X. I. N. G. O. Lucas: Yeah, and if you find these insights valuable, consider joining us there. It helps keep the production quality high and the ads out. Luna: Thanks for listening. Now, back to those trust centers. What are the essential components? Lucas: Start with the basics. A live status page showing uptime and incident history. A downloadable security white paper that explains your encryption standards in plain English. And a clear contact method for security inquiries. Luna: Make sure the white paper is written by engineers, not marketers. Engineers speak the language of the people reviewing it. Lucas: Agreed. Avoid fluff. Use diagrams. Show the data lifecycle from ingestion to deletion. Visuals are processed much faster than text by busy executives. Luna: What about third-party integrations? Enterprises love to plug systems together, but that introduces risk vectors. Lucas: This is critical. You must disclose every integration point. If you connect to Salesforce or Slack, explain how you handle their tokens. Buyers need to know that a breach at one partner does not compromise your core system. Luna: So supply chain security is part of your story now. It is not just about your walls; it is about who lets you in. Lucas: Precisely. And you should list your own vendors. If you rely on AWS or Azure, mention that. It borrows their credibility while showing you are transparent about dependencies. Luna: That builds immense trust. It shows you are not hiding behind a cloud provider, but leveraging it responsibly. Lucas: Finally, update these materials quarterly. Stale security docs are worse than no docs. They signal neglect. Regular updates prove that your commitment to safety is active, not historical. Luna: Active commitment. That is the phrase I would steal. It changes the narrative from compliance to culture. Lucas: Culture wins deals. Compliance just clears hurdles. If you build a culture of security, the hurdles disappear. Luna: Do you think smaller SaaS companies can compete on this front without spending millions on audits? Lucas: They can. They just need to be honest about their stage. A seed-stage startup does not need a SOC 2 report yet. But they do need a clear, concise security statement that outlines their current safeguards. Luna: Honesty scales better than perfection. Buyers appreciate knowing where you stand rather than guessing. Lucas: Exactly. Set expectations early. Manage the review process tightly. And treat security as a feature, not a formality. Luna: It seems like the barrier to entry for enterprise sales is rising, but the reward for getting it right is higher than ever. Lucas: It is. The vendors who master trust engineering today will define the next decade of B2B software adoption. Luna: And those who ignore it will remain stuck in the mid-market, wondering why their pipeline keeps leaking at the finish line. Lucas: We will see. For now, focus on the details. The rest will follow.