Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise Software Prospects Now Demand a Business Value Assessment Before the Demo
Transcript
- Lucas: If these conversations are useful for what you're building or running, stick with us. Today we're tackling something that's quietly reshaping the enterprise sales cycle: the Business Value Assessment, or BVA, that buyers now expect before they'll even sit through a demo. Luna: I've been hearing that term a lot lately. A BVA is different from a proof of value, right? It's more about the financial case upfront. Lucas: Exactly. A proof of value usually happens after a demo, during a pilot. But a BVA happens before the demo. The buyer says, 'I'm not going to waste my team's time looking at your product until you show me, in my numbers, that it makes business sense.' Luna: That's a pretty significant gate to pass. Who's driving this demand? Lucas: Procurement teams, CFOs, increasingly even line of business leaders who've been burned by software purchases that didn't deliver. I saw a Gartner survey from late last year—72 percent of enterprise buyers said a quantified value model is now table stakes before they'll engage seriously. Luna: Wow. So if you show up without a BVA, you're basically invisible. Lucas: Right. And the interesting thing is, this isn't just about cost savings. The best BVAs also model revenue uplift, productivity gains, risk reduction. They basically build a mini business case for the buyer to take to their own decision committee. Luna: So the vendor is doing the buyer's homework for them? That seems like a lot of work for a sales team. Lucas: It is. But the vendors that do it well see higher win rates and shorter sales cycles. For example, I talked to a VP of Sales at a mid-market SaaS company last month. They implemented a mandatory BVA step for any deal over $100,000. Their average deal cycle dropped from nine months to six. Luna: That's a 33 percent improvement. But what does a BVA actually look like in practice? Is it a spreadsheet, a deck, a tool? Lucas: It can be all of those. But the best ones are interactive. Usually, the sales rep or a value engineer sits down with the buyer's team—could be finance, operations, IT—and they build a model together. They input the buyer's current costs, headcount, process inefficiencies. Then they map how the software changes those variables. Luna: So it's collaborative. That makes sense—if the buyer helps build the model, they trust the output more. Lucas: Exactly. There's a company called ValueSelling Associates that trains reps on this. They call it 'co-creating value.' And the data backs it up: deals where the buyer participates in building the BVA close at a 60 percent higher rate. Luna: That's huge. But I wonder—does this trend favor larger vendors who have dedicated value engineering teams? A startup with three sales reps can't exactly build custom financial models for every prospect. Lucas: That's a real concern. But I've seen startups get creative. Some use templates that are 80 percent pre-built, with just a few inputs the rep fills in during discovery. Others use tools like Medallia's Value Coach or even just a well-structured Excel workbook. The key is to be transparent about assumptions. Luna: Because if the assumptions are flimsy, the buyer will see right through it. And that could backfire. Lucas: Exactly. In fact, I've heard of deals that stalled because the seller's BVA was too aggressive—it projected a 200 percent ROI in year one. The buyer's finance team just laughed and said, 'Come back when you're serious.' So credibility is paramount. Luna: Let's talk about the skills side. Are sales reps being trained to build these models? Or is this a new role? Lucas: Both. Many companies are hiring value engineers specifically for this. But existing reps are also being upskilled. I've seen training programs that teach reps to speak in terms of net present value, payback period, total cost of ownership. It's a big shift from the old 'features and benefits' pitch. Luna: It's almost like sales and finance are merging. The rep has to think like a CFO. Lucas: Right. And that raises the bar for who can be an enterprise sales rep. It's no longer just about relationship building. You need analytical chops. Luna: I'm curious about the buyer's side. If I'm a procurement manager, a BVA sounds great. But some vendors might use it to lock me into their framework. How do buyers protect themselves? Lucas: Smart buyers bring their own data and challenge the assumptions. They might run a parallel model internally. And increasingly, procurement teams are standardizing their own BVA templates that they require all vendors to fill out. That levels the playing field and makes comparisons easier. Luna: So the BVA is becoming a required document, like an RFP response. Lucas: Exactly. And that's where we're headed. I think within a few years, any enterprise deal above a certain threshold will have a formal BVA attached to it, just like a business case. Luna: That's a big shift. And it ties back to something we touched on earlier—the need for reps to understand the buyer's business deeply. Lucas: Absolutely. And you know, conversations like this are exactly why we keep doing this show ad-free. We want to dig into the real mechanics without any sponsored spin. Luna: Yeah, it's important to have that space. And if listeners find value in what we're sharing, they can support the show at buy me a coffee dot com slash fexingo. It's a simple way to keep these deep dives coming. Lucas: No pressure, just an option. Now, back to the BVA—one more angle I want to explore is how this affects deal timing. Luna: Is it faster or slower overall? On one hand, you're adding a step upfront. On the other, you're qualifying out bad fits early. Lucas: Exactly. The data I've seen suggests that deals with a BVA actually close faster, because you avoid the 'demo then stall' pattern. But if the BVA reveals that the ROI isn't there, you lose the deal earlier. That's actually a good thing—you don't waste months. Luna: So it forces honesty. That might scare some sales leaders, but it's probably healthier for the business. Lucas: I think so. And it also gives the sales team a clear language to talk about pricing. Instead of arguing over cost, you're talking about return on investment. If the BVA says you'll save $2 million over three years, then a $500,000 license fee looks reasonable. Luna: That's a much better conversation than 'our price is competitive.' Lucas: Right. So the BVA is really changing the entire sales conversation—from features to outcomes, from cost to investment. Luna: And it's not just for new purchases. I imagine it's also used for renewals and expansions, right? Lucas: Absolutely. In fact, some vendors now do an annual business value review with existing customers. It's a way to demonstrate the value delivered and justify a higher renewal price or an upsell. Luna: That's a great retention strategy. It turns the customer success team into value consultants. Lucas: Exactly. So whether you're selling or buying enterprise software, understanding the BVA framework is becoming essential. It's no longer a nice to have; it's the price of entry. Luna: Good to know. And for our listeners who are building or scaling a SaaS company, I'd say invest early in a value engineering capability, even if it's just a template and a trained rep. Lucas: Wise advice. That's all for today. Thanks for being here.