Objection Map

Most objection handling fails because it counters the stated objection instead of reframing it. The Price objection is usually a value objection. The Timing objection is usually a fear objection. Countering the stated form creates resistance. Asking the right question first reveals what the objection is actually protecting. This skill maps all five categories — price, timing, authority, need, trust — with a diagnosis (logic vs emotion), the reframe question to ask before you say anything, the talk track for after you hear the answer, and a 2-3 sentence copy version to handle it proactively in your pricing page, proposal, or email.

1. Click "Copy prompt" above and paste it into Claude or ChatGPT to start the session.
2. To map all five objections: provide your product, buyer profile, the objections you've actually heard, and your strongest proof point.
3. To handle one specific objection: describe it and the context. Get the full diagnosis + reframe + talk track for that one.
4. To write a FAQ: once the map is done, ask it to reformat the copy versions as a buyer-facing FAQ.
5. To write a champion email: provide your champion, their stakeholder, and the main concern. Get the email they can forward internally.

Input:
Product: Claros pipeline analytics, $1,200/month
Buyer: VP Sales at Series B SaaS, needs CRO sign-off
Objections heard: "we already use Salesforce," "not the right time," "too expensive"
Proof: cut Orion's pipeline review from 4 hours to 45 minutes

OBJECTION 2 — TIMING
Stated form: "Let's revisit in Q3"
Diagnosis: Emotion — fear of change dressed as a calendar objection.
Reframe question: "What would need to be true for this to make sense to look at now?"
Talk track: "Most teams who say Q3 are usually waiting for something specific to happen. What's that thing?"
Copy version: "The teams that move fastest are usually the ones already feeling the cost. If you're spending 3+ hours a week on pipeline reviews, that cost compounds every quarter you wait."