Latest / Closing the Deal with Fexingo: Sales, Negotiation, and Revenue Conversations for Operators / How One Rep Won by Bringing a Cost-Benefit Analysis
Transcript
- Lucas: So there's a moment in almost every B2B deal where the buyer looks at your price, then looks at the competitor's price, and says, 'Why should I pay 30 percent more?' And most reps answer with a feature list. But there's a better move. Luna: Let me guess — you're about to say 'bring a cost-benefit analysis.' Lucas: Exactly. But not just any analysis. I'm talking about a one-page spreadsheet you build during the discovery phase, then present at the final meeting — before you give your price. I've seen this single tactic increase deal size by 20 percent on average. Luna: Okay, I'm intrigued. Give me a real example. Lucas: Last year I worked with a SaaS company selling a project management tool. Their price was $50,000 a year. The competitor was $38,000. The rep was losing to price every time. So we built a cost-benefit sheet that compared not just features, but the total cost of adoption — implementation time, training hours, error rates, integration costs. Luna: And what did the sheet show? Lucas: The competitor's tool required 80 hours of implementation. Ours required 20. Their training was 40 hours per team member; ours was 10. Their error rate — because of a clunky interface — was 15 percent on task assignments. Ours was 3 percent. When you added all that up, the total cost of switching to the competitor was actually $72,000 over the first year. Our $50,000 looked cheap. Luna: So the rep essentially reframed the conversation from 'our software costs X' to 'here's what it really costs to use either option'. Lucas: Right. And the key was that the rep didn't just show the sheet and say 'see, we're better.' He walked the buyer through it. He asked them to validate each number. 'Does 80 hours of implementation sound right for your team?' That turned the sheet into a collaborative tool, not a sales weapon. Luna: But doesn't this only work if you have hard data? What if you're selling a new category where there's no baseline? Lucas: You can still build the sheet using the buyer's own estimates. Ask them during discovery: 'How many hours does your team spend on X per week? What's the average cost of a mistake?' They'll give you rough numbers. You use those as your assumptions. That makes the analysis even more credible because it's their data. Luna: So you're essentially co-creating the ROI model with the buyer over the course of the sales cycle. Lucas: Exactly. And there's a specific structure that works. Top of the sheet: the two options — your product versus the status quo or a competitor. Then three rows: upfront costs, ongoing costs, and benefit line. The benefit line is where you put the value of time saved, reduced errors, increased revenue. You want the total benefit minus total cost to show a 3x return within 12 months. Luna: 3x within 12 months — that's your threshold? Lucas: Yeah. If the buyer can't see at least a 3x return in the first year, the deal either isn't a fit or you haven't quantified correctly. I've seen reps try to force a 1.5x return and the buyer just says 'that's not worth the risk.' You need a clear multiple. Luna: What about the objection 'these numbers are made up'? I've had buyers push back on the assumptions. Lucas: That's actually a good sign — it means they're engaged. When that happens, don't defend. Say 'Great, let's adjust them. What number would you use?' Then you change the cell together. That's when the buyer starts owning the analysis. I've closed deals where the buyer literally took the spreadsheet, changed a few assumptions, and then said 'Okay, at these numbers it makes sense.' Luna: So the spreadsheet becomes a negotiation tool. But let's talk about the timing. You said present it before your price. Why? Lucas: Because if you show the value first, the price becomes a logical conclusion. If you show the price first, you're fighting against a number. In that SaaS deal, the rep presented the cost-benefit sheet, walked through it, and at the end the buyer said 'So what does your software cost?' He said '$50,000 a year.' The buyer didn't flinch. He just said 'That makes sense.' Luna: And how did that compare to the competitor's process? Lucas: The competitor just sent a proposal with features and a price. No analysis. The buyer later told our rep, 'Your competitor never helped me think about the total cost. They just gave me a number.' Luna: So the cost-benefit analysis also builds trust. It shows you understand their business beyond just the software. Lucas: That's the hidden benefit. When you show a well-researched sheet, you're signaling that you've done the homework. You're not just a salesperson — you're a consultant. That alone can differentiate you in a commodity market. Luna: Are there any risks? I'm thinking of situations where the analysis might reveal that your product isn't a good fit. Lucas: Absolutely. And that's a feature, not a bug. If the numbers don't add up, you shouldn't push the deal. I've had reps tell me they built a sheet, realized the ROI wasn't there, and actually recommended the buyer stay with their current solution. That buyer remembered them and came back six months later when the situation changed. Luna: So it's also a qualification tool. If you can't build a compelling case, you know not to waste your time. Lucas: Exactly. I'd rather lose a deal early than chase a bad fit for three months. Now, there's one more nuance: how you present the sheet. I recommend a physical copy — one page, printed. Bring two pens. Hand it to the buyer and let them read it in silence for 30 seconds. Then say, 'Let's walk through this together.' Luna: Why printed? Why not a screen share? Lucas: A printed sheet commands attention. It's a physical artifact. The buyer can write on it, circle numbers, take notes. It becomes their document. I've had buyers keep that sheet on their desk for weeks after the meeting. A screen share disappears when you close the laptop. Luna: That's a great tip. I also like the 'two pens' detail — you're inviting them to co-own it. Lucas: Right. And the final piece: after they sign off on the analysis, assume you have the deal. Say 'Great, so it looks like this makes financial sense. Let's talk about what a smooth implementation would look like.' You've already closed the value conversation. Now you're just negotiating logistics. Luna: And if they still bring up price? Lucas: Then go back to the sheet. Ask them which assumption they disagree with. Usually it's one number. Adjust it and see if the ROI still holds. Nine times out of ten, it does. Luna: What about enterprise deals with procurement? They're trained to ignore value and focus on line items. Lucas: Procurement is tough. But even they respond to a clear comparison. I've seen reps print a version of the sheet that strips out assumptions and just shows hard costs — implementation, training, integration, support. Procurement can't argue with those numbers if they're from the buyer's own estimates. Luna: So the analysis has to be tailored to the audience. For the economic buyer, focus on ROI. For procurement, focus on total cost of ownership. Lucas: Exactly. You can have two versions of the same sheet. One page, different emphasis. Just make sure the numbers are consistent. Luna: I want to try this in my next deal. But I'm nervous about building the sheet from scratch. Any template? Lucas: Simple template: three columns — 'Current State', 'Option A ', 'Option B '. Rows: Implementation Cost, Annual Subscription, Training Cost, Integration Cost, Maintenance Cost, Benefit Line. Then a total row at bottom. The key is to never leave a cell empty. If you don't have data, put a dash and say 'we can estimate'. Luna: And the benefit line — how do you quantify something like 'time saved'? Lucas: Ask the buyer: 'How many hours per week does your team spend on manual reporting?' They'll give you a number, say 10 hours. Multiply by hourly cost, say $50. That's $500 per week, $26,000 per year. If your tool automates that, you can claim at least 80 percent savings, so $20,800 benefit. That's a real number. Luna: Okay, that's straightforward. I'm sold. One more question: how do you handle the situation where the buyer says 'we'll do our own analysis'? Lucas: Great question. Don't compete with their analysis. Instead, say 'That's smart. Can I share my assumptions so we're aligned? Then when you do yours, you can validate them.' That way you stay involved in the process. And you can offer to help them build their model. Luna: So you become a resource, not a push. Lucas: Exactly. And that's the whole philosophy behind the cost-benefit analysis. It's not about tricking the buyer. It's about helping them see the full picture. Most buyers want to make the right decision. They just don't have all the data. You provide it. Luna: That's a solid takeaway. I'm going to start building a template this week. Lucas: If these conversations have helped sharpen your approach, and you'd like to support the show staying ad-free, you can always buy us a coffee at buy me a coffee dot com slash fexingo. No pressure — just a way to keep these episodes coming. Luna: Yeah, and it genuinely helps us invest more time into finding these tactics and bringing you real examples. We appreciate everyone who's ever chipped in. Lucas: Alright, back to the sheet. The last thing I'll say is this: don't overcomplicate it. A one-page cost-benefit analysis, built with the buyer's input, presented on paper before the price — it's simple, but it works. Try it on your next deal and see what happens. Luna: I will. And I'll report back. Thanks, Lucas. Lucas: Thanks, Luna. That's it for this episode of Closing the Deal. Go build that sheet.