Skip to content
Skills Library
Sales & customer service · Writing

objection-handler

/objection-handler

Use this skill when a prospect raises an objection in a reply, on a call or in a deal: \"how do I respond to 'too expensive'\", \"handle this objection\", \"build an objection handling guide\", \"they said they're happy with their current vendor\". Diagnoses what the objection really means, picks the response pattern (clarify, reframe, prove, defer or walk away), writes responses for email, call and LinkedIn, and builds a reusable objection library with proof for each.

Repository
gtm-skill ↗
Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use this skill when a prospect raises an objection in a reply, on a call or in a deal: \"how do I respond to 'too expensive'\", \"handle this objection\", \"build an objection handling guide\", \"they said they're happy with their current vendor\". Diagnoses what the objection really means, picks the response pattern (clarify, reframe, prove, defer or walk away), writes responses for email, call and LinkedIn, and builds a reusable objection library with proof for each.

Triggers from the description

how do I respond to, \re happy with their current vendor\
Original author description

Use this skill when a prospect raises an objection in a reply, on a call or in a deal: \"how do I respond to 'too expensive'\", \"handle this objection\", \"build an objection handling guide\", \"they said they're happy with their current vendor\". Diagnoses what the objection really means, picks the response pattern (clarify, reframe, prove, defer or walk away), writes responses for email, call and LinkedIn, and builds a reusable objection library with proof for each.

How it works

  1. Inputs
  2. The play
  3. What good looks like
  4. Rules
  5. Example prompts
Original SKILL.md headings · 56 lines, 444 words
SKILL.md preview
---
name: objection-handler
description: "Use this skill when a prospect raises an objection in a reply, on a call or in a deal: \"how do I respond to 'too expensive'\", \"handle this objection\", \"build an objection handling guide\", \"they said they're happy with their current vendor\". Diagnoses what the objection really means, picks the response pattern (clarify, reframe, prove, defer or walk away), writes responses for email, call and LinkedIn, and builds a reusable objection library with proof for each."
license: MIT
metadata:
  title: Objection handler
  category: replies-meetings
  tags: "SDR, Sales, Founders, Sales Leaders"
  author: prosyo
  version: "1.0.0"
  keywords: "sales objection handling, objection handling scripts, too expensive objection, claude objection handling skill, b2b sales objections"
  inputs: "The objection in their words, Context and stage, Proof points"
  outputs: "Diagnosis, Response per channel, Objection library entry"
---

Use this when a buyer pushes back. Most objections are questions in disguise; the response that works first finds out which question.

## Inputs

- The objection, in the buyer's exact words.
- Context: cold reply, discovery call, late-stage deal; who said it.
- Proof available: customer stories, numbers, documents.

## The play

### 1. Diagnose before answering
| Surface objection | Often really means |
| --- | --- |
| "Too expensive" | Value not clear yet, wrong package, budget timing, or a competitor quote |
| "We already have a solution" | Switching feels risky; current pain not acknowledged |
| "Not a priority" | Problem not tied to something they are measured on |
| "Send me some info" | Polite exit, or genuinely busy |
| "I need to talk to my team" | Not the decision-maker, or not convinced enough to champion |
| "We tried something like this" | Past failure; fear of repeating it |

### 2. Choose the pattern
- **Clarify**: ask a question that surfaces the real concern. Default first move.
- **Reframe**: change the comparison (cost of the problem vs the price; risk of doing nothing).
- **Prove**: a peer who had the same concern and what happened.
- **Defer**: agree a specific later moment when the condition changes.
- **Walk away**: when the objection reveals a genuine bad fit, say so. It builds trust and saves time.

### 3. Write the response
Acknowledge in a few words (no "I totally understand"), then the pattern. Keep email responses under 80 words. On calls, ask and then stop talking.

Read [references/objection-library.md](references/objection-library.md) for responses to the 12 most common B2B objections, by stage.

### 4. Log it
Every objection goes into the library with the response that worked. Patterns across deals feed messaging and product.

## What good looks like

- The first response is usually a question.
- Proof matches the objection: a security concern gets a security document, not a ROI story.
- Bad-fit objections are accepted, not "overcome".
- The common mistake is arguing: answering a price objection with a list of features.

## Rules

- MUST clarify before rebutting when the real concern is unclear.
- MUST use only approved proof points and real pricing.
- NEVER pressure with fake deadlines or "this price ends Friday" unless it is true.
- NEVER disparage a competitor the buyer uses.

## Example prompts

- "Prospect replied 'we're happy with our current vendor'. Draft a response."
- "Build an objection library for our sales team from these 20 call notes."
- "On calls I freeze at 'it's too expensive'. Give me a talk track."
Files in this package (2)
  • SKILL.md 3 KB
  • references/objection-library.md 2 KB

Versions

RepositoryScoreLicence
This page · prosyo-ai/gtm-skill100MIT
alebgl77/claude-inc100MIT
Jakeschincariol/whale-skill100MIT
SkillMedev/skills100MIT
enrichments-io/claude-clay-gtm-skills100MIT
Navinspire-ia/navin90AGPL-3.0

Database snapshot: 13.11.2026 · package version f5b33ce53331 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100handle-objection
    Work through a live objection or competitive threat - what's really being said, the response that has worked before, and the proof points to use, grounded in your own win/loss history and customer quotes. Use when the user says "they said we're too expensive", "how do I respond…
  • 100reply-objection-handler
    Reply & Objection Handler — classifies prospect replies, drafts objection handling, drives to a booked meeting, and sets the CRM next step. Operates inside the brief-driven protocol. Also known as Ricky Reply. Use when user says handle a reply, objection handling, book the…
  • 100objection-handling
    When the user wants to prepare for objections, build an objection playbook, handle a specific objection, or deal with a prospect who went dark. Also use when the user says 'how do I handle this objection,' 'they said it's too expensive,' 'build me an objection playbook,'…
  • 100competitive-objection-response
    Handle one live competitive objection from a buyer, prospect, rep, or account with current facts, a concise response posture, discovery questions, supportable proof, and honest qualification. Use for "what do I say?", "the buyer just said...", competitor claims about price,…
  • 100pm-objection-handler
    Objection handling playbook organized by category. Teaches reps to diagnose the real concern behind the stated objection and respond with evidence, not clever comebacks. Use when someone says "objection handling", "how do we respond when they say", "too expensive", "competitor…
  • 100objection-handling
    Handle sales objections using tactical empathy. Use when the user says "how do I handle this objection", "prospect said [X]", "they pushed back on price", "they said they're not ready", "how to respond to 'we already have a solution'", "they said 'send me more information'",…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.