Common sales objections and how to handle them

The most common sales objections are price, timing, "send me some information", an existing competitor, no authority, no need, status quo and trust. Each one has a usual meaning behind it and a question that finds the real concern. This guide covers all eight, with what to say on the call and a short exchange your team can practice.

If you manage a team, use the exchanges as roleplay scripts. If you sell, read the "what it usually means" part first, because the right response depends on the real reason behind the words.

Why an objection is a good sign

An objection means the buyer is engaged. Someone who has no interest in your product does not explain why it might not work. They go quiet, skip the next meeting or say "sounds good" and never reply.

When a buyer says "that's expensive" or "we already use something," they are comparing your product to their situation. That is the work a buyer does before they buy. Your job is to find out what they are weighing and help them weigh it.

Most objections fall into three groups:

• Real concerns: the buyer sees a risk or a gap you can address (price, trust, competitor).
• Missing information: the buyer does not know enough yet to see the value (no need, status quo).
• Brush-offs: the buyer wants the call to end (timing, "send me some information").

You cannot tell which group you are in from the first sentence. That is why the method below starts with a question.

A 4-step method for any objection

Use the same four steps for every objection in this guide: listen, clarify, respond, confirm.

1. Listen. Let the buyer finish. Do not start your answer while they are still talking. Pause for a second after they stop.
2. Clarify. Ask a question to understand the objection before you answer it. "Help me understand, what makes you say that?" works for almost everything.
3. Respond. Answer the specific concern you just heard, not the general objection. Use one example, one number or one story.
4. Confirm. Check that your answer helped: "Does that address it?" or "Is that the main thing holding you back?" Then move to the next step of the deal.

Here is the method on one example. The buyer is Dana, an operations director at Northwind Freight.

Dana: We looked at this last year and it didn't work out.

Seller: That's useful to know. What happened last year? (clarify)

Dana: We rolled it out to everyone at once and nobody used it. The team found it confusing.

Seller: So the problem was adoption, not the idea itself. We'd start with one team of five and expand once they use it daily. Would a smaller start fit how you work? (respond)

Dana: That's different. A pilot would be easier to sell internally.

Seller: Great. Is adoption the main concern, or is there something else I should know about? (confirm)

The seller did not defend the product. They asked one question, found the real concern (adoption) and answered that. This pattern repeats in every objection below.

The objection handling course teaches a longer version of this approach, called RECIPES, with video lessons by Matt Doyon.

1. Price: "It's too expensive"

What it usually means. Price is rarely about the number alone. The buyer may not see enough value yet, may be comparing you to a cheaper option, or may not have the budget approved. Sometimes it is a way to get a discount.

What to say:

• "Too expensive compared to what? Help me understand what you're comparing it to."
• "If price were not a factor, would this solve the problem you described?"
• "Let's look at what the problem costs you today. You mentioned about 12 hours a week spent on manual reporting. What is that time worth?"

Do not discount first. A discount before you understand the objection teaches the buyer that your price is negotiable and that you did not believe in it. If the deal was already lost on price, see how to win it back later.

Sample exchange. The buyer is Priya, a head of finance at Corvane.

Priya: It's more than we expected to spend.

Seller: Fair. What number did you have in mind, and what was it based on?

Priya: About half of that. It's what we pay for our current tool.

Seller: Got it. Your current tool covers reporting. Earlier you said approvals also take your team two days a month. If this removes that, how would you compare the two?

Priya: Then it's not the same comparison. I'd need to show that to my CFO.

2. Timing: "Not right now"

What it usually means. Either something else has a higher priority, or the buyer does not feel the problem is urgent enough to act on. "Not right now" is often a polite way of saying "not a priority."

What to say:

• "That makes sense. What is taking priority right now?"
• "What would need to change for this to become a priority?"
• "If we waited until next quarter, what would happen to the problem you described in the meantime?"

The goal is to learn whether timing is a real constraint (a launch, a budget cycle, a reorganization) or whether the problem does not feel big enough. A real constraint gets a specific date for a follow-up. A weak priority goes back to discovery.

