Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / How Enterprise Software Vendors Sell to Procurement
Transcript
- Lucas: Last week we talked about how enterprise buyers are ganging up on vendors. A lot of you wrote in saying, okay, I get that procurement is tougher now — but what do I actually do about it? So today I want to walk through a specific playbook. One that a cybersecurity vendor I'll call ShieldLayer used to cut their average enterprise close time by 23 percent. Luna: Twenty-three percent — that's significant. What was their approach? Lucas: They started by mapping out procurement's actual decision criteria. Not what the vendor thought mattered — security features, ease of use, reference calls — but what the sourcing team was literally scoring them on internally. Luna: So procurement has an internal scorecard? Lucas: Almost always. At large enterprises, procurement runs a weighted evaluation matrix. It typically covers four buckets: commercial terms — price, discount structure, payment terms. Contractual risk — indemnification, liability caps, data handling. Operational fit — implementation timeline, training requirements. And vendor viability — financial health, third-party audits, customer concentration. Luna: And vendors don't see that matrix before they submit their proposal. Lucas: Right. That's exactly the problem. ShieldLayer realised they were guessing at weights and missing the things procurement cared about most. So they changed their initial discovery call. Instead of just demoing the product to the technical buyer, they asked for a fifteen-minute conversation with sourcing before they ever sent a proposal. Luna: And procurement agreed to that? Lucas: Surprisingly, yes — because the ask was framed as 'help us make sure we submit a complete package so you don't have to chase us for missing items.' Procurement loves anything that reduces their own work. In that call, they learned that ShieldLayer's standard liability cap of one times annual fees was a non-starter. The enterprise had a hard policy of three times. So instead of negotiating that for weeks in legal review, ShieldLayer proactively offered three times upfront with a mutual limitation on consequential damages. Luna: That's smart. You remove a friction point before it becomes a delay. Lucas: Exactly. And the data backs it up. According to a 2025 survey by Revenue.io, the average enterprise deal that goes through more than two rounds of legal redlines takes 47 percent longer to close. ShieldLayer's preemptive positioning eliminated two full rounds of back and forth on their top ten deal-killer clauses. Luna: Let's talk about the security questionnaire piece. That's a huge time sink for vendors. Lucas: It's the single biggest bottleneck in deals over one million dollars in annual contract value. A typical enterprise sends a vendor security questionnaire of two hundred to three hundred questions. ShieldLayer used to treat it as a compliance task — the security team fills it out, sends it back, done. But procurement was scoring them on response time. If it took more than five business days, they lost points. Luna: So they started pre-populating answers for the most common frameworks — SOC 2, ISO 27001, FedRAMP — and created a portal where procurement could see status in real time. Lucas: Exactly. They reduced average response time from twelve days to three. That alone moved them from the second tier of vendors to the first tier in procurement's evaluation. And here's the thing — the technical buyer on the business side barely noticed the change. But the sourcing manager noticed immediately. And in enterprise sales, the sourcing manager often controls the timeline. Luna: So the lesson is: don't just sell to the champion. Sell to procurement's process. Lucas: Right. And that means understanding procurement's internal incentives. A sourcing manager is evaluated on how many deals they close within their standard terms, how quickly they process each vendor, and how many exceptions they grant. Every exception adds work. So the vendor who shows up with fewer exceptions — even if their price is slightly higher — is easier to push through. Luna: That's a counterintuitive point. Most vendors think price is the main lever. Lucas: And in many cases, it's not. A 2024 study from Gartner found that for deals over five hundred thousand dollars, contract complexity was a stronger predictor of deal velocity than discount depth. Vendors who offered a 10 percent discount but required seven special terms actually closed slower than vendors who offered no discount but used a completely standard contract. Luna: That's wild. So the playbook is: standardise everything you can before you engage procurement. Lucas: And only deviate when you understand which deviations matter to this specific buyer. One more thing ShieldLayer did that I think is worth mentioning — they created what they called the 'deal readiness checklist.' Before any proposal went out, a deal desk analyst verified that ten items were complete: pricing within published bands, liability cap within policy, data processing agreement attached, security questionnaire pre-filled, implementation timeline with named resources, and so on. Luna: That's a simple operational fix, but I bet most vendors don't have it. Lucas: Most don't. And the ones that do see measurable improvement. ShieldLayer's 23 percent close time reduction wasn't from one magic change — it was from a dozen small ones that each removed a day or two of friction. The pre-meeting with procurement saved about a week. The pre-filled security questionnaire saved another. The proactive liability cap saved three weeks of legal negotiation. It adds up. Luna: If today was actually useful to you — especially if you're on a revenue team or running deal desk — the way these episodes stay ad-free is listener support. You can find us at buy me a coffee dot com slash fexingo. Lucas: Yeah, we keep the show independent because of folks who chip in. Appreciate it. So where do you see vendors still falling short? The security questionnaire piece seems obvious in hindsight, but I know a lot of companies still treat it reactively. Luna: I think the biggest miss is not having a dedicated procurement liaison. Most vendors have a sales engineer for the technical buyer, an account executive for the economic buyer, but nobody whose sole job is to manage the procurement relationship. ShieldLayer actually created that role — they called it 'deal operations partner.' Lucas: And that person's job was to track each procurement gate, flag upcoming deadlines, and preemptively address questions before they became blockers. It's a low-cost role — usually a mid-level ops person — but it had a huge ROI. In their first year, they reduced the number of deals that stalled in legal review by over 40 percent. Luna: Forty percent fewer stalls. That's the kind of metric that gets a CFO's attention. Lucas: Exactly. Because stalled deals tie up sales capacity, extend the forecast horizon, and increase the risk of the deal going cold. Every week a deal is in legal review, the win rate drops by about 5 percent. That's from a study by Salesforce's deal desk team published last year. Luna: So if you can cut that review time, you're not just closing faster — you're closing more deals overall. Lucas: Right. The funnel math is compelling. Let's say you close 100 deals a year at one million dollars each. If you can increase your win rate by even 5 percent by reducing legal stalls, that's an extra five million dollars in revenue. And the cost of adding a deal operations partner is maybe 150,000 fully loaded. Luna: That's a 33x return. Not bad for one role. Lucas: And that's before you count the compound effect on forecast accuracy, sales morale, and customer reference ability. I think the broader takeaway is that procurement is not an obstacle to be overcome — it's a process to be navigated. The vendors that treat it as a design problem, not a negotiation problem, are the ones that win. Luna: And that starts with understanding that procurement has its own scorecard, its own incentives, and its own timeline. If you don't align with that, you're fighting the process instead of working with it. Lucas: Exactly. Next time, I want to look at the flip side: what happens when vendors start using procurement's own tactics against them. There's a trend of vendors building 'deal rooms' that mirror the buyer's evaluation matrix. Luna: I've heard about that — it's like turning the procurement process into a collaborative workspace instead of a document exchange. Lucas: We'll dig into that next week. For now, if you're working on an enterprise deal this week, look at your own contract terms. Pick the three clauses that have caused the most redlines in your last five deals. See if you can preemptively align them with what your top ten accounts typically demand. It might save you a month.