How to Handle Sales Objections: 7 Real Ones and Exactly What to Say

Go read any article on handling sales objections and you'll find the same advice. Emphasize the value. Focus on ROI. Address the root concern.

None of those are sentences you can say out loud on a call.

That's the problem with most objection training: it gives you a category and a strategy, then leaves you to invent the words in real time, under pressure, while somebody waits on the other end of the phone. Reps don't lose deals because they didn't know price objections are about value. They lose because at 2:14pm on a Tuesday, someone said "that's more than we wanted to spend" and their mouth got there before their brain did.

So this is the version with the actual words.

What you'll learn

• Why most objections were created by you, earlier in the call, before anyone said no
• The three seconds that decide whether you handle the objection or argue with it
• Seven real objections, what each one actually means, and the exact response
• How to tell a real objection from a brush-off - and when to stop
• How to practice this so it survives contact with a live buyer

First: most objections are your own work coming back

Here's the thing that reframes all of this.

An objection is rarely new information. It's almost always something that was true the entire call, that you didn't surface, that the buyer is now telling you at the worst possible moment.

"It's too expensive" usually means you presented price before establishing what the problem costs them. "I need to talk to my boss" usually means you didn't ask who else weighs in. "Send me some information" usually means you pitched before you understood what they cared about.

None of those are objections. They're receipts.

An objection at the end of a call is usually a question you skipped at the start of it.

This matters because it changes where you spend your effort. Most reps try to get better at responding. The bigger gain is getting better at discovery, so fewer objections show up at all. The best objection handling is the objection that never gets raised, because you already dealt with it while it was still just a question.

That said - you're going to get objections anyway. So.

The three seconds that decide everything

When someone objects, there's a gap between what they said and what you say next. What you do in that gap determines the outcome more than your actual answer.

Most reps fill it with a reflex:

• They defend. "Well, actually, our pricing includes -"
• They discount. "I might be able to do something on price."
• They agree too fast. "Totally, I get it, no problem."

All three end the conversation in different ways. Defending makes it a debate. Discounting confirms the price was fake. Agreeing too fast tells them you weren't confident in the first place.

What should happen instead is almost nothing. You acknowledge, and then you ask.

Acknowledge, then question. That's it. That's the whole mechanic, and it works on every objection below.

Acknowledging is not agreeing. "That's fair" doesn't mean "you're right and I'll drop the price." It means I heard you and I'm not going to fight you about it. Then the question does the actual work, because the objection they said out loud is almost never the objection they have.

The 7 objections, and what to actually say

1. Price - "That's more than we wanted to spend"

What it usually means: Not "I can't afford this." Almost always "I haven't decided this is worth that." Those need completely different responses, and you can't tell which it is yet.

What to say:

"That's fair. What are you basing that on?"

Five words that do a lot. It's neutral, it doesn't defend the price, and the answer tells you which objection you're actually dealing with. If they say "we budgeted 10k and you're at 25," that's a real budget problem. If they say "it just seems like a lot," that's a value problem and you have room to work.

What not to say: anything that starts with "but." "But when you consider the ROI -" is a debate, and you will lose it, because arguing with someone about their own money is unwinnable.

2. Authority - "I'd have to run this by my boss"

What it usually means: You're talking to the wrong person, or you're talking to the right person too early. Either way this is a qualification miss, not an objection.

What to say:

"Makes sense. What does your boss need to see to say yes?"

You're not fighting to get past the gatekeeper. You're recruiting them. That question turns the person in front of you into your internal advocate and hands you the actual criteria at the same time.

The prevention: ask in discovery. "Besides you, who else usually weighs in on something like this?" Ask it early and this objection mostly stops happening.

3. Timing - "We're not looking at this until Q4"

What it usually means: Either a genuine budget cycle, or a polite no. You need to know which, and there's one question that reliably separates them.

What to say:

"Got it. What changes in Q4 that makes this easier then?"

If they have a real answer - budget resets, a hire lands, a contract expires - it's a real timeline and you should work it. If they stall, there's no Q4 reason. It's a no, and you're better off knowing.

Then, if it's real: find the cost of waiting. "What does it cost you to run it the current way for another two quarters?" Not as pressure. As arithmetic.

4. Incumbent - "We already have something in place"

What it usually means: They're not thrilled, but switching is work and nobody's forcing them. Inertia, not loyalty.

What to say:

"Good - what's the one thing it doesn't do well?"

Do not attack the incumbent. When you criticize the tool they chose, you're criticizing their decision, and people defend their decisions. Ask them to criticize it instead. They will, if the question is specific enough, and "the one thing" is specific enough to be answerable.

5. The brush-off - "Just send me some information"

What it usually means: A soft no, roughly 80% of the time. Sending the deck is how the deal quietly dies.

