Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / How SaaS Vendors Handle Procurement Friction
Transcript
- Lucas: So here is the thing about enterprise software sales in October twenty twenty six: we have stopped measuring success solely by how fast you close a deal, and started measuring it by how much pain you inflict on your own customers during the process. Luna: That sounds harsh, but I think you are right because the buyer has so many options now. Lucas: Exactly. And what hurts them is not just the price or the feature set, it is the sheer administrative weight of signing up. We are seeing average sales cycles stretch out by nearly thirty percent compared to last year, and a huge chunk of that delay happens after the handshake, once the procurement team gets involved. Luna: Right, so the real bottleneck is no longer finding the lead, it is clearing the legal and security hurdles. Lucas: Precisely. And before we dive into the specifics of those hurdles, I want to mention something quick. If these conversations about building efficient businesses help you in your daily work, consider supporting the show directly. Luna: Yeah, listener support is really what keeps this ad-free and allows us to keep digging into these topics. Lucas: If you want to chip in, you can find us at buy me a coffee dot com slash fexingo. It makes a huge difference for us. Luna: Thanks for that, and let's get back to why those contracts are taking so long to sign. Lucas: Let's talk about the Security Questionnaire, which has basically become the gatekeeper for every serious enterprise deal. Five years ago, a standard fifty question survey might take a vendor two days to fill out. Today, a comprehensive SOC two type two plus ISO one nine thousand sixty seven review requires hundreds of pages of evidence. Luna: I remember reading that some fintech vendors spend over four hundred hours just answering initial security requests. Lucas: That number feels about right for the higher end. And the problem is that this isn't just a compliance checkbox anymore. Buyers are using these questionnaires as a scoring mechanism to rank vendors against each other. If your answers are vague or delayed, you drop down the list, even if your product is technically superior. Luna: So it becomes a test of operational maturity rather than just technical capability. Lucas: It absolutely does. And this is where we see the biggest divergence between well-funded incumbents and agile startups. The big players have entire teams dedicated to responding to these RFPs and security forms. They treat procurement friction as a feature, not a bug. Luna: But startups don't have those resources, so how do they compete without slowing down? Lucas: They have to be ruthless about scope. I spoke with a founder last week who told me they now refuse to answer any security questions that aren't strictly necessary for the deal size. They use a tiered approach where small deals get a simplified self-assessment, while only large enterprise contracts trigger the full deep-dive audit. Luna: That seems like a smart way to protect their engineering time. Lucas: It is, but it also requires strong pricing discipline. You cannot offer a low-risk, low-friction path for small buyers if you are trying to push everyone toward an enterprise contract with heavy legal overhead. The structure has to match the customer segment. Luna: What about the legal side? I hear horror stories about redlining contracts for months. Lucas: Oh, the redlining process is brutal. We are seeing cases where simple indemnification clauses turn into weeks of back and forth between general counsels who rarely talk to each other. One recent study showed that legal negotiations account for nearly forty percent of the total time spent in the final stage of a B2B SaaS deal. Luna: Forty percent is staggering when you think about how much revenue is on the line. Lucas: It is. And the worst part is that most of this friction is artificial. Buyers often demand terms that their own internal policies don't actually require, just to make the lawyers happy. Vendors who push back early with clear, standard terms tend to win more trust than those who try to accommodate every single request. Luna: So standing your ground on standard terms can actually speed things up? Lucas: Often, yes. Because it signals confidence. When a vendor says, 'this is our standard, we will not negotiate unless it is a material risk,' the buyer's legal team often just accepts it because they know they won't save anything by fighting it. Luna: That makes sense. It shifts the dynamic from negotiation to verification. Lucas: Exactly. And this brings me to another point about integration. In twenty twenty six, buyers are less interested in flashy APIs and more interested in whether your tool fits cleanly into their existing identity management systems. Luna: Like SSO and SCIM provisioning? Lucas: Spot on. If you do not support Single Sign On out of the box, you are automatically flagged as a high-maintenance vendor. IT directors are tired of managing separate passwords and fragmented access logs. They view seamless integration as a baseline requirement, not a nice to have bonus. Luna: It really changes the conversation when you present your tech specs. Lucas: It does. I saw data from a major analyst firm indicating that deals lacking proper SSO integration are closing at half the rate of those that have it fully configured. That is a massive competitive advantage that costs very little to implement if you plan it early. Luna: So the technical debt of skipping integration now is paying off in lost deals later. Lucas: Always. And this connects back to the idea of procurement as a partnership. The best vendors treat the procurement phase as an extension of the sales relationship, not a hurdle to jump through. Luna: How do they do that without giving away too much leverage? Lucas: By being transparent about timelines upfront. A good vendor will say, 'our security review takes three weeks, and our legal team typically responds within forty eight hours.' Setting expectations reduces anxiety on both sides. Buyers know what to ask their bosses for, and sellers know how to manage their pipeline forecast. Luna: Predictability is probably the most valuable currency in a stalled deal. Lucas: It really is. And I think we are going to see more tools emerge specifically designed to automate these responses. There are platforms already helping vendors auto-fill security questionnaires based on past audit results. Luna: That sounds like a game changer for smaller teams who can't afford dedicated compliance staff. Lucas: It levels the playing field significantly. But even with automation, the human element remains critical. You still need someone who understands the nuance of why a buyer is asking a certain question. Luna: Because a canned response can sometimes raise more red flags than a thoughtful explanation. Lucas: Absolutely. Context matters. And this is where experienced sales operators add value. They know how to translate technical constraints into business language that procurement teams understand. Luna: So it is not just about filling forms, it is about storytelling throughout the process. Lucas: Precisely. And as we look at the rest of the quarter, I expect to see more companies treating procurement efficiency as a core KPI, alongside pure revenue numbers. Luna: That would be a welcome shift given how much time is wasted right now. Lucas: It will be. The companies that master this flow will likely pull away from the pack in terms of sustainable growth. Luna: I hope we see more focus on that metric in future earnings calls. Lucas: Me too. It is fascinating to watch how the definition of a successful sale is evolving beyond just the signature. Luna: Definitely. Thanks for breaking down such a messy part of the industry. Lucas: Anytime. Let's see if we can untangle a few more knots next week.