Close & Expand Deal ExecutionAESDR/BDRSales LeadershipCustomer SuccessFounder

Craft Responses to a Tough Objection

Turn a specific objection into the clarifying question to ask first, the likely root causes, and three honest, non-defensive responses that advance the deal.

StageClose & Expand
Best forAE, SDR/BDR, Sales Leadership, Customer Success, Founder
Works withClaude, ChatGPT, Gemini
When to use it

When to use it

Use this when a deal hits a real objection, price, timing, status quo, a competitor, 'send me some info', and you want a few strong, honest ways to respond instead of a defensive reflex. It earns its keep both live (when you have a minute to think before replying) and in prep, where you generate responses to the objections you expect and rehearse the one that fits your voice. It's also a coaching tool: build a small library for your top recurring objections.

Do NOT use the responses as scripts to fire back the instant an objection lands, the single most important output is the CLARIFYING QUESTION, because most objections are a symptom and you'll lose the deal responding to the wrong root cause. 'No budget' might mean 'no budget,' or 'I can't sell this internally,' or 'I'm not convinced it's worth it', three different deals. Also do not feed the model spin; responses built on honest trade-offs land, and ones built on denial collapse on the second question.

The principle: handle objections by getting calm, finding the real issue underneath the words, and advancing, never by being pushy, defensive, or dishonest. Acknowledge, reframe with evidence, advance with a concrete next step. If the honest answer is that you're a poor fit, saying so builds more trust (and more future deals) than arguing the buyer out of a correct concern.

The prompt

The prompt

Prompt, paste into Claude, ChatGPT, Gemini
You are an elite sales coach. You handle objections by staying calm, acknowledging the concern honestly, finding the real issue underneath the surface words, and advancing the deal, never by being pushy, defensive, or dishonest. You are willing to say we're a poor fit when that's the truth.

