15 Sales Objection Examples to Practice

Knowing objections are coming is not the same as being ready for them. The problem is recognizing which kind of resistance you are actually facing when it arrives.

For a broader framework, see our Sales Roleplay guide.

A prospect who says "I'm not interested" thirty seconds into a cold call is doing something different from a prospect who says "We already have a contract with your competitor through the end of the year." Both sound like resistance. Only one carries a specific concern worth addressing. Treating them the same way is one of the most common execution errors in sales, and it is almost impossible to fix without deliberate practice on the real language prospects use.

This library organizes 15 realistic objection examples across seven categories: price, timing, trust, authority, competition, need, and status quo. For each example, you will find the exact language a prospect might use, what makes that objection difficult to handle in the moment, and what skill to focus on when drilling it. The goal is recognition and practice readiness, not a collection of scripted rebuttals to memorize.

If you want a structured methodology for building a practice routine around these examples, How to Practice Objection Handling in Sales covers deliberate practice frameworks in detail. If you want to work through these objections in a roleplay format, Objection Handling Roleplay has session structures you can use. And if you want to practice these specific objections with an AI partner, How to Use AI Roleplay to Practice Sales Objections explains how that works.

Start with the distinction that shapes everything else: is what you are hearing a brush-off or a real objection?

Why Each Objection Category Requires a Different Response Posture

Price, timing, trust, authority, competition, need, and status quo are not seven versions of the same problem. Each category signals a different underlying concern, and that concern determines what the rep needs to accomplish conversationally to move forward.

A price objection is usually about perceived value, not arithmetic. The prospect is telling you that what you are offering does not feel worth what you are asking. The conversational move is not to defend the number; it is to rebuild or reframe the value equation.

A timing objection is about priority and readiness. The prospect may have genuine constraints, or they may be using timing as a low-conflict way to avoid a decision. The rep needs to distinguish between a real external constraint and a prioritization problem, because the response to each is different.

A trust objection signals that the prospect does not yet believe the rep, the company, or the claims being made. Pushing harder on benefits makes this worse. The move is to reduce perceived risk and build credibility through specificity, not assertion.

An authority objection means the person in the conversation cannot or will not make the decision alone. The rep's job is to understand the actual decision process and find a path to the people who can act, without alienating the contact they already have.

A competition objection means the prospect has an alternative in mind, whether a current vendor, a competing solution, or the option to do nothing. The rep needs to understand what the prospect values about that alternative before making any comparison.

A need objection means the prospect does not yet see the problem clearly enough to justify a solution. The conversational move is discovery, not persuasion.

A status quo objection means the prospect is comfortable with how things work today. The risk of change feels larger than the potential benefit. The rep needs to make the cost of staying put concrete and credible.

A single rebuttal template fails across these categories because it cannot address seven different underlying concerns. Applying a value-articulation response to a trust objection, or a discovery question to a price objection, produces a conversation that feels tone-deaf. Recognizing the category first is what makes the right response possible.

Price Objections (Examples 1-3)

Price objections are among the most common a rep will hear, and also among the most misread. The instinct is to treat them as a budget problem, which leads reps toward discounting or payment plan conversations before they have understood what is actually happening. In practice, price objections are often value objections in disguise. The prospect is not saying they cannot find the money; they are saying the value you have described does not justify the number you have quoted. For most price objections, the more useful practice target is value articulation rather than price negotiation.

Example 1: "It's too expensive."

Exact prospect language: "I appreciate you walking me through everything, but honestly, it's just too expensive for us."

What makes this hard is its vagueness. "Too expensive" relative to what? Relative to their current spend? Relative to what a competitor quoted? Relative to what they expected to hear? The rep does not know, and without knowing, any response is a guess. Reps who have not practiced this objection often either defend the price immediately or offer a discount, both of which skip the step that actually matters: understanding what the prospect is comparing the price against.

The practice target here is value articulation combined with diagnostic questioning. When drilling this objection, focus on staying curious rather than defensive. Practice asking a follow-up that surfaces the comparison point before saying anything about the price itself. The skill is holding the price steady while reopening the value conversation, not capitulating or arguing.

Example 2: "We don't have budget right now."

Exact prospect language: "We'd love to do something like this, but the budget just isn't there right now. Maybe next quarter."

This objection sits at the intersection of price and timing, which is what makes it tricky. It sounds like a hard constraint, and sometimes it is. But "no budget" is also one of the easiest low-conflict exits a prospect can offer, because it puts the obstacle outside their control. The rep cannot argue with a budget cycle.

