Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise Software Vendors Are Hiring Value Engineers
Transcript
- Lucas: If these conversations are useful for what you're building or running, that's the whole point. The way we keep this ad-free is listener support — buy me a coffee dot com slash fexingo. Low-key, just people who find it valuable chipping in. Now, let's get into today's angle. Luna: Yeah, it's a small thing that makes a big difference. So what are we digging into today? Lucas: Value engineering teams. If you've sold enterprise software in the last two years, you've probably bumped into a prospect who says 'Show me the ROI — prove it before we sign.' That's where value engineers come in. Luna: I've seen the title more on LinkedIn lately. Is this just a fancy name for a sales engineer who can do math? Lucas: Close, but not exactly. A sales engineer focuses on technical fit — does the product integrate, does it scale, does it meet security requirements. A value engineer focuses on financial fit. They build a detailed business case alongside the prospect's team, mapping current costs — like legacy license fees, manual labor hours, downtime penalties — against the projected savings or revenue lift from the new software. Luna: So they're essentially an on-call consultant embedded in the sales cycle. Who's doing this well? Lucas: Salesforce has had a value engineering practice for years, but it's gone from a niche resource to a core part of their enterprise motion. Workday too. And newer players like Gong and Figma are building value engineering teams as they move upmarket. The data from a few vendor case studies I've seen suggests that deals with value engineering involvement close 20 percent more often and cycle times shrink by about 30 percent. Luna: Thirty percent shorter cycle is huge when you're chasing a six-figure annual contract. But does that hold up across industries? Lucas: It varies, but the trend is clear. The reason is that procurement teams have gotten much more sophisticated. They don't just want a discount; they want a defensible rationale for the spend. If your vendor provides a third-party-validated ROI model, procurement can take that to the CFO and say 'This is a justified investment, not a gamble.' Luna: So value engineers are essentially pre-empting the procurement objection before it surfaces. That feels like a game changer. Lucas: Exactly. And it shifts the conversation from price to value. Instead of haggling over a five percent discount, you're discussing whether the projected savings are 40 or 50 percent. The value engineer owns that narrative. Luna: What kind of background do these people have? I'm guessing former consultants from Bain or McKinsey? Lucas: Often, yes. But also FP&A analysts, former procurement professionals, and even product managers who are financially literate. The skill set is a mix of financial modeling, storytelling, and customer empathy. They need to be credible enough to sit in a room with the CFO's team. Luna: And is this just a sales tactic, or does it actually improve customer outcomes? I've seen some companies where the ROI model is basically a spreadsheet full of optimistic assumptions. Lucas: That's the risk — if the value engineer overpromises, you get a happy buyer who becomes a disappointed customer six months later. The best teams track actual results post-sale and feed that data back into the models. They'll say 'Based on our experience with 50 similar deployments, the average time to value is four months, not two.' Honesty builds trust. Luna: So the value engineer role is also a bridge between sales and customer success. They set realistic expectations upfront. Lucas: Exactly. And that's why some companies now have the value engineer stay involved through the first quarter after go-live, helping to measure and communicate the realized value. It reduces churn and opens up expansion conversations. Luna: I want to talk about a concrete example. Can you walk through a typical value engineering engagement from start to finish? Lucas: Sure. Let's say a mid-market company is evaluating a CRM platform like Salesforce. The value engineer starts with discovery — they interview the prospect's sales ops leader, finance director, and a few reps. They gather data on current license costs, average deal size, close rates, time spent on data entry, and lead response times. Luna: So they're building a baseline. That sounds like a mini consulting project. Lucas: It is. Then they model two or three scenarios — conservative, moderate, aggressive — based on typical improvements from similar deployments. For example, a 20 percent increase in lead response speed might yield a 10 percent lift in conversion. They quantify that in dollars. The output is a one-page executive summary and a detailed model the prospect can share with their board. Luna: And that becomes a key artifact in the procurement process. Does it also help the vendor justify pricing without discounting? Lucas: Yes. If the model shows a three-year net present value of two million dollars, a 200-thousand-dollar annual subscription looks like a bargain. The conversation stops being about the price and becomes about which scenario is most likely. The vendor's pricing feels anchored in value. Luna: That's a powerful dynamic. But I imagine not every vendor can afford a dedicated value engineering team. What about startups moving upmarket? Lucas: Startups often start with a fractional value engineer — maybe a former consultant hired as a part-time contractor for specific deals. Or they train their top sales reps to build basic ROI models. The key is having someone who can speak the language of finance, not just product. Luna: Are there any tools that help smaller teams do this without hiring a full-time person? Lucas: Yeah, platforms like ValueSelling and ROI Builder offer templates and calculators specifically for B2B SaaS. Some are even free for early-stage companies. But the data input still requires judgment. A template is only as good as the assumptions you feed it. Luna: I've also heard of vendors using third-party ROI validation firms to add credibility. Is that common? Lucas: It's growing. Firms like Forrester and Gartner have TEI — total economic impact — studies that vendors can license. But those are expensive and generic. A custom value engineering engagement tailored to a specific prospect is more persuasive. Luna: So what's the downside? I'm trying to think if procurement ever pushes back on these models. Lucas: They do. Sophisticated procurement teams will challenge assumptions — 'Why do you assume a 15 percent productivity gain? Our reps are already pretty efficient.' The value engineer needs to defend those assumptions with data, ideally from the prospect's own benchmarks. If they can't, the model loses credibility. Luna: So the value engineer also has to be a diplomat. They're advocating for the vendor but also maintaining enough objectivity to be trusted. Lucas: Exactly. The best ones I've seen are genuinely curious about the prospect's business. They ask tough questions that sometimes reveal the prospect isn't ready for the software — and they'll flag that internally. That saves everyone time. Luna: That's a real value-add. So if a founder is listening and thinking about building a value engineering capability, where should they start? Lucas: First, identify your top five enterprise deals in the pipeline. See if any of them are stalling because of ROI justification. Then hire one person — ideally with a consulting background and some sales exposure — and have them shadow your best sales rep on a few calls. Let them build a model for one deal and see if it moves the needle. Luna: And measure success not just by closed deals but by whether the deal closed faster or with less discounting. Lucas: Right. A value engineer who helps you close a single five-hundred-thousand-dollar deal at full price more than pays for their salary. The ROI on the role itself is pretty clear. Luna: That's a good note to end on. Next episode, maybe we can talk about how procurement is reacting to this trend — are they building their own value engineering teams to push back? Lucas: I've heard whispers of that. Some large buyers now have 'value assurance' managers who audit vendor ROI claims post-implementation. That could be a whole episode. Luna: Let's do it. Thanks for listening — we'll be back with more on that soon.