20 AI Prompts for Objection Handling

The money round. Every counter here validates first — the price conversation is where trust is won, not where discounts are handed out to make the discomfort stop.

You are a B2B sales coach who specializes in price objections. My prospect at [PROSPECT COMPANY] just said some version of “it’s too expensive.” Context: I sell [YOUR PRODUCT] to [PERSONA] in [INDUSTRY], and the sticking point surfaced at [DEAL STAGE].

Draft a response I can deliver on a live call. Structure it in three beats: (1) validate the concern in one sentence without conceding that the price is wrong, (2) reframe the conversation from price to the cost of the problem we discussed — reference [THE SPECIFIC PAIN THEY ADMITTED] — and (3) end with one calibrated question that invites them to weigh the two numbers themselves.

Constraints: under 120 spoken words, plain conversational language, no marketing adjectives, no discounting, and never argue that the product is cheap. The tone is a consultant thinking alongside them, not a rep defending a number. If you are missing the pain point or the deal stage, ask me for them before drafting. Output the response as a short spoken script, then add two alternate closing questions I can swap in depending on how warm the call feels.

Act as a revenue strategist who has watched hundreds of deals die on “there’s no budget” — and hundreds survive it. My prospect is a [PERSONA] at [PROSPECT COMPANY] in [INDUSTRY]. I sell [YOUR PRODUCT]. Their stated blocker is budget, but they have confirmed the problem is real: [THE PROBLEM THEY CONFIRMED].

Write a two-part response. Part one validates the constraint honestly — budgets are real and I will not pretend otherwise. Part two opens a different door: ask where the cost of this problem currently lives (headcount, tooling, missed revenue, manual hours) and whether teams like theirs have ever funded a fix from that line instead of a new one.

Then give me three follow-up questions, ordered from safest to boldest, that help me learn how spending decisions actually get made at their company — who approves, on what cycle, and what evidence moves them.

Constraints: nothing that sounds like pressure, no assuming they are hiding money. Keep the full response under 150 words, in plain first-person language I can say on a call or send as written. Ask me up to three clarifying questions first if any bracketed input is vague.

You are a competitive-deal advisor. My prospect at [PROSPECT COMPANY] told me [COMPETITOR] came in cheaper, and they are waiting to see what I do with that. I sell [YOUR PRODUCT]; the honest differences between us are [YOUR REAL DIFFERENTIATORS] and the honest tradeoffs are [WHERE THE COMPETITOR IS LEGITIMATELY STRONG].

Draft a response that does three things without ever disparaging the competitor: (1) acknowledge that the comparison is fair and worth making carefully, (2) reframe from price-per-seat to what each option costs to get the same outcome — implementation effort, adoption, what breaks at scale — using only the differences I listed, and (3) offer to build a side-by-side evaluation sheet on their criteria, not mine.

Constraints: conversational, under 140 words, zero superlatives, zero claims I did not give you. If my listed differentiators are vague or sound like marketing copy, stop and make me sharpen them with specific questions before you draft anything. Output the spoken response first, then a five-row starter outline for the evaluation sheet with one column per vendor.

Act as a negotiation coach who works in give-get trades. My prospect at [PROSPECT COMPANY] asked for a discount on [YOUR PRODUCT] at the [DEAL STAGE] stage. Current terms: [CURRENT PRICE AND TERMS]. What I can flex: [WHAT I CAN ACTUALLY TRADE — TERM LENGTH, PAYMENT TIMING, SCOPE, ONBOARDING].

Draft a response that treats the ask with respect — wanting a better deal is rational, and I will say so — and then converts it from a one-way concession into a two-way trade. Every give must be paired with a get from my flex list: a longer term, a reference call, a signed rollout plan, an expanded seat count.

Then list three trade packages, labeled by what the prospect values most (lowest cost, fastest start, least risk), each with the exact language for proposing it.

Constraints: never grant a naked discount, never scold them for asking, no invented time pressure of any kind, under 160 words for the main response. Plain language throughout. If my flex list is empty or unclear, ask me what I can trade before drafting — do not invent concessions I never offered.

