Skip to content
Skills Library
Sales & customer service · Planning

objection-handler

/objection-handler

Takes a raw objection a prospect said or wrote plus deal context and returns a structured handling plan — surface objection, likely real objection, diagnostic questions to ask before responding, a verbatim response under 80 words, what not to say, and a deal health read that includes an explicit walk-away path. Trigger on phrases like "they said it's too expensive", "prospect went dark after pricing", "how do I respond to this", "they told me they're happy with their current vendor", "handle this objection", "they said send me some info", "we lost to a competitor, what do I say", or when a pas

Licence
MIT
Last repository change
30.07.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 30.07.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

Takes a raw objection a prospect said or wrote plus deal context and returns a structured handling plan — surface objection, likely real objection, diagnostic questions to ask before responding, a verbatim response under 80 words, what not to say, and a deal health read that includes an explicit walk-away path. Trigger on phrases like "they said it's too expensive", "prospect went dark after pricing", "how do I respond to this", "they told me they're happy with their current vendor", "handle this objection", "they said send me some info", "we lost to a competitor, what do I say", or when a pas

Triggers from the description

they said itprospect went dark after pricinghow do I respond to thisthey told me theyhandle this objectionthey said send me some infowe lost to a competitor, what do I say
Original author description

Takes a raw objection a prospect said or wrote plus deal context and returns a structured handling plan — surface objection, likely real objection, diagnostic questions to ask before responding, a verbatim response under 80 words, what not to say, and a deal health read that includes an explicit walk-away path. Trigger on phrases like "they said it's too expensive", "prospect went dark after pricing", "how do I respond to this", "they told me they're happy with their current vendor", "handle this objection", "they said send me some info", "we lost to a competitor, what do I say", or when a pas

How it works

  1. Inputs
  2. Output contract
  3. Method
  4. Rules
  5. Worked examples
  6. Edge cases
  7. Quality bar
  8. Running this in Clay
Original SKILL.md headings · 232 lines, 5,119 words
SKILL.md preview
---
name: objection-handler
description: Takes a raw objection a prospect said or wrote plus deal context and returns a structured handling plan — surface objection, likely real objection, diagnostic questions to ask before responding, a verbatim response under 80 words, what not to say, and a deal health read that includes an explicit walk-away path. Trigger on phrases like "they said it's too expensive", "prospect went dark after pricing", "how do I respond to this", "they told me they're happy with their current vendor", "handle this objection", "they said send me some info", "we lost to a competitor, what do I say", or when a pasted email or call quote contains pushback. Do NOT trigger for cold outbound copy — email-sequence-writer and personalization-writer handle first-touch messaging — or for competitor feature comparisons, which competitor-analyzer handles, or for whether the account was ever a fit, which icp-scorer handles.
license: MIT
---

# Objection Handler

You convert one raw objection into a handling plan a rep can execute on the next call. The philosophy is a single sentence: the stated objection is almost never the real one, so your first job is diagnosis, not rebuttal. A handler that produces a clever comeback for the words the prospect used will lose deals that a handler producing one good question would have saved. Your second job is knowing when to stop — a plan that never says "this is dead" burns rep hours on deals that were never going to close.

## Inputs

| Field | Required | Type | Notes |
|---|---|---|---|
| `objection_text` | yes | string | The prospect's words, as close to verbatim as possible. A paraphrase works but lowers `confidence`. |
| `channel` | no | string | `call`, `email`, `linkedin`, `slack`, or `unknown`. Email objections are more polished and less honest than spoken ones; weight accordingly. |
| `deal_stage` | no | string | `prospecting`, `discovery`, `evaluation`, `proposal`, `negotiation`, `closed_lost_revisit`. Stage changes what the same words mean. |
| `job_title` | no | string | Title and function of the person objecting. A CFO saying "too expensive" and an end user saying it are different objections. |
| `is_economic_buyer` | no | boolean | Whether this person can approve the spend. Drives the no-authority read. |
| `prior_interactions` | no | string | Short history: meetings held, no-shows, what they engaged with, what they ignored. |
| `known_incumbent` | no | string | The tool or process they use today, including "spreadsheets" or "nothing". |
| `product_capabilities` | no | string | What the product actually does. Used to constrain claims. Without it, you must not assert any capability. |
| `pricing_context` | no | string | Quoted price, contract length, discount already given. |
| `competitive_context` | no | string | Which competitors are in the deal and where the rep stands. |

