Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / How Enterprise Software Reps Use ROI Calculators Against Procurement
Transcript
- Lucas: If these conversations are useful for what you're building or running, stick with me for a second — I want to share something quick. Lucas: A small group of listeners already chips in monthly through buy me a coffee dot com slash fexingo, and that's really what keeps this show ad-free and independent. No sponsors, no pressure — just a handful of people who find the episodes worth a coffee. Luna: And it genuinely makes a difference. The team behind Fexingo puts a ton of research into every episode, and listener support is what lets them keep doing it without chasing advertisers. Lucas: Right. So if you're getting value from the show and want to help keep it going, that's the place. Otherwise, let's get into today's topic. Lucas: So here's something I've been watching closely — enterprise software reps are now showing up to first meetings armed with an ROI calculator that's pre-loaded with the prospect's own data. Luna: Wait, like they've done the math before the demo even happens? Lucas: Exactly. I'm talking about a custom spreadsheet or interactive web tool that takes the prospect's number of users, average salary, current tool costs, and spits out a projected savings number. And it's not just a rough estimate — it's granular. Workday, for example, has a calculator that factors in HR headcount reduction, payroll error rates, audit costs. Salesforce's latest version ties directly to the prospect's CRM data if they're already a customer. Luna: So the rep walks in with a number that says 'you will save $2 million over three years' before procurement has even written the RFP. That changes the entire conversation. Lucas: It does. Because now the negotiation starts from the vendor's baseline, not procurement's. The rep sets the anchor. Procurement's job becomes trying to disprove the model, which is harder than building their own from scratch. Luna: I've heard of procurement teams actually hiring data scientists to audit those models. Is that common? Lucas: More common than ever. I spoke with a procurement director at a large financial services firm — they now have a two-person analytics team whose sole job is to stress-test vendor ROI claims. They'll ask for the raw assumptions, run Monte Carlo simulations, and come back with a 'credibility score' for the vendor's business case. Luna: Monte Carlo simulations in procurement — that's a long way from the old days of 'can you give us 20 percent off list price?' Lucas: Exactly. And the vendors know this, so they're getting more sophisticated. ServiceNow's ROI calculator now includes a 'confidence interval' slider that adjusts the projected savings based on how aggressive the assumptions are. It's a really clever move — it makes the tool seem more transparent, but it also forces the prospect to engage with the vendor's logic. Luna: I want to get into the mechanics. How do these calculators actually build the number? Lucas: Let me give you a concrete example. Say a company has 5,000 employees and is considering a new HR platform. The calculator starts with the current cost per employee for HR admin — let's call it $150 per head per year. That's $750,000 annually. Then it factors in efficiency gains: the new platform automates benefits enrollment, onboarding, payroll integration. The vendor claims a 30 percent reduction in admin time, which translates to maybe $225,000 saved. Luna: But that's based on the vendor's internal benchmark, not the prospect's actual process. Lucas: Exactly right. And that's where the friction happens. A good procurement team will say, 'our current admin time is actually half what you've assumed, so your savings are overstated.' But the vendor's counter is, 'we're basing this on industry averages from our 10,000 customers — here's the data.' Suddenly you're arguing over methodology, not price. Luna: And the vendor has the home-field advantage because they control the model. Lucas: That's the key insight. The ROI calculator is a persuasion tool disguised as an analytical tool. It makes the vendor the expert on the prospect's own business. And by the time procurement gets involved, the business stakeholders — the VP of HR, the COO — have already seen a number that makes them want the software. Procurement ends up fighting not just the vendor, but their own internal teams. Luna: So how should procurement fight back? What's the counter-play? Lucas: The most effective one I've seen is requiring the vendor to submit their ROI model in an open format — Excel with unlocked cells, not a black-box web tool. Then procurement builds a parallel model using their own assumptions. If the vendor's number doesn't hold up under realistic inputs, they call it out early. I've seen deals die because the vendor's ROI fell from $2 million to $200,000 after adjusting for the prospect's actual churn rate or implementation timeline. Luna: So it's about taking control of the math. But not every procurement team has the resources to do that. Lucas: And that's exactly why vendors are pushing these calculators harder than ever. The asymmetry works in their favor. Smaller companies especially — they might not have a dedicated procurement analytics team, so they take the vendor's ROI at face value. I've seen startups sign three-year contracts based on a calculator that assumed they'd grow 50 percent year-over-year, and when growth slowed, they were stuck with a tool they couldn't fully utilize. Luna: That's a real risk. So what's the best practice for a company that wants to use these calculators without getting burned? Lucas: First, never let the vendor run the calculator live in a meeting without having your own numbers ready. Come with your current costs, headcount, process times — and challenge every assumption. Second, ask for a sensitivity analysis: what happens if growth is half what you projected? What if implementation takes four months instead of two? A good vendor will share that willingly; a less confident one will hedge. Luna: And I'd add: look at the implementation costs. A lot of calculators show dramatic savings in year two and three but gloss over the disruption and training costs in year one. Lucas: That's a great point. Implementation costs can eat up 30 to 50 percent of first-year savings. And the calculator usually assumes a perfect rollout with no hiccups. I've seen a deal where the vendor claimed 18-month payback, but the actual payback was 28 months when you factored in the two-month delay and the extra consulting fees. Luna: So the ROI calculator is a powerful starting point, but it's not the whole story. It's a negotiation tool, and both sides need to treat it as one. Lucas: Right. And the vendors who are winning right now are the ones who embrace that transparency. They give procurement the model, they talk openly about assumptions, and they adjust the numbers in real time during the negotiation. That builds trust and often leads to a faster close. Luna: I've seen that too. When a vendor says, 'here's our model, change whatever you want,' it's disarming. It makes you want to work with them. Lucas: Exactly. So the ROI calculator is here to stay. The question is whether you're using it as a weapon or a bridge. If you're a vendor, build it with integrity. If you're a buyer, question everything. Either way, the math is the new battlefield. Luna: And it's a battlefield that rewards preparation. I think we've given listeners a solid framework for entering that fight. Lucas: Absolutely. That's all for today. See you next time.