“Later” is the politest way a deal dies. Three counters that respect the calendar and still find a way to move.

You are a B2B sales coach who treats “call me next quarter” as a data point, not a defeat. My prospect, a [PERSONA] at [PROSPECT COMPANY], asked me to circle back in [TIMEFRAME]. The problem we discussed: [THE PROBLEM]. What they said is driving the delay: [THEIR STATED REASON].

Draft a response with this shape: validate the timing constraint as legitimate — quarters are real and their calendar is not mine to argue with — then ask one gentle, concrete question about what the problem costs between now and then, using only facts they have already given me. Close by proposing the smallest useful thing we could do before the callback date: a benchmark, a short working session, a summary for their planning cycle.

Also draft the calendar-hold message I send after the call so the follow-up is anchored to their date, framed as keeping my word rather than chasing.

Constraints: no pressure language, no manufactured urgency, no “the price goes up” games — ever. Under 130 words for the spoken response. If I have not given you their stated reason for the delay, ask for it first; the response changes completely depending on whether it is budget cycle, bandwidth, or polite deflection.

Act as a sales strategist who specializes in overloaded buyers. My prospect at [PROSPECT COMPANY] says the team is slammed — [WHAT IS CONSUMING THEM, IF KNOWN] — and cannot take on an evaluation of [YOUR PRODUCT] right now.

Write a response built on one idea: I am not asking them to add a project; I am offering to shrink one. Validate that busy is the default state of every good team, then propose the single smallest step that produces value without a rollout — pick the best fit from: a 20-minute working session on their real data, a one-page summary their team can read asynchronously, or a scoped pilot that I run and they review.

Give me the response, then a shorter follow-up version for when the first one gets silence, spaced for [FOLLOW-UP WINDOW].

Constraints: under 110 words each, no guilt, and no “I know you’re busy, but” openers — find a sharper first line. Plain language, written the way a helpful colleague talks. Before drafting, ask me what is actually consuming their team if I left that bracket empty; the proposed step must connect to their current fire, not compete with it.

You are a discovery coach. My prospect, a [PERSONA] at [PROSPECT COMPANY], told me this is not a priority. Their stated top priorities this [QUARTER/YEAR] are: [THEIR STATED PRIORITIES]. I sell [YOUR PRODUCT], which most credibly connects to those priorities through [THE HONEST CONNECTION, IF ANY].

First, judge the connection: if the link between my product and their priorities is genuinely thin, say so plainly and draft a graceful step-back message that leaves the door open without pretending — respect earns the next conversation.

If the link is real, draft a response that never argues my thing should outrank theirs. Instead it accepts their ranking and asks one bridging question: how are they measuring progress on [TOP PRIORITY], and what happens to that number if [THE PROBLEM I SOLVE] stays as it is?

Constraints: under 120 words, no reframes that sound like a sales trick, no diminishing their priorities. Output the response plus two alternate bridging questions with a one-line note on when each fits. If my honest-connection bracket is empty, interrogate me until we find one or conclude there is none.

The incumbent, the existing tool, the internal build. Three counters that never throw a punch at what is already working — respect for the status quo is what earns the right to question it.

Act as a competitive strategist who never trash-talks an incumbent. My prospect at [PROSPECT COMPANY] is satisfied with [CURRENT VENDOR] for [THE JOB IT DOES]. I sell [YOUR PRODUCT]. What I honestly do differently: [YOUR REAL DIFFERENCE].

Draft a response with this posture: happiness with a vendor is a good sign — it means they invest in this problem and hold tools to a standard. Say that sincerely. Then offer one thing, not a pitch: a benchmark. Propose a low-effort way for them to see how their current results compare on the one dimension where I differ — framed as calibration they keep regardless of whether we ever talk again.

Then write the two-sentence answer for the follow-up they will ask: “why should we even look if nothing is broken?”

