Objection handling: how to answer 20 common sales objections

This guide is for SDRs, account executives and founders who sell to businesses, on the phone, in meetings or by email. It covers the method first, then responses to the 20 objections you'll hear most, grouped by type, then drills to make them automatic. The responses are starting points. The best version of each uses your own customers' words and a fact about the account in front of you. For the first ten seconds of a cold call, the outbound call scripts have shorter branches.

First, work out what kind of objection it is

Every objection is one of four things. The right response depends on which.

The last row is the one sellers get wrong. To tell a condition from an objection, ask three things: Is it true? Will it change soon enough to matter? Can you change it? If it's true, won't change for a year and you can't change it, it's a condition. Thank them, ask when it changes, set a reminder and spend your time on accounts that can buy.

A six-step method for any objection

1. Let them finish, then pause. Interrupting tells the buyer you weren't listening. A two-second pause often brings out the real reason.
2. Restate it in their words. "So the concern is the time it takes engineers away from billable work?" Being corrected here is useful.
3. Ask one question to find what's behind it. "Compared with what?" or "What's driving that?" The first objection often hides another.
4. Answer the real concern, briefly, with something specific to them: a fact about their business, a similar customer, or an option.
5. Check it landed. "Does that answer it, or is there more to it?"
6. Agree a next step, or accept the no. A small, dated step if it's resolved. If it's a real no, ask when it might change.

Popular frameworks, honestly

Most objection frameworks are variations on the same idea: acknowledge, explore, respond. Each has a place, and each fails in a predictable way.

Feel, felt, found is the most taught and the most mocked. Its weak point is the "found": it only works if a real customer like this one found that result. If you put it in writing, treat it as marketing. The FTC's Endorsement Guides require endorsements to reflect the endorser's honest experience, and a customer's result on a key point is likely to be read as typical unless you say otherwise. Use real, similar customers, and only with their permission.

The 20 objections you'll hear most, with responses

Each card gives what's usually behind the objection, what to say, and what to do next. Change the brackets for each account.

Price

Behind it: no reference point yet, or the value isn't clear.

Say: "Fair. Compared with what: another quote, or the cost of leaving it as it is?"

Then: Another quote: compare total cost over the full term, on their numbers. Doing nothing: ask what the problem costs them now.

Real no: the problem is worth less than the price. Say so and leave the door open.

Behind it: money isn't allocated, or the problem isn't a priority yet.

Say: "Understood. Is that 'nothing until next year', or 'this would need a business case'?"

Then: Business case: offer to build the numbers together. Next year: ask when budgets are set.

Real no: budget is frozen and the problem can wait. Follow up when planning starts.

Behind it: a buying habit, a real limit, or a competitor's quote.

Say: "Possibly. What would you need to see to sign this month: a lower total, a smaller start, or different terms?"

Then: Trade, don't give. A smaller scope, a longer term or an earlier signature in return for any change.

Never: cut the price before they've agreed to everything else.

Behind it: a real quote and a budget gap, or a negotiating lever.

Say: "They may well be. Can we compare the same scope over the full term, including setup and minimums?"

Then: If they're cheaper like for like, name the one difference worth paying for, or concede gracefully.

Timing

Behind it: a busy day, or a low priority.

Say: "Got it. Is that 'this week is busy' or 'this isn't a priority this year'?"

Then: Busy: book a specific time. Not a priority: "What would need to change for it to become one?"

Behind it: politeness, or a real planning cycle.

Say: "Happy to. What happens next quarter that makes it a better time?"

Then: A real event (budget, a hire, a contract end): book the call now for just before it. No event: it's probably a soft no, so ask directly.

Behind it: a genuine limit on time and people.

Say: "That makes sense. When does it go live? Would it help to plan now, so you can start once it's done?"

Then: Ask whether the project makes the problem worse. Sometimes it's the reason to act.

Status quo and competitors

Behind it: switching cost, loyalty, or no felt pain.

Say: "Most teams I speak to do. What do you like most about them? And if you could change one thing?"

Then: Ask how they handled [the situation from your research].

Real no: happy and under contract. Ask when it renews.

Behind it: control, cost, or pride in what they built.

Say: "Makes sense. Who looks after it, and how much of their week does it take?"

Then: Compare the people time with your price. Sometimes in-house is the right answer, and saying so builds trust.

Behind it: no felt pain.

Say: "Good to hear. Out of interest, how are you handling [the trigger, e.g. the 40 new hires]?"

Then: If the answer shows a gap, explore it. If not, believe them, and ask what would make them look again.

Behind it: a bad experience and fear of a repeat.

Say: "That's useful to know. What went wrong?"

Then: If you'd hit the same problem, say so. If not, explain exactly what's different and offer a small test.

Authority

Budget and authority objections are easier to avoid than to answer. The BANT questions surface them in discovery, before they become objections.

Behind it: a real process, or a polite exit.

Say: "Of course. What do you think they'll ask? What would they need to see to say yes?"

Then: Offer a one-page summary they can forward, or ten minutes with them. Agree a date to reconnect.

Behind it: usually true.

Say: "Thanks for telling me. Who looks after [specific area]? Would you mind if I mention you pointed me to them?"

