10 Common Sales Objections (and How to Overcome Them)

An objection is information, not a verdict

A sales objection tells you what a buyer still needs to understand, believe, or resolve before moving forward. The most useful response is rarely a polished rebuttal. It is a short sequence of listening, clarifying, answering, and checking that you addressed the real concern.

That distinction matters because the first sentence a prospect offers is often incomplete. “It is too expensive” may mean the value is unclear, the timing is wrong, or the buyer cannot defend the purchase internally. Treating every price objection as a request for a discount skips the discovery that could save the opportunity.

1–3: Price, budget, and timing objections

1. “It is too expensive.” Ask what the buyer is comparing the price with and which outcome must justify the investment. Reconnect the proposal to the problem they described; do not rush into discounting before you understand the gap.
2. “We do not have the budget.” Clarify whether funds are unavailable, already allocated, or dependent on another stakeholder. If the need is real but the budget cycle is the constraint, agree on a concrete point to revisit and document what must be true then.
3. “Now is not a good time.” Ask what is competing for attention and when that condition is likely to change. A useful follow-up has a date, an owner, and a reason to reconnect—not a vague promise to circle back someday.

4–6: The status quo, an existing provider, and past disappointment

1. “We are happy with our current approach.” Respect what already works. Ask what they would preserve and what, if anything, still creates friction. A credible seller can acknowledge that staying put may be reasonable while exploring whether an unresolved problem is worth examining.
2. “We are under contract with another provider.” Learn the renewal date, the evaluation process, and the shortcomings the buyer would want corrected next time. The immediate goal may be earning a place in the next review rather than forcing a premature switch.
3. “We tried something similar and it did not work.” Invite the buyer to describe what failed: adoption, implementation, reliability, support, or expectations. Explain your approach only where it directly addresses that history, and be candid about any risk that remains.

Trust objections demand specificity. General assurances such as “we are different” carry little weight. A clear implementation plan, an honest explanation of limitations, or a relevant proof point is more useful than a long list of features.

7–10: Authority, fit, information, and indecision

1. “I need to talk with my team.” Ask who will be involved, what each person is likely to care about, and how you can help the buyer prepare. When appropriate, suggest a short working session with the relevant stakeholders instead of making your contact relay the entire proposal.
2. “We need a feature you do not have.” Understand the job behind the feature request. There may be another path to the same outcome, a planned capability, or a genuine mismatch. Never promise functionality that does not exist.
3. “Just send me some information.” Agree, then ask what decision the material should help them make. Send a focused resource and secure a specific next step so the information has context.
4. “I need to think about it.” Give the buyer room while gently surfacing the open question. Ask which part deserves more thought and what information would make the decision clearer. If there is no compelling need or mutual fit, recognize that honestly.

Coach from real conversations

A static list of rebuttals becomes stale quickly. Build your objection playbook from the language buyers actually use. Conversation intelligence helps managers review call moments, group recurring concerns, and see where strong discovery changed the direction of a conversation.

• Tag the objection and the stage of the sales process in which it appeared.
• Capture the rep’s clarifying question before evaluating the answer they gave.
• Look for patterns by segment, role, use case, and deal stage rather than treating every call alike.
• Turn effective moments into short coaching clips and practice variations in role-play.
• Review whether the call ended with a clear next step, even when the answer was no.

The strongest objection handling sounds less like a contest and more like careful problem solving. When reps feel prepared to investigate concerns instead of defeating them, buyers get a more respectful conversation and managers gain a repeatable coaching process.