Latest / Closing the Deal with Fexingo: Sales, Negotiation, and Revenue Conversations for Operators / The Sales Rep Who Won by Telling the Buyer He Was Wrong
Transcript
- Lucas: Today's episode starts with a deal that almost didn't happen, because the buyer was convinced they knew exactly what they needed — and they were wrong. Luna: Oof. Telling a buyer they're wrong. That's a risky move. How did it play out? Lucas: It was a B2B software rep I'll call Dana — selling a project management tool to a mid-size construction firm. The VP of operations came into the first meeting with a very specific requirement: they needed Gantt charts, resource leveling, and integration with their accounting system. Dana's product had none of that. Luna: So most reps would walk away, or try to sell around it. What did Dana do? Lucas: She asked why. The VP said, 'Because that's how we've always managed projects.' Dana asked if their current tool had all those features. The VP said yes. Then Dana asked, 'And are you happy with it?' The VP hesitated. Luna: That's a great opening. She's getting the buyer to admit there's a gap, without confrontation. Lucas: Exactly. The VP admitted that despite having all those features, they were still missing deadlines by an average of 18 days per project. So Dana gently pointed out that maybe the issue wasn't about features — it was about workflow discipline. She said, 'What if a simpler tool that enforces a clear process could actually reduce those delays?' Luna: But the VP still wanted Gantt charts. How did Dana handle that? Lucas: She didn't argue. She said, 'Let me show you something.' She pulled up a case study from a similar construction firm that had switched to Dana's tool and reduced delays by 40 percent. Then she offered a 14-day pilot with just three project managers — no Gantt charts, just a simple Kanban board and daily checklists. Luna: She let the data speak. That's classic challenger sale — teach, tailor, take control. Lucas: Right. The VP agreed to the pilot. After two weeks, the three project managers reported that they felt less overwhelmed and that handoffs were clearer. The VP still had doubts, but the pilot results were undeniable. They ended up buying a site license for $1.2 million over three years. Luna: So the key wasn't just being right — it was proving it in the buyer's environment, with their own people. Lucas: That's the takeaway. Dana told the buyer they were wrong, but she did it with evidence and a low-risk trial. She didn't say 'you are wrong' — she said 'here's a different way to think about it, and here's proof.' Luna: And the buyer respected her for it. That VP later told Dana that she was the only rep who challenged his assumptions. Everyone else just tried to match the spec sheet. Lucas: That's the thing — when you challenge respectfully, you build credibility. The buyer remembers you as the one who helped them see a blind spot. Luna: But there's a fine line. If you come across as arrogant, you lose the deal. Dana's approach was humble: she used third-party data, not her own opinion. Lucas: She also asked permission before challenging. She said, 'Would you be open to exploring a different approach?' That gave the VP psychological safety. Luna: I love that. It's like the doctor who says, 'I have a different theory — do you want to hear it?' Lucas: Exactly. And that's the framework for this episode: how to tell a buyer they're wrong without triggering their ego. Step one: surface the pain. Step two: present alternative evidence. Step three: offer a controlled test. Luna: Let's flesh that out. Surface the pain — what does that look like in practice? Lucas: You ask questions that make the buyer realize their current solution isn't working. For example: 'How much time does your team spend on status meetings?' Or 'What's your average project delay?' Get them to quantify the gap. Luna: And if they say 'everything is fine'? Lucas: Then you probably don't have a deal. But in Dana's case, the VP already knew there was a problem — he just assumed the fix was more features. Dana's job was to reframe the problem. Luna: Which leads to step two: present alternative evidence. What counts as good evidence here? Lucas: Third-party benchmarks, case studies from similar companies, analyst reports, or even a simple spreadsheet comparing outcomes. The key is that it's objective, not your opinion. Luna: And step three: the controlled test. That's the pilot, the proof of concept. It lets the buyer experience the new approach without committing fully. Lucas: Right. And it's crucial that the test measures what matters to the buyer. For Dana, it was time saved and reduced delays. She made sure the pilot produced numbers that the VP cared about. Luna: I want to talk about when this approach works best. It's not for transactional deals, right? Lucas: No. This is for complex B2B sales where the buyer has a strong opinion but the stakes are high. If you're selling a $50 widget, you don't challenge the buyer's worldview. But for a six-figure deal, the relationship can handle a thoughtful challenge. Luna: There's also a risk: you might be wrong. What if the buyer's original requirement actually was the right one? Lucas: Then you learn something. Dana did her homework — she talked to other customers in that industry before the meeting. She was confident the real problem was process, not features. But if you're not sure, you can still use the same framework but with a softer hypothesis: 'I wonder if...' rather than 'I think you're wrong.' Luna: Fair. So the skill is less about confrontation and more about intellectual honesty. You're trying to solve the buyer's problem, not win an argument. Lucas: Exactly. And if you do it right, you earn the right to close. Dana's deal closed in six weeks — faster than her average. Because once the VP saw the pilot results, the decision was obvious. Luna: That's a nice segue. If today's episode gave you a new way to think about handling buyer objections or a technique you might try, that's exactly why we do this show ad-free. We keep it that way through listener support at buy me a coffee dot com slash fexingo. It's a simple way to say this content moved your work forward. Lucas: Yeah, we appreciate that. It lets us focus on stories like Dana's without any sponsor noise. So if you've gotten value from Closing the Deal, that link is the way to keep it going. Luna: Now, back to the story. One thing I found fascinating is that after the deal closed, the VP actually asked Dana to present the pilot results to his board. He used her data to justify the switch to his CEO. Lucas: That's the holy grail — when your buyer becomes your champion because you made them look smart. Dana didn't just win a deal; she gained an internal advocate. Luna: So the next time you're in a meeting and the buyer says 'I need X,' maybe don't just nod. Ask 'why' and see if you can offer a better path. Lucas: And if you do it with respect and evidence, you might just close a deal that everyone else walked away from.