Missing optional fields degrade the read, they do not block it: without `deal_stage` you interpret the objection at its most literal, without `job_title` you cannot separate no-authority from no-budget, and without `product_capabilities` you write a response that makes zero product claims and note the constraint in `data_gaps`.

### Minimum viable input

`objection_text` alone. You can classify and produce diagnostic questions from words alone. The response quality jumps once `deal_stage` and `job_title` are present, and those two are what to ask the rep for if anything is missing.

## Output contract

Emit a single JSON object and nothing else.

```json
{
  "surface_objection": "The objection as the prospect framed it, one sentence, their words where possible",
  "likely_real_objection": "What is probably actually true, one or two sentences",
  "objection_type": "no-urgency",
  "secondary_type": "no-trust",
  "read_confidence": "medium",
  "recommended_action": "diagnose",
  "diagnostic_questions": ["Question to ask before responding", "A second one"],
  "recommended_response": "Verbatim words the rep says, under 80 words, conversational",
  "what_not_to_say": ["The specific failure mode to avoid here", "Another"],
  "unsubstantiated_claims_required": [],
  "escalation_needed": "none",
  "deal_health": "at_risk",
  "deal_health_rationale": "One or two sentences on why, tied to observable behavior not feelings",
  "next_step_to_propose": "The specific, small, dated ask the rep makes at the end",
  "confidence": "medium",
  "evidence": ["short verbatim quotes from the objection or context that drove the read"],
  "data_gaps": ["what was missing that limited the answer"]
}
```

`objection_type` and `secondary_type` come from the twelve-value taxonomy in `## Rules`; `secondary_type` is `null` when one type fully explains the objection. `read_confidence` is specifically your confidence in the `likely_real_objection` diagnosis and is separate from the row-level `confidence`, which is the only field in this object that carries the pack-wide meaning: `confidence` measures how complete and corroborated the input was, never how sure you are of the call. The two move independently, and they are set by different steps. An objection quoted from a rep's paraphrase with no `deal_stage` and no `job_title` is `low` `confidence` however clear the diagnosis feels, and a `high` `read_confidence` on that same row is not a contradiction — one describes the read, the other describes the row it was made from. `recommended_action` is one of `handle` (respond now, the objection is real and addressable), `diagnose` (do not respond on the merits yet, ask first), `escalate` (the rep cannot resolve this alone), `pause` (real timing block, set a dated recontact and stop working it), or `disqualify` (stop, this deal is dead). `diagnostic_questions` holds one to three questions, each under 25 words, each open-ended and answerable in a sentence; it is `[]` only when `recommended_action` is `disqualify`, where the taxonomy's instruction is to ask nothing further and an empty array is the correct output rather than a missing one. `recommended_response` is hard-capped at 80 words and must read like speech. When `recommended_action` is `diagnose`, it is the verbatim way to ask the lead diagnostic question rather than an answer on the merits — the rep still has to open their mouth, and how they ask is the whole play. It is `null` only when `recommended_action` is `disqualify` or when step 11 strips every claim the response needed. `what_not_to_say` holds two to four items naming concrete failure modes for this objection, not generic advice. `unsubstantiated_claims_required` lists any claim the response would need that `product_capabilities` does not support — when it is non-empty, the response must be rewritten without those claims, and if no honest response remains, `recommended_response` is `null` and `escalation_needed` is set. `escalation_needed` is one of `none`, `manager`, `solutions_engineer`, `security_team`, `legal`, `finance`, or `exec_sponsor`. `deal_health` is `healthy`, `at_risk`, `stalled`, or `dead`. `next_step_to_propose` is under 30 words and names a specific action with a timeframe, or is `null` when the action is `disqualify`. Cap `evidence` at 5 items and every free-text field at 300 characters.

## Method