What makes this objection worth practicing is learning to distinguish a real budget constraint from a prioritization decision. If the prospect genuinely has budget authority and the problem is real, money tends to appear when the urgency is high enough. The practice target is ROI framing and urgency building: can the rep make the cost of waiting concrete enough that "next quarter" starts to feel expensive? Drill the moment where the rep acknowledges the constraint and then asks a question that surfaces what solving the problem is actually worth.

Example 3: "I can get something similar for less."

Exact prospect language: "We've been looking at a few options, and honestly, I can get something pretty similar for a lot less."

This is a price objection with a competitive edge. The prospect is making a comparison, which means the rep is now in a conversation about differentiation whether they want to be or not. The instinct to immediately defend quality or list differentiating features is understandable but usually premature, because the rep does not yet know what "similar" means to this prospect or what they are actually comparing.

The practice target is separating price from value by first understanding what the prospect is evaluating. Drill the discipline of asking what the alternative includes before making any comparison yourself. The skill is not winning a feature argument; it is helping the prospect see that "similar" may not be doing the work they think it is. Reps who can do this without sounding defensive or dismissive of the competitor will handle this objection far more effectively in live conversations. For cold call variants of price and competitive resistance, Cold Call Objections covers how these often surface earlier and with less context.

Timing Objections (Examples 4–5)

Timing objections are among the most difficult to read because they sit on a spectrum. On one end, the prospect has a genuine constraint: a budget freeze, a pending merger, a product launch consuming all available attention. On the other end, timing is a polite way to avoid saying no without creating conflict. The words sound identical in both cases, which is why reps who treat every timing objection the same way either push too hard on real constraints or let soft deflections kill deals that were alive.

The skill to practice is not a rebuttal. It is diagnosis followed by a concrete next step. A rep who accepts a vague "let's talk later" without understanding why later is setting up a follow-up that goes nowhere. A rep who challenges a genuine timing constraint damages the relationship. Practice should put you in both situations so you can develop the judgment to tell them apart.

Example 4: "Now isn't a good time."

Prospect language: "Look, I appreciate the call, but now really isn't a good time for us to be looking at something like this."

This objection arrives early, often before the rep has established much value. It can mean the prospect is genuinely slammed, or it can mean the prospect wants off the call without being rude. Practice focus: ask a single clarifying question that surfaces whether there is a real constraint or a polite exit. Something like "Is there a specific reason now doesn't work, or is it more about timing in general?" gives the prospect room to be honest without feeling cornered. Then practice securing a specific date and reason for that date rather than a vague future check-in. If the prospect cannot name a reason or a timeframe, that tells you something.

Example 5: "Let's revisit this next quarter."

Prospect language: "We're heads-down right now. Reach back out next quarter and we can have a real conversation."

This version sounds more cooperative than Example 4, which makes it more dangerous. The prospect has offered a future window, so the rep often accepts it and moves on. The problem is that next quarter arrives with no context, no commitment, and no reason for the prospect to remember why they agreed to talk. Practice focus: confirm what will be different next quarter. If the prospect cannot articulate what changes, the timing objection may be masking something else entirely, an authority issue, a budget problem, or a lack of perceived need. Also practice converting a vague future into a scheduled call before ending the current conversation.

Trust Objections (Examples 6–7)

Trust objections are hard for experienced reps and harder still for newer ones. An experienced rep can draw on customer results, recognizable logos, or a track record in the industry. A newer rep often has none of that. The instinct is to assert credibility, "we've helped a lot of companies like yours," but assertion without specificity does almost nothing to move a skeptical prospect. What actually builds trust in a sales conversation is specificity: a concrete example, a relevant detail, a result that sounds real rather than rehearsed.

When you are new and lack your own credibility stories, practice using the company's proof rather than personal proof. Learn two or three specific customer examples well enough to describe them in plain language, not marketing language. Practice delivering them conversationally, not as a pitch. The rep who says "we worked with a mid-size logistics company that was dealing with the same concern, and here's what happened" sounds more credible than the rep who says "our clients see tremendous results."

Example 6: "I've never heard of your company."

Prospect language: "I'm not familiar with you guys. Who are you exactly?"

This is not necessarily a hostile objection. It is often genuine curiosity mixed with low initial trust. The prospect is asking for a reason to keep listening. Practice focus: respond with a specific, plain-language description of what the company does and who it helps, followed immediately by a relevant proof point. Avoid the instinct to over-explain the company history or pivot to a product pitch. The goal is to give the prospect enough to calibrate against their own situation. Practice keeping this response under thirty seconds and then returning control to the prospect with a question.

Example 7: "How do I know this actually works?"

Prospect language: "That all sounds fine, but how do I actually know this is going to work for us? We've tried things before that didn't pan out."