Behind it: process, not resistance.

Say: "Good to know now. What does that involve, how long does it usually take, and who runs it?"

Then: Send your security documents and standard terms before they're asked for. Put each step in a shared plan with dates.

Trust and risk

Behind it: risk. Nobody gets blamed for choosing the known name.

Say: "Fair. We work with [type of company], including [customer you may name]. What would you need to see to trust a smaller supplier?"

Then: Offer a reference call with a similar customer.

Behind it: interest, plus risk.

Say: "You shouldn't take my word for it. What would a fair test look like, and what result would convince you?"

Then: Agree a small pilot with success criteria written down before it starts.

Behind it: a real cost that sellers often underplay.

Say: "It is some work. Here's what it takes from your side, week by week. Which part worries you most?"

Then: Be specific about their time. Vague reassurance makes this worse.

Brush-offs and stalls

Behind it: a polite exit, or real interest with no time.

Say: "Happy to. So it's worth reading: which matters more right now, [outcome A] or [outcome B]?"

Then: Send two lines on that, with a proposed time to talk.

Behind it: a reflex, or a real no.

Say: "Understood. Is that because [problem] isn't an issue for you, or because now isn't the time?"

Then: Not an issue: thank them and stop. Timing: ask when to check back.

Behind it: a concern they haven't said out loud.

Say: "Of course. When people say that, there's usually one part they're unsure about. What would you be thinking over?"

Then: Answer that, then agree a date to decide.

For competitor objections in depth, build a sales battlecard for each rival you meet often.

How account context changes the response

Generic responses fail because the buyer has heard them before. A response that uses something true about their business gives them something to confirm or correct. Here's the same objection, "We already do security training", from a training vendor's point of view, at four different accounts:

Before an important call, spend five minutes on the facts that tend to decide each type of objection:

Bebop account playbooks include the objections each account is likely to raise, based on what's happening at the company. Treat them like your own research: a starting list to check, not a script.

Practice drills

Reading responses doesn't make them automatic. Saying them out loud does. Four drills that take under 20 minutes:

1. The objection ladder (pairs, 10 minutes). The "buyer" raises the same objection three times, each more firmly. The rep must respond differently each time, and accept a third no gracefully.
2. Questions only (5 minutes). The coach reads ten objections. The rep may only answer with a question. It builds the habit of diagnosing first.
3. Real no or not? (5 minutes). The coach reads ten objections with a line of context. The rep sorts each into brush-off, concern, missing information or condition, and says why.
4. Call mining (weekly, 20 minutes). Pull five objections from last week's recorded calls, word for word. Score the responses with the card below, and rewrite one response card.

Score each 0 (no), 1 (partly) or 2 (yes). 10 or more is good.

[ ] Let the buyer finish before responding
[ ] Restated the objection in the buyer's words
[ ] Asked a question before answering
[ ] Answer used something specific to this account
[ ] Checked whether the answer landed
[ ] Agreed a dated next step, or accepted the no and asked when to return

Objection (verbatim):
What was really behind it:
Better response next time:

Worked example: three objections on one call

Illustrative example. Sentrel, Calder Ridge Engineering, the people and all figures are fictional, to show the method.

The seller: Sentrel (sentrel.example) sells security awareness training and phishing simulations for $24 per employee per year. The account: Calder Ridge Engineering (calderridge.example), 450 staff, which opened a sixth office in September and is hiring 40 people. The contact: Elena, IT Director, who booked 20 minutes after a cold email.

Elena: I'll be honest, we already do training. Our IT provider runs an annual video course.

Rep: That's common. How do people who join after the course get trained? You're hiring about 40 this year.

Elena: They wait for next year's course, I suppose.

Rep: So some new starters could go most of a year without it. Is that a concern, or fine for now?

Elena: It's a concern. But budget's set until January.

Rep: Understood. Is that "nothing until January", or "this would need a business case"?

Elena: January. And Ray, our managing partner, would have to sign off. He hates anything that takes engineers off billable work.

Rep: That helps. How long is the annual course?

Elena: About an hour.

Rep: Our modules take four minutes a month, about 48 minutes a year. Would it help if I wrote the time comparison up for Ray?

Elena: That's the argument he'd listen to.

The note the rep sent that afternoon:

They agreed a 20-minute call with Elena and Ray in early December, before January budgets are final.

What made this work:

• The status quo objection got a question about a gap tied to a researched fact (the 40 hires), not an attack on the incumbent.
• The rep asked which kind of "no budget" it was instead of offering a discount.
• The authority objection hid the real concern, billable time. The rep answered it in the partner's own measure.
• Every number came from the buyer or a public fact, so Elena could check it.

Common mistakes

• Answering before you understand. A fluent answer to the wrong concern loses the buyer faster than a pause.
• Arguing. If the buyer has to defend their position, they'll dig in.
• Discounting first. It tells the buyer the price was never real.
• Treating every no as an objection. Pushing past a real condition burns the relationship you'll need when it changes.
• Using proof that isn't similar. An enterprise case study won't reassure a 200-person firm.

Next step: put your top five objections and the answers that work into the objections module of your sales playbook, so every rep starts from the same answers.