Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / How Enterprise Software Reps Sell Through Procurement Gatekeepers
Transcript
- Lucas: If these conversations are useful for what you're building or running — let's start with a wall that every enterprise SaaS rep hits: the procurement gatekeeper. Luna: You mean the person who sits between you and the budget, right? The one who seems to exist only to ask for discounts and delay signatures. Lucas: Exactly. But here's the thing — the best reps I've seen don't treat procurement as an obstacle. They treat it as a stakeholder they need to sell to, with their own priorities. Procurement's mandate isn't 'save money at any cost.' It's 'get the best value with the least risk.' Luna: So the classic adversarial relationship — me vs. procurement — is actually a failure to understand their job. Lucas: Right. And there are three specific moves I've seen work consistently. First, build a procurement-specific business case. Not the business case you gave the VP — that's about ROI and outcomes. Procurement needs a procurement business case: total cost of ownership, implementation timeline, termination clauses, data migration costs. Luna: So you're almost writing two different documents for the same deal. Lucas: Exactly. Second move: get legal involved early — on your side. Procurement often escalates to legal for data privacy and indemnification. If you've already aligned with your own legal team on standard terms, you can answer those questions in hours, not weeks. Luna: And the third move? Lucas: The vendor security questionnaire. This is the one that kills deals silently. Procurement sends a 200-question spreadsheet about your SOC 2, your encryption, your subprocessors. If you don't have those answers ready — or if you hand them a generic PDF — you're signaling that you're not enterprise-ready. Luna: It's almost like procurement is running a mini-audit before they even let you near the decision-maker. Lucas: And that's actually a good frame. If you pass that audit, you've proven you can handle the scrutiny. One data point: we looked at our own pipeline at a previous company — deals where the rep sent a tailored security package within 48 hours closed 30% faster than ones where it took a week. Luna: Thirty percent — that's huge. But I want to push back a little. For a startup with a five-person sales team, building all these artifacts for every deal — a procurement business case, legal playbook, security package — that's a lot of overhead. Does it scale? Lucas: It doesn't scale if you build them per-deal. But if you build them once as templates and customize only the pricing page, it scales fine. The procurement business case is 80% boilerplate: implementation timeline, standard SLAs, data processing location. You fill in the price and the term length. Luna: And for security? SOC 2 Type II is table stakes now. If you don't have it, procurement won't even start the conversation. Lucas: Exactly. So the real question for a startup is: are you ready for enterprise procurement? If you're not, focus on mid-market first. But if you are, invest in those templates upfront. It's a one-time cost per deal that pays for itself in deal velocity. Luna: I want to bring up something else — the human side. Procurement officers are people too. They get pressure from their own bosses to show they negotiated something. If you come in with your best price and say 'take it or leave it,' they have no win to report. But if you give them a range — say, 'list price is $100K, but if you sign by month-end, I can do $90K' — they get to show they saved $10K. Lucas: That's the fourth move, honestly. Give them a structured concession — one they can take credit for. It's not about giving away margin; it's about engineering a win for their internal narrative. And it works. I've seen procurement teams champion a deal internally because they got a 'special' discount. Luna: So to recap: procurement-specific business case, early legal alignment, ready security package, and a structured concession. That's the playbook. Lucas: That's the playbook. And if today was actually useful to you, the way these stay ad-free is listener support — buy me a coffee dot com slash fexingo. Luna: Yeah, it's how we keep doing deep dives like this without sponsors. Appreciate everyone who's chipped in. Lucas: So back to the playbook. One thing I didn't mention is that procurement teams are increasingly using vendor scorecards. They'll rank you on security, pricing, support, and compliance. If you can get a copy of their scorecard early — sometimes procurement will share it if you ask — you can see exactly where you need to improve. Luna: Have you ever seen a rep actually get the scorecard before the evaluation? Lucas: Yes. It happens when you've built a relationship with procurement early. If you call the procurement lead before you submit the formal proposal and say, 'We'd love to make sure our submission aligns with your evaluation criteria — can you share your scorecard template?' — about half the time they'll send it. It shows you're transparent and want to be a good partner. Luna: That's a great tactic. And it also signals that you know how enterprise procurement works. Lucas: Exactly. And once you have the scorecard, you can address each dimension. Maybe you're weak on support — so you offer a dedicated account manager. Maybe your pricing is above their threshold — so you propose a phased rollout that lowers the first-year cost. Luna: So it's not just about selling to procurement; it's about partnering with them to build a package that their internal stakeholders will approve. Lucas: That's the mindset shift. Procurement is not the enemy. They're the person who can either kill your deal or fast-track it. And they're more likely to fast-track if you've made their job easier. Luna: I want to talk about one more thing — the timing. When do you first engage procurement? At the beginning of the sales cycle, or after you've won over the business champion? Lucas: That's a debate in the SaaS community. Some say bring them in early so they're not surprised. Others say wait until you have a champion who can push internally. My view is: bring them in when you have a solid business case and a champion who's willing to co-present. If you go in too early without a champion, procurement may see you as just another vendor trying to sell. If you go in too late, they feel like you're trying to bypass them. Luna: So the sweet spot is after the demo and the technical validation, but before the final price negotiation. Lucas: Exactly. That way you have leverage — the champion wants the deal, the tech team has approved it — and procurement's job becomes structuring the contract, not deciding whether to buy. Luna: One last question — what about multi-year deals? Procurement seems to hate those because they lock in spend. But vendors love them for predictable revenue. Lucas: Procurement's objection to multi-year is that it reduces flexibility. But if you build in an annual opt-out with notice, or a price cap that protects them if you raise prices, you can address that. I've seen deals close on three-year terms with a 10% discount and a 5% annual price cap. Procurement gets the discount, the company gets predictability. Luna: So it's about creative structuring — not just discounting. Lucas: Exactly. And that's where a good rep can really differentiate themselves. The ones who understand procurement's constraints and can craft a deal that works for both sides — they're the ones who close the big ones. Luna: I think the through-line here is that procurement is becoming more sophisticated. The old stereotype of the penny-pincher is fading. They're strategic, they use data, and they have a seat at the table. Lucas: And if you as a seller don't adapt to that, you're leaving money on the table. Literally — because those deals either stall or die. Luna: Alright, so next time someone says 'the deal's stuck in procurement,' we have a list of things to check. Lucas: We do. And I hope our listeners can put some of these into practice. Thanks for being here, Luna. Luna: Thanks, Lucas.