This objection often signals a past disappointment, not just general skepticism. The prospect is telling you they have been burned before, which means generic reassurance will land flat. Practice focus: acknowledge the concern directly without dismissing it, then offer a specific and verifiable proof point rather than a promise. Practice the difference between "I understand, and here's why we're different" (assertion) and "That's a fair concern. Here's a specific example of what happened with a company in a similar situation" (evidence). Also practice asking what "working" would look like for them, which surfaces their actual criteria and gives you something concrete to address.

Authority Objections (Examples 8–9)

Authority objections are distinct from every other category because the person raising them may be telling you the complete truth. They genuinely may not own the decision. The mistake reps make is treating every authority objection as a deflection and pushing through it, which can alienate a contact who is actually trying to help you navigate their organization. The other common mistake is accepting the objection at face value and waiting passively for an introduction that may not materialize.

The skill to practice is decision-process mapping. You want to understand who is involved, what the process looks like, and what role your contact plays in it, without making them feel interrogated or bypassed. A rep who maps the decision process well can stay in motion without damaging the relationship with the person in front of them. A rep who either ignores the authority structure or treats the contact as an obstacle tends to lose deals that were winnable.

Example 8: "I need to run this by my boss."

Prospect language: "This looks interesting, but I'd need to get my manager's sign-off before we go any further."

This is the most common authority objection and the one reps are most likely to mishandle. It can mean the contact genuinely needs approval, or it can mean the contact is not convinced and is using the manager as a buffer. Practice focus: first, confirm whether the contact is recommending this internally or simply passing it along. Those are very different situations. Then practice helping the contact prepare for that internal conversation: what information will the manager want, what objections might come up, and how can you support the process. A rep who helps the contact look good internally becomes an ally rather than a vendor to be filtered out.

Example 9: "This isn't really my decision."

Prospect language: "Honestly, I'm not the one who makes these calls. You'd need to talk to someone else."

This version is more ambiguous than Example 8. The contact may be directing you to the actual decision maker, or may be stepping back from a conversation they do not want to own. Practice focus: ask who the right person is and what a good path to that conversation might look like, without making the current contact feel dismissed. If the contact is willing to facilitate an introduction, that is a strong signal they see value. If they redirect you to a general inbox or a name with no context, that tells you something different. Also practice staying engaged with the current contact even as you pursue the decision maker, since contacts who feel bypassed rarely become advocates.

Competition Objections (Examples 10–11)

Competition objections are tricky because the instinctive response is to defend your product by attacking the alternative. That instinct usually backfires. Prospects who have already invested in a competitor, or who are actively evaluating one, will read a feature comparison as a sales pitch and a criticism of their judgment. The more useful posture is curiosity: ask questions that surface what the prospect actually values before you say anything about your own offer.

The goal in practice is not to memorize a rebuttal. It is to get comfortable slowing down, asking a follow-up question, and listening before you respond.

Example 10: "We're already using [competitor]."

What the prospect says: "We're already using [competitor]. We've been with them for about two years now."

Why this is hard: The prospect is not expressing a concern, they are stating a fact. There is no obvious pain to address. The rep has to resist the urge to immediately list reasons the competitor falls short, because the prospect has not signaled dissatisfaction yet. Jumping to a comparison before understanding what the prospect values comes across as presumptuous.

Practice focus: Work on asking a question that opens the conversation rather than closes it. Something like, "What's been working well with them?" or "What made you choose them originally?" gives the prospect space to talk, and it often surfaces a gap or a frustration the rep can then address honestly. In roleplay, practice staying in discovery mode even when you feel the pressure to differentiate immediately. If you find yourself launching into a feature list before the prospect has said anything negative about their current setup, that is the habit to break.

Example 11: "We're evaluating a few options."

What the prospect says: "We're still in the evaluation phase. We're looking at a few different options right now."

Why this is hard: This objection can feel cooperative because the prospect is not saying no. But it often signals that the rep has not yet established a reason to be the clear choice. The prospect is keeping options open, which means the rep has not yet surfaced what matters most to them or connected the offer to a specific outcome they care about.

Practice focus: Drill the question that helps you understand what the prospect is actually evaluating against. "What criteria are most important to you as you compare?" or "What would make the decision straightforward for you?" moves the conversation from a feature race to a values conversation. In practice, pay attention to whether you are asking those questions or defaulting to a pitch. The rep who understands the prospect's decision criteria before presenting has a structural advantage over the rep who presents first and asks questions later.

Need Objections (Examples 12–13)

