Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise Software Deals Now Include a Joint Business Case
Transcript
- Lucas: So I was on the phone last week with a VP of Sales at a mid-market logistics software company. They're trying to land a two-point-three-million-dollar deal with a regional freight firm, and the buyer's CFO said something that I think is becoming the norm: 'I don't want your ROI calculator. I want a joint business case that my controller and I co-author with you.' Luna: Joint business case. That's a phrase I'm hearing more and more. What's actually different from the standard ROI spreadsheet vendors have been pushing for years? Lucas: The big difference is ownership. In a typical ROI calculator, the vendor builds a model that assumes best-case productivity gains, best-case cost savings, best-case everything. The buyer looks at it, discounts it by fifty percent, and the negotiation starts from this adversarial place. Lucas: A joint business case, by contrast, starts blank. Both sides agree on baseline assumptions—current headcount, current error rates, current downtime. Then they model the improvement together, using numbers the buyer's finance team actually trusts because they supplied them. Luna: Right, so the vendor loses control of the narrative, but they gain credibility. I can see why a CFO would prefer that. Lucas: Exactly. And there's a real teeth component too. The deal I mentioned—the warehouse management system—the joint business case included a section called 'Value Assurance Triggers.' If the software doesn't reduce picking errors by at least thirty percent within nine months, the vendor rebates a portion of the license fee. Luna: That's effectively a performance guarantee tied to the joint assumptions. That's pretty far from the old 'trust us, you'll see ROI' approach. Lucas: Far indeed. And here's the stat that really got my attention: a 2025 survey from DealSignal found that deals with a formal joint business case close twenty-seven percent faster and see forty percent fewer post-signing disputes. The reason is obvious when you think about it—both sides have already negotiated what success looks like before the contract is signed. Luna: Let me play skeptic for a second. Is this really a new thing, or is it just a rebranding of what good enterprise sales reps have always done informally—working with the champion to build an internal justification? Lucas: Fair question. I think the difference is structure and scale. In the old model, the champion—usually an operations director or a VP of something—would build a PowerPoint deck for the steering committee. It was ad hoc, often optimistic, and the CFO's office would tear it apart. Lucas: The joint business case formalizes that process. It's usually a ten- to fifteen-page document with clear sections: baseline metrics, projected improvements, payback period, risk mitigations, and value assurance triggers. Both the vendor's VP of Sales and the buyer's CFO sign it. It becomes part of the contract appendix. Luna: So it's not just a sales tool—it's a governance document. That changes the skill set needed from the sales rep, doesn't it? They have to be more of a facilitator and less of a presenter. Lucas: Hugely. I asked the VP I spoke with how he's training his team. He said he now runs mock joint business case workshops where the reps role-play with someone from their own finance department acting as the buyer's CFO. The reps have to defend their assumptions against real financial scrutiny. It's a completely different muscle. Luna: And this is exactly the kind of deep, practical insight that we can explore on this show because we're not trying to please a sponsor or sell ad slots. You know, it's something I really value about what we do here—we can follow the thread wherever it goes. Lucas: It's true. We deliberately don't run ads on these episodes. If you find this kind of unvarnished conversation useful for what you're building or running, and you want to support that choice, the link is buy me a coffee dot com slash fexingo. No pressure, just an option for people who like the model. Luna: Yeah. And it keeps us honest—we're not beholden to anyone's messaging. So back to the joint business case. I'm curious about the vendors who are leading on this. Is it mostly the bigger enterprise players, or are mid-market SaaS companies adopting it too? Lucas: It's spreading fast in the mid-market because that's where deal risk is highest. A two-million-dollar deal can make or break a SaaS company's quarter. So they're willing to try anything that increases close rates. The logistics company I mentioned has about two hundred employees. They're not Salesforce. They just need every deal to count. Lucas: The other trend I see is that procurement teams are now asking for the joint business case upfront. I talked to a procurement director at a large European retailer, and she told me that if a vendor doesn't propose a joint business case in the first meeting, she assumes they're hiding something. Luna: That's a pretty stark signal. It means the absence of a joint business case becomes a red flag. So vendors who don't adapt risk being filtered out before they even get to the demo. Lucas: Exactly. And it's not just about getting to 'yes.' It's about staying in 'yes' after the contract is signed. The value assurance triggers mean the vendor has skin in the game post-implementation. If the software doesn't deliver, the vendor writes a check. That aligns incentives in a way that standard SLAs never did. Luna: I want to dig into one nuance. The joint business case requires the buyer to share operational data that they might consider sensitive—headcount costs, error rates, downtime figures. How do vendors handle the confidentiality concern? Lucas: Great question. The best practice is to have a mutual non-disclosure agreement that explicitly covers the business case data. Some vendors also use a 'clean room' approach where the buyer's finance team inputs the data into a shared model that the vendor can see but can't export. The output is what gets signed. Lucas: There's also a growing trend of using third-party facilitators—consultants who run the joint business case workshop for a fee paid by both sides. That completely eliminates the concern about vendor bias or data misuse. Luna: Interesting. So the market is evolving its own infrastructure around this. It's not just a sales technique anymore; it's becoming a category of service. Lucas: Right. And I think that's healthy. The more standardized the process becomes, the less it depends on individual sales rep charisma and the more it depends on actual evidence. That's a win for buyers and for disciplined sellers. Luna: Let's talk about a specific example. You mentioned the warehouse management system deal. Walk me through what that joint business case actually looked like. Lucas: Sure. The vendor was a company called LogiNext—about eighty million in ARR, selling to distribution centers. The buyer was a regional freight firm with four warehouses. The joint business case had five sections. Lucas: First, current state: they measured average pick error rate at 1.8%, average labor cost per order at $4.20, and average order cycle time at 47 minutes. Second, projected improvements: the software aimed to cut errors to 0.5%, labor cost to $3.50, and cycle time to 32 minutes within twelve months. Lucas: Third, financial summary: total investment of two point three million over three years, net present value of one point one million, payback period of fourteen months. Fourth, risks and mitigations: listed three risks—data migration delays, user adoption curve, and integration with legacy ERP—with specific mitigation plans for each. Luna: And the fifth section? Lucas: Value assurance triggers. If error rate didn't drop below 1% within nine months, the vendor would credit fifteen percent of the first-year license fee. If cycle time didn't improve by at least twenty percent, another ten percent credit. The CFO liked that because it put real money on the table. Luna: Did the deal close? Lucas: It did. The VP told me it took three workshops over six weeks. The first workshop was just agreeing on baseline numbers. The second was modeling scenarios. The third was finalizing the triggers. He said it was more work upfront, but the implementation phase has been smoother than any deal they've done without a joint business case. Luna: That aligns with the survey data you mentioned—fewer disputes. It makes intuitive sense. If you've already argued about what success looks like before you sign, you're not arguing about it after. Lucas: Exactly. And I think this is the direction enterprise software procurement is heading. We're moving from 'vendor sells, buyer buys' to 'both sides co-create the rationale for the investment.' The joint business case is the artifact that makes that tangible. Luna: So for our listeners who are on the vendor side—what's the one thing they should do this week to start moving in this direction? Lucas: Start with your own finance team. Invite your CFO or a senior analyst to a half-day workshop where you simulate building a joint business case for your most typical deal. Use real data from a past win and a past loss. See where the assumptions break down. That'll tell you exactly what you need to change in your sales process. Luna: And for buyers? Lucas: Next time a vendor pitches you their ROI calculator, ask them: 'Can we build this together from scratch? And can we put a value assurance trigger on it?' If they hesitate, that's useful information. Luna: That's a strong litmus test. I'll be using that one myself. Lucas: It's one of those shifts that feels small but changes the entire dynamic of the relationship. And I think it's ultimately good for both sides—more honest, more aligned, more likely to succeed.