How a Rep Closed by Asking the Buyer to Teach Them

Lucas: So we talk a lot on this show about what you say to close a deal. But this episode is about what you ask - specifically, asking the buyer to teach you something. Luna: You mean like, 'Explain your process to me'? That feels almost counterintuitive. You're supposed to be the expert. Lucas: Right, and that's exactly why it works. There's a well-documented cognitive bias called the protégé effect - when you teach someone, you actually become more invested in their success. But we'll get to the psychology. Let me start with the specific case. Luna: Please. I want the real email. Lucas: So this is a rep selling a compliance workflow platform - think mid-six-figure annual contract, seven-figure total value over three years. The buyer is a director of compliance at a regional bank. The deal has been stuck for six weeks after the demo. The procurement team keeps asking for pricing breakdowns and competitor comparisons. Luna: Classic stall pattern. They're using analysis as a shield. Lucas: Exactly. So the rep sends a very short email - I've seen the text. It says, 'I realize I may be overcomplicating this. You've obviously thought deeply about how your team deploys compliance tools. Could you spend ten minutes walking me through your actual deployment process - specifically how you sequence the rollout across branches? I want to make sure I'm not missing anything that would make our solution a bad fit.' Luna: That's smart. He's not asking for a meeting to pitch again. He's asking to be taught. Lucas: The buyer agrees. They schedule a 15-minute call. What happens next is the key move - and this is where most reps would screw it up. Luna: By pitching again. Lucas: Exactly. But this rep doesn't pitch. He takes notes. He asks clarifying questions. He says 'That makes sense' and 'I hadn't considered that.' He treats the buyer as the authority. At the end of the call, he says, 'Based on what you've described, I think our platform actually aligns with your sequencing better than I realized. Would it be useful for me to send you a one-page diagram showing how our deployment maps to the process you just walked me through?' Luna: And the buyer says yes. Because now it's not a sales asset - it's a custom artifact built from their own thinking. Lucas: Exactly. The rep sends the diagram. Three days later, the buyer schedules a call with their steering committee and asks the rep to present the same walkthrough - but this time, the buyer introduces it. 'I asked him to map our process, and here's what he came back with.' The deal closes seven days after that. Luna: So the teaching request flipped the dynamic. The buyer went from gatekeeper to sponsor. Lucas: That's the protégé effect in action. When you ask someone to teach you, you're signaling that you value their expertise. That creates a subtle debt - the buyer wants to see you succeed because they've invested time in you. It's a form of cognitive commitment. Luna: There's also a cognitive fluency angle. When you ask someone to explain something in their own words, they become more fluent with the information. It reinforces their own belief in the solution. Lucas: That's a great point. The buyer literally becomes more confident in their own reasoning because they've articulated it out loud. There's research from Carnegie Mellon showing that people who explain a product to someone else rate it higher on features they've taught - even if the features were neutral before. Luna: So the rep effectively let the buyer sell themselves. Lucas: Right. But this only works if you're genuinely curious. If you fake it, the buyer will sense it. The rep I spoke to said he actually didn't understand the deployment sequencing when he asked - he was genuinely confused. That authenticity is nonnegotiable. Luna: When does this tactic backfire? Lucas: If the buyer is time-pressed and transactional. If they're a procurement officer whose job is to commoditize vendors, asking to be taught can feel like a waste of time. It works best with domain experts - people who take pride in their knowledge. Luna: So it's a compliance director, not a sourcing manager. Lucas: Exactly. And it works better in complex deals where the buyer has to coordinate internally. If it's a simple $5,000 subscription, just send the proposal. But for anything with multiple stakeholders and a deployment phase, the teaching request can be the unlock. Luna: Let me ask a practical question. What's the exact language you'd use in an email? I want the template, not just the concept. Lucas: You start with a concession - 'I may be overcomplicating this.' That lowers defensiveness. Then you state the specific area you want to learn about - not 'tell me about your company,' but something narrow like 'how you sequence rollout across branches' or 'how you evaluate vendor risk post-implementation.' Then you add the qualifier: 'I want to make sure our solution is actually a good fit.' Luna: And on the call, you actually take notes. You don't interject with features. Lucas: Correct. The hardest part for most reps is staying quiet. But the payoff is that the buyer becomes your champion. They'll start using your language - the language they helped create - with the steering committee. Luna: There's also a reciprocity element. By giving the buyer the gift of deference, you earn the right to ask for something later - like that one-page diagram. Lucas: Exactly. And the diagram itself is a subtle closing tool. Because once the buyer sees their own process mapped to your product, the gap between where they are and where they could be becomes visual. It's harder to ignore. Luna: I want to test this. I've got a deal right now with a manufacturing company - the IT director is a former engineer. He loves explaining architecture. I think this would work with him. Lucas: Engineers especially. They often feel that salespeople don't understand their complexity. Asking to be taught is almost a relief - it shows you respect their depth. Just make sure you pick a genuinely interesting question. Something you actually want to know. Luna: So if I'm a rep listening right now, what's the one takeaway? Don't send another proposal. Send an email asking to be taught. Lucas: And if the buyer says yes, resist the urge to sell. Just learn. The sale happens in the follow-up - the diagram, the summary, the acknowledgment. That's where you reassert your expertise without undermining theirs. Luna: Before we wrap, one more thing. If this episode actually gave you a tactic you're going to use this week, that's exactly why these conversations stay ad-free. If it's useful to you, the way to keep that going is listener support - buy me a coffee dot com slash fexingo. We don't run ads, so it's genuinely how the show exists. Lucas: Yeah, and that's a low-bar way to say 'this mattered.' No pressure, just an invitation. Okay - back to the tactic. One more nuance I want to mention: timing. Luna: When do you send that email? After the demo? After the proposal? Lucas: The sweet spot is after you've presented a proposal and the buyer is stalling. They've seen the product. They have the pricing. But they're not deciding. That's the moment to pivot to teaching mode. It gives you a reason to re-engage without being pushy. Luna: And it works even if you've already had multiple conversations? Lucas: Yes - as long as you pick a genuinely unresolved question. Maybe you don't understand how they'll handle change management across departments. Maybe you're fuzzy on their compliance audit cycle. If you've been selling for a while, there's always something you don't fully grasp. That's your entry point. Luna: So the move isn't about convincing - it's about creating a collaborator. Lucas: Exactly. And once the buyer becomes a collaborator, they have a stake in the deal closing. They've taught you. They've invested. Now they want to see you win.