When a prospect says they do not need what you are selling, the most common reason is not that they have genuinely evaluated the offer and found it irrelevant. It is that the rep has not yet connected the offer to a problem the prospect recognizes and cares about. Need objections are often a discovery gap wearing the costume of a rejection.

The practice posture for need objections is not to defend the product. It is to re-open discovery. If the prospect does not see the problem, the rep's job is to ask questions that help the prospect articulate their own situation, not to explain why they are wrong about not needing the solution.

Example 12: "We don't really need this."

What the prospect says: "Honestly, I don't think this is something we need right now."

Why this is hard: This objection feels like a closed door, and many reps respond by defending the product or listing features. That approach rarely works because the prospect has not said they dislike the product, they have said they do not see the problem it solves. Defending the solution before the problem is established is arguing in the wrong direction.

Practice focus: Work on asking a question that surfaces the underlying situation without being confrontational. Something like, "What does your current process look like for [relevant area]?" or "How are you handling [specific challenge] today?" invites the prospect to describe their reality rather than defend their position. In roleplay, practice recognizing the moment you feel the urge to justify the product, and replace that impulse with a discovery question. The skill being built here is staying curious under pressure rather than pivoting to a pitch when the prospect pushes back.

Example 13: "We're handling it fine on our own."

What the prospect says: "We've got a process in place. It's working fine for us."

Why this is hard: "Fine" is doing a lot of work in that sentence. Prospects who say things are fine are often describing an absence of acute pain, not an absence of cost or inefficiency. The challenge is that the rep cannot simply assert that things are not actually fine, that is dismissive and creates friction. The rep has to help the prospect surface the cost of the current approach themselves.

Practice focus: Drill questions that invite the prospect to examine their current process more closely without feeling interrogated. "What does that process typically take in terms of time or resources?" or "What happens when [edge case or volume increase] comes up?" can surface friction the prospect has normalized. In practice, pay attention to whether your follow-up questions feel like genuine curiosity or like a cross-examination. The tone matters as much as the content. If the prospect feels challenged, they will defend their current process more firmly.

Status Quo Objections (Examples 14–15)

Status quo objections are often the hardest category to practice because there is no obvious problem to solve. The prospect is not complaining about price, questioning your credibility, or comparing you to a competitor. They are comfortable. Comfort is a powerful force, and the instinct many reps have, manufacturing urgency or implying the prospect is falling behind, tends to produce resistance rather than reflection.

The practice goal with status quo objections is to surface latent dissatisfaction honestly. That means asking questions that help the prospect examine what they are accepting as normal, without pressure and without exaggerating consequences. If there is a real cost to staying put, a good question will help the prospect find it. If there is not, the deal may not be there yet.

Example 14: "We've always done it this way."

What the prospect says: "This is just how we've always operated. It's worked for us."

Why this is hard: This objection is not really about the product at all. It is about identity and habit. The prospect is describing a process they are attached to, and any response that implies the process is wrong will be heard as a criticism of the people who built it. Reps who push back directly often make the prospect more committed to the status quo, not less.

Practice focus: Work on questions that create a moment of examination without judgment. "What would it look like to handle [relevant area] at twice the current volume?" or "Are there parts of the process that take more time than you'd like?" invites the prospect to notice friction on their own terms. In roleplay, practice sitting with the silence after that question rather than filling it with a pitch. The rep's job at this point is to listen, not to convince. If the prospect identifies something they would change, that is the opening. If they do not, the conversation needs more discovery before it can go further.

Example 15: "Things are working well enough for us."

What the prospect says: "I mean, things aren't perfect, but they're working well enough. I'm not sure we need to change anything."

Why this is hard: Unlike the previous example, this prospect has already acknowledged imperfection. "Not perfect" is a small opening, but many reps miss it by moving too fast. They hear "working well enough" and either accept the objection or pivot immediately to a product pitch. The more useful move is to slow down and explore what "not perfect" actually means to the prospect.

Practice focus: Drill the follow-up that picks up on the concession without amplifying it artificially. "You mentioned things aren't perfect, what does that look like in practice?" is a low-pressure way to invite the prospect to describe the friction they have already acknowledged. In roleplay, practice staying with that thread rather than jumping to a solution. The cost of inaction is real in many situations, but the prospect has to arrive at it themselves. A rep who tells the prospect what the cost is will be argued with. A rep who asks questions that help the prospect calculate it themselves is more likely to be heard.

For structured formats to practice all fifteen of these examples in a deliberate session, see Objection Handling Roleplay: How to Practice Sales Objections Effectively. If you want to work through these scenarios with an AI partner and get scored on your responses, How to Use AI Roleplay to Practice Sales Objections covers how that process works.