Sample exchange. The buyer is Marcus, a VP of Operations at Halcyon Labs.

Marcus: This looks interesting, but now isn't a good time.

Seller: Understood. Is it the timing of the project, or something else on your plate?

Marcus: We're in the middle of a migration until the end of the quarter.

Seller: That's a real constraint. When the migration finishes, what's the first thing your team will focus on?

Marcus: Reporting, probably. It's a mess right now.

Seller: Then let's book 30 minutes in the first week of next quarter, and I'll send you a one-page plan before then.

3. "Send me some information"

What it usually means. This is the most common brush-off. Sometimes the buyer really does need something to share with a colleague. More often they want the call to end without saying no.

What to say:

• "Happy to. So I send the right thing, what are you hoping to learn from it?"
• "Who else will look at it, and what will they want to see?"
• "Let's pick a time now to go through it together, so you can ask me questions while it's fresh."

Sending a generic deck and waiting is the weakest next step. Ask what the information is for, send something specific to that, and book the next conversation before you hang up.

Sample exchange. The buyer is Elena, a sales director at Brightline Dental.

Elena: Can you just send me some information?

Seller: Of course. What would be most useful for you to see?

Elena: Honestly, I'm not sure. Something I can show to my team.

Seller: Got it. I'll send a two-page summary built around the call-review problem you described. Would you be open to 15 minutes on Thursday so I can walk your team through it?

Elena: Thursday afternoon works.

4. "We already use [competitor]"

What it usually means. The buyer has a solution and does not see a reason to switch. It does not mean they love it. Most people who use a tool have a list of things they wish it did better.

What to say:

• "That's great, a lot of our customers started there. What do you like most about it?"
• "If you could change one thing about it, what would it be?"
• "How well does it handle [the problem you discovered]?"

Never criticize the competitor. Ask questions that let the buyer describe the gaps. Then connect those gaps to something you do differently.

Sample exchange. The buyer is Tom, a head of enablement at Corvane.

Tom: We already use another tool for call recording.

Seller: Good, so you already see the value of reviewing calls. What does your team do with the recordings?

Tom: Managers listen to a few each week. It takes a lot of time.

Seller: How many calls do they get through?

Tom: Maybe five or six out of a few hundred.

Seller: That's a gap worth looking at. Would it help to see how scoring every call against your playbook works alongside what you have today?

5. No authority: "I need to run it by my boss"

What it usually means. Either the buyer is not the decision maker, or they are not convinced enough to put their name on a recommendation. Both are useful to learn early.

What to say:

• "Of course. What do you think your boss's first question will be?"
• "Who else is involved in a decision like this?"
• "Would it help if I joined that conversation, or prepared a short summary you can forward?"

You want to equip your contact to sell internally, and you want to meet the decision maker. Ask who they are, what they care about and how decisions get made.

Sample exchange. The buyer is Sam, a sales manager at Northwind Freight.

Sam: I like it, but I'd need to run it by my boss.

Seller: Makes sense. What do you think she'll ask first?

Sam: Probably cost, and whether the team will actually use it.

Seller: Those are fair questions. Would it help if I put together a one-page answer to both, and joined a 20-minute call with her next week?

Sam: Yes, that would make it much easier.

6. No need: "We don't need this"

What it usually means. The buyer does not see a problem worth solving, or they do not connect your product to their problem. This is often a discovery gap: you have not yet shown that the problem exists in their business.

What to say:

• "That's fair. How are you handling [the process] today?"
• "When was the last time [the problem] caused trouble for your team?"
• "What would have to be true for this to become useful?"

Do not argue. Ask about their current process and let the gaps show up. If no gap exists, you may be talking to the wrong buyer or the wrong company, and it is fine to say so.

Sample exchange. The buyer is Hannah, a COO at Halcyon Labs.

Hannah: I don't think we need this. Our managers already coach their teams.

Seller: Good to hear. How do they decide which calls to review?

Hannah: They pick a few at random, or when someone asks for help.

Seller: And how do they know if a call they didn't hear went badly?

Hannah: They don't, really. Unless the customer complains.

