Latest / Closing the Deal with Fexingo: Sales, Negotiation, and Revenue Conversations for Operators / How One Rep Won by Asking for the Buyer's Internal Data
Transcript
- Lucas: All right, I want to tell you about a rep who closed a deal that was basically dead, and the weapon he used was the buyer's own internal data. Luna: Oh, I love this. Not a new feature, not a discount — just facts from the buyer's own house. Lucas: Exactly. So the scenario: a mid-market logistics company, we'll call them RouteCo. They were evaluating route optimization software. They had three vendors in the final round. Our rep's product was the most expensive by a solid 30 percent. Luna: Yikes. So he's the premium option in a commodity-feeling category. Lucas: Right. And the buyer's procurement team was leaning toward the cheapest option. The rep's champion inside RouteCo — a mid-level operations manager — was getting nervous. She said, 'Look, I love your product, but I can't justify the price difference to my CFO. I need something concrete.' Luna: So the rep asked for something unusual. Lucas: He asked for the raw route data from the previous quarter. Not aggregated reports, not summaries. He wanted the actual driver logs, delivery times, fuel consumption per route, and the queue of unassigned orders. Luna: And the buyer just handed that over? That's pretty sensitive. Lucas: The champion trusted him, and she was desperate. Plus, he framed it as 'help me build a case for you.' He said, 'If I can show, using your own numbers, that my software would reduce your cost per delivery by at least 15 percent, will you at least keep me in the running?' She agreed. Luna: So he's not asking for a commitment to buy. He's asking for a commitment to look at the evidence. Lucas: Exactly. So he takes the data — about 12,000 delivery records — and runs it through a model. He finds that RouteCo's current system has a 22 percent rate of inefficient routing: drivers crisscrossing the same zone, empty backhauls, priority orders being delayed because of poor sequencing. Luna: And he quantifies the dollar cost of that inefficiency. Lucas: He calculates that fixing those specific gaps would save RouteCo roughly $340,000 per year in fuel and overtime. The price difference between his product and the cheap alternative was $120,000. So the net benefit of going with him was $220,000. Luna: That's a no-brainer once you see it. But the cheap vendor never showed that math because they didn't have the data. Lucas: Right. And the rep didn't just send a spreadsheet. He scheduled a meeting with the champion and the CFO. He put the data side by side: 'Here are your actual routes from Q2. Here's the cost. Here's where the waste is. Here's how my system would re-route each of those problem deliveries.' Luna: I bet the CFO's ears perked up when he saw his own numbers on the screen. Lucas: The CFO said, 'This is compelling, but how do I know these savings are real and not just theoretical?' The rep had an answer: he offered a 90-day pilot with a money-back guarantee if the savings didn't hit 10 percent. That was bold. Luna: That de-risks the decision completely. The CFO can say yes without looking foolish if it fails. Lucas: And that's exactly what happened. They signed a one-year contract with a clause that if the pilot didn't deliver, they could cancel. But the rep knew the data was solid. Within 60 days, RouteCo saw a 14 percent reduction in fuel cost per delivery. The CFO became an internal evangelist. Luna: So the key lesson: the rep didn't sell his product. He sold the buyer's data back to them, with a story. Lucas: Exactly. And I think that's a deeper principle. Most salespeople present their own features. The best ones present the buyer's reality, with a fix attached. Luna: It also builds massive trust. Because you're not hiding anything. You're saying, 'Look, your own numbers tell you this is worth it.' Lucas: Yeah. And that leads me to a question: how do you ask for that kind of sensitive data without sounding like you're snooping? The rep in this story had a specific framing. Luna: What did he say exactly? Lucas: He said, 'I want to help you build the business case internally. To do that, I need to see what you're working with. Would you be comfortable sharing your route logs from last quarter? I'll sign an NDA.' Luna: So it's collaborative. He's not demanding. He's offering to do work for them. Lucas: Right. And he made it concrete: 'I need this specific dataset for this specific analysis.' Not 'give me all your data.' That matters. Luna: I think a lot of reps are afraid to ask for data because they think the buyer will say no. But if you have a relationship, and you frame it as helping them, most buyers will say yes. Lucas: And if they say no, that tells you something too. It tells you they're not really invested in finding the best solution. They might just be price shopping. Luna: That's a good filter. If they won't share the data, they're not serious about optimizing. Lucas: Exactly. Now, there's a second layer to this story. After the deal closed, the rep told me that the real breakthrough wasn't the data analysis itself. It was the question he asked before he even looked at the data. Luna: What was that? Lucas: He asked the champion: 'What metric does your CFO care about most? Is it cost per delivery, on-time percentage, or something else?' She said it was cost per delivery. So he designed his entire analysis around that one number. Luna: That's smart. He didn't try to impress with ten different metrics. He focused on the one that mattered to the decision-maker. Lucas: Right. And he knew that if he could move that number, the CFO would listen to anything else he said. So he built the case around a single KPI. Luna: I think that's a great takeaway for any salesperson: before you crunch numbers, find out which number the buyer is measured on. Lucas: Absolutely. And honestly, if this episode moved your thinking forward in some small way, that's the link — buy me a coffee dot com slash fexingo. Listener support is what keeps these conversations ad-free and focused on real tactics. Luna: Yeah, it's a tiny gesture that makes a big difference for us. We appreciate it. Lucas: So back to the data question. I want to dig into one more angle: how do you handle it when the buyer's data actually shows your product isn't a good fit? That takes guts. Luna: Have you seen a rep do that? Lucas: I have. A friend of mine sells inventory management software. He asked a retailer for their stock-out data. After analyzing it, he realized his product would only solve 40 percent of their problem. The other 60 percent was a supply chain issue his software couldn't touch. Luna: Ouch. So what did he do? Lucas: He told them the truth. He said, 'My product will help with these three specific stock-out causes, but you also need to fix your supplier lead times. Here's a consultant I can recommend for that.' Luna: That's risky. He could have lost the deal entirely. Lucas: He almost did. The buyer appreciated the honesty, but they put the project on hold for six months while they fixed the supply chain. But when they came back, they bought from him without even evaluating competitors. Luna: So the honesty paid off in the long run. But it took patience. Lucas: Exactly. And that's the flip side of using buyer data. You have to be willing to walk away if the data doesn't support your product. Otherwise, you lose credibility. Luna: I think that's what separates a true consultant from a typical salesperson. A consultant tells you what you need, even if it's not their product. A salesperson tells you what they have. Lucas: Right. So to wrap it up: ask for the data, find the metric that matters, build the case around it, and be honest about what your product can and can't do. That's how you win with the buyer's own numbers. Luna: And you might just turn a CFO into a champion. Lucas: Yeah. That's a good place to leave it for today.