Objection Handler

Handles sales objections with proven response frameworks

Security Scan

This is an instruction-only sales objection helper that is internally consistent with its description and does not request credentials, binaries, or install any code.

Purpose & Capability

The name/description (sales objection handling) matches the SKILL.md content (LAER framework, objection categories, response templates). The skill requires no binaries, env vars, or config paths — which is proportionate for a conversation-guidance skill.

Instruction Scope

The runtime instructions are limited to conversational guidelines, follow-up questions, and response templates. They do not instruct the agent to read files, access environment variables, call external endpoints, or transmit data. No vague 'gather any context you need' language appears.

Install Mechanism

There is no install spec and no code files — the skill is instruction-only, so nothing is written to disk or fetched during install. README contains an external link to optional context packs, but SKILL.md does not require fetching it.

Credentials

The skill declares no required environment variables, credentials, or config paths. That is appropriate for a purely conversational, non-integrated tool.

Persistence & Privilege

always is false and the skill is user-invocable. disable-model-invocation is false (agent may invoke autonomously), which is the platform default — acceptable here because the skill has no elevated access or credential requests.

Assessment

This skill is instruction-only and appears safe: it only supplies templates and questions for handling sales objections and requests no secrets or installs. Before enabling it, consider whether you want the agent to be able to call the skill autonomously (it's allowed by default) and whether you’re comfortable with the agent using persuasive language in customer interactions. Also note README links to an external site for optional 'context packs' — those are outside this skill and would require you to visit or fetch content separately if desired.

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