mcpField
O
objection-handling

objection-handling

github.com/gtmagentsMarketing & growth431104 installsUpdated 30w ago
Repository

About objection-handling

objection-handling is a sales and marketing skill for diagnosing prospect objections and preparing concise responses. It applies the LACE framework and adapts scripts for email, calls, and social channels.

Key features

  1. 01Uses the Listen, Acknowledge, Clarify, Educate framework
  2. 02Diagnoses objection type and root cause
  3. 03Builds responses with empathy, proof, and a CTA
  4. 04Adapts scripts across communication channels
  5. 05Tracks outcomes to refine messaging

Use cases

  1. 01Prepare replies to budget or timing concerns
  2. 02Draft concise sales emails and call scripts
  3. 03Create objection battlecards for enablement teams
  4. 04Review objection trends for marketing content

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gtmagents/gtm-agents --skill objection-handling

After installing, type/objection-handlingin Claude Code to confirm it loaded.

Details

From the project README

Objection Handling Skill

When to Use

  • Prospects push back on timing, budget, priority, or vendor choice.
  • SDRs/AEs need concise, value-first rebuttals for email, phone, or social.
  • Enablement teams are building battlecards and talk tracks.

Framework

  1. LACE – Listen, Acknowledge, Clarify, Educate for every objection.
  2. Diagnosis – identify category (budget, timing, competition, info) and root cause.
  3. Response Construction – combine empathy statement + proof + CTA for next step.
  4. Channel Adaptation – adapt scripts for email, call, social with same backbone.
  5. Feedback Loop – log outcomes in objection tracker to refine messaging.

Templates

  • Common objection table with diagnosis + recommended responses.
  • Email snippet:
Hi {name}, totally hear you on {objection}. Many {persona}s said the same until they saw {proof point}.

How about we {next step} so you can evaluate without interrupting your week?
  • Call script snippets (“If {metric} improved by 15%, would it merit a closer look?”).
  • Battlecard snippets and micro case studies linked per objection.

Tips

  • Mirror the exact language the prospect used before responding.
  • Ask one clarifying question before presenting proof—often the real objection surfaces.
  • Tailor proof to persona (finance → ROI, ops → efficiency, IT → security).
  • Track objection frequency weekly to inform marketing content and enablement.

Comments

Markdown supported