objection-handling
/objection-handling
Buduje playbooki obsługi zastrzeżeń: taksonomia sześciu kategorii, ramy AER, battlecardy per konkurent i wcześniejsze rozbrajanie zastrzeżeń w outreach.
- Autor
- LeadMagic ↗
- Repozytorium
- gtm-skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 14.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 6
- Skrypty
- 1
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 14.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 1 skrypt w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: scripts/check-output.py
Co robi i kiedy
Buduje playbooki obsługi zastrzeżeń: taksonomia sześciu kategorii, ramy AER, battlecardy per konkurent i wcześniejsze rozbrajanie zastrzeżeń w outreach.
Wyzwalacze z opisu
Oryginalny opis (EN)
Build comprehensive objection handling playbooks — 6-category taxonomy, AER framework, battlecards per competitor, pre-handling in outreach. Use when creating objection responses, building an objection playbook, or preparing reps for tough conversations. Triggers on: "objection handling", "objection", "how to respond to", "they said", "pushback", "handle objection", "what to say when", "objection playbook", or any request about responding to prospect pushback.
Jak działa
- Overview
- When to Use
- Authoritative Foundations
- Step-by-Step Process
- Output Format
- Quality Check
- Common Pitfalls
- Execution Artifacts
- Related Skills
Podgląd SKILL.md
--- name: objection-handling description: >- Build comprehensive objection handling playbooks — 6-category taxonomy, AER framework, battlecards per competitor, pre-handling in outreach. Use when creating objection responses, building an objection playbook, or preparing reps for tough conversations. Triggers on: "objection handling", "objection", "how to respond to", "they said", "pushback", "handle objection", "what to say when", "objection playbook", or any request about responding to prospect pushback. license: MIT compatibility: Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed metadata: version: "1.0.0" author: LeadMagic category: sales-revops tags: [objections, sales, handling, playbooks] related_skills: [buyer-indecision, battlecard-builder, competitive-intel, cold-email-copywriting, demo-scripts, pipeline-management] frameworks: [Force Management Command of the Message, Sandler Pain Funnel, Brent Adamson Challenger Sale, Todd Caponi Transparency Sale, Matthew Dixon JOLT Effect, Anthony Iannarino Eat Their Lunch] --- # Objection Handling ## Overview Objections aren't rejections — they're information. A prospect who says "we don't have budget" might mean "I don't see enough value to create budget." The difference determines whether you walk away or win the deal. This skill builds a structured objection handling system: a 6-category taxonomy, the AER framework (Acknowledge → Explore → Redirect), and pre-handling objections in outreach sequences before they're raised. ## When to Use - "Build an objection handling playbook" - "How do I respond when a prospect says [objection]?" - "Create objection battlecards for our sales team" - "Prepare responses for common pushback" - "Handle the 'too expensive' objection" - "What do I say when they mention [competitor]?" For **"I need to think about it"** after verbal fit — load `buyer-indecision` (JOLT). Objections are pushback; indecision is FOMU (fear of messing up). ## Authoritative Foundations Force Management's Command of the Message framework teaches that objections reveal gaps in the Value Messaging Framework — if a prospect doesn't see the value, the Before Scenario wasn't compelling or the PBOs weren't tied to their specific pain. Sandler's Pain Funnel surfaces the real objection: budget objections are usually value objections in disguise, timing objections are usually priority objections. Never answer the first objection — explore what's behind it. Challenger's reframing principle: when a prospect objects from a mistaken assumption, teach them something that changes how they see the problem. **Brent Adamson (Challenger Sale)** — Teach-Tailor-Take Control with a **Commercial Teaching Insight** before pitching. → `references/brent-adamson-challenger.md` **Anthony Iannarino (*Eat Their Lunch*)** — Level up value vs incumbents: match → differentiate → teach why status quo costs them → strategic partner. Pair Challenger insight with Iannarino **discipline** on pipeline honesty. → `references/anthony-iannarino-sales-discipline.md` ## Step-by-Step Process ### Phase 1: Build Objection Taxonomy Categorize every objection your team hears: | Category | Examples | Root Cause | |---|---|---| | **Value / ROI** | "Too expensive," "No budget" | Haven't quantified the pain or proven the ROI | | **Timing** | "Not right now," "Next quarter" | Pain isn't urgent enough to prioritize | | **Competition** | "We use [competitor]," "They're cheaper" | Haven't differentiated clearly | | **Authority** | "I need to check with [boss]" | Haven't engaged the economic buyer | | **Status Quo** | "We're fine with current solution" | Haven't made the cost of inaction real | | **Trust / Risk** | "Too risky," "Not sure it'll work" | Insufficient social proof or technical validation | ### Phase 2: AER Framework For every objection, structure the response: 1. **Acknowledge** — Validate the concern. "That makes total sense." Never argue. Acknowledgment builds trust. 2. **Explore** — Ask a question that uncovers what's behind the objection. "When you say budget is tight — is it a priority question or a timing question?" Sandler Pain Funnel: go deeper before answering. 3. **Redirect** — Reframe with insight, proof, or a new angle. "We actually see that companies who invest now during [condition] capture [outcome], because [insight]. Here's what [similar company] saw." ### Phase 3: Pre-Handling in Outreach The best objection response is one you never need to give. Pre-handle common objections in your outreach sequence: | Objection | Pre-Handle in Sequence | |---|---| | Timing | "Most teams tell us they wish they'd started 3 months sooner — here's why" | | Budget | "Companies our size typically see [ROI figure] within [timeframe]" | | Competition | "Unlike [competitor], we [differentiator] — here's what that meant for [customer]" | ### Phase 4: Objection Battlecards Create per-competitor battlecards with objection-specific responses: ``` Objection: "[Competitor] is cheaper" Acknowledge: "They are less expensive — I see why you'd compare on price." Explore: "When you look at the total cost including [factor], does that change the math?" Redirect: "Customers who switched from [competitor] to us actually saved [amount] because [reason]. Here's the breakdown." Proof: [Case study with specific ROI data] ``` ## Output Format Objection handling playbook with taxonomy, AER responses per objection (20-30+ objections), pre-handling sequence inserts, and per-competitor objection battlecards. ## Quality Check - [ ] 6-category taxonomy populated with real objections from your calls - [ ] AER structure applied to every objection - [ ] Pre-handling language integrated into outreach sequences - [ ] Per-competitor battlecards include specific, sourced proof points - [ ] Playbook searchable by objection keyword ## Common Pitfalls 1. **Answering before exploring.** "Too expensive" → "But we're worth it!" The first objection is rarely the real objection. Explore first. 2. **Arguing with the prospect.** "That's not true, actually..." You may win the argument and lose the deal. Acknowledge, then redirect. 3. **Generic responses.** "We have great ROI" isn't an objection response. "Customers in your industry see 3x ROI within 6 months. Here's how [similar company] did it." — that's a response. 4. **No competitive objection prep.** If you know the competitor's cheaper, prepare the response before it comes up. Pre-handling beats reacting. 5. **One-size responses.** A CTO's security objection needs a different response than a VP Sales' budget objection. Tailor by persona. ## Execution Artifacts - `references/framework-notes.md` — Named frameworks and reference tables - `templates/output-template.md` — Deliverable shell for agent output - `scripts/check-output.py` — Lightweight deliverable validator - `references/brent-adamson-challenger.md` — Challenger reframing - `references/anthony-iannarino-sales-discipline.md` — Competitive leveling ## Related Skills - **battlecard-builder**: Competitive battlecards this skill feeds - **competitive-intel**: Research to populate objection-specific proof - **cold-email-copywriting**: Pre-handle objections in sequence copy - **demo-scripts**: Address objections during the demo flow
Pliki w paczce (6)
- SKILL.md 7 KB
- references/anthony-iannarino-sales-discipline.md 3 KB
- references/brent-adamson-challenger.md 3 KB
- references/framework-notes.md 2 KB
- scripts/check-output.py 1 KB
- templates/output-template.md 1 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · LeadMagic/gtm-skills | 100 | MIT |
| sarojkjha/aaj-marketing-skills | 100 | MIT |
| criptogus/agent-evolve-network | 100 | Apache-2.0 |
| qa-aman/claude-skills | 100 | MIT |
| burnoutscript/sales-skills | 100 | MIT |
| andreworia/claude-finance-skills | 100 | MIT |
| thecraighewitt/skills | 100 | MIT |
| deciqAI/knowledge-skills | 90 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki ea8069c4a33d (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100pm-objection-handler
Tworzy podręcznik odpowiedzi na obiekcje klientów pogrupowane według kategorii, uczy handlowców rozpoznawać prawdziwą obawę i odpowiadać dowodami. - 90objection-handling-library
Buduje bibliotekę obiekcji z realnych odpowiedzi klientów, z przetestowaną odpowiedzią na każdą obiekcję. - 100deal-playbook
Pisze playbooki sprzedażowe: sekwencje outboundowe, przewodniki rozmów discovery, skrypty obsługi zastrzeżeń i schematy demo. - 100reply-objection-handler
Klasyfikuje odpowiedzi potencjalnych klientów, przygotowuje obsługę zastrzeżeń i prowadzi do umówienia spotkania oraz kroku w CRM. - 100objection-analyzer
Analizuje zastrzeżenia pojawiające się w odpowiedziach na wiadomości outbound, ocenia, jak zespół je obsłużył, szereguje najczęstsze i podpowiada kolejne odpowiedzi oraz playbook. - 100objection-handler
Diagnozuje, co naprawdę znaczy zastrzeżenie klienta, i pisze odpowiedzi do maila, rozmowy telefonicznej lub wiadomości na LinkedIn.