How to Use This Library in a Deliberate Practice Session

A library of 15 objection examples is only useful if you practice with it deliberately. Reading through the examples and feeling familiar with them is not the same as being able to retrieve a response naturally under pressure. The gap between knowing what to say and saying it without hesitation is closed through repetition, not recognition.

The method that works is simple: isolate one objection, drill it until the response feels automatic, review what happened, and repeat with variation before moving to the next.

Isolate one objection at a time

Do not try to practice all 15 examples in a single session. Pick one objection from one category. Run the full scenario: the prospect raises the objection, you respond, the conversation continues. Then stop and evaluate. Did you acknowledge before responding? Did you ask a question or go straight to a counter? Did the conversation feel natural or scripted?

Isolating one objection at a time lets you focus on the specific skill that objection demands. A price objection requires a different posture than a trust objection. Mixing categories in a single session makes it harder to identify what actually needs work.

How many repetitions before it feels natural

There is no universal number, but a useful benchmark is this: if you can respond to the same objection three times in a row without hesitating, fumbling the acknowledgment, or reverting to a canned line, you are ready to add variation. Variation means changing the prospect's tone, the stage of the conversation, or the specific wording of the objection. A prospect who says "we already have something in place" is raising the same status quo objection as one who says "honestly, the team is pretty happy with how things work," but the phrasing changes how the response should open.

Once variation feels manageable, move to the next objection in the same category before switching categories. Finishing all the objections in one category before moving to the next builds the response posture for that category into muscle memory, rather than leaving you with a scattered set of half-practiced responses.

Building a routine across all seven categories

A practical weekly structure might look like this: spend two or three sessions on one category, then rotate. Over several weeks, you work through price, timing, trust, authority, competition, need, and status quo. When you return to a category you practiced earlier, you will often find that the responses feel more automatic and that you can handle variation more easily. That is the signal that practice is working.

If a category consistently feels harder than the others, spend more time there before rotating. Difficulty is information. It usually means the response posture for that category has not been internalized yet.

Using AI to practice without a partner

One practical constraint of deliberate objection practice is that it requires a partner willing to raise the same objection repeatedly, adjust their tone on request, and give useful feedback afterward. Finding someone available for that kind of focused, on-demand drilling can be difficult to arrange consistently. AI roleplay removes the scheduling problem and lets you run as many repetitions as you need, on your own schedule, with configurable difficulty.

For a structured approach to running these sessions, the deliberate practice guide for objection handling covers how to structure repetition and review. If you want a roleplay format built specifically around objection scenarios, objection handling roleplay walks through how to set up and run those sessions. For reps who want to practice these specific examples with an AI partner, AI roleplay for objection handling explains how that works in practice. If your focus is cold call objections specifically, cold call objections covers the variants that appear most often at the top of a call.

Frequently Asked Questions

How do I practice trust objections when I have no credibility stories yet?

Trust objections are hard for newer reps because the most common instinct is to reach for a customer story or a case study, and those take time to accumulate. The good news is that trust objections are not primarily about proof. They are about whether the rep can hold the conversation without becoming defensive or overselling.

When you are new, practice the acknowledgment and the question rather than the proof. A response like "That's fair, we're not well known in your space yet. Can I ask what would make this worth a closer look for you?" keeps the conversation open without fabricating credibility you do not have. Over time, you build real examples. In the meantime, practice staying calm, asking a question, and not collapsing under the skepticism. That skill transfers directly once you do have stories to tell.

How do I know if an objection is real or just a stall?

The clearest signal is specificity. A real objection usually has some detail behind it: a named competitor, a specific budget constraint, a concrete reason the timing is wrong. A stall tends to be vague and deflecting: "I need to think about it," "send me some information," or "now's not a great time" without any explanation of why.

The practical test is to ask a question that would be easy to answer if the objection were real. If a prospect says timing is wrong, ask what would need to change for the timing to be right. A prospect with a genuine timing constraint can usually answer that. A prospect who is stalling will often deflect again or go quiet. The answer tells you which situation you are in and what to do next.

How do I build a weekly practice routine across all seven objection categories?

A simple structure that works: assign one or two categories per week and rotate through all seven over a month. Within each week, pick one specific objection from that category and run focused repetitions until the response feels natural, then add variation before moving to the next objection in the same category.

Keep sessions short. Twenty to thirty minutes of focused practice on a single objection is more useful than an hour of loosely structured conversation that touches many things without drilling any of them. At the end of each session, note what felt rough. That is the input for the next session. After a full rotation through all seven categories, return to the ones that felt hardest. Difficulty on the second pass is usually smaller, which is a reliable signal that the practice is working.