TL;DR: Objection handling prompts turn a category of pushback into a fast, honest first draft you adapt to the specific conversation, instead of either freezing or reaching for a canned line that doesn't fit. The 25 prompts below cover five categories: price, timing, trust and status quo, competitor comparisons, and finding the real blocker before a close. One rule runs through all of them: never fabricate a claim to win an objection.
Most objection-handling advice sells confidence: sound sure of yourself, don't let the prospect see you flinch, always have a comeback ready. That advice produces reps who sound smooth and prospects who feel handled rather than heard. The actual skill objection handling requires is faster than that framing suggests: hearing the specific concern underneath the stated objection, and responding to that concern honestly, in your own words, without a ten-second pause while you scramble for a line.
There's a reason this matters more in sales than almost anywhere else in business writing. A prospect who feels genuinely heard, even in a call that ends in a no, remembers the interaction as respectful and is more likely to come back later or refer someone else. A prospect who feels handled, even in a call that ends in a yes, has learned exactly what kind of vendor you are, and that impression follows the relationship into every renewal conversation for as long as they're a customer. The response matters as much as the outcome, which is exactly why a rehearsed but honest answer beats either freezing or reaching for a script.
That's the job these prompts do. Not scripting what to say word-for-word, but building a fast, honest first draft of a response so you walk into a call already having thought through the five objections you'll actually hear, instead of improvising all of them live. One rule runs through every prompt on this page and it matters more than any individual response: never draft a claim about the product, a competitor, or the roadmap that isn't actually true. An objection response that closes the deal on a lie costs you a customer, a reference, and eventually a reputation, all at once, later, when it matters more.
| Category | The underlying question | Where a prompt earns its keep |
|---|---|---|
| Price | Is this worth it, can we afford it now | Reframing value and separating budget from timing |
| Timing | Why not later, why not never | Making the cost of waiting concrete and specific |
| Trust & status quo | Why change from what we have | Addressing switching risk honestly, not dismissing it |
| Competitor | Why you and not them | Honest comparison, including where they're better |
| Closing | What's actually stopping the yes | Surfacing the real blocker instead of guessing at it |
Read the table before the prompts below. Each category maps to one section, in the order objections most commonly surface in a real sales cycle.
Two categories tend to blur together in practice and are worth separating explicitly: price and timing. A prospect who says "not right now" is sometimes making a genuine timing statement, and sometimes using timing as a softer way to decline what's really a price or trust objection they don't want to state directly. Treating every "not right now" as a scheduling problem, when it's actually a value problem in disguise, wastes a follow-up call on the wrong fix. The prompts in both sections below include a step for telling the two apart before responding to either.
How do you handle a price objection without just discounting?
By treating "too expensive" as two separate questions, is this worth it, and can we afford it right now, and answering the one the prospect is actually asking instead of defaulting to a discount that answers neither.
Price is the objection reps reach for a discount on fastest, and it's usually the wrong move for two reasons. First, a discount answers a question the prospect may not have actually asked; plenty of "too expensive" objections are really about value uncertainty, not budget, and a lower number does nothing to resolve doubt about whether the thing works. Second, a discount offered too easily teaches the prospect that your price is negotiable by default, which follows the relationship into every renewal and every referral they make. The five prompts below are built to answer the actual question before reaching for the lever that changes the number.
1. Value-reframe for a price objection
A prospect said our price is too high. Here's what we actually solve for
them and what the cost of not solving it looks like: "[THE PROBLEM, THE
COST OF THE STATUS QUO, WHAT OUR PRODUCT CHANGES]"
Draft a response that reframes the conversation from cost to value,
using only facts I've given you. Do not invent an ROI number I haven't
provided.
2. Budget-vs-value separator
Help me figure out whether this price objection is really about budget or
really about doubting the value. Here's what the prospect said: "[EXACT
WORDS OR PARAPHRASE]"
Suggest one clarifying question I could ask to tell the two apart, and a
short response for each possible answer.
3. Cost-of-inaction framing
Here's the problem this prospect currently has and roughly how it's
costing them: "[DESCRIBE THE COST — TIME, MONEY, RISK, WHATEVER APPLIES]"
Draft a short, specific way to frame the cost of staying with the status
quo, using only what I've told you. Don't invent a dollar figure I
haven't given you — describe it qualitatively if that's all I have.
4. Tiered-option response
The prospect wants a lower price than our standard plan. Here are the
options we can actually offer: "[LIST REAL OPTIONS: LOWER TIER, ANNUAL
DISCOUNT, SMALLER SCOPE — WHATEVER'S ACTUALLY AVAILABLE]"
Draft a response presenting only the real options I've listed, without
inventing a discount or package that doesn't exist.
5. "Compare to what" price question
The prospect said our price is too high compared to "[WHAT THEY'RE
COMPARING TO — A COMPETITOR, DOING IT MANUALLY, NOT SOLVING IT AT ALL]"
Draft a response that asks what specifically they're comparing to, since
the honest answer differs a lot depending on what "too high" is relative
to.
How do you handle "not right now"?
By making the specific cost of waiting concrete, rather than pushing generically for urgency the prospect doesn't actually feel.
Manufactured urgency is easy to spot and it costs credibility the moment a prospect notices it. A limited-time framing that isn't actually true, or a vague "prices go up soon" with no real basis, works occasionally and damages trust every other time it's tried. Real urgency, when it exists, comes from something concretely true about the prospect's own situation: a cost that keeps compounding while they wait, a deadline they've already told you about, a problem that's getting harder to fix the longer it's left alone. The prompts below are built to surface that kind of urgency honestly, or to admit plainly when none exists.
6. Cost-of-delay, made specific
The prospect wants to wait until "[WHEN]". Here's what continuing the
status quo actually costs them in the meantime: "[SPECIFIC COST, IF
KNOWN]"
Draft a response that makes the cost of waiting concrete and specific,
using only information I've given you. If I don't have a specific cost,
say so rather than inventing urgency that isn't real.
7. "What changes between now and then" question
The prospect said they want to revisit this in "[TIMEFRAME]". Draft a
question I can ask to understand what specifically will be different
then that isn't true now — new budget, a different priority, something
else finishing first.
8. Low-commitment next step
The prospect isn't ready to commit but seems genuinely interested. Here's
what we could offer as a smaller next step: "[TRIAL, PILOT, SMALLER
SCOPE — WHATEVER'S REAL]"
Draft a response proposing a real, smaller next step from the options
I've given you, not a made-up offer.
9. Re-engagement email for "check back later"
Write a short follow-up email to send at "[AGREED FOLLOW-UP DATE]",
referencing what we discussed: "[KEY POINTS FROM THE CONVERSATION]"
Under 120 words. Reference the specific conversation, not a generic
check-in. Ask one clear question rather than a vague "just checking in."
10. Distinguishing real timing from a soft no
Here's how the prospect phrased their timing objection: "[EXACT WORDS OR
PARAPHRASE]"
Based only on this, suggest whether this reads more like a genuine timing
constraint or a soft way of declining, and what follow-up question would
clarify it. Say plainly if the wording doesn't give you enough to tell.
How do you handle "we're happy with what we have"?
By addressing the real switching cost honestly instead of dismissing the prospect's loyalty to their current solution as irrational.
"We're happy with what we have" is rarely a lie. Most of the time it's an accurate description of a real, if imperfect, working relationship the prospect has with their current tool or vendor, and treating that loyalty as an obstacle to argue away tends to put the prospect on the defensive. The stronger move is acknowledging the switching cost is real, since it is, and then making the honest case that the gap between the two options is worth paying that cost to close. That only works if the gap is genuinely real and genuinely stated, not invented for the pitch.
11. Honest switching-cost acknowledgment
The prospect is attached to their current solution: "[WHAT THEY'RE
USING]". Here's what switching to us would actually require: "[REAL
MIGRATION EFFORT, TRAINING, TRANSITION TIME]"
Draft a response that honestly acknowledges the switching cost rather
than minimizing it, then explains why it's worth it given what I've told
you about the gap.
12. Gap-identification question
The prospect said their current solution is "fine." Draft three specific
questions to ask that would surface a real gap, if one exists, without
assuming there is one. If they genuinely have no gap, that's useful
information too — don't lead the questions toward a predetermined answer.
13. Status-quo risk, stated plainly
Here's a real risk of staying with the current approach, if one applies:
"[SPECIFIC RISK — COST GROWING, TEAM OUTGROWING IT, A KNOWN LIMITATION]"
Draft a response stating this risk plainly and specifically. If I haven't
given you a real, specific risk, don't manufacture a vague one just to
create urgency.
14. Reference or proof-point request
The prospect wants proof this works before switching. Here's what we
actually have available: "[REAL CASE STUDIES, REFERENCES, DATA WE CAN
SHARE]"
Draft a response offering only the real proof points I've listed. Don't
imply we have a case study or reference that doesn't exist.
15. Trust-building without pressure
The prospect seems hesitant but hasn't stated a specific objection. Here's
what I know about their hesitation: "[WHATEVER YOU'VE OBSERVED]"
Suggest a response that builds trust and creates space for them to name
the real concern, rather than pushing toward a decision they're not ready
for.
How do you handle a competitor comparison honestly?
By naming where the competitor is genuinely better when it's true, since a comparison that only ever favors you stops sounding credible after the second point.
A prospect evaluating two vendors has usually done at least some homework already, and a comparison that claims total superiority on every single point reads as either dishonest or uninformed, neither of which helps you. Conceding a genuine competitor strength costs almost nothing in the moment and buys real credibility for the rest of the comparison, because the prospect now has evidence you're giving them a straight answer rather than a sales pitch dressed up as analysis.
16. Honest feature comparison
The prospect is comparing us to "[COMPETITOR]" on "[SPECIFIC FEATURE OR
DIMENSION]". Here's what I actually know about both, including where
they're stronger: "[YOUR HONEST KNOWLEDGE, INCLUDING GAPS ON OUR SIDE]"
Draft a comparison that states the honest picture, including where
they're ahead, rather than only listing our advantages. Do not claim we
match a competitor feature we don't actually have.
17. Concede-and-redirect for a valid gap
The prospect pointed out something the competitor does that we genuinely
don't: "[THE GAP]". Here's why it might still make sense to choose us
anyway: "[YOUR HONEST REASONING — DIFFERENT PRIORITY, ROADMAP, OVERALL FIT]"
Draft a response that concedes the gap honestly first, then makes the
case for us on its actual merits, without minimizing or talking around
the conceded point.
18. "Why not both" scenario
The prospect is considering using both us and "[COMPETITOR]" for
different purposes. Here's how our actual scope differs: "[REAL
DIFFERENCE IN SCOPE OR USE CASE]"
Draft a response addressing whether that makes sense, honestly, based on
the actual overlap or lack of overlap I've described.
19. Unverified-claim guardrail check
Review this draft competitor comparison for any claim I can't actually
verify: "[PASTE DRAFT]"
Flag any sentence that states something about the competitor as fact
without a source I've given you. I'd rather soften an unverified claim
than have it come back on me later.
20. Switching-from-competitor case
This prospect is currently using "[COMPETITOR]" and considering switching.
Here's what's prompting the switch, if known: "[REASON, IF STATED]"
Draft a response acknowledging their reason for considering a switch and
addressing it directly, rather than a generic pitch that ignores why
they're even having this conversation.
How do you find the real blocker before a close?
By asking directly, since the stated objection at the closing stage is frequently a stand-in for a different, unstated concern.
By the time a deal reaches the closing stage, the stated reason for hesitating is often not the whole story. A prospect who says they need "more time" may actually be waiting on a stakeholder who hasn't weighed in yet, or quietly uncertain about a feature they're too polite to bring up again, or simply not the actual decision-maker they presented themselves as earlier in the process. Guessing at the real blocker wastes a call; asking directly, respectfully, usually surfaces it in one exchange.
21. Surfacing the real objection
The prospect gave this reason for hesitating: "[STATED REASON]", but it
feels like there might be something else going on. Suggest a direct,
respectful question to ask that would surface the real concern without
being pushy.
22. Multi-stakeholder objection mapping
Here's what I know about the different people involved in this decision
and where each one seems to stand: "[LIST STAKEHOLDERS AND THEIR
POSITIONS, AS FAR AS YOU KNOW]"
Help me map out whose objection actually needs to be addressed to move
this forward, based only on what I've told you.
23. Silent-prospect re-engagement
This prospect went quiet after seeming interested. Here's the last thing
we discussed: "[LAST TOPIC OR OPEN ITEM]"
Draft a short, low-pressure message re-opening the conversation, referencing
the specific last topic rather than a generic "haven't heard from you."
24. Post-loss honest debrief question
We lost this deal. Here's what I know about why: "[WHAT WAS SAID OR
OBSERVED]"
Draft two honest questions I could ask the prospect, if they're open to
it, to understand the real reason we lost — not to relitigate the deal,
but to learn something for the next one.
25. Objection-pattern review across recent deals
Here are the objections that came up across our last several deals:
"[LIST OBJECTIONS FROM RECENT DEALS]"
Group these into recurring categories and flag which one shows up most
often. This is meant to surface a pattern worth fixing upstream — in
pricing, positioning, or the pitch itself — not just handled better
one call at a time.
The short version
Objection handling gets faster with practice, but it gets better with honesty, and those are different improvements. The 25 prompts above are organized around five categories a real sales cycle actually produces, and every one of them is built around a single constraint: draft the response from facts you know to be true, never from a claim that sounds good enough to close. A deal won on an honest, specific answer to a hard objection tends to stay closed. A deal won on a claim that doesn't survive the first month of actual use costs you the customer, the reference, and the next deal that customer would have sent you.
Use these to prepare before calls, not to script them live. A rehearsed answer delivered in your own words, adjusted to what the prospect actually said, reads as confidence. The same answer read verbatim off a card reads as exactly what it is.
The pattern review in prompt 25 deserves more attention than reps usually give it. Objection handling improves call by call, but the bigger, cheaper win usually sits one level up: if the same objection keeps showing up across most of your deals, that's rarely a coaching problem for individual reps to solve one conversation at a time. It's a signal about pricing, positioning, or the pitch itself that's worth fixing once, upstream, rather than handling gracefully forever downstream. Run that review monthly if you run a team, or after every handful of deals if you're selling solo, and treat what it finds as a product and messaging question, not just a sales-skill one.