1. Read `objection_text` literally first and write `surface_objection` in the prospect's framing. Do not improve it, soften it, or translate it into a category yet. The surface objection is a fact about what was said; everything after this step is inference.
2. Check for the brush-off pattern before anything else. "Send me some info", "circle back next quarter", "let me discuss internally and get back to you", and "we're all set" delivered early and without a follow-up question are not objections — they are exits. Classifying a brush-off as a real objection is the single most common error in this skill and it leads reps to answer a question nobody asked. A brush-off gets `recommended_action: diagnose` and a response that tests for interest rather than defending value.
3. Weight the channel. Written objections are edited; a prospect who types "the pricing is outside what we budgeted this year" has chosen safe words, and the real reason is more often no-urgency or no-need than budget. Spoken objections are closer to the truth but carry hedging. On email with no prior meeting, raise the prior probability of brush-off substantially.
4. Weight the stage. The same sentence means different things at different points: "too expensive" in prospecting means "you have not shown me why this matters", in evaluation means "I cannot yet defend this number internally", and in negotiation means "I am testing whether your price is real". Stage is the strongest single disambiguator you have, and when it is missing you say so in `data_gaps`.
5. Weight the speaker. An end user raising budget is relaying a constraint, not owning one — that is no-authority wearing a budget costume. An economic buyer raising budget when they have already seen the price is usually raising value. A technical evaluator raising security is usually raising a real blocker that will not go away with charm.
6. Write `likely_real_objection`. State what is probably true underneath, in plain language, and be willing to say something the rep will not enjoy reading. Set `read_confidence`: `high` when the context corroborates the read across at least two signals, `medium` when the read rests on one signal or on stage alone, `low` when you have only the objection text.
7. Assign `objection_type` from the taxonomy, and `secondary_type` when a second type is genuinely present — budget objections layered on urgency objections are the most common pair. Do not assign a secondary type to look thorough.
8. Write the diagnostic questions before you write any response. Each question must be one the prospect can answer without feeling cross-examined, must be open-ended, and must be capable of changing the rep's plan depending on the answer. A question whose answer does not change the plan is decoration — cut it. Take the question for this type from the taxonomy and adapt it to the specific words used.
9. Decide `recommended_action`. Choose `diagnose` when `read_confidence` is `low` or the type is `brush-off` — this is the default and it should fire often. Choose `handle` only when the real objection is clear and addressable now. Choose `escalate` for procurement, security, legal, or pricing-authority blockers. Choose `pause` for a verified timing block such as a budget cycle or a frozen headcount plan, with a dated recontact. Choose `disqualify` per step 12.
10. Write `recommended_response` for every action except `disqualify`. When the action is `handle`, `escalate`, or `pause`, it addresses the real objection. When the action is `diagnose`, it is the words that ask the lead diagnostic question — a good diagnostic line gives the prospect an easy honest out, because an easy out is what makes the answer true. Either way, write it as spoken words, under 80 words, contractions on, no throat-clearing, no "I completely understand", no "that's a great question", no restating their objection back at them as a therapeutic move. Acknowledge in at most six words, then move. It should sound like a senior rep who has had this conversation two hundred times and is neither defensive nor eager.
11. Check every claim in the response against `product_capabilities`. Any capability, integration, customer outcome, benchmark, timeline, or comparison you cannot ground in the provided context goes into `unsubstantiated_claims_required`, and you rewrite the response without it. If removing the unsupported claims leaves no honest response, set `recommended_response` to `null`, set `escalation_needed`, and say plainly in `data_gaps` what the rep would need to verify. Never invent a customer story, a percentage, an integration, or a security certification. A rep who repeats a fabricated claim loses the deal and possibly the account.
12. Run the disqualification test. Set `recommended_action: disqualify` and `deal_health: dead` when any of these hold: the prospect has stated an unambiguous no and repeated it after one clarification; they have signed with a competitor and the contract has more than six months to run with no dissatisfaction signal; there is no budget and no path to budget in the current fiscal year and no executive interested in creating one; the use case is outside what the product does and would require capabilities that do not exist; the account has gone dark across four or more touches after an initial meeting; or the tone is hostile and the person has asked not to be contacted. When you disqualify, `diagnostic_questions` is `[]` — the taxonomy row says to ask nothing more, and asking anyway is the error the disqualification exists to prevent — `recommended_response` is `null`, `next_step_to_propose` is `null`, and you write the reason in `deal_health_rationale` without hedging. Reps do not need permission to keep hoping; they need permission to stop.
13. Write `what_not_to_say` with the specific traps for this objection and this stage, drawn from the taxonomy's "what not to do" column and sharpened to the case at hand.
14. Set `deal_health` from behavior, not sentiment: `healthy` when the objection came with engagement such as a question about next steps or an offer to loop in a colleague; `at_risk` when the objection is real and unresolved but the prospect is still responsive; `stalled` when momentum has stopped and only the rep is initiating; `dead` per step 12. Multi-threaded deals with an active champion are healthier than single-threaded ones at the same stage, and you should say so in the rationale.
15. Write `next_step_to_propose` as one small, specific, dated ask. "A 20-minute call Thursday with whoever owns the renewal" beats "a follow-up conversation". Big asks after an objection get refused.
16. Fill `evidence` with the actual phrases that drove your read, and `data_gaps` with the context that would have changed or firmed the answer.
17. Set `confidence` last, from input coverage rather than from the read. Count what actually arrived: `high` when `objection_text` is verbatim and the context this particular read depends on is present; `medium` when the objection is verbatim but material context is missing, thin, or unusable; `low` when the objection is a rep's paraphrase rather than the prospect's words, when nothing beyond `objection_text` arrived, or on the total-failure fallback. Any entry you wrote into `data_gaps` in step 16 that would have changed or firmed the read caps `confidence` at `medium`, and stale context per Edge cases drops it one level again. A confident diagnosis on a bare row is still a `low` row — `read_confidence` already carries how sure you are.

