Latest / Sales Leadership with Fexingo: Quota Carriers, Sales Managers, and Revenue Teams / How Sales Reps Can Turn Customer Pushback Into Closed Deals
Transcript
- Lucas: There's a moment in almost every big B2B deal where the customer gives you an objection that feels like a wall. 'We're not ready,' 'Your price is too high,' 'We need to think about it.' And most sales reps instinctively do the wrong thing. Luna: They push back. They argue. They try to prove the customer wrong. Lucas: Exactly. And that almost never works. In fact, research from Gong, the conversation analytics platform, shows that when a rep responds to an objection by immediately presenting a counterargument, the likelihood of closing that deal drops by about 40 percent. Luna: Forty percent. That's huge. So what's the right move? Lucas: The best reps treat objections as information gaps, not resistance. They don't fight the objection; they get curious about it. There's a framework called 'objection deconstruction' that a lot of top-performing enterprise sales teams use, and it's surprisingly simple. Luna: Okay, lay it out for us. Lucas: It's three steps. Step one: validate the objection. Say something like, 'That's a fair concern, I've heard that from other teams.' Step two: ask a diagnostic question. 'Can you help me understand what specifically is driving that hesitation?' Step three: reframe the objection as a discovery opportunity. 'If we could address that concern, would that move us forward?' Luna: That third step is the key. Because you're not just deflecting the objection; you're using it to qualify the deal further. Lucas: Right. And the really good reps prepare for objections in advance. They don't wing it. I talked to a VP of Sales at a cybersecurity firm—let's call her Sarah—and she had her team build what they called an 'objection library.' They documented every objection they'd heard in the past year and wrote out a three-sentence response for each one. Luna: That's a lot of prep. But I can see why: if you've already thought through the response, you don't get flustered in the moment. Lucas: Exactly. And Sarah told me about a specific deal that was worth about $2 million in annual recurring revenue. The prospect was a large financial services firm. Everything was going well until the security team raised a concern about data residency. They said, 'We can't store our data on your servers.' Luna: That's a classic objection that can kill a deal if you don't handle it well. Lucas: Sarah's rep didn't panic. He validated the concern, then asked, 'What specific data residency requirements do you have?' It turned out the prospect's policy was more flexible than the security team initially thought. The rep was able to show them a configuration option that addressed their concern. The deal closed three weeks later. Luna: So the objection wasn't really about data residency. It was about a lack of information on the prospect's side. Lucas: Exactly. That's the insight. Objections are often just a signal that the customer doesn't have enough information to feel comfortable saying yes. Your job as a rep is to provide that information—not to argue. Luna: There's another common objection: 'We're not ready.' I've heard that one a lot. How do you deconstruct that? Lucas: That one is tricky because it can mean many things. Sometimes it means the decision-maker isn't fully bought in. Sometimes it means they have a competing priority. Sometimes it means they're afraid of making a mistake. The diagnostic question there is, 'What would need to be true for you to feel ready?' Luna: That's a great question. It forces the customer to articulate the gap. Lucas: Right. And once they articulate it, you can address it directly. I remember a deal where a prospect said they weren't ready because they were in the middle of a restructuring. The rep asked that question, and the prospect said, 'We need to finalize our budget for next quarter.' The rep was able to propose a phased implementation that aligned with their budget cycle. That deal closed six months later. Luna: So patience is part of it too. You don't always have to push for a close right away. Lucas: Exactly. Sometimes the best response is to step back and let the customer's timeline work in your favor. But you have to stay engaged. You can't just go silent. Luna: I want to come back to the objection library idea. How do you build one effectively? Lucas: Sarah's approach was straightforward. She had each rep log every objection they heard in a shared spreadsheet for three months. Then she categorized them: price, timing, competition, security, integration, and so on. For each category, the team brainstormed the best responses. They tested them in role-plays and refined them based on what worked. Luna: And that becomes a resource the whole team can use. New hires don't have to reinvent the wheel. Lucas: Exactly. And it also helps with coaching. If you see a rep struggling with a specific objection, you can pull up the library and say, 'Here's how other reps have handled this.' It's a concrete tool, not just abstract advice. Luna: It's interesting that you mentioned role-playing. I think a lot of sales teams skip that because it feels awkward. But the data shows it's one of the most effective ways to improve objection handling. Lucas: Absolutely. There's a study from the Sales Management Association that found teams that do regular role-playing outperform those that don't by about 20 percent in quota attainment. And it makes sense. You're building muscle memory for a high-pressure moment. Luna: So let's talk about the 'price is too high' objection. That's probably the most common one, and it's also the one that reps tend to handle worst. Lucas: Yeah, because it feels personal. But the best reps don't immediately drop the price. They ask, 'Compared to what?' Because often the customer is comparing your product to doing nothing, or to a cheaper solution that doesn't have the same capabilities. You need to understand the frame of reference. Luna: And then you can reframe the conversation around value. Show them the ROI of your solution versus the cost of the problem they're trying to solve. Lucas: Exactly. I saw a great example from a sales rep at a marketing automation company. The prospect said, 'Your software costs $50,000 a year. That's too much.' The rep asked, 'How much are you spending on manual lead processing right now?' The prospect estimated about $120,000 in labor costs. Suddenly, $50,000 looked like a bargain. Luna: That's a perfect reframe. You're not defending the price; you're showing the cost of not buying. Lucas: Right. And that's a skill you can develop. It's not about being naturally persuasive. It's about preparing those comparative numbers in advance. Another thing that helps is to ask for the objection in writing. 'Could you send me an email outlining your concerns?' That forces the customer to be specific, and it gives you time to craft a thoughtful response. Luna: That's a great tactic. It also shows the customer that you're taking their concern seriously. Lucas: Yes. And sometimes, when they put it in writing, they realize the objection isn't as strong as they thought. I've seen deals where the customer wrote the email and then said, 'Actually, never mind, we're good.' Luna: That's the ideal outcome. So, what about objections that are really deal-breakers? Like a regulatory requirement that your product genuinely can't meet? Lucas: Then you have to be honest. The worst thing you can do is overpromise and then fail to deliver. That destroys trust and kills future opportunities. But even then, you can ask, 'Is there a workaround or a phased approach?' Sometimes the customer will accept a partial solution. And if not, you qualify them out and move on. That's better than wasting time on a deal that will never close. Luna: That's a mature perspective. It's not about winning every objection; it's about finding the right customers. Lucas: Exactly. And speaking of finding the right approach, we've been having these conversations on Sales Leadership with Fexingo for fourteen episodes now. And something I'm proud of is that we've kept this show completely ad-free. No sponsor interruptions, no commercial breaks. That's intentional. Luna: Yeah, and it means the content is driven purely by what we think is useful for you, not by what an advertiser wants. We want to keep it that way. Lucas: If these conversations have moved your work forward in some small way, and you'd like to support that choice, the link is buy me a coffee dot com slash fexingo. No pressure, just an option for those who find value here. Luna: And now back to objection handling. One more thing I want to touch on: how do you handle objections in a group setting, like a presentation to multiple stakeholders? Lucas: That's a great question. In a group, objections can come from different people with different agendas. The key is to address each concern individually. Don't let one dominant voice derail the whole conversation. I recommend acknowledging the objection, then saying, 'I'd like to address that, but I also want to make sure everyone else's questions are heard. Can we go around the room?' That way, you get a full picture. Luna: And you avoid getting stuck in a one-on-one debate while the other decision-makers tune out. Lucas: Right. And after the meeting, follow up with each person individually. Often, people are more willing to share their real concerns one-on-one. That's where you can dig deeper. Luna: So the overarching theme is: objections are not obstacles; they're opportunities for discovery. If you approach them with curiosity instead of defensiveness, you'll close more deals. Lucas: Exactly. And the best part is, this is a skill you can practice and get better at. Start small. Pick one objection you hear often. Write out a three-step response. Role-play it with a colleague. Then try it in a real conversation. You'll be surprised how quickly it becomes second nature. Luna: I think that's a great note to end on. Thanks for listening. Lucas: Until next time, keep selling smart.