Constraints: the incumbent is never criticized, named or unnamed; the word “but” cannot appear after the compliment — restructure instead. Under 120 words for the main response, plain language, no superlatives. If my stated difference is generic (faster, easier, better), reject it and ask me for the specific, checkable version before drafting.

You are a solutions consultant. My prospect at [PROSPECT COMPANY] says they already have a tool that covers this: [THEIR EXISTING TOOL, IF NAMED]. I sell [YOUR PRODUCT]. The jobs my product does: [LIST THE 3–5 JOBS YOUR PRODUCT DOES].

Build me an overlap map. Column one: each job from my list. Column two: whether their existing tool typically handles it fully, partially, or not at all — reasoning from what that tool category is built for, clearly labeled as an assumption for them to correct, never stated as fact about their setup. Column three: the question I should ask to find out.

Then draft a short spoken response that validates the instinct — nobody needs another tool for a solved problem — and offers the map as a five-minute exercise: if every row comes back “covered,” I will say so and leave.

Constraints: response under 100 words; the map is the deliverable, the talk track just earns it. No assuming their tool is bad. Plain language. Output the map as a simple three-column table. Ask me for my job list first if I left it vague — the map is worthless with fuzzy inputs.

Act as a former engineering leader who has both built and bought. My prospect at [PROSPECT COMPANY] handles this with an internal build — [WHAT THEIR BUILD DOES, IF KNOWN] — maintained by [WHO MAINTAINS IT, IF KNOWN]. I sell [YOUR PRODUCT].

Draft a response that opens with genuine respect: an in-house build means a team that understood the problem well enough to ship an answer, and I should say that like I mean it. Then ask the only question that matters, softly: what does keeping it current cost — engineer hours, roadmap trades, single points of failure when the maintainer changes teams?

Frame it as curiosity about their world, not a setup for a pitch. Close with an offer that respects the build: a comparison on the dimensions builds rarely cover — [YOUR HONEST EDGE, E.G., COVERAGE, UPDATES, SUPPORT] — positioned as a way to pressure-test their roadmap, not replace their work.

Constraints: under 130 words, zero condescension toward internal tools, no horror stories about builds gone wrong. Plain, technically respectful tone. If I did not tell you what their build does, ask before drafting — guessing here reads as arrogance.

The decision lives somewhere you are not. Three counters that arm your champion instead of going over their head.

You are a deal coach who treats “I need to run it by my boss” as a promotion, not a dodge: my contact just became the internal seller, and my job is to arm them. Context: my champion is a [CHAMPION ROLE] at [PROSPECT COMPANY]; the approver is a [APPROVER ROLE]; the problem we agreed on: [THE AGREED PROBLEM]; my product: [YOUR PRODUCT].

Build a champion kit with three parts: (1) a five-line summary of the case, written in the approver’s language — outcomes and risk, not features; (2) the three questions the approver is most likely to ask, each with a suggested answer my champion can deliver without me; (3) a one-line ask that makes the next step easy to say yes to.

Then draft the message I send my champion with the kit — collaborative, brief, and clear that they own the room and I work for them.

Constraints: the kit fits on one page; no jargon; nothing my champion would be embarrassed to forward. If I have not given you the approver’s role, ask — a CFO and a VP of Sales need different cases. Output the kit, then the message.

Act as a cold-call coach. I just got the classic brush-off — “send me an email” — from a [PERSONA] at [PROSPECT COMPANY] during a call about [YOUR PRODUCT]. What I learned in the 40 seconds before the brush-off: [ANYTHING THEY SAID OR CONFIRMED].

Do two things. First, draft the ten-second response for next time that takes the brush-off at face value while earning one more question — agree to send it, then ask what would make it worth opening, so the email has a target instead of a template.

Second, draft the actual email for this prospect: subject line under six words, body under 90 words, built entirely from what they said on the call, ending with a single low-effort ask — a yes/no question or a one-line reply, not “do you have 30 minutes.”

Constraints: no “as promised” or “per our call” openers; no attachments mentioned; no bullet-list feature dumps. The email should read like a person closing a loop, not a sequence firing. If my bracket for what they said is empty, ask me for it — an email built on nothing will earn nothing.

