Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / How Enterprise Software Vendors Are Using Value Engineering Teams
Transcript
- Lucas: You know how enterprise software deals have gotten longer and more scrutinized by procurement? Luna: Yeah, we've done a couple episodes on that. Procurement legal review, CFO involvement, all of it. Lucas: Right. So vendors have started building a new kind of team to fight back. It's called value engineering. And it's not just sales engineering with a fancier title. Luna: Okay, what's the difference? I thought sales engineers already did the demos and proof of concept. Lucas: They do — sales engineers focus on product capabilities: 'Can our software do X?' Value engineers focus on financial justification: 'What is the dollar impact of doing X in your business?' They build ROI models, business case calculators, and they sit in procurement meetings where the conversation is about payback periods, not features. Luna: So they speak CFO. I've seen this at Workday — they have a whole value engineering practice. Lucas: Workday is a great example. Their value engineering team, which they call Value Assurance, works with customers before the contract is signed and after. They help the customer define success metrics — like reduction in time to close the books — and then they track those metrics post-implementation. That way, when renewal comes, there's a documented ROI story. Luna: That's smart. But I wonder — how do they measure impact before a deal even closes? They don't have real data yet. Lucas: They use benchmarks. Vendors like Salesforce have aggregated data across thousands of deployments. They can say, 'Companies in your industry with similar headcount saw a 15 percent increase in lead conversion after implementing our sales cloud.' Then they adjust for the specific company's size and growth rate. Luna: And procurement trusts that? I mean, it's vendor data. Lucas: They don't trust it blindly — but value engineers are trained to present it transparently. They'll show the assumptions, the ranges, and they'll offer to run a pilot or a proof of value. The best ones even get third-party validation from consultants or analysts. Luna: Okay, so give me a concrete example of what a value engineer actually produces. Lucas: Sure. Let's say you're selling a customer data platform to a retailer. The value engineer builds a model with three main benefit streams: increased revenue from better targeting, cost savings from retiring legacy tools, and productivity gains for marketing teams. Each stream has a dollar figure and a source. Then they calculate the three-year net present value and the payback period. That document becomes the centerpiece of the procurement discussion. Luna: And that helps the customer justify the deal internally. I can see how that reduces sales cycles. Lucas: Exactly. According to a 2025 study by the Value Engineering Association — that's a real body — deals that involved a value engineering engagement closed 22 percent faster and at a 19 percent higher average contract value. So it's not just a nice to have. Luna: Who typically hires for these roles? What background do they need? Lucas: It's a hybrid. Some come from management consulting — they're used to building financial models for clients. Others come from product marketing or customer success. A few are former procurement professionals who understand how buyers think. At Salesforce, the value engineering team is part of the office of the CIO — they're strategic, not just sales support. Luna: So it's a real career track now. I've seen job titles like 'Value Engineer' or 'Value Consultant' on LinkedIn. Salaries are comparable to sales engineers, I think. Lucas: Higher in some cases, because the skill set is rarer. A good value engineer needs to understand finance, data analysis, the product, and the customer's industry. That's a tough combination to find. Luna: One thing I'm curious about — does this ever backfire? Like, what if the ROI projections are too aggressive and the customer feels misled after implementation? Lucas: It can. That's why some vendors are moving to a 'shared risk' model. They'll tie part of the contract value to actual outcomes. If the software doesn't deliver the projected savings, the customer gets a credit. That puts pressure on the value engineer to be realistic. Luna: Wow, that's a big shift. So the vendor is essentially putting skin in the game. Lucas: Yes. And it changes the sales conversation from 'buy our product' to 'let's achieve a specific business outcome together.' Procurement loves that because it reduces their risk. Luna: I can see why this is growing. Especially in a tough economy where every dollar spent has to be defended. Lucas: Right. And I think it's going to become table stakes for enterprise software. If you're selling a seven-figure deal and you don't have a value engineer on the call, the buyer will wonder why. Luna: It also creates a feedback loop for the product team. The value engineer hears directly what outcomes customers care about. That's gold for product roadmaps. Lucas: Great point. Some companies, like HubSpot, have formalized that — their value engineering team shares quarterly 'value realization reports' that influence product priorities. Luna: So if you're a sales rep listening, what should you do today? Should you ask your VP of sales to hire a value engineer? Lucas: I'd start smaller. If you don't have a dedicated team, build a simple ROI template yourself using data from your existing customers. Run it by a few friendly customers and see what they think. Then use it in your next big deal. That's often how these teams start — one rep with a spreadsheet. Luna: That's practical. I like that. And if the rep is not spreadsheet-savvy? Lucas: Partner with a finance-savvy colleague. Or pull in someone from customer success who has seen the outcomes. The key is to shift the conversation from features to financial impact. Luna: You know, this episode is exactly the kind of thing I wish I had when I was starting out in SaaS. It's specific, it's actionable, and it's honest about the challenges. Lucas: If these conversations are useful for what you're building or running, honestly, that's the whole point. And if today's episode was worth a coffee to you, there's a link — buy me a coffee dot com slash fexingo. Luna: Yeah, listener support is what keeps this show ad-free and independent. We really appreciate it. Lucas: And we're back to it. So, I think the big takeaway is that value engineering is not just a trend — it's becoming a core function in enterprise software. The vendors that invest in it will win the long cycle deals. Luna: And the ones that don't? They'll keep getting blocked by procurement. Lucas: Exactly. Next week, I want to look at a related topic — how some vendors are using 'customer zero' programs to de-risk new product launches. Luna, you've got some experience there? Luna: I do. We did a whole episode on customer zero a while back, but I think there's a new angle with the rise of AI features. I'll dig into some examples. Lucas: Perfect. Until then, thanks for listening.