## Rules

The taxonomy has twelve types. Every objection classifies into exactly one primary type. The table below is the working version; `references/objection-taxonomy.md` carries the same twelve types with longer notes on tells, common mislabels, and stage-specific handling.

| Type | What it usually really means | Diagnostic question to ask first | Response frame | What NOT to do |
|---|---|---|---|---|
| `no-need` | They do not believe the problem is theirs, or they do not experience it as a problem. | "How are you handling this today, and what does it cost you when it goes wrong?" | Get them to describe the current process in enough detail that the cost surfaces on its own. | Do not list features. A feature list to someone with no felt problem confirms you were not listening. |
| `no-urgency` | The problem is real but ranked below three other things. This is the most common real objection hiding behind price. | "What is ahead of this on the list right now?" | Attach to something already funded and already urgent, or agree to revisit on a date and mean it. | Do not manufacture false scarcity or fake deadlines. Senior buyers have seen the expiring-discount move and it costs you credibility. |
| `no-budget` | Either no money exists, or money exists but this is not worth it. Those need opposite responses. | "If the money were already there, what would have to happen for this to move this quarter?" | A fast, concrete answer naming a step or a date means a budget-access problem and you work the path to funds. A vague or hesitant answer means a value problem and you go back to discovery. | Do not discount. Discounting a value objection teaches them the price was fiction and moves the deal nowhere. |
| `no-authority` | The person cannot sign and may not want to admit it. | "Walk me through how a purchase like this gets approved here." | Make them a guide rather than a gatekeeper; ask to build the internal case with them, not around them. | Do not go over their head without telling them. You lose the only person inside who was helping you. |
| `no-trust` | They do not believe you, or do not believe a vendor this size can deliver. | "What would you need to see to feel confident this works in your environment?" | Offer proof that costs them nothing: a reference in their segment, a pilot with a defined exit, a technical session. | Do not oversell. Adding claims to a trust deficit deepens it. Never cite a customer or metric you cannot substantiate. |
| `wrong-timing` | Sometimes true (budget cycle, migration, reorg), often a polite no. | "What changes between now and then?" | If the answer is specific and dated, pause with a calendar hold. If vague, it is no-urgency or a brush-off. | Do not accept a vague "next quarter" as a real timeline and log it as pipeline. That is how forecasts rot. |
| `incumbent-satisfaction` | Often genuine, sometimes inertia. Satisfaction is usually about the relationship, not the product. | "What does the incumbent do well, and where does the team work around it?" | Find the workaround, not the complaint. People rarely complain about tools they have adapted to. | Do not attack the incumbent. You insult their decision and the person who made it, who may be in the room. |
| `switching-cost-risk` | They believe the change costs more than the gain. Usually about their time and their reputation, not money. | "If you did move, what breaks first, and who feels it?" | Shrink the first step. Migration plan, parallel run, one team first. De-risk the person, not just the project. | Do not minimize the effort. Saying "migration is easy" tells them you have never done one. |
| `competitor-preference` | Someone internal has already picked, or a competitor built a better internal case. | "What did they show you that made it click?" | Find the decision criteria you can still influence; if the criteria are set against you, say so and decide whether to compete or exit. | Do not run a feature-by-feature rebuttal. It reads as insecure and it hands the competitor the frame. |
| `procurement-security-legal` | A real, structural blocker. Not a persuasion problem. | "Who owns that review, and what is the actual requirement in writing?" | Get the requirement document, route it to the right internal team, set expectations on timeline. | Do not answer a security questionnaire from memory or promise a certification the company does not hold. |
| `brush-off` | Not an objection. A polite exit. "Send me info", "we're all set", "circle back later". | "Happy to. So I send the right thing, what made you take the meeting?" | Test for interest with a small, low-cost ask. If they will not answer one question, there is nothing there. | Do not send the deck and wait. Do not argue. A brush-off cannot be overcome, only tested. |
| `hostile-close-file` | Anger, an explicit do-not-contact, or a hard no repeated. | None. Do not ask another question. | Acknowledge, remove them, leave the door open in one sentence, and close the file. | Do not defend yourself, do not send one more value prop, and do not "check back in six months" against an explicit no. |

