Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise Software Reps Are Teaching Procurement Teams
Transcript
- Lucas: If these conversations are useful for what you're building or running, we hope you'll consider supporting the show. We deliberately don't run ads on these — and that's a choice tied to today's topic. If you want to support that ad-free principle, the link is buy me a coffee dot com slash fexingo. Luna: Yeah, it's a small gesture that keeps us independent. And it ties in perfectly because we're about to talk about how education changes the dynamic between vendors and buyers. Lucas: Exactly. So here's the angle I want to drill into today. You've probably heard the phrase 'the educated buyer is a better buyer.' Enterprise software vendors have been saying that for years. But what if that buyer isn't just better — they're actually faster? What if vendors should be proactively teaching procurement teams how to evaluate their software? Luna: That's interesting because the typical dynamic is adversarial. Procurement tries to squeeze every term, vendors try to hold the line. Teaching them seems counterintuitive. Lucas: It is, which is why it's not widespread yet. But I've been looking at data from a few vendors who've started formal procurement education programs. One is a mid-market SaaS company — we'll call them DataFlow — that sells data integration software. Their average deal size is about $500,000, and their typical procurement cycle was running 8.3 months. After they started offering a half-day workshop for procurement teams on 'How to Evaluate Data Integration Platforms,' that cycle dropped to 5.1 months. Luna: Eight-point-three to five-point-one months? That's a huge compression. What's in that workshop? Lucas: It's not a sales pitch. They walk through the technical architecture, the compliance certifications, how to audit data flows, what standard SLAs look like in the category, common gotchas in the contract language. It's essentially a mini mba in their product category. And procurement teams love it because they don't have to become experts overnight. Luna: I can see why that speeds things up. If procurement understands the product better, they ask fewer irrelevant questions and they don't request absurd terms out of fear of the unknown. Lucas: Right. The fear-driven term is the enemy of velocity. I talked to a VP of Procurement at a large manufacturer who told me that before a vendor offered education, she'd default to asking for a 50% audit clause because she didn't know what was standard. After the workshop, she realized that 20% was the norm and that the vendor's SOC 2 Type II report was already more than sufficient. That one change saved three weeks of legal back and forth. Luna: So the vendor is essentially pre-empting the friction. But isn't there a risk that this looks like the vendor is coaching procurement to be less rigorous? I mean, is it education or manipulation? Lucas: That's the critical question. And the vendors who are doing this well are very careful to make it genuinely educational. They bring in a value engineer or a product manager — not a sales rep. The content is about the category, not their specific product. They'll show three different pricing models and explain the trade-offs. They'll discuss what a fair data retention policy looks like across the industry. Luna: So it's almost like objective category education, but obviously they're the ones delivering it. There's still an inherent conflict of interest. Lucas: There is. And the solution some vendors use is to partner with a third-party research firm to co-deliver the workshop. Gartner or Forrester will provide the category benchmarks, and the vendor provides the product-specific implementation details. That gives it more credibility. But it's expensive — you're talking about $50,000 to $100,000 per workshop if you bring in an analyst. Luna: That's a big investment for a deal that might not close. But if it cuts the cycle by three months and reduces the chance of a blow-up in legal, maybe it pays for itself. Lucas: That's exactly the ROI calculation. Let's look at a concrete example. Workday has been running something they call 'Procurement Partner Education' for about two years now. It's not widely publicized, but I've spoken to a couple of their enterprise sales directors. They told me that for deals over $1 million, they now offer a structured three-session program. Session one is on data security and compliance. Session two is on contract terms and SLAs. Session three is on implementation timelines and success metrics. Luna: And what kind of results are they seeing? Lucas: They measure two things: time to close and net retention rate. For customers who participated in at least two of the three sessions, time to close was 22% faster on average. And net retention was 4 percentage points higher — about 118% versus 114% for non-participants. The theory is that if procurement understands the product better, they set more realistic expectations, which leads to higher satisfaction. Luna: Four points on net retention is massive. That's worth millions over a customer lifecycle. Lucas: Exactly. And it's not just Workday. I've seen similar programs at Salesforce, though they're more ad-hoc. Salesforce's 'Procurement Navigator' is actually a set of on-demand modules that account executives can share with their prospects. It covers topics like 'Understanding True-Up Clauses' and 'How to Evaluate Multi-Cloud Discounts.' Luna: So it's scalable. You don't need a live workshop every time. But I wonder — does this change the role of the sales engineer? They're the ones who usually handle technical deep dives. Lucas: It absolutely does. In many of these programs, the sales engineer becomes a teacher rather than a demo machine. They're not just showing features; they're explaining architecture, security, compliance. That requires a different skill set. Some vendors are hiring former procurement professionals into their value engineering teams specifically for this reason. Luna: So you're seeing a convergence — the value engineer used to be about ROI calculators and business cases. Now they're also educating procurement on how to buy. Lucas: Exactly. And I think this trend is going to accelerate. Because the alternative — just hoping procurement will figure it out — leads to longer cycles, more concessions, and lower satisfaction. I spoke to a Chief Revenue Officer at a $200 million ARR company who said, 'We used to treat procurement as a gate we had to push through. Now we treat them as a partner we need to train.' Luna: That's a fundamental mindset shift. And it seems like a more sustainable approach than the typical adversarial negotiation. Lucas: It is. But there are risks. If the education is too product-specific, it can backfire and make procurement more cynical. If it's too generic, it's not worth the time. The vendors who are doing it best are the ones who treat it as a genuine investment in the relationship, not a sales tactic. Luna: And I imagine there's also a risk of creating a compliance liability. If you teach procurement how to evaluate, and then they find something in your product that doesn't match what you taught, that could be a problem. Lucas: That's a real concern. One vendor I spoke to actually had to pull a module because it inadvertently highlighted a limitation in their own product compared to a competitor. They had to rewrite it to be more balanced. The legal team was nervous about any comparative claims. Luna: So there's a fine line between being helpful and being exposed. But the vendors who are succeeding seem to be those who are transparent about their own weaknesses upfront. Lucas: Exactly. And that actually builds trust. One procurement manager I interviewed said, 'When a vendor spends time teaching me what to look for, and then admits where they don't excel, I'm more likely to believe everything else they say.' Luna: That's the power of vulnerability in sales. So what's the one thing a B2B SaaS founder should take away from this? Lucas: I'd say: if you're selling to enterprises and your procurement cycle is longer than six months, consider building a procurement education program. Start small — maybe a one-hour webinar on 'How to Evaluate Software.' Measure the impact on time to close and net retention. You might find that teaching your buyers is the best sales investment you can make. Luna: And with that, I think we've just given procurement a reason to come to work tomorrow — they get to learn something new. Lucas: Hopefully they do. And hopefully the vendors are ready to teach.