Seller: That's the gap I'd look at. Would it help to see what a week of scored calls would show you?

7. Status quo: "We're happy with how things are"

What it usually means. Change feels risky or costly, and nothing is forcing the decision. The status quo is your biggest competitor, because doing nothing is free and familiar.

What to say:

• "That's good to hear. What's working best right now?"
• "If nothing changes in the next 12 months, what do you expect the result to be?"
• "What would a better version of this look like for you?"

Help the buyer see the cost of staying where they are. Use their own numbers and goals from discovery, not general statistics.

Sample exchange. The buyer is Luis, a director of customer success at Brightline Dental.

Luis: We're pretty happy with our current process.

Seller: Glad to hear it. When we spoke earlier, you mentioned you want to cut onboarding time from 60 days to 45. Is that still the goal?

Luis: Yes, by the end of the year.

Seller: How close are you today?

Luis: Honestly, we haven't moved much.

Seller: Then the current process may be working well, but not toward that goal. Can we look at what would need to change to reach it?

8. Trust: "I've never heard of you"

What it usually means. The buyer sees risk in choosing a company they do not know. They worry about whether you will still exist, whether the product works and whether they will look bad if it fails.

What to say:

• "That's fair, we're not as well known as some. What would you need to see to feel comfortable?"
• "Here is a customer in a similar situation. I can introduce you if you'd like to hear it from them."
• "Would a small pilot with clear success criteria make this easier to approve?"

Do not try to argue your way out of being unknown. Reduce the risk instead: references, a pilot, a trial, a clear contract. Make it easy for the buyer to be right.

Sample exchange. The buyer is Grace, a procurement lead at Northwind Freight.

Grace: I've never heard of your company.

Seller: That's fair. What would help you feel comfortable moving forward?

Grace: References, mainly. And I'd want to try it before we commit.

Seller: Both are easy. I'll introduce you to a customer in logistics who started with a 30-day pilot. What would you need to see by day 30 to say yes?

Grace: Usage from the whole team, and no issues with our systems.

Brush-offs versus real objections

A real objection has a reason behind it and the buyer will talk about it. A brush-off is a way to end the conversation. The two look similar on the surface, so test them with one open question.

Try this: "I hear you. Just so I understand, is it [the specific reason], or is there something else behind it?" A real objection gets a real answer. A brush-off gets "no, that's it" or silence.

If you hit a brush-off, do not push. Ask for one small, specific next step with a date. If the buyer refuses even that, move on and spend your time on buyers who engage.

Quick reference: objection, meaning and first question

Print this table for new hires or put it in your playbook.

How to practice objection handling

Reading a guide does not change what people say under pressure. Practice does. You need three things: a weekly drill, a checklist for your own calls and a log. None of them needs a tool.

A weekly 20-minute drill in pairs

Pair people up once a week. Pick one objection from this guide and write it on a card with two lines: the objection in the buyer's words, and the hidden real reason (for example, "It's too expensive" and "my CFO set the budget at half this number").

1. Minutes 0 to 5: Person A plays the buyer from the card and says the objection. Person B runs listen, clarify, respond, confirm.
2. Minutes 5 to 10: Person A gives the real reason only if B asks a good clarifying question. Then A tells B what worked and what felt like a pitch.
3. Minutes 10 to 15: Swap roles with the same card.
4. Minutes 15 to 20: Rotate to a new objection and run it once more.

Use the sample exchanges above as starting scripts, then try the same objection in your own words. The goal is to ask the clarifying question without thinking about it.

A self-review checklist for your own calls

Record your calls (with permission) and re-listen to the moments where a buyer pushes back. Score each one yes or no.

If you want to turn this checklist into a scorecard for a whole team, see how to build one.

An objection log

Keep a simple spreadsheet. After every call with an objection, add one row.

After a month, sort by objection. The ones that appear most often are the ones to drill first. If one objection keeps hiding the same reason, the fix is usually earlier in the call, in discovery.

For a deeper walkthrough, take the free Mastering Objection Handling course, or watch the objection handling masterclass session.