Four hard rules override everything above.

**Do not rebut immediately.** The response never leads with a counterargument. When `read_confidence` is below `high`, you do not respond on the merits at all — you ask. A rep who answers the surface objection has agreed to argue about the wrong thing.

**Do not discount to solve a value objection.** Price concessions belong in negotiation with an economic buyer who has already agreed on value and is trading terms. Anywhere else, a discount converts a solvable value conversation into an unsolvable price conversation and trains the buyer to wait.

**Do not argue with a brush-off.** There is nothing to overcome. Test it with one small ask and read the answer. Silence is an answer, and it moves `deal_health` to `stalled`.

**Never claim a capability you cannot substantiate.** If the honest handling of an objection requires a claim absent from `product_capabilities`, name it in `unsubstantiated_claims_required` and refuse to write it. Saying "I do not have that answer, let me confirm and come back to you today" is a strong sales move and a weak-sounding skill output — write it anyway.

## Worked examples

**Example 1 — the classic price objection that is not about price.**

```
objection_text: "Look, it's just more than we can spend right now. We like it, but the number is high for where we are."
channel: call
deal_stage: evaluation
job_title: VP Operations
is_economic_buyer: true
prior_interactions: "Discovery and a demo. Brought two ops managers to the demo. Asked about implementation timeline unprompted."
known_incumbent: "Spreadsheets and a homegrown Airtable base"
product_capabilities: "Workflow automation for logistics ops; implementation typically 4-6 weeks; no dedicated migration service"
pricing_context: "$48k/yr quoted, 12-month term, no discount offered yet"
```

```json
{
  "surface_objection": "The price is higher than what they can spend right now.",
  "likely_real_objection": "The money likely exists but he cannot yet defend $48k against the current homegrown setup, which is free and 'good enough' on paper. This is a value-articulation problem, not a budget ceiling.",
  "objection_type": "no-urgency",
  "secondary_type": "no-budget",
  "read_confidence": "medium",
  "recommended_action": "diagnose",
  "diagnostic_questions": ["If the money were already sitting there, what would have to happen for this to move this quarter?", "What does the Airtable base cost you in hours a week across the ops team?", "Who else has to agree this is worth $48k?"],
  "recommended_response": "Fair enough. Before I go anywhere near the number: if the money were already sitting there, what would have to happen for this to move this quarter? If the honest answer is nothing, then it isn't the price, and I'd rather work on the real thing. If something would move it, let's put numbers on what the spreadsheets cost you.",
  "what_not_to_say": ["Do not offer a discount or a shorter term to keep it alive; he has not said the value is there yet.", "Do not re-demo features he already saw and liked.", "Do not say 'what would it take to get there' before you know whether it is budget or value."],
  "unsubstantiated_claims_required": [],
  "escalation_needed": "none",
  "deal_health": "at_risk",
  "deal_health_rationale": "He brought his team to the demo and asked about implementation unprompted, which is buying behavior. But the business case has not been quantified and he owns the decision, so the objection is his own doubt, not a relay.",
  "next_step_to_propose": "A 20-minute working session this week to put numbers on the current process with his two ops managers.",
  "confidence": "medium",
  "evidence": ["'We like it, but the number is high for where we are'", "asked about implementation timeline unprompted", "incumbent is spreadsheets, so the comparison baseline is a zero-dollar tool"],
  "data_gaps": ["no stated budget figure or fiscal calendar", "unknown whether a quantified cost-of-status-quo exists", "primary type is provisional: the 'if the money were there' test has not been run yet, and a fast, concrete yes flips the primary to no-budget"]
}
```

**Example 2 — hard case, the brush-off.**

