Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / How Enterprise Software Vendors Use ROI Calculators to Close Deals
Transcript
- Lucas: So you're in a procurement meeting, and the buyer says, 'Your software costs five hundred thousand dollars a year. Show me the return.' What do you do? Luna: You pull out the ROI calculator. Every enterprise vendor has one now. Lucas: Exactly. But most of them are terrible. And I think that's actually a fascinating angle because the ROI calculator has become a make or break tool in enterprise sales. Not just a nice to have — a required artifact in the deal cycle. Luna: How bad are the bad ones? Lucas: They're generic spreadsheets that assume every customer saves the same amount of time. They don't account for industry, company size, or implementation complexity. I've seen one that claimed a fifty-person accounting team would save four hundred thousand dollars a year just by using a better approval workflow. That's a hundred percent of their total payroll. It's fantasy. Luna: And procurement sees through that immediately. Lucas: They do. And once you lose credibility on the numbers, you've lost the deal. So the smart vendors have invested heavily in building calculator tools that are defensible — tied to real benchmarks, auditable, and customisable per deal. Luna: What's an example of a good one? Lucas: Let me use a concrete case. There's a mid-market HR tech company I've been following — they sell a performance management platform. Their calculator starts with three baseline inputs: current head count, average manager hours spent on reviews per cycle, and the cost of voluntary turnover. That last one is key. They use industry data from the Society for Human Resource Management — SHRM — which says the cost of replacing a salaried employee is six to nine months of salary on average. So if you have a thousand employees and you reduce turnover by two percent, that's twenty people you don't have to replace. At seventy-five thousand dollars per replacement, that's one point five million in savings. Luna: That's a much stronger number because it's based on an external benchmark. Lucas: Exactly. And they don't stop there. They also calculate productivity gains from shorter review cycles — from, say, ten hours per manager to four hours. For two hundred managers, that's twelve hundred hours saved per cycle. At a blended rate of fifty dollars per hour, that's sixty thousand dollars per review cycle. Multiply by four cycles a year, you get two hundred and forty thousand dollars. So now the total quantified benefit is over one point seven million dollars, against a fifty-thousand-dollar annual subscription. The ROI is thirty-four to one. Luna: That's a compelling story for a CFO. But procurement is going to challenge the assumptions. How do you defend the numbers? Lucas: That's the second layer. The best vendors include what they call a 'confidence interval' or a 'sensitivity analysis' within the calculator itself. You can adjust each assumption — maybe you only get half the turnover reduction, or only half the time savings — and it recalculates the ROI in real time. So the buyer can see that even in a conservative scenario, the payback period is under twelve months. That's what makes the calculator credible. Luna: Let me ask about the sales process itself. When in the cycle does this calculator come out? Lucas: Traditionally, the ROI calculator was a late-stage tool — you'd bring it out when procurement asked for justification. But the forward-looking vendors are using it much earlier. Some reps now open with the calculator in the first discovery call. They ask the prospect for three or four numbers — team size, average salary, current tool spend — and they build a preliminary ROI right there on the screen. That immediately frames the conversation around value, not features. Luna: That's interesting because it also qualifies the deal early. If the ROI doesn't stack up at two times or three times, the rep knows not to invest months in that prospect. Lucas: Exactly. It becomes a qualification tool. A lot of sales leaders I talk to say that using an upfront calculator has reduced their sales cycle length by about twenty percent, because they stop chasing deals that can't clear the economic hurdle. And the deals that do move forward are better qualified and close at higher win rates. Luna: I want to push back a little. Isn't there a risk that the calculator becomes just another sales tactic — a 'magic number' that procurement has seen a hundred times? Luna: I've been in meetings where the vendor shows an ROI of twenty to one, and the procurement person just smiles and says, 'Okay, but show me the proof for your specific product in our specific context.' Lucas: That's the right question. And the vendors that win are the ones that can point to third-party validation. For example, some companies commission Forrester or Gartner to do a Total Economic Impact study — a TEI — which is a structured methodology that includes interviews with existing customers. Then the calculator is built on the data from that study. It's not the vendor's own numbers; it's an analyst's numbers. That carries a lot more weight in procurement. Luna: So the calculator is only as good as the data behind it. Lucas: Right. And the data has to be specific to the buyer's industry and use case. A generic 'everyone saves thirty percent' doesn't work. But if you can say, 'For financial services companies with over five hundred employees, the median reduction in compliance reporting time is forty-seven percent, based on a study of twelve similar firms,' that's a number procurement can engage with. Luna: Let's talk about the dark side. What about vendors that deliberately inflate the numbers? Lucas: It happens. There's a short-term benefit — you might close a deal — but the long-term cost is huge. If the customer implements the software and doesn't achieve the promised ROI, they'll churn, and they'll tell others. In enterprise SaaS, reputation is everything. The most successful vendors I know actually under-promise in the calculator. They set conservative baselines, and then they over-deliver. That builds trust and leads to expansions. Luna: That's a theme we've seen before: the best enterprise sales strategies are the ones that align incentives between vendor and buyer. Lucas: Yes. And I think the ROI calculator is a perfect example of that alignment done right. When done well, it's not a manipulation tool — it's a communication tool. It helps both sides agree on what value looks like, and then measure it after the sale. That's why some vendors now tie the calculator to a 'value realisation' dashboard that runs post-implementation. They track actual savings against the calculator's projections. Luna: That's a powerful feedback loop. It makes the sales team accountable for the promises they made. Lucas: Exactly. And it changes the conversation from 'buy our software' to 'let's achieve a specific business outcome together.' That's a fundamental shift in enterprise selling. Lucas: And here's something I find interesting: the best calculators are increasingly built by the product team, not the sales team. Product managers embed ROI logic directly into the software — so when a customer uses the product, they can see, 'This feature saved me X hours this month.' That data feeds back into the calculator for the next deal. Luna: So the calculator becomes a live product of customer usage data, not a static spreadsheet. Lucas: Exactly. Companies like Salesforce and Workday have been doing this for years. Their value engineering teams create detailed ROI models that integrate with customer data. A Workday rep can show a prospect how much time their HR team spends on manual data entry, based on benchmarks from thousands of implementations. That's hard to argue with. Luna: Let's zoom out. What's the single most important thing a vendor should get right when building an ROI calculator? Lucas: I'd say it's the baseline. If you don't accurately measure the current state — the 'before' — the entire calculus is suspect. You need to spend time with the prospect to understand their actual costs, not just use industry averages. That means asking questions like, 'How many hours per week does your team spend on X? What is the fully loaded cost of that time? What is the cost of a mistake or a delay?' The calculator should be a reflection of their reality, not a template. Luna: And if they don't know the answers? Lucas: Then the rep needs to help them figure it out. That's part of the value the rep brings. A good rep doesn't just sell software — they help the buyer build a business case. That's a consultative skill that can't be automated. And it's one reason why enterprise sales reps with strong analytical skills are in high demand. Luna: I think this is a good moment to step back and note something about the show itself. Lucas: What's that? Luna: We've been doing these episodes for a while now, and one thing I really appreciate is that we don't have advertisers. No sponsors, no mid-roll interruptions. It's just us digging into topics like this because we find them genuinely interesting. Lucas: That's intentional. We want the content to be the product. And the way that stays sustainable is through listeners who find value in it and choose to support it. There's a link — it's buy me a coffee dot com slash fexingo. That's the whole thing. No pressure, just if you want to help keep this ad-free. Luna: Yeah, exactly. And we mean that. So back to the ROI calculator — you mentioned Salesforce. How do they actually use it in their sales process? Lucas: Salesforce has a dedicated value engineering team that works with the sales reps on deals over a certain size. They'll spend a full day with the prospect's finance and operations teams, mapping out current costs and projected savings. The output is a detailed business case that goes into the procurement package. It's not uncommon for that business case to run fifty pages. Luna: Fifty pages? That seems excessive. Lucas: It does, but in a seven-figure deal, procurement wants every assumption documented. And Salesforce has found that deals with a formal value engineering engagement close at a higher rate and with larger deal sizes. The investment pays for itself. Luna: What about smaller vendors? They can't afford a value engineering team. Lucas: They can use tools. There are now SaaS platforms that automate ROI calculator creation — companies like ROI Builder and ValueCloud. You plug in your pricing, your typical customer profile, and some benchmark data, and it generates a calculator you can embed on your website or use in sales calls. The best ones allow real-time customisation during a call. Luna: So the barrier to entry has come down. Lucas: Yes. But the differentiator is still the quality of the data. A tool is only as good as the assumptions you feed it. If you use generic industry averages, you'll get a generic calculator. The vendors that win are the ones that invest in gathering real customer data and updating their benchmarks regularly. Luna: One more thing: how do you measure the effectiveness of an ROI calculator itself? Lucas: Good question. Some metrics: the time from calculator use to close — does it shorten the cycle? The win rate for deals where the calculator was used versus not. And the accuracy of the projections — if you track actual savings post-implementation, does the calculator's estimate hold up? That last one is the gold standard. Vendors that track that can continuously improve their models. Luna: And that continuous improvement creates a moat, because they have proprietary data on what works. Lucas: Exactly. It's a virtuous cycle. Better data leads to better calculators, which lead to more wins, which generate more data. For me, that's the real insight: the ROI calculator isn't just a sales tool — it's a strategic asset that compounds over time. Luna: Alright, so if you're building a B2B SaaS company today, what's the one action you'd take this week? Lucas: Audit your top ten deals from last quarter. For each one, ask: did we have a quantified ROI case? If not, why did we win? If you won without one, maybe you don't need it. But if you lost — and many of those losses were on price — an ROI calculator might have made the difference. Then start building one based on your actual customer outcomes, not your wishful thinking. Luna: That's practical. I think a lot of listeners will do that. Lucas: Hope so. Because the era of 'trust us, it's great' is over. Enterprise buyers want numbers. If you can't give them a number, they'll find someone who can.