CONTEXT
What we sell (product + outcome): {{WHAT_WE_SELL}}
The objection (their exact words if possible): {{OBJECTION}}
Deal context (stage, who said it, what's at stake, who else is involved): {{DEAL_CONTEXT}}
What I know about their priorities: {{PRIORITIES}}
Our honest strengths AND weaknesses in this situation: {{STRENGTHS_WEAKNESSES}}

TASK
Help me handle this objection honestly and effectively.

METHOD
1. Diagnose ROOT CAUSE: what might this objection really mean underneath the words? List 2-3 distinct possibilities, these are usually different deals requiring different responses.
2. Write ONE clarifying question that confirms which root cause is real before I respond. This is the most important step.
3. For the most likely root cause, write 3 distinct responses, each in the shape ACKNOWLEDGE -> REFRAME or EVIDENCE -> ADVANCE (a concrete next step). Vary the tone: consultative, direct, peer-to-peer.
4. Name WHAT NOT TO SAY: the defensive or salesy phrases that backfire here.
5. If our honest weaknesses make us a poor fit for this concern, say so and tell me how to handle it with integrity.

OUTPUT FORMAT
ROOT CAUSE (2-3 possibilities)
CLARIFYING QUESTION (1)
RESPONSES (3, each labeled with its tone, each under 80 words and speakable aloud)
WHAT NOT TO SAY (2-3)
FIT CHECK (1 line: are we actually a fit for this concern, honestly?)

CONSTRAINTS
- Be honest about our weaknesses; never invent proof, customers, or numbers.
- Each response under 80 words and natural to say out loud, no corporate phrasing a human wouldn't speak.
- No pressure tactics, no arguing the buyer is wrong, no fake urgency.
- If DEAL_CONTEXT or STRENGTHS_WEAKNESSES is thin, ask me one question before responding.
Run it from the terminal

Run it from the terminal

bash
$# key stays in the environment, never on the command line
$test -n "$ANTHROPIC_API_KEY" && echo key-loaded
key-loaded
$# call the Anthropic Messages API directly with the prompt in request.json
$jq -Rs '{model:"claude-sonnet-4-6",max_tokens:1024,messages:[{role:"user",content:.}]}' prompts/objection.md > request.json
$curl -s https://api.anthropic.com/v1/messages -H "x-api-key: $ANTHROPIC_API_KEY" -H "anthropic-version: 2023-06-01" -H "content-type: application/json" -d @request.json | jq -r '.content[0].text'
ROOT CAUSE - The money genuinely isn't allocated, but a strong ROI case could reallocate it. - The champion believes in it but can't yet sell it to the CFO. - A timing/priority objection dressed up as a budget objection. CLARIFYING QUESTION "When you say no budget this year, is it that the dollars aren't there at all, or that this hasn't made it onto the CFO's priority list yet?" RESPONSES 1. Consultative: "That's fair. Given the margin pressure on the grocery launch, it might be worth me building a simple ROI view you can take to your CFO..." 2. Direct: "Budget usually comes down to priority. If a 10%+ cut in driver hours pays this back in a quarter, is that worth 15 minutes with your CFO?" 3. Peer-to-peer: "I've watched ops leaders park this and watch the cost compound..." WHAT NOT TO SAY - "Can't you just find the budget somewhere?" - "We've got a discount if you sign this quarter." (fake urgency) FIT CHECK Genuine fit if the ROI holds, but the 6-week implementation must clear Q3, be honest.
$# ask the clarifying question first, never fire a response at the wrong root cause
$
Variables to swap

Variables to swap

VariableWhat to put there
{{WHAT_WE_SELL}}Your product/service and outcome
{{OBJECTION}}The objection, ideally in the prospect's own words
{{DEAL_CONTEXT}}Stage, who raised it, what's at stake, who else is involved
{{PRIORITIES}}What you know about their goals and pressures
{{STRENGTHS_WEAKNESSES}}Your honest pros AND cons in this specific situation
Worked example

Worked example

Input

Filled-in example
WHAT_WE_SELL: AI route optimization software
OBJECTION: "This is interesting but we don't have budget this year."
DEAL_CONTEXT: Post-demo; VP Ops is the champion; CFO controls budget; competitor demo happening next week
PRIORITIES: Protecting margin on a new grocery contract launching in Q3
STRENGTHS_WEAKNESSES: Strong ROI story and fast time-to-value; weakness: implementation takes ~6 weeks and we lack deep WMS integration

Output

What the model returns
ROOT CAUSE
- The money genuinely isn't allocated, but a strong ROI case could reallocate it.
- The champion believes in it but can't yet sell it to the CFO.
- It's a timing/priority objection dressed up as a budget objection.

CLARIFYING QUESTION
"When you say no budget this year, is it that the dollars aren't there at all, or that this hasn't made it onto the CFO's priority list yet?"

RESPONSES
1. Consultative: "That's fair. Given the margin pressure on the grocery launch, it might be worth me building a simple ROI view you can take to your CFO, even if we don't start until next quarter. Want me to put that together?"
2. Direct: "Budget usually comes down to priority. If a 10%+ cut in driver hours pays this back in a quarter, is that worth a 15-minute conversation with your CFO?"
3. Peer-to-peer: "I've watched ops leaders park this and then watch the cost compound through a launch. What if we scoped a small pilot that fits a discretionary budget so you're not waiting on next year?"

WHAT NOT TO SAY
- "Can't you just find the budget somewhere?"
- "We've got a discount if you sign this quarter." (fake urgency)
- Anything that implies the budget concern isn't real.

FIT CHECK
Genuine fit if the ROI math holds and the grocery launch creates real urgency, but the 6-week implementation must clear the Q3 deadline; be honest about that timeline or it bites you later.
Tips

Tips to get more out of it

  • Feed the objection in the prospect's exact words. 'We don't have budget' and 'I don't have budget for this right now' point to different root causes, the nuance changes your whole response.
  • Always ask the clarifying question first in real life. Responding confidently to the wrong root cause is worse than saying nothing; it tells the buyer you're not listening.
  • Pick the response that matches your natural tone. A polished script you can't deliver convincingly is worse than a rougher one in your own voice, rehearse it out loud before the call.
  • Be honest in STRENGTHS_WEAKNESSES. The model can only build trustworthy reframes if it knows your real trade-offs; spin in, spin out.
  • Take the FIT CHECK seriously. If the model says you're a poor fit for this concern, walking away gracefully wins you a reputation (and a future deal) that arguing never will.
  • Build a library for your top 5 recurring objections and run a 15-minute team rehearsal on them. Objection handling is a muscle, and reps freeze on the ones they haven't practiced.
  • For a competitor objection specifically, pair this with the battlecard prompt so your reframe lines up with where you honestly win and lose.

Get new prompts in your inbox

The best GTM prompts and AI use cases, every couple of weeks.

Subscribe →