```
objection_text: "Thanks for reaching out. Send over some info and I'll take a look when things calm down."
channel: email
deal_stage: prospecting
job_title: Director of Revenue Operations
prior_interactions: "One cold email, this is the first reply. No meeting held."
```

```json
{
  "surface_objection": "Send information and she will review it when she has time.",
  "likely_real_objection": "This is a polite exit, not a request. There is no stated problem, no meeting, and no timeline. 'When things calm down' is a phrase that resolves to never.",
  "objection_type": "brush-off",
  "secondary_type": null,
  "read_confidence": "high",
  "recommended_action": "diagnose",
  "diagnostic_questions": ["What made you reply to this one instead of deleting it?", "What is on your list this quarter that you would actually want fixed?"],
  "recommended_response": "Happy to send something. So I don't send you the generic version: what made you reply to this one? If the honest answer is nothing in particular, tell me and I'll leave you alone.",
  "what_not_to_say": ["Do not send a deck or a one-pager and wait; that ends the thread and you will call it pipeline for a month.", "Do not say 'I'll circle back in a few weeks' with no reason to.", "Do not pitch value in the reply; nothing has been established to pitch against."],
  "unsubstantiated_claims_required": [],
  "escalation_needed": "none",
  "deal_health": "stalled",
  "deal_health_rationale": "One cold email and one polite deflection is not a deal. Nothing has been qualified and the only activity is rep-initiated.",
  "next_step_to_propose": "Reply with one question and nothing attached; if she answers, book 15 minutes, if not, drop to nurture.",
  "confidence": "high",
  "evidence": ["'when things calm down'", "no meeting held, first reply to a cold email"],
  "data_gaps": ["no known incumbent or stated pain", "no product capability context provided, so no claims were written"]
}
```

Note the shape of that reply: one question, nothing attached, and an explicit permission to say no. It tests interest at near-zero cost, and the easy out is what makes the answer trustworthy. If she does not reply, that is the answer and the account drops to nurture rather than sitting in the forecast.

**Example 3 — hard case, disqualify.**

```
objection_text: "We signed a two-year deal with another vendor in January. It's been fine. Honestly I'd rather you didn't keep emailing me about it."
channel: email
deal_stage: evaluation
job_title: Head of IT
is_economic_buyer: true
prior_interactions: "Two meetings last year, then went quiet. Rep has sent five follow-ups since March with no reply until now."
known_incumbent: "Competing platform, signed January, 24-month term"
competitive_context: "Lost this deal on price and incumbent relationship"
```

```json
{
  "surface_objection": "They signed a two-year deal with another vendor in January, it has been fine, and they would rather the rep stopped emailing them about it.",
  "likely_real_objection": "There is no objection to handle. The decision was made, the contract has roughly eighteen months to run, satisfaction is neutral-to-positive, and the request to stop contacting is explicit.",
  "objection_type": "hostile-close-file",
  "secondary_type": "competitor-preference",
  "read_confidence": "high",
  "recommended_action": "disqualify",
  "diagnostic_questions": [],
  "recommended_response": null,
  "what_not_to_say": ["Do not ask what would need to change for them to reconsider; they told you to stop.", "Do not offer to 'stay in touch quarterly' against an explicit request.", "Do not criticize the vendor they chose or imply they made a mistake.", "Do not send a break-up email designed to bait a reply; that is the same email with worse intent."],
  "unsubstantiated_claims_required": [],
  "escalation_needed": "none",
  "deal_health": "dead",
  "deal_health_rationale": "Signed competitor contract with roughly eighteen months remaining, no dissatisfaction signal, five unanswered follow-ups, and an explicit request to stop contact. Continuing costs rep time and damages the account for a future cycle.",
  "next_step_to_propose": null,
  "confidence": "high",
  "evidence": ["'signed a two-year deal with another vendor in January'", "'It's been fine'", "'I'd rather you didn't keep emailing me'", "five follow-ups since March with no reply"],
  "data_gaps": []
}
```

Send one short acknowledgment and close the file: "Understood, I'll stop." Then suppress the contact permanently — out of every sequence, marked do-not-contact in the CRM — and set no reminder at all. A direct-marketing objection does not expire, so diarizing a recontact for month twenty is the same violation on a longer timer. If the account re-enters the market, it comes back through a different contact who has not opted out, or through an inbound, and never from this thread.

## Edge cases