You are an enterprise-deal strategist. My deal at [PROSPECT COMPANY] for [YOUR PRODUCT] now needs sign-off from [THE STAKEHOLDER LIST — E.G., IT, LEGAL, FINANCE, SECURITY]. My champion is a [CHAMPION ROLE]. Deal context: [ONE-PARAGRAPH DEAL SUMMARY].

Treat the stakeholder wall as a map, not a moat. For each stakeholder on my list, produce: (1) what they are actually protecting when they review a purchase like this, (2) the two questions they will most likely raise, (3) the artifact that answers those questions before they are asked — a security summary, a terms walkthrough, a cost breakdown — and (4) whether my champion or I should deliver it.

Then draft the note to my champion proposing we sequence these reviews in parallel rather than single file, with a suggested order and a plain reason for it.

Constraints: no stakeholder is framed as an obstacle — each one is doing their job, and the plan should say so. Keep each stakeholder profile under 80 words. Ask me for the deal summary if the bracket is empty; generic multithreading advice is worthless.

Scar tissue, proof, the security review. Three counters that treat skepticism as a fair question deserving a structural answer — not a reassurance.

Act as a trust-repair specialist. My prospect at [PROSPECT COMPANY] told me they tried something like [YOUR PRODUCT CATEGORY] before and it went badly: [WHAT THEY SAID WENT WRONG, IF SHARED]. Now every vendor in my category inherits that scar.

Draft a response in three moves. One: validate specifically, not generically — name what failing looks like from their side (the rollout that stalled, the promises that outran the product) so they hear that I understood, not that I sympathize professionally. Two: ask one question about what went wrong that no salesperson has probably asked: what would have had to be true for it to work? Three: propose evaluating me against exactly that failure — the criteria are theirs, drawn from the burn, and I go last, after they define them.

Constraints: never criticize the previous vendor, never say “we’re different” — show it structurally by handing them the evaluation pen. Under 140 words, plain and unhurried; this response should feel slower than a normal sales reply. If they have not told me what went wrong, the entire response becomes the question — draft that version instead.

You are an evaluation designer for B2B software. My prospect, a [PERSONA] at [PROSPECT COMPANY], asked the fairest question in sales: how do I know this will work for us? I sell [YOUR PRODUCT]. What success would look like for them, in their words: [THEIR STATED SUCCESS CRITERIA, IF KNOWN].

Do not draft a persuasion response. Draft a proof plan: (1) restate their question as the design requirement it is; (2) propose a small, time-boxed test on their real work — scope, duration, who touches it, and the specific result we would both look at when it ends; (3) name the honest conditions under which the test would show my product is NOT the right fit, and say I will call that out myself if we hit them.

Then write the short spoken version that introduces the plan on a call, under 90 words.

Constraints: no case-study name-dropping, no invented numbers, no “trust me” energy — the entire answer is structure. Plain language a skeptic would respect. If their success-criteria bracket is empty, your first output is the three questions that fill it.

Act as a security-fluent sales engineer. My prospect at [PROSPECT COMPANY] — likely channeling their [SECURITY/IT/COMPLIANCE] team — raised data and security concerns about [YOUR PRODUCT]. What I actually know about my product’s security posture: [YOUR REAL SECURITY FACTS — HOSTING, ENCRYPTION, CERTIFICATIONS, DATA HANDLING, RETENTION].

Draft two artifacts. First, a spoken response for the moment the concern lands: validate it as the sign of a serious company, commit to answering in their security team’s language rather than sales language, and ask who the right reviewer is and what framework they evaluate against. Second, a plain-language summary of my security facts, organized under the headings their reviewer will actually use — where data lives, who can see it, how long it is kept, what happens on termination — using ONLY the facts I provided.

Constraints: if a fact is missing from my list, write [CONFIRM WITH TEAM] in its place — never fill a security gap with plausible-sounding language; a wrong answer here ends deals and deserves to. Spoken response under 80 words. No acronym soup without a plain-language gloss.