Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise Buyers Demand Proof of Value Before Signing
Transcript
- Lucas: Last week I was talking to the VP of IT at a $12 billion industrial manufacturer. He told me that before they even look at a contract, they now require a 90-day proof of value pilot. No exceptions. Luna: That's a big shift from the standard demo and a PowerPoint deck. What drove that? Lucas: They got burned by a $2 million CRM implementation two years ago. The vendor sold it on a slick demo, but once deployed, adoption cratered. They basically wrote off the investment. So now they want to see the product actually deliver value in their environment before committing. Luna: And this is becoming common? Not just for huge deals? Lucas: It's spreading fast. Gartner released data in their latest buying behavior survey — 60% of enterprise software purchases now include a POV clause, up from 30% just three years ago. And it's no longer reserved for seven-figure deals. I'm seeing it on contracts as low as $250,000. Luna: That fundamentally changes how vendors have to sell. What's the right way to structure a POV from the vendor side? Lucas: The first rule is to be selective. Don't say yes to every pilot request — you'll burn your implementation team. Qualify the opportunity just like you would a full deal. Is there a real budget? A champion? A timeline? Luna: Once you agree to run a POV, what are the key components? Lucas: You need three things: clear success criteria agreed upfront, a defined scope limited to one department or use case, and a dedicated project manager on the customer side. I've seen too many pilots fail because the customer didn't assign anyone to coordinate. Luna: And metrics — measurable outcomes that both sides can track? Lucas: Exactly. For example, if you're selling a customer service platform, the success criteria might be 'reduce average handle time by 15% within 60 days.' You measure baseline data before the pilot, then compare. The best POVs end with a joint business case showing projected ROI. Luna: What about length? Is 90 days standard? Lucas: It's the most common, but I'm seeing 30- and 60-day pilots for simpler products. The risk with longer pilots is scope creep. The customer starts asking for customizations before they've even bought the product. You have to hold the line — this is a proof of value, not a proof of concept for every edge case. Luna: That's a distinction worth underlining. Proof of value is about showing the core product delivers business outcomes. Proof of concept is more about technical feasibility. Lucas: Right. And enterprises increasingly want the former. They know the technology works — they want to know it works for them, with their data and their people. Luna: I've also heard vendors complain that some customers use POVs to get free consulting. How do you avoid that? Lucas: Set a hard time limit and a clear scope document. Also, put a price on the POV — not necessarily charging, but at least have the customer commit resources. If they won't assign a project manager or provide data within two weeks, that's a red flag. Luna: So the POV itself is a sales filter. If the customer isn't serious enough to participate, you probably don't want them as a client. Lucas: Exactly. And the conversations we have on this show are about helping operators and builders navigate these exact dynamics. If today's episode gave you a useful framework for handling proof of value requests, the way these stay ad-free and without sponsors is listener support. You can help at buy me a coffee dot com slash fexingo. Luna: Yeah, it's a small thing that keeps the show independent and focused on what actually works in the field. Lucas: So back to the pilot structure — another common mistake is giving away too much during the POV. Vendors often over-deliver in hopes of closing faster, but that sets an unsustainable expectation. Be generous with your time, but keep the product scope exactly what they'd get in the standard package. Luna: And what about the customer side? Any best practices for how they should run a POV? Lucas: Yes. The customer should treat the POV as the beginning of the implementation, not a separate experiment. Assign a business owner, not just IT. Define what 'success' looks like in their own terms. And at the end, conduct a debrief with a clear go/no-go decision criteria. Luna: I've seen some companies institutionalize this — they have a standard POV playbook that every vendor must follow. Lucas: That's a sign of procurement maturity. And it's becoming the norm. I think within three years, a POV will be a standard step in any enterprise software deal over $250,000. It's a smarter way to buy and sell — reduces risk for the buyer and shortens the sales cycle for the vendor when done right. Luna: But what if the POV fails? Does that kill the deal? Lucas: Not necessarily. Sometimes the failure reveals a mismatch between what the vendor promised and reality. That's valuable information. The buyer saves millions on the wrong solution, and the vendor can either adjust or move on. A failed POV is better than a failed deployment. Luna: So it's a win-win if both sides approach it with integrity. Lucas: Exactly. And that's where I think the market is heading — more transparency, more shared risk, and more evidence before commitment. Luna: Alright, thanks Lucas. I think we've given our listeners a solid playbook for the new POV era. Lucas: Glad to. Next time we'll look at how AI is starting to change the POV itself — automated benchmarks, synthetic data tests — but that's for another episode.