What to say:

"Happy to. What specifically do you want me to cover, so I'm not sending you twelve pages you don't need?"

If they can tell you what to include, they're interested and you just got a requirements list. If they can't, they were being polite, and that's worth finding out now rather than after two weeks of follow-up emails.

6. The stall - "Let me think about it"

What it usually means: There's a specific unresolved thing, and they'd rather end the call than say it. It's almost never a general need to reflect.

What to say:

"Of course. What part do you want more clarity on before you decide?"

You're giving permission for the real objection. Most people take it. And whatever comes back is the thing you should have been handling for the last ten minutes.

7. The open - "Not interested"

What it usually means: Thirty seconds into a cold call, this isn't an objection at all. They don't know enough to be uninterested. It's a reflex to being interrupted.

What to say:

"Fair enough - most people aren't when I call. Can I have twenty seconds to tell you why I did, and you can hang up on me if it's not relevant?"

Naming the reflex out loud defuses it, and asking for twenty seconds instead of "a few minutes" is a small enough ask to be worth saying yes to.

When to stop

Here's the part most sales content leaves out, and it's the part that separates a professional from a pest.

Three objections handled with skill is professional. Pushing past a clear no twice is something else.

There's a real difference between someone who has concerns and someone who has decided. Concerns come with questions. Decisions come with closure - short answers, no follow-ups, an obvious desire to get off the phone. When you hit the second clear no, exit cleanly:

"Understood - I'll get out of your way. If it changes, you know where I am."

You keep the relationship, you keep your reputation, and you get the twenty minutes back. Some of the best deals I've seen came from a rep who left the door open instead of forcing it six months earlier.

Why reading this won't make you better at it

You just read seven responses. You'll remember maybe two of them on your next call, and neither will come out the way they read here.

That's not a knock on you. It's how skill works. Objection handling is a reflex, not a knowledge set, and reflexes are built by repetition under something resembling pressure. Reading the answer and having the answer are different things, and the gap between them is reps.

The traditional fix is roleplay with your manager, which has two problems: your manager is busy, and they go easy on you. The alternative most reps land on is practicing on live prospects, which works, but you're paying tuition in real pipeline.

How Rex drills this

This is the part where I tell you what I built, so weigh it accordingly.

Rex is an AI sales trainer that runs objection drills. You pick objection mode, he plays the buyer, and he doesn't go easy. The part that matters isn't the roleplay though - plenty of tools do roleplay. It's the scoring.

Every objection rep gets graded against four named criteria, and you see them before you start:

1. Acknowledged the objection before answering it
2. Reframed without arguing or discounting
3. Asked a question back instead of monologuing
4. Moved toward a specific next step

Four out of four is Strong. Three is Needs Work. Anything less is a miss. You see exactly which box you dropped, every single rep - so instead of a vague sense that the call went badly, you find out you keep skipping the acknowledgment and going straight to the rebuttal.

He also tracks which objections keep beating you. Miss "price" enough times and it becomes a tracked gap he keeps bringing back until you beat it. Beat something you used to fail and it's logged as a comeback, which is the only stat in the whole system I actually care about.

No participation trophies. If the rep was weak, he says so.

See how the objection drills work →

Key takeaways

• Most objections are receipts for questions you skipped in discovery. Fix the front of the call and the back gets easier.
• Acknowledge, then ask. Never defend, never discount, never agree too fast.
• The stated objection is rarely the real one. The question you ask after is what surfaces it.
• Price is usually value, not budget - but ask before you assume.
• "Send me information" is a soft no most of the time. Qualify before you send.
• Two clear nos means stop. Exit clean, keep the door open.
• Reading responses doesn't build the reflex. Reps do.

FAQs

What's the best way to overcome a sales objection?

Acknowledge it without agreeing, then ask a question that surfaces what's actually behind it. The objection someone says out loud is usually not the one stopping the deal.

Should I offer a discount when I get a price objection?

Not as your first move. Discounting immediately tells the buyer your original price wasn't real, and it converts a value conversation into a negotiation you started losing. Find out what they're comparing against first.

How many times can I handle the same objection before it's pushy?

Three handled well is professional. After two clear, closed nos, exit gracefully. The difference is whether their responses still contain questions - concerns ask things, decisions don't.

How do I get better at objections without burning real prospects?

Repetition against something that pushes back, with feedback specific enough to act on. That means roleplay where you find out which part of the response you dropped - not just whether the call "went well."

Are objections a bad sign?

Usually the opposite. Silence and polite agreement are worse. An objection means they're engaged enough to tell you what's in the way.

Related reading

• Objection handling training with Rex - how the drills and scoring work
• Is an AI sales coach worth it? - an honest look, including who shouldn't buy one
• Cold outreach that gets replies - fewer objections start earlier than you think