Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise Software Deals Now Require a Business Case Before Procurement
Transcript
- Lucas: You know that moment in an enterprise deal where the rep thinks the room is sold, the demo went great, the product champion is nodding along — and then procurement says, 'Great, where’s the business case?' Luna: I’ve seen that happen. And it used to be that the business case was just a formality. A one-pager with some rough numbers. Lucas: Right. But in the last 18 months, that’s flipped. Now the business case is often the first thing procurement asks for — before they even schedule a demo. I’m looking at data from a 2025 survey by Gartner that says 62 percent of enterprise SaaS deals over $100,000 now require a formal written business case before procurement even enters a conversation. Luna: That’s a huge shift. So the rep has to essentially pre-sell the CFO before they ever get to pitch their product. Lucas: Exactly. And this is happening because procurement teams have gotten more sophisticated. They’ve been burned by too many software implementations that promised the moon and delivered a crater. So they want to see the math upfront. And I’m not talking about a simple ROI calculator. I mean a full business case: total cost of ownership, implementation timeline, expected productivity gains, risk factors, and a payback period. Luna: That sounds almost like a mini-board deck. Who builds that? The rep? Lucas: Increasingly, yes. Or the rep plus a value engineer from the vendor. This is why value engineering teams have exploded. Companies like Salesforce and Workday now have dedicated value engineering orgs whose sole job is to build business cases for prospects. And those teams are often staffed with former consultants from McKinsey or Deloitte — people who know how to build financial models. Luna: So the rep’s job just got harder. They need to understand not just their product, but also the customer’s financial metrics. Lucas: Much harder. I talked to a VP of sales at a mid-market SaaS company last month. He said his top performers can now build a discounted cash flow model in their sleep. And the ones who can’t — they’re struggling. Because procurement will literally reject the deal if the business case has flawed assumptions. Luna: I have a story about that. A friend of mine is a procurement manager at a large insurance firm. They were evaluating a $2 million CRM platform. The vendor sent over a business case that assumed a 30 percent increase in sales productivity. My friend’s CFO looked at it and said, 'Show me any source that proves a CRM alone can do that.' They couldn't. Deal dead. Lucas: And that’s the new gate. It’s not about relationship anymore — it’s about evidence. And that’s healthy, honestly. It forces vendors to be honest about what their software actually delivers. But it also means the sales cycle is lengthening. If the business case has to go through three rounds of review, you’re adding weeks. Luna: Yeah. And if the show is useful for what you’re building or running, listener support is what keeps it ad-free. You can find us at buy me a coffee dot com slash fexingo. Lucas: And we mean that genuinely — every contribution helps us keep digging into these sales dynamics without any sponsor pressure. Luna: Exactly. So back to that lengthening cycle — what are vendors doing to speed it up? Lucas: Some are building what I call 'business case templates' for specific verticals. So if you’re selling to a bank, you don’t start from scratch. You have a template that already includes industry benchmarks for cost savings and compliance risk reduction. Then the rep just customizes the numbers. Luna: That helps, but only if the benchmarks are credible. If they’re too aggressive, procurement will smell it. Lucas: Absolutely. And that’s where the best vendors are using third-party data. For example, they’ll cite Forrester or IDC studies that show average productivity gains for a specific software category. That adds credibility. Some are even doing pilot programs where the business case is validated with a small-scale deployment before the full deal. Luna: That’s smart. It turns the business case from a theoretical document into a real-world proof point. Lucas: Right. And it also reduces risk for the buyer. If the pilot delivers the promised outcomes, the business case is already proven. I’ve seen vendors offer a 'no-commitment pilot' — the customer pays nothing until they see the results. That’s a bold move, but it works. Luna: But that requires the vendor to have a lot of confidence in their product. Not all do. Lucas: Exactly. And that’s the market signal. The vendors that are confident in their ROI are the ones winning deals. The ones that can’t back up their claims are getting filtered out by the business case requirement. So in a weird way, this trend is actually improving the quality of enterprise software. Luna: So what does this mean for sales training? Are we going to see more financial modeling courses? Lucas: Yes. I know of at least three SaaS companies that have partnered with online learning platforms to create certification programs in 'value selling' — which is basically business case construction. And some are even tying compensation to whether the rep can independently build a business case that passes procurement’s review. Luna: That’s a big change. Traditionally, comp was tied to closed revenue, not the quality of the business case. Lucas: Right. But now, if the business case is weak, the deal might not close. So it’s a leading indicator. Some companies are paying bonuses when the business case is approved, not just when the contract is signed. Luna: Interesting. That shifts the incentive to build a realistic case rather than an optimistic one. Lucas: Exactly. And it aligns the vendor with the buyer. The buyer wants a realistic business case. The vendor should want that too, because if the case is realistic, the implementation is more likely to succeed, and you get a referenceable customer. Luna: So what about smaller vendors? They can’t afford a value engineering team. Are they at a disadvantage? Lucas: They are, unless they get creative. Some are using AI tools to generate business cases. You feed in the customer’s industry, company size, and pain points, and the tool spits out a draft. But the quality varies. I’ve seen some that are laughably generic. Procurement teams are trained to spot that. Luna: So the human element still matters. The rep has to understand the customer’s specific context. Lucas: Completely. And that’s where the best reps differentiate. They don’t just fill in a template. They interview the customer’s finance team to understand their actual cost structure and what metrics they care about. Then they build a case that speaks to those metrics. That’s hard to automate. Luna: So if you’re a rep listening, what’s the one thing you should do this week? Lucas: Learn your customer’s language of value. For a CFO, it’s not 'we improve workflow efficiency' — it’s 'we reduce cost per transaction by 12 percent.' And have third-party data to back it up. If you don’t have that, you’re going to lose to someone who does. Luna: That’s a solid takeaway. And for procurement teams, what’s your advice? Lucas: Don’t just accept the business case at face value. Ask for the assumptions. Ask for the source of the benchmarks. If a vendor can’t provide that, it’s a red flag. The business case should be a starting point for a conversation, not a final verdict. Luna: Right. Because the goal isn’t to kill deals — it’s to make sure the ones that go through actually deliver value. Lucas: Exactly. And that’s better for everyone — the buyer, the vendor, and the end users who have to use the software every day. Luna: So next time you hear a rep say 'we don’t do business cases,' you know what to think. Lucas: Yeah. They’re probably not closing many enterprise deals.