What you'll get
- 7 copy-ready blocks
- 7 min read
Sales objection handling fails when the reply arrives faster than the understanding. Every reply in this bank follows one pattern: acknowledge without surrendering, ask one question to find the real shape, then answer the real thing. The 25 below are grouped by what the buyer is actually saying, which is rarely the words used.
The three-step pattern
1. Acknowledge "That is fair" or "most people say that". No "but".
2. Ask One question that locates the real objection.
3. Answer The real thing, briefly, with proof where you have it.Step 2 is the one sellers skip, and it is the step that works: half the objections below dissolve into something more specific once asked about.
Group 1: Price and budget (what they are saying: justify it or leave)
1. "Too expensive."
"Compared with what? Doing nothing has a cost too; what is the
problem costing now?" Then price against that number, not the air.
2. "No budget this year."
"Understood. When does the budget get set, and what would need to be
on the table by then?" Park with a date tied to their cycle.
3. "Your competitor is cheaper."
"They might be. What does their quote include? List against list is
usually a different conversation than price against price."
4. "We need a discount to proceed."
"What I can do is adjust scope so the price fits the budget. What is
the number that works?" Trade scope, never just margin.
5. "Send pricing first."
"Pricing depends on scope, so a number now would mislead you. Give me
15 minutes to scope it and the quote will be real."Group 2: Timing (what they are saying: not today, maybe not ever)
6. "Call me next quarter."
"Happy to. What changes next quarter?" If the answer is real, park
with that date. If it is vague, the objection is not timing.
7. "We are too busy right now."
"That is usually when this problem costs the most. What is eating
the time, and does it touch [the problem]?"
8. "We just started another big project."
"Makes sense. Does it depend on [area you fix]? If yes, worth 15
minutes now; if no, when does it land?"
9. "It is not a priority."
"Fair. What are the top two, so I know whether we are relevant to
either?" Their answer either connects you or releases you.Group 3: Status quo and competitors (what they are saying: moving is risky)
10. "We already have a vendor."
"Most of our clients did. What would the current one have to get
wrong for you to look around?" Log the renewal month.
11. "We built something in-house."
"Respect. Who maintains it, and what happens when they leave?"
In-house tools die by bus factor; ask, do not argue.
12. "We tried something like this and it failed."
"What failed, the tool or the rollout? That history is exactly what
I would want to design around." The failure story is gold; mine it.
13. "Excel works fine for us."
"It usually does, until a specific moment. What breaks first when
volume doubles?" Scale the pain, not the pitch.
14. "Switching costs are too high."
"Sometimes true. Can we list them? Half the time the list is
shorter than the fear, and if not, I will say so."Group 4: Trust and size (what they are saying: you are a risk)
15. "We have never heard of you."
"Reasonable. Here is [peer company] on the same problem, and two
clients who will take your call. What proof would move it for you?"
16. "You are too small for us."
"Small means you get our senior people, not a ticket queue. The
real question is risk; what would de-risk it: a pilot, references,
an exit clause?"
17. "Can you even support our region or hours?"
Answer factually, including the limits. One honest limit buys more
trust than three assurances.
18. "We would need this through procurement and security review."
"Good, that is normal. Here is our standard pack; who runs that
process so I can work with them directly?" Procurement named early
is a gift.Group 5: Product and fit (what they are saying: convince the evaluator)
19. "It does not integrate with [system]."
If true: "Correct, today. Here is what clients do instead, and the
roadmap answer if you need it in writing." Never bluff integrations.
20. "It is missing [feature]."
"What would you use it for?" Half the time the job is doable another
way; the other half, say plainly it is not there.
21. "Our case is different."
"Every client said that, and it was partly true. Which part of your
case is genuinely unusual? That is where we should spend the demo."
22. "The team will not adopt it."
"What did they refuse to adopt before, and why? Let us put a user
in the next meeting; adoption objections are best answered by users."Group 6: Process and authority (what they are saying: I cannot say yes)
23. "I need to check with my boss."
"Of course. What will they ask you, and would it help if I gave you
a one-pager answering exactly that?" Arm the champion; do not
bypass them.
24. "Send me something and I will circulate it."
"Will do. Who is on the circulation list? I will tailor it so each
person sees their part answered." The list is the committee map.
25. "We decided to do nothing for now."
"Thanks for telling me straight. What would reopen it, and may I
check in when [their stated trigger] happens?" Park with the
trigger logged, then actually leave.Worked example (illustrative, not a real company)
On a call with Pellow and Rook, Sam Carter hears objection 12: "we tried scheduling software two years ago and the drivers hated it." Old reflex: defend the category. The pattern instead: acknowledge, then ask what failed. Answer: the rollout gave drivers no training and the interface was desktop-only. That history becomes the proposal's spine: a driver pilot, mobile-first, training included, and the sceptical depot manager invited to design it. The objection was the account plan, arriving disguised. All names are invented.
Five mistakes to avoid
- Answering the words instead of the meaning. "Too expensive" has five different meanings in group 1 alone. The question in step 2 finds which one you got.
- Winning the exchange, losing the room. A clever counter the buyer cannot answer feels like victory and reads as pressure. The pattern leaves them room to move.
- Bluffing on product objections. Group 5 replies work because they include honest limits. One caught bluff retires every other answer you gave.
- Treating authority objections as brush-offs. Numbers 23 and 24 are invitations to multithread; armed champions and circulation lists are how committee sales move.
- Handling the same objection twice. The second time you hear it from the same account, it is not an objection, it is a decision you have not accepted yet. Name it gently and ask.
Why this works on named accounts
Common questions
What is the best way to handle sales objections?
Acknowledge without arguing, ask one question to find what the objection really is, then answer that briefly with proof where you have it. The question in the middle is the step that matters: most stated objections are standing in for a more specific one that is easier to answer.
How do you handle the price objection?
Find the comparison first: too expensive against what? Against doing nothing, price the problem using their numbers. Against a competitor, compare what each quote includes. Against the budget, trade scope rather than discounting the same scope. A naked discount answers none of the three.
Should you ever accept an objection and walk away?
Yes, and visibly. When the answer to "what would change this?" is nothing you can affect, thank them, log the trigger that might reopen it and leave politely. On named accounts the graceful exit is a sales asset: the market is small, people move jobs and the seller who left well gets the next call.
More from the Academy
Outbound Call Script (Three Branches)
For anyone whose cold calls go fine until the prospect answers.
You leave with one honest opener, three word-for-word branches for interested, not now and no, and three objection replies that do not argue.
Discovery Call Question Bank by Function
For sellers whose first call with a new stakeholder sounds like the last one.
You leave with a call plan, 36 questions for 6 functions, 4 closing questions, a notes header and one plan filled in.
Second-Meeting Plan
For sellers whose first meetings go well and then go quiet.
You leave with a close for the last five minutes of meeting one, three things to change before meeting two, a 25-minute agenda and an honest parking rule.
Want this in your inbox?
Optional. We use your email only to send you this, nothing else.