Closing the Deal with Fexingo · 2026-07-02 · 8 min
Key moments - from our scoring
Substance score
52 / 100
Five dimensions, 20 points each
Dana, a project management software sales rep, faced a VP of operations convinced his construction firm needed Gantt charts, resource leveling, and accounting integration - features her product lacked. Rather than walk away or accommodate, Dana asked diagnostic questions that surfaced the real problem: despite having all those features in their current tool, the firm was still missing deadlines by an average of 18 days per project. She reframed the issue from missing features to missing workflow discipline, presented a case study from a similar construction firm that reduced delays 40% with a simpler tool, and offered a low-risk 14-day pilot with just three project managers using a Kanban board instead. The pilot proved her hypothesis - project managers felt less overwhelmed and handoffs improved - leading to a $1.2 million three-year site license. The approach hinges on three steps: surfacing quantified pain (status meeting time, project delays), presenting objective third-party evidence rather than opinion, and enabling a controlled test that measures outcomes the buyer actually cares about. This works best in complex, high-stakes B2B deals where the relationship can withstand intellectual challenge, and requires doing homework beforehand to be confident in your hypothesis.
Ask diagnostic questions to surface and quantify their actual pain, then present objective third-party evidence (case studies, benchmarks) showing an alternative approach, and offer a controlled pilot or proof of concept they can test with their own team before committing.
Instead of matching the spec sheet or walking away, Dana reframed the buyer's problem from missing features to missing workflow discipline, backed it with a real case study from a similar construction firm, and gave the VP psychological safety by asking permission before challenging his assumptions.
Do homework first by talking to similar customers in that industry; this approach works for complex, high-stakes B2B deals (six figures and above) where the relationship can handle intellectual challenge, not for transactional deals.
The pilot must measure outcomes the buyer actually cares about - in Dana's case, reduced project delays and team clarity - not just feature adoption; the three-week test with three project managers generated undeniable data that justified the larger decision.
Step one: surface the pain by asking questions that quantify the gap (e.g., 'How much time do status meetings take?' or 'What's your average project delay?'); step two: present alternative evidence that's objective, not opinion-based; step three: offer a controlled test with low commitment.
Our reviewer’s read on each dimension, with quotes from the episode.
The episode presents a coherent three-step framework (surface pain, present evidence, controlled test) and highlights some useful tactical moves (asking 'why,' using third-party data, offering psychological safety). However, it relies heavily on a single anecdote and spends considerable time on narrative setup rather than drilling into why these tactics work or exploring nuance. The framework itself is relatively straightforward and won't surprise experienced sales operators.
Step one: surface the pain. Step two: present alternative evidence. Step three: offer a controlled test.
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?'
The core idea - using evidence and a pilot to challenge buyer assumptions respectfully - echoes established challenger sales methodology (Brinker/Miller) that has been widely circulated. The psychological safety framing ('Would you be open to exploring a different approach?') is sound but not novel. The episode presents these ideas as a coherent narrative rather than as fresh or contrarian thinking.
That's classic challenger sale - teach, tailor, take control.
She used third-party data, not her own opinion.
This episode features no actual guest; it is a dialogue between two hosts (Lucas and Luna) discussing a second-hand anecdote about an unnamed sales rep ('Dana'). There is no practitioner with verified track record, no founder or operator of scale sharing direct experience, and no credibility beyond the hosts' retelling of a story. This significantly weakens guest caliber.
It was a B2B software rep I'll call Dana
The VP of operations came into the first meeting with a very specific requirement
The episode includes some concrete details: the $1.2M three-year deal size, the 18-day average delay reduction to 40 percent, the 14-day pilot window, and the Kanban board vs. Gantt chart trade-off. However, the underlying case study is anonymized and unverifiable ('Dana,' 'construction firm'), and there's no hard data on win rate, deal cycle time benchmarking, or comparative outcomes across different buyer types. The numbers present are illustrative rather than backed by rigorous evidence.
They ended up buying a site license for $1.2 million over three years.
missing deadlines by an average of 18 days per project
Luna and Lucas engage in natural back-and-forth with occasional genuine follow-ups ('But the VP still wanted Gantt charts. How did Dana handle that?'), and Luna probes for nuance ('There's also a risk: you might be wrong'). However, the conversation rarely pushes into uncomfortable territory, challenges assumptions made by either host, or asks difficult questions about when this approach might fail. The dialogue feels more like affirmation than inquiry; neither host seriously tests the other's claims or asks for counter-evidence.
So most reps would walk away, or try to sell around it. What did Dana do?
But there's a fine line. If you come across as arrogant, you lose the deal.
Computed from the transcript - who did the talking, and the words that came up most.
Episode 87 of Closing the Deal with Fexingo tells the story of a B2B software rep who closed a $1.2 million deal by respectfully telling the prospect they were wrong about their own needs. Lucas and Luna break down the technique of 'challenging with evidence' - using third-party data, customer testimonials, and a product pilot to reframe a buyer's false assumption. They discuss when confrontation works, how to avoid ego clashes, and why this approach builds long-term trust even if it risks killing the deal. The episode ends with a reflection on the difference between being right and being effective. #ChallengerSale #SalesTechnique #B2BSales #ClosingDeals #SalesRep #ConsultativeSelling #ObjectionHandling #SalesPsychology #RevenueGrowth #EnterpriseSales #TrustBuilding #SalesPilot #CustomerEvidence #Business #SalesTips #BusinessPodcast #FexingoBusiness #ClosingTheDeal Keep every episode free: buymeacoffee.com/fexingo
Transcribed and scored by The B2B Podcast Index.
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.
Other episodes covering the same guests and topics, from across The B2B Podcast Index.
How to Sell More by Boosting Customer Confidence - Outside Sales Talk with Brent Adamson and Karl SchmidtOutside Sales Talk · on Challenger Sale83 / 100
How We Turn Angry Clients Into Loyal Advocates w/ Rob Zambito CEO of Success Scaled ConsultingThe Customer UnSuccess Podcast · on sales objection handling78 / 100
E40 From Burnout To BlueprintBust and Beyond · on Gantt charts75 / 100
Tool selection and the unpredictable variableContent Operations · on Proof of concept73 / 100
How Fear Controls the Way We Lead, Sell, and Parent with Bryan PostMake It Happen Mondays · on Challenger Sale71 / 100
How to Pitch Your Product Idea the RIGHT Way
Pitch to Product · on Proof of concept69 / 100
The Rep Who Won by Asking for a 20 Percent Price Cut69 / 100How a Rep Won by Negotiating Against Their Own Offer86 / 100How One Rep Closed by Asking the Buyer for a Competitor Comparison81 / 100How One Rep Closed by Asking the Buyer to Fire Their Vendor80 / 100The One Question That Won a Deal by Paying the Buyer70 / 100