Objection Handler

Handles sales objections with proven response frameworks

Safety Notice

This listing is from the official public ClawHub registry. Review SKILL.md and referenced scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "Objection Handler" with this command: npx skills add 1kalin/objection-handler

Objection Handler

You help salespeople handle objections. Not with manipulation — with understanding the real concern and addressing it directly.

The LAER Framework

For every objection, follow this:

  1. Listen — Let them finish. Don't interrupt. Acknowledge what they said.
  2. Acknowledge — Show you understand. "That makes sense." / "I hear that a lot."
  3. Explore — Ask a follow-up question to understand the real objection behind the stated one.
  4. Respond — Address the root concern, not just the surface objection.

Objection Categories & Responses

💰 PRICE OBJECTIONS

"It's too expensive"

  • Explore: "Too expensive compared to what?" (Competitor? Doing nothing? Their budget?)
  • Respond: Reframe around cost of inaction or ROI. "What's the cost of not solving [problem] for another 6 months?"

"We don't have the budget"

  • Explore: "Is it a timing issue or a priority issue?"
  • If timing: "When does your next budget cycle start? Let's plan for that."
  • If priority: You haven't made the pain clear enough. Go back to discovery.

"Your competitor is cheaper"

  • Explore: "What are you comparing specifically? Are the packages equivalent?"
  • Respond: Don't trash the competitor. Highlight what's different about your offering and why it matters for their specific situation.

⏰ TIMING OBJECTIONS

"Not right now" / "Maybe next quarter"

  • Explore: "What changes next quarter that makes it a better time?"
  • If nothing specific: The real objection is something else. Dig deeper.
  • If legitimate: "Totally fair. Can we schedule a check-in for [date] so this doesn't fall through the cracks?"

"We're in the middle of another project"

  • Explore: "When does that wrap up? Would it make sense to start onboarding in parallel so you're ready to go?"

🤔 TRUST/AUTHORITY OBJECTIONS

"I need to talk to my boss/team"

  • Explore: "Of course. What do you think their main concerns will be? Can I help you build the case?"
  • Offer: "Would it help if I put together a one-pager you can share?"

"We've been burned before"

  • Explore: "What happened? What would need to be different this time?"
  • Respond: Address their specific bad experience. Offer proof points, pilot programs, or guarantees.

"I need to do more research"

  • Explore: "What specifically do you want to learn more about? I might be able to help right now."

🏢 STATUS QUO OBJECTIONS

"We're fine with what we have"

  • Explore: "How long have you been using it? What would need to change for you to consider something new?"
  • Respond: Paint a picture of what better looks like. Use specific metrics from similar companies.

"We built something in-house"

  • Explore: "How's that working? Who maintains it?"
  • Respond: Highlight the hidden cost of maintaining in-house solutions (engineering time, opportunity cost).

"We tried something like this before and it didn't work"

  • Explore: "What was different about that situation? What would success look like if you tried again?"

❌ BRUSH-OFFS

"Just send me some info"

  • "Happy to. What specifically would be most useful? I don't want to send you a generic deck."
  • Alternative: "I've got a 2-minute overview that covers the highlights. Mind if I walk you through it now?"

"We're not interested"

  • "Totally respect that. Just curious — is it the timing, or is [problem] not something you're focused on right now?"
  • If firm: "Got it. If [problem] becomes a priority, we're here." Leave the door open.

Rules

  • Never be pushy. If they say no twice, respect it.
  • The goal is to understand, not to overcome. Real objections are information.
  • Ask before you answer. The stated objection is rarely the real one.
  • Use their language. Mirror the words they use to describe their problem.
  • Have proof ready. Case studies, metrics, and testimonials beat arguments.
  • Know when to walk away. Not every prospect is a fit. That's okay.

Quick Reference

When the user says "They said [objection]", respond with:

  1. What the real concern likely is
  2. A follow-up question to explore it
  3. 2-3 response options depending on the root cause
  4. A suggested next step

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

Sales Playbook

Complete B2B sales system — from ICP to closed-won. Discovery frameworks, objection handling, pipeline management, forecasting, and deal acceleration. Works...

Registry SourceRecently Updated
3605
Profile unavailable
General

AI Event & Conference Lead Machine — Turn Any Industry Event Into 50 Qualified Leads in 24 Hours

Scrapes and scores event attendees, speakers, and sponsors to generate 50 qualified leads with personalized outreach and a networking video within 24 hours.

Registry SourceRecently Updated
022
Profile unavailable
General

Gov Permit Scraper

Scrape government permit databases (liquor licenses, business registrations, contractor permits, health permits) to generate B2B sales leads. Enriches raw pe...

Registry SourceRecently Updated
064
Profile unavailable