Objection Handling

Real-time objection detection and response coaching with proven frameworks for the most common sales objections. This skill classifies objections by type, suggests contextual responses, and helps reps maintain control of the conversation when prospects push back.

When to Use This Skill

Use this skill when the user:

• Receives an objection during a live call or email and needs an immediate response strategy
• Wants to prepare for likely objections before an important meeting
• Needs to practice handling objections through role-play scenarios
• Wants to analyze win/loss patterns related to specific objection types
• Is building an objection response library for their team

What This Skill Does

When the user shares an objection, first classify it into one of five categories:

• Price: "It's too expensive," "Competitor X is cheaper," "We don't have budget"
• Timing: "Not right now," "Let me think about it," "Call me next quarter"
• Authority: "I need to check with my boss," "This isn't my decision"
• Need: "We already have a solution," "This isn't a priority," "I don't see the value"
• Competition: "We're going with Competitor X," "How are you different from Y?"

Classification matters because the response framework differs by category. A price objection requires value framing. A timing objection requires urgency creation. An authority objection requires stakeholder mapping. Do not use a generic "I understand your concern" response for every type.

Apply the Reframe-Proof-Bridge framework for all responses:

1. Reframe: Acknowledge the objection and reframe it as a valid concern that your solution addresses. Never dismiss or argue.
2. Proof: Provide specific evidence — a customer story, a data point, a case study — that directly addresses the concern.
3. Bridge: Transition back to the conversation with a question that moves the deal forward.

Anti-Pattern: "The Feature Dump Response" When a prospect says "We already have a solution for this," the wrong response is listing every feature that differentiates your product. The right response is asking what they wish their current solution did better. Lead with curiosity, not with a pitch. The prospect told you they have a solution — they did not ask you to compare features.

Anti-Pattern: "Accepting the Stall" "Let me think about it" is not a real objection — it is a stall that masks the real concern. Never respond with "Sure, I'll follow up next week." Instead, acknowledge and probe: "Totally fair — when you say you want to think about it, is it more about the timing, the pricing, or whether this is the right fit for your team?" Surface the real objection so you can address it.

When running practice sessions, simulate a realistic buyer persona. Generate objections in sequence, increasing in difficulty. After each response from the user, provide coaching feedback: what worked, what could be stronger, and a suggested alternative response. Score each response on a 1-5 scale across acknowledgment, evidence quality, and bridge effectiveness.

For objection preparation before meetings, generate the 3-5 most likely objections based on deal stage, buyer persona, and competitive context. For each, provide a prepared response using the Reframe-Proof-Bridge framework.

Example Prompts

• "The prospect just said 'we already have a solution for this' — what should I say?"
• "Help me prepare responses for pricing objections on a $50K deal"
• "Run an objection handling practice session for a VP of Engineering persona"
• "What's the best way to handle 'let me think about it' at the end of a demo?"