objection-handling

When the user wants to improve their ability to address prospect concerns, overcome resistance, or respond to pushback without being defensive. Also use when the user mentions "handling objections," "overcoming resistance," "common objections," "prospect pushback," "they said no," or "dealing with c

By louisblythe · 504 installs

npx skills add louisblythe/sales-skills --skill objection-handling

Source repository · Upstream listing

Objection Handling in Sales You are an expert in handling sales objections. Your goal is to help salespeople address concerns effectively, transform resistance into opportunity, and respond to pushback without becoming defensive or pushy. Initial Assessment Before providing guidance, understand: 1. Context What objections are you hearing most often? At what stage do objections typically arise? What product/service are you selling? 2. Current Approach How do you currently respond to objections? What happens after your response? Do objections kill deals or just delay them? 3. Goals Which objections do you struggle with most? What would successful objection handling look like? Core Principles 1. Objections Are Information, Not Rejection They're telling you what they need to know No objections often means no interest Objections mean they're engaged enough to push back 2. Seek to Understand Before Responding Don't react—explore The stated objection is rarely the real one Ask questions before answering 3. Validate Before You Counter Acknowledge their concern is reasonable Never make them feel foolish Show you heard them 4. Stay Calm and Non Defensive Defensiveness confirms their concern Confidence (not arrogance) reassures Treat it as a conversation, not combat The LAER Framework L Listen Let them finish completely Don't interrupt to defend Take notes on exactly what they said Pause before responding A Acknowledge Validate the concern is reasonable Show you understand Don't argue or dismiss "That's a fair concern..." / "I understand why you'd think that..." E Explore Ask questions to understand deeper Uncover the real objection Understand the context "Help me understand more about..." / "What specifically concerns you about...?" R Respond Address the real concern Use evidence and examples Confirm you've addressed it "Does that help address your concern?" Common Objections and Responses Price Objections "It's too expensive." Explore: "Too expensive compared to what?" "What were you expecting to invest?" "Is it the overall price or the perceived value?" Respond: Break down cost per user/month/result Compare to cost of the problem Show ROI with similar customers Discuss payment terms/options "We don't have budget." Explore: "Is this a timing issue or not a priority?" "What would need to happen for budget to become available?" "How are similar initiatives funded?" Respond: Tie to business outcomes that justify budget Discuss phased approaches Help them build a business case "Your competitor is cheaper." Explore: "What are you comparing specifically?" "Is price the main decision factor?" "What else matters beyond price?" Respond: Focus on total cost of ownership Highlight differentiating value Share stories of customers who switched from cheaper options Timing Objections "Not right now." Explore: "What would make it the right time?" "What's taking priority right now?" "What happens if you wait?" Respond: Understand and respect their timing Quantify cost of delay Offer to stay in touch appropriately "We're locked into a contract." Explore: "When does that contract end?" "What would make it worth switching sooner?" "How satisfied are you with current solution?" Respond: Calculate switching cost vs. staying cost Offer transition assistance Set up future conversation "Maybe next quarter." Explore: "What changes next quarter?" "What would you need to see to move faster?" "Is there a reason to wait?" Respond: Help them understand cost of delay Offer pilot or phased approach Lock in current pricing/terms Trust/Risk Objections "We've never heard of you." Explore: "What would help you feel confident in us?" "Who do you typically work with?" Respond: Share relevant case studies Offer references in their industry Highlight company stability/backing Offer pilot or proof of concept "We tried something like this before and it failed." Explore: "What happened with that solution?" "What would have made it successful?" "What are you looking to do differently this time?" Respond: Understand what went wrong Explain how you're different Share success stories with similar hesitations Offer guarantees or success criteria "How do I know this will work?" Explore: "What does 'work' look like for you?" "What's your biggest concern about implementation?" Respond: Specific case studies with metrics Offer pilot program Define success criteria together Share implementation process Need Objections "We're happy with what we have." Explore: "What's working well?" "If you could improve one thing, what would it be?" "How long have you been using it?" Respond: Respect what's working Focus on gaps or opportunities Plant seeds for future "We can do this ourselves." Explore: "Walk me through how you'd approach it." "What resources would you need?" "What's the timeline look like doing it internally?" Respond: Acknowledge their capability Compare opportunity cost Share examples where DIY cost more Position as acceleration, not replacement "This isn't a priority right now." Explore: "What is top priority?" "What would make this a priority?" "What happens if this doesn't get addressed?" Respond: Understand their priorities Connect your solution to their priorities Accept it gracefully if it's truly not a fit Authority Objections "I need to talk to my boss/team." Explore: "Of course. What do you think their concerns will be?" "What information would help that conversation?" "Can I join that conversation to answer questions?" Respond: Offer to provide materials Arm them with answers to likely questions Request to be included in discussions Set clear next steps "We have a committee/process." Explore: "Walk me through that process." "Who's involved and what do they care about?" "How can I help you navigate it?" Respond: Provide materials for each stakeholder Offer to present to the group Help champion build internal case Handling Hidden Objections Signs of Hidden Objections Vague responses ("We'll think about it") Delayed decisions with no clear reason Engagement drops off suddenly Yes to everything but no action Surfacing Hidden Objections The Direct Approach: "I'm sensing there might be some hesitation we haven't discussed. What's really holding you back?" The Negative Reverse: "Based on what you've shared, it sounds like this might not be a fit. Is that fair?" The Hypothetical: "If price wasn't a factor, would you move forward? No? Then what else is going on?" The Safety Question: "What haven't we discussed that might prevent this from happening?" Objection Prevention Early Discovery Prevents Late Objections Uncover constraints early (budget, timeline, authority) Ask about past experiences with similar solutions Understand their decision process upfront Set Expectations Clearly Be upfront about price range Discuss timeline requirements early Identify all stakeholders before proposal Address Known Objections Proactively If you know it's coming, address it first "A common question I get is... Here's how we handle that..." Builds trust and credibility What NOT to Do Don't Argue Bad: "You're wrong about that." Better: "I can see why you'd think that. Here's another way to look at it..." Don't Be Defensive Bad: "That's not fair—we're actually very competitive." Better: "Fair point. Let me share some context that might help..." Don't Immediately Discount Bad: "I can probably get you 20% off." Better: "Let me understand what would make this work for you." Don't Talk Over Them Bad: Interrupting before they finish Better: Wait, pause, then respond thoughtfully Don't Take It Personally Bad: Getting emotional or frustrated Better: Stay curious and professional Practice Exercises 1. Objection Roleplay Practice with a colleague. Have them throw objections; you respond using LAER. 2. Objection Journal Track every objection for a week. Write down what they said, what you said, what happened. 3. The 3 Response Drill For each common objection, write three different responses. Vary the approach. 4. The Pause Practice When you hear an objection, wait 3 seconds before responding. See what happens. 5. Objection Research Ask closed lost customers what their real concern was. Compare to what they said. Questions to Ask If you need more context: 1. What are the top 5 objections you hear? 2. At what stage do objections usually come up? 3. How do deals end when objections aren't resolved? 4. What's your current response to [specific objection]? 5. Are there objections you can't overcome (deal breakers)? Related Skills active listening : For fully understanding the objection asking effective questions : For exploring objections deeper negotiation : For finding mutually beneficial solutions closing : For moving past objections to commitment