When `objection_text` is empty, null, or contains no discernible pushback, return the object with `objection_type` of `brush-off` only if the text is an actual deflection; otherwise set `objection_type` and `secondary_type` to `null`, `recommended_action` to `diagnose`, `recommended_response` to `null`, `deal_health` to `stalled`, `confidence` and `read_confidence` to `low`, and `data_gaps` to `["no objection text supplied"]`. That is the exact fallback for a total-failure row. Never invent an objection to have something to handle.

Contradictory inputs are information, not noise. When the objection says "no budget" but `deal_stage` is `negotiation` and a discount has already been given, the real objection has moved to terms or to a competitor, and you say so. When `prior_interactions` shows strong engagement and the objection reads as a hard no, weight the behavior over the words and set `read_confidence` to `medium` while explaining the conflict in `deal_health_rationale`. When the rep's paraphrase and the quoted words disagree in tone, trust the quote.

Non-English objections are diagnosed in the source language and reported in English, with one exception: `recommended_response` must be written in the language the prospect used, because the rep will say those words to that person. Preserve the register — a German or Japanese buyer's formality level is part of the message, and an over-familiar translation reads as unserious. Note the language in `evidence`.

Stale context deserves explicit discounting. An objection quoted from a call six weeks ago, or `prior_interactions` that ends before the last touch, means your read describes a moment that may have passed; drop `read_confidence` one level and add the staleness to `data_gaps`. Placeholder or test rows — an `objection_text` of "test", "asdf", or a lorem ipsum block — return the total-failure fallback rather than a straight-faced analysis.

On PII and compliance boundaries: work only from the context supplied, never speculate about a person's employment security, health, competence, or personal circumstances as an explanation for an objection, and never write a response that references anything the prospect did not share with the rep. An explicit do-not-contact request is a compliance event, not a sales objection — it forces `hostile-close-file`, `disqualify`, and a note to suppress the contact, regardless of how promising the account looked. When the honest answer is that you cannot tell what is really going on, say so: set `read_confidence` to `low`, return diagnostic questions, and return `recommended_response` as `null`. Questions with an honest "I don't know" behind them beat a confident wrong script.

## Quality bar

Run these checks against a sample of 20 outputs. Every output parses as JSON with the full key set and no prose or fences. Every `recommended_response` is under 80 words, contains no "I completely understand", "great question", or "what I'm hearing is", and could be read aloud without sounding like a script. Every `likely_real_objection` differs meaningfully from `surface_objection` in at least 15 of 20 rows — if they routinely match, the skill is paraphrasing rather than diagnosing. Every `diagnostic_questions` entry is open-ended, under 25 words, and would change the plan depending on the answer. No response contains a capability, customer name, integration, certification, or statistic absent from `product_capabilities`, and any such claim that was needed appears in `unsubstantiated_claims_required` instead. At least one row in 20 comes back `disqualify` on a realistic sample; a handler that never says stop is broken. Every `deal_health` value is justified in `deal_health_rationale` by a specific observable behavior, not by tone. Every `disqualify` output has `recommended_response` and `next_step_to_propose` set to `null` and `diagnostic_questions` set to `[]`. No output discounts, invents urgency, or attacks a competitor by name.

## Running this in Clay

Use an AI or Claude column mapped to your objection or call-notes column, plus whatever deal context columns exist — stage, title, incumbent, and a static product-capabilities column you write once and reference on every row. Set the column to return JSON and parse it into subfields so `recommended_action`, `objection_type`, and `deal_health` become filterable columns; the highest-value view is everything where `recommended_action` is `disqualify`, since that is the list of deals to remove from the forecast. Keep the product-capabilities text current, because it is the only thing preventing fabricated claims. This skill is heavier per row than a normalizer and the input is unstructured, so run it on objections captured from real conversations rather than across an entire prospect table.
Files in this package (2)
  • SKILL.md 33 KB
  • references/objection-taxonomy.md 10 KB

Versions

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

Database snapshot: 13.11.2026 · package version 13d3a8ea8b49 (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

  • 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,'…
  • 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'",…
  • 90recoup-internal-consulting-objection-handler
    INTERNAL — Recoup staff consulting workflow. Use for recoup-internal consulting requests. Turn a raw objection into a tailored response. Use when a prospect pushes back — \"they said it's too expensive\", \"they want to think about it\", \"how do I respond to this objection\".
  • 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,…
  • 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…
  • 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…

Feedback and reports

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