The five steps of objection handling are: listen to the whole objection, ask what sits behind it, confirm your understanding back to the buyer, answer the concern they confirmed, and check that the answer settled it before moving on.
- 01Listen fully
- 02Ask what is behind it
- 03Confirm it back
- 04Answer the confirmed concern
- 05Check it is settledThen agree the next step
The short version
Published lists of objection handling steps vary in wording and agree on the order: listen and question before any answer. The first thing a buyer says is often not the real objection, and the steps exist to stop the rep answering the wrong one. That is why most of the work sits in the first three. The answer is often short once the rep knows what the buyer meant.
Objections are one part of running a good first conversation; our discovery call guide covers the rest.
What counts as an objection
An objection is any reason the buyer gives for not taking the next step: not now, not at this price, not without someone else, not with this vendor. A question is different. "How long does implementation take?" asks for information. "We can't take on an implementation this quarter" is a reason to stop. A question gets an answer. An objection gets the five steps, because the reason the buyer states may not be the one that matters.
Brush-offs sit in between. "Send me some information" at the end of a cold call is often a polite way to end it. Treat it as an objection, ask what the buyer would want to see in that information, and the conversation often keeps going. Treat it as a request and the email goes unread.
The five steps, side by side
| Step | What it sounds like | How it usually goes wrong |
|---|---|---|
| Listen fully | Silence until the buyer stops, then a short acknowledgment: "That's fair." | The rep answers mid-sentence |
| Ask what is behind it | "What are you comparing it to?" or "Is there anything else in the way?" | A defensive question that sounds like an argument |
| Confirm it back | "So the concern is how finance reads a second tool this year?" | Skipped, so the rep answers their own guess |
| Answer the confirmed concern | The buyer's own numbers from discovery, set against the concern | A generic value pitch with placeholder figures |
| Check it is settled | "Does that cover it, or is there more?" Then agree the next step | The rep moves on and the objection returns in procurement |
Two moves from other versions of the list belong inside these five. In step two, ask whether anything else stands in the way, which stops a second objection appearing after the first is answered. In step five, ask what happens next inside their organization and offer what the champion will need.
Each step in detail
1. Listen fully
Let the buyer finish, including the second sentence. Buyers often state the objection and give the reason in the next breath ("It's too expensive. We spent a lot on the last tool and nobody used it."), and a rep who answers after the first sentence never hears the second. Acknowledge without agreeing or arguing. "That's fair" or "I can see why that comes up" tells the buyer they were heard and commits the rep to nothing. Avoid "I hear you, but", which cancels the acknowledgment in the same breath.
The habit worth practicing is a two-second pause after the buyer stops. It feels long on a call. The buyer rarely notices it, and they often fill it with the real concern.
2. Ask what is behind it
Ask one open question about the objection itself, using the buyer's words: "Too expensive compared with what?", "What changes next quarter?", "Who else would want a say?" Then isolate it: "Apart from that, is there anything else that would stop this going ahead?" If a second concern comes out, you know the order to handle them in, and you will not answer the first only to meet the second in procurement.
The probe has to sound curious. "Why would you say that?" sounds like a challenge, and a challenged buyer defends the objection instead of explaining it.
3. Confirm it back
Restate the concern in one sentence, in the buyer's words, and ask if that is right: "So the price is fine against the problem, and the worry is getting a second budget line approved this year?" The buyer either agrees or corrects you, and both help. A correction costs ten seconds. Answering the wrong concern can cost the deal.
This is the step that gets dropped under pressure, because the answer feels ready. It is also the step that shows the buyer the rep was listening, which makes the answer easier to hear.
4. Answer the confirmed concern
Answer only what the buyer confirmed, as briefly as you can, and from their own evidence where you have it. Start from what the buyer said in discovery: the cost they put on the problem, the deadline they named, the people they said were affected. "You mentioned the team loses four hours a week to manual reports" is hard to dispute, because the number is theirs. A customer story can follow if it matches their situation closely.
If discovery did not produce that evidence, a smaller next step is often the honest answer: a pilot with one team, a call with a reference customer, a session with the person who holds the concern. That still counts as an answer. It keeps the deal moving while the evidence is gathered.
5. Check it is settled
Ask whether the answer covers it: "Does that deal with it, or is there more to it?" Silence or a vague "I guess so" means it is not settled, so go back to step two. When the buyer says yes, agree the next step with a date, and ask who else inside their organization will raise the same concern. A convinced champion still has to convince a CFO, and they will need the answer in a form they can forward: two lines, in their words, with the figure they gave you. Objections from multiple decision makers covers that part of the job.
After the five steps, one job remains once the call ends: write down what the objection said about the deal. A timing objection may mean the cost was never stated. An authority objection may mean the approver was never met. That note is what a manager coaches in the next deal review.
Example: one objection, five steps (illustrative)
This deal is invented. Jordan sells analytics software to a head of operations, who says: "We'd need to wait until next quarter."
Jordan lets her finish and says it is fair. He asks what changes next quarter. She says the budget resets, and adds that her CFO is wary of new tools after a failed rollout. Jordan confirms: "So timing is about the budget, and the bigger question is whether the CFO trusts the rollout?" She agrees.
Jordan answers the second part: the four hours a week she said her analysts lose to manual reports, and a two-week pilot with one team. He checks: "Would that be enough for the CFO to look at it this quarter?" She says it might, and books a call with the CFO. Afterward Jordan logs the gap: the CFO had not been met, and the stated cost came from the head of operations alone.
Handling an objection that arrives by email
Some objections arrive in writing: "Thanks for the proposal. We've decided to hold off for now." The steps still apply, but email is poor at steps two and three, because a written probe reads as pressure and the buyer can simply not reply. Keep the reply short, acknowledge the decision, and ask for a call to understand it: "Understood, and thanks for telling me. Could we take fifteen minutes this week so I can hear what changed? It would help me either way." On the call, start at step two.
If the buyer will not talk, ask one question in writing and make it easy to answer: "Is it timing, or something about the proposal itself?" A one-word reply still tells you which group the objection belongs to.
Common objections, run through the steps
The objection a buyer states usually falls into one of six groups. The middle column is a starting guess about what sits behind it; step two is there to test the guess on the call.
| Type | Sounds like | Often means | Probe | Evidence the answer needs |
|---|---|---|---|---|
| Price | "It's too expensive." | The cost of the problem was never agreed, or the budget sits with someone else | "Too expensive compared with what?" | The cost the buyer put on the problem, and who owns the budget |
| Timing | "Let's revisit next quarter." | Another priority won, or the problem does not feel urgent yet | "What changes next quarter?" | A deadline or event on the buyer's calendar |
| Authority | "I need to run it past my boss." | The rep has not met the approver, or the contact is unsure how to sell it inside | "What will your boss want to know first?" | The approver's name and what they will judge it on |
| Need | "We're fine with what we have." | The problem has not been tied to a cost anyone cares about | "How is the current setup handling the backlog you mentioned?" | A problem the buyer described in their own words |
| Risk | "We tried something like this and it failed." | A past rollout cost someone credibility | "What went wrong last time?" | What a smaller, safer first step looks like to them |
| Incumbent | "We already have a vendor for that." | Switching cost, or a relationship worth protecting | "What would have to be true for you to look at an alternative?" | The gaps in the current setup, in the buyer's words |
Price needs one extra note. A discount offered at step four answers a concern nobody confirmed. If the buyer confirms the issue is the total, a change to scope or price may be right. If it is the timing of the budget, payment terms may solve it. If it is value, a discount makes things worse, because it suggests the first price was never real. How to handle price objections and how to handle competitor objections go further on those two groups.
Objections by deal stage
The same five steps apply all the way through a deal, and the objections change as it moves. Knowing which ones each stage tends to produce helps a rep prepare the probe before the call.
First call. Brush-offs and need objections: "We're fine with what we have," "Send me something." The buyer has not yet described a problem, so step two is mostly discovery. Ask about the current setup and listen for something that costs them.
Discovery and evaluation. Fit and risk objections: "Does it work with our system?", "We tried this before." These are often questions dressed as objections. Confirm which it is at step three, and answer a question with information.
Proposal. Price and timing: "It's more than we expected," "Let's wait for the new budget." These are where the discovery evidence pays off, because the answer is the cost the buyer already put on the problem.
Approval and procurement. Authority and process: "Legal needs to review," "The CFO wants to see alternatives." The rep is often not in the room, so step five matters most. Give the champion what they need to carry the answer, and ask to meet the person raising it.
Preventing objections in discovery
The cheapest objection to handle is the one discovery already answered. Most late objections trace back to something the rep did not establish early: the cost of the problem, who approves the spend, or what happens if the buyer waits.
A rep who leaves discovery with the buyer's own figure for the problem, the approver's name and a date driven by an event on the buyer's side will still hear objections. They will be smaller, and the answer to each one is already in the notes. When the same objection keeps coming up across a team's deals, look at discovery before writing a better response for the playbook.
Mistakes that undo the steps
Correcting the buyer. "That's not quite right, we're cheaper than..." wins a point and makes the buyer defend their position. Fix: acknowledge first, then ask.
Treating every objection as price. Reps who expect price hear price, and a rep who discounts a deal whose real objection is an unmet approver gives away margin and still has to meet the approver. Fix: confirm it back before answering, even when the answer seems obvious.
Reading the answer from a script. Scripted probe and confirm lines help, because they keep the rep calm. A scripted answer sounds like one, and it ignores what this buyer said. Fix: script the questions, build the answer from the deal.
Handling it by proxy. The champion reports that the CFO thinks the price is high, and the rep sends the champion a reply to forward. Fix: ask to meet the CFO, or at least to brief the champion on a call before they go in.
Turning the five steps into an objection handling playbook
A team playbook is the five steps written against the objections your reps hear on live deals. To build one:
- Collect objections in the buyer's exact words from recent calls.
- Group them by what they usually mean: price, timing, authority, need, risk or an incumbent.
- For each group, write the probe question and a confirm-back line a rep can say without reading it.
- Next to each, note the discovery evidence the answer needs, such as a stated cost or the approver's name.
- Review the playbook in deal reviews and add any objection that has come up twice.
An illustrative entry: "We'd need to wait until next quarter." Probe: "What changes next quarter?" Confirm: "So the timing is about the budget reset?" Evidence needed: the cost the buyer stated, and who can approve spend outside the cycle.
How to practice the five steps
Reps get better at objection handling by doing it on their own deals with someone listening. Three habits make that happen.
In the deal review, when a rep reports an objection, ask for the buyer's exact words, the probe the rep asked and what the buyer confirmed. If the rep cannot say, the next call has a job: find out what the objection meant.
Before a call where an objection is likely, rehearse the probe and the confirm line out loud. A line said once before the call comes out more naturally during it.
Then practice against the deal itself. Our AI sales experts, such as Caty, do this on a call: the rep talks the deal through, the expert builds a roleplay from what this buyer has said so far, the rep runs the five steps against the objection they expect, and the expert debriefs it. After the real call, the rep comes back to debrief what the buyer said, and the expert notes what the objection revealed about the deal. To watch it run on a live deal, talk to us.
Related guides
The full job is in objection handling, and the after-call step lives in the objection handling worksheet. Want to know which step your reps skip? Talk to us.
FAQ
Which step of objection handling matters most?
In our view, asking what sits behind the objection matters most, because the first thing a buyer says is often not the real concern. A rep who answers the surface objection can win the argument and still lose the deal. Confirming the concern back before answering protects that step.
What is the difference between the 4 Ps and the five steps?
The 4 Ps and the five steps describe the same sequence with different labels. The 4 Ps (often pause, probe, paraphrase, provide) compress listening and questioning into two words each. The five-step versions add an explicit check at the end that the answer settled the concern and that the next step is agreed.
How do you know an objection has been handled?
An objection is handled when the buyer says the answer covers it and then acts: they agree a dated next step. Agreement with no next step usually means the objection has gone quiet. Check at the start of the next call: "Last time the concern was the budget timing. Is that still where it is?"
When should you walk away from an objection?
Walk away when step two shows the objection is a fact about fit. If the buyer needs something the product does not do, or there is no budget this year and nothing will change that, say so and agree when to talk again. Pushing past a real fit problem tends to produce a deal that stalls in procurement or a customer who leaves at renewal.
How do you prepare for objections before a call?
Read the deal and list the objections it is likely to raise. A missing approver predicts an authority objection; a cost the buyer never stated predicts a price one. For each, write the probe and the confirm line, and note the discovery evidence you would answer with. If that evidence is missing, the call has a discovery job before it has an objection to handle.
Should you handle an objection immediately or later?
Handle it when it comes up if it blocks the conversation, and park it if it does not. Say you will come back to it, note it, and return before the call ends. Unanswered objections tend to resurface at the approval stage, where the rep is not in the room.