SalesDiscovery & Qualification

AI Prompts for Objection Handling and Response Libraries

Objections are information. 'Too expensive' can mean the value is not clear, the budget sits elsewhere, or the prospect is negotiating; each needs a different response. A useful objection library is organized by underlying concern rather than by the words used, gives a response structure rather than a script, and includes the question that reveals which concern you are actually facing.

This page keeps the original library prompt and adds the classification and rehearsal prompts around it. Price negotiation and discount pushback have their own page; the responses here are for the objections that arise during discovery, evaluation and proposal.

Before you use these

Have these ready to replace the highlighted [variables]:

The objections you actually hear, with the stage and role they come from
Your proof points with numbers
Competitors and the claims prospects repeat about them
Where each objection sits in your win/loss data (which ones predict losses)

The prompts

1. Create the objection response library
2. Classify objections by underlying concern
3. Rehearse responses to specific objections

1. Create the objection response library

Best forA structured library for the most common objections, built around the underlying concern.

Inputs needed

Product
Audience
Competitor

How to use itThe original prompt from this page. Replace the example objections in brackets with the ones you actually hear.

Expected outputEight objections, each with the underlying concern, a validating first sentence, a reframe, one proof point and a forward-moving question.

Act as a senior AE. Create a response library for the 8 most common objections when selling [product] to [audience] (e.g., 'too expensive', 'we use [competitor]', 'not a priority', 'send me info'). For each: the underlying concern, a validating first sentence, a reframe, one proof point, and a question that moves the deal forward. Conversational tone, no scripts that sound rehearsed.

2. Classify objections by underlying concern

Best forUnderstanding what an objection actually means before responding to it.

Inputs needed

Objection list with context
Win/loss patterns

How to use itGive real objections with stage, role and what happened next. The model maps each to a concern category and gives the diagnostic question.

Expected outputObjection taxonomy: concern categories, the objections in each, the diagnostic question, the response strategy per category, and the objections that predict losses.

Act as a sales enablement lead classifying objections for [product / segment].

Objections heard: [each with the stage, the role who raised it, the exact words, and what happened to the deal]
Win/loss notes: [objections that appear in losses; objections won through]

1. Group the objections by underlying concern: value not clear; wrong problem/priority; risk (change, implementation, vendor); trust/proof; budget ownership; timing; competitive preference; internal politics; genuine misfit; negotiating tactic.
2. For each category: the objections that belong to it, the diagnostic question that confirms it (e.g. for 'too expensive': 'compared to what — the budget you have, or the value you expected?'), and the response strategy (evidence, reframe, escalate, accept).
3. Objections that mean different things depending on stage or role, and how to tell.
4. The objections most associated with losses in the notes, and whether they are answerable or signs of misfit that should trigger disqualification.
5. The objections that are actually buying signals (asking about implementation, contract terms, references).
6. A one-page rep card: hear this → ask this → then respond with this.

Do not treat every objection as something to overcome. Some are correct.

3. Rehearse responses to specific objections

Best forPracticing the acknowledge → clarify → reframe → question structure on the objections that matter in a live deal.

Inputs needed

Specific objection with context
Underlying concern
Proof and constraints

How to use itGive the model the exact objection and the situation. Ask for a rehearsal: their line, your response, their likely pushback, your next line — two rounds deep.

Expected outputTwo-round rehearsal per objection with the response structure marked, the tone notes, the trap to avoid, and the point at which to stop and ask.

Act as a sales role-play partner rehearsing objection responses for [deal / situation].

Objection: [exact words, who said it, when]
Likely underlying concern: [from classification, or unknown]
Our proof and constraints: [what we can say, what we cannot promise]
My voice: [phrases I would use]

Run two rounds:
Round 1 — Their objection. My response using: acknowledge (one line, no 'but'), clarify (the diagnostic question), then — depending on their answer — reframe with one proof point, and a forward question.
Round 2 — Their most likely pushback to my response (make it realistic, not a strawman). My next line, and the point at which I should stop responding and ask what would need to be true for them.

Then:
1. Mark the structure in each response so I can see it.
2. Tone notes: where I risk sounding defensive or salesy.
3. The trap in this objection (arguing, over-explaining, discounting too early) and how the responses avoid it.
4. If the objection turns out to be genuine misfit, the honest line that says so.
5. Two alternative reframes in case the first does not land.

Keep every line short enough to say naturally.

Related prompts

Logical next step

After this, most sales teams move on to Sales Negotiation and Discount Pushback.

B2B Sales Prospecting System ($39) — goes further: a repeatable outbound engine: research → sequence → objections → follow-up. See what's inside →

Get the free B2B Sales AI Starter Kit → Nine of these prompts as a target → engage → qualify workflow with an intake worksheet, delivered by email. See what's inside

All Sales prompts · Search the full library