By Siddharth GangalCommon sales objections are buyer statements that signal a constraint, concern, missing fact, preference, request for proof, soft refusal, or final refusal. A useful response does not “overcome” the buyer. It identifies which condition exists, answers only what the rep can support, and agrees on an honest next step—or closes the loop.
Direct answer. Acknowledge the statement, ask one neutral diagnostic question, reflect the answer, then choose one move: answer with approved evidence, verify and return, involve the right person, change scope, schedule around a real event, or stop. The 25 scripts below are starting language, not promises or buyer-psychology facts.
The library stays broad by design. For deeper methods, use the sales objection-handling framework, the dedicated price-objection guide, the competitor-objection guide, and the facilitator-ready objection role-play scenarios.
Printable common sales objections desk reference
Print this table as the desk reference; use the full library when preparing. The diagnostic column matters more than the response move. Never treat the label as proof of motive.
| # | Buyer says | Diagnose | Safe move |
|---|---|---|---|
| 1 | “It is too expensive.” | Compared with what and against which required outcome? | Re-scope or compare complete value and cost |
| 2 | “We do not have the budget.” | No allocation, no authority, or no business case? | Map approval; do not invent budget |
| 3 | “I can get this cheaper elsewhere.” | Are the requirements and costs comparable? | Build a like-for-like comparison |
| 4 | “No budget until next fiscal year.” | What planning event and date control the decision? | Plan to the real cycle or close |
| 5 | “I need to think about it.” | Which question, risk, or decision remains open? | Answer, verify, or give space |
| 6 | “Now is not a good time.” | Is the constraint calendar, capacity, priority, or fit? | Name a real trigger or stop |
| 7 | “Call me next quarter.” | What becomes different next quarter? | Schedule around the event |
| 8 | “We are too busy.” | Is evaluation capacity unavailable? | Reduce evaluation burden; never promise instant payoff |
| 9 | “This is not a priority.” | What is prioritized and is there a genuine dependency? | Disqualify or revisit on a named change |
| 10 | “We already use a competitor.” | Is there an unmet requirement or only curiosity? | Respect incumbent; explore gaps |
| 11 | “We are locked into a contract.” | What do the signed terms and decision window say? | Never imply an exit; plan evaluation timing |
| 12 | “We tried this before.” | What failed: fit, process, implementation, adoption, or evidence? | Compare failure conditions honestly |
| 13 | “Competitor has a feature you lack.” | Is it required, how often, and what outcome depends on it? | Confirm gap; never fabricate roadmap |
| 14 | “We are happy with the status quo.” | Is there any funded problem? | Respect no-change preference |
| 15 | “We do not see the need.” | Did discovery establish a relevant problem? | Return to discovery or disqualify |
| 16 | “Manual works fine.” | What does the current process cost and where does it fail? | Measure; do not supply a benchmark |
| 17 | “This does not apply to us.” | Which assumption, workflow, or requirement misses? | Reframe with verified relevance or exit |
| 18 | “I need to ask my boss.” | What decision and evidence does the approver own? | Support the contact; ask permission to include approver |
| 19 | “A committee must approve.” | Who owns which question and process? | Map stakeholders without bypassing champion |
| 20 | “Send more information.” | Which decision should the material support? | Send a specific approved asset and optional follow-up |
| 21 | “Procurement must be involved.” | What process, documents, owner, and timing apply? | Start the authorized process |
| 22 | “I have never heard of you.” | Which risk needs evidence? | Provide verifiable company, security, and reference facts |
| 23 | “How do I know it will work?” | What result and proof standard would reduce uncertainty? | Propose a bounded pilot or valid proof |
| 24 | “What if your company fails?” | Which continuity dependency matters? | Provide approved contractual and operational evidence |
| 25 | “Your reviews are mixed.” | Which review and concern is material? | Acknowledge, verify, contextualize without dismissing |
Diagnose before responding
Do not answer the first sentence until you know what job it performs. “Too expensive” can mean the buyer compared a lower quote, cannot justify value, lacks authority, dislikes the term, needs a smaller scope, or is declining politely. A memorized rebuttal can answer the wrong concern and create another.
- Acknowledge: “That makes sense to examine,” “Thanks for being direct,” or “I hear the concern.” Do not agree to a false premise.
- Ask one neutral question: “What are you comparing it with?” or “Which part is most uncertain?” Avoid a stack of leading questions.
- Reflect: “So the concern is implementation capacity this quarter, not whether the workflow matters. Is that accurate?” Let the buyer correct the diagnosis.
- Choose a bounded response: answer, demonstrate, verify, involve a specialist, change scope, schedule, or stop.
- Confirm the next step: owner, artifact, date, decision, and what happens if the evidence fails.
Original research on listening during disagreement examined how manipulated listening quality affected speakers across four experiments. Separate original conversation research on question asking reported that follow-up questions can signal responsiveness and relate to liking. Neither study proves sales conversion. They support the narrower practice of listening and following up rather than racing to a comeback.
Accept “no.” If the buyer withdraws consent to continue, asks not to be contacted, states a fixed disqualifier, or declines without inviting a further conversation, acknowledge and follow applicable CRM and suppression policy. Objection handling is not permission to pressure.
Price objections: 5 word-for-word responses
Price responses should clarify comparison, scope, authority, and economic evidence without manufacturing ROI.
1. “It is too expensive.”
Scenario: Pricing review; scope and value are not yet comparable. Say: “That is fair to examine. What are you comparing the price with—the current process, another proposal, or the budget you expected? If we identify the required outcomes and complete cost, we can see whether the gap is scope, value, or fit.” Next: Build a line-by-line comparison or reduce scope. Do not invent savings.
2. “We do not have the budget for this.”
Scenario: The contact may lack allocation or approval. Say: “Understood. Does that mean there is no approved line, the business case has not cleared the threshold, or another owner controls this category? I do not want to assume there is budget that does not exist.” Next: Map the real process. If no path exists, agree on a planning event or close the opportunity.
3. “I can get a cheaper version elsewhere.”
Scenario: A lower alternative exists. Say: “You should choose the option that meets the requirements at the right total cost. Can we compare the same users, capabilities, implementation, usage, support, retained tools, and exit? If the lower-cost option passes, that is useful to know.” Next: Use a neutral scorecard; never attack the competitor.
4. “We do not have budget until next fiscal year.”
Scenario: A stated budget cycle. Say: “Thanks for the timing. When does planning begin, who owns the submission, and what evidence must be ready? I do not want to force an off-cycle case unless your process genuinely allows one.” Next: Set a permissioned planning checkpoint tied to the real calendar. The deeper timing-objection guide covers deferrals.
5. “I need to think about it.”
Scenario: An open question or request for space; motive unknown. Say: “Of course. Is there a specific question, risk, or tradeoff you still need to work through, or would it be more helpful if I gave you space and checked back only if you ask?” Next: Answer one defined gap, agree on a date, or close the loop without chasing.
Timing objections: 4 word-for-word responses
Timing responses should locate a real constraint or event; they should not manufacture urgency.
6. “Now is not a good time.”
Scenario: Calendar, capacity, competing project, weak priority, or soft no. Say: “Understood. Is the constraint evaluation capacity, implementation capacity, another priority, or simply that this is not a fit? Any answer is useful.” Next: Reduce burden only if requested, schedule around a named event, or stop.
7. “Call me back next quarter.”
Scenario: A future period without a confirmed trigger. Say: “Happy to respect that. What changes next quarter, and when should I ask permission to reconnect? If nothing specific changes, I would rather not create a calendar placeholder that is not useful.” Next: Record the event and date; do not enroll the buyer in an unsolicited cadence.
8. “We are too busy to evaluate anything new.”
Scenario: Evaluation work itself is the barrier. Say: “That is a real constraint. What is the maximum time your team could responsibly give an evaluation, if any? We can scope within that limit or pause.” Next: Offer a bounded proof using approved data. Never claim setup or benefits happen immediately unless documented and applicable.
9. “This is not a priority right now.”
Scenario: The problem may be real but unfunded. Say: “Fair. What is above it, and is this workflow actually connected to that priority—or would that be a stretch? I am comfortable disqualifying it if there is no genuine link.” Next: Document the priority and trigger, or close. See the dedicated not-a-priority analysis.
Competitor objections: 4 word-for-word responses
Competitor responses should respect the incumbent, verify requirements, and acknowledge real gaps.
10. “We already use a competitor.”
Scenario: Existing relationship; satisfaction unknown. Say: “Good context. What is working well, and is there any required job the current setup does not complete? If it meets the need, I do not want to manufacture a reason to switch.” Next: Explore only a verified gap and the real renewal window.
11. “We are locked into a contract until next year.”
Scenario: A contractual constraint. Say: “We should respect the signed terms. When does the decision window open, and how long does a responsible evaluation take? I will not assume an exit right exists without your legal or procurement team confirming it.” Next: Plan a non-disruptive evaluation or wait.
12. “We tried something similar before and it did not work.”
Scenario: Prior failure creates a reasonable evidence threshold. Say: “What failed: category fit, process design, data, implementation, adoption, support, or the expected outcome? If the same condition exists here, we should not repeat it.” Next: Build a failure comparison and pilot stop rules; never dismiss the history.
13. “Your competitor offers this feature and you do not.”
Scenario: A documented feature gap. Say: “You are right; we do not currently document that capability. How often is it required, who uses it, and what fails without it? If it is a hard requirement, the competitor may be the better fit.” Next: Verify with product. Never promise a roadmap item or workaround without approval.
Need objections: 4 word-for-word responses
Need responses return to the buyer’s workflow and evidence; they do not tell the buyer what should matter.
14. “We are happy with how things are.”
Scenario: A legitimate no-change preference. Say: “That is a valid outcome. Is there any part of the current workflow you are actively trying to change, or should we stop here?” Next: If no funded problem exists, disqualify. Do not invent a cost of inaction.
15. “We do not see the need for this.”
Scenario: Relevance has not been established. Say: “I may have started with the product instead of your situation. Is there a workflow or outcome you are trying to change that this should be evaluated against? If not, there may be no need.” Next: Return to the discovery framework or exit.
16. “We do this manually and it works fine.”
Scenario: The process may genuinely be acceptable. Say: “Then automation has to earn its complexity. Could we measure actual volume, active time, error, exception work, and delay for a short baseline? If the manual process clears your thresholds, keeping it is rational.” Next: Measure; do not supply generic time-saving claims.
17. “I do not see how this applies to our business.”
Scenario: Industry, size, process, system, or policy mismatch. Say: “Which assumption misses your reality? I can restate the fit using verified facts, but I do not want to force an irrelevant customer story onto your business.” Next: Use a permissioned comparable reference or acknowledge no fit.
Authority objections: 4 word-for-word responses
Authority responses clarify the decision system while protecting the contact’s agency and internal relationships.
18. “I need to run this by my boss.”
Scenario: Another person approves or contributes. Say: “What decision does your boss own, and what evidence will they need? I can provide an approved one-page summary, or—if you think it helps—join a conversation with you. I do not want to go around you.” Next: Let the contact choose the introduction and artifact.
19. “We have a committee that needs to approve this.”
Scenario: Multiple stakeholders own distinct requirements. Say: “Could we map the roles, questions, approval order, and decision criteria? I want each person to receive relevant evidence without repeating or changing the claim.” Next: Use the multi-threading guide; respect access boundaries.
20. “Send me more information and I will take a look.”
Scenario: A request for material, a polite exit, or both. Say: “Certainly. Which decision should it support: fit, security, economics, implementation, or product? I will send the smallest approved asset. Would you like a follow-up, or should I wait for you to respond?” Next: Honor the buyer’s contact preference.
21. “Procurement has to be involved.”
Scenario: Formal vendor process. Say: “What is the authorized process, who owns it, which documents are required, and when should commercial, security, legal, and business reviews begin? I will work through your process.” Next: Provide current approved documents; do not claim procurement involvement proves purchase intent.
Trust objections: 4 word-for-word responses
Trust responses provide verifiable evidence, limitations, and risk controls; assertions do not repair uncertainty.
22. “I have never heard of your company.”
Scenario: Brand recognition is standing in for business, security, support, or continuity risk. Say: “That is reasonable. Which risk concerns you most? I can provide current company information, security documentation, support terms, data-export terms, and permissioned references. Please verify them rather than relying on my description.” Next: Escalate to the document owner.
23. “How do I know this will actually work for us?”
Scenario: The buyer needs evidence for their own environment. Say: “You do not know yet. Let us define the job, baseline, test data, pass threshold, cost, risk, and stop rule. We can use a bounded pilot if it is safe and proportionate.” Next: Never substitute an unrelated testimonial or promise for a reproducible test.
24. “What happens if your company goes under?”
Scenario: Business continuity and exit. Say: “That risk deserves a written answer. Which dependencies matter—data export, service continuity, source access, transition support, escrow, or contract rights? I will bring the authorized owner and documents.” Next: Do not improvise runway, funding, SLA, insurance, or legal terms.
25. “Your reviews online are mixed.”
Scenario: A named review creates a specific concern. Say: “Which review and issue stood out? I will not dismiss it. We can check whether it concerns the current product, segment, plan, implementation, or support model, then verify against current documentation and a permissioned reference.” Next: Disclose material changes; never fabricate dates or score movement.
Practice, escalation, and QA rubric
Practice should score observable behavior, not whether a rep forced the conversation forward. Use the printable table for rapid recall and the full scenarios for role-play. Rotate buyer, seller, observer, and claim-checker roles. Give the buyer a hidden diagnosis and permission boundary so the seller must listen.
| Criterion | 0: unsafe or absent | 1: partial | 2: observable pass |
|---|---|---|---|
| Listening | Interrupts or assumes motive | Acknowledges but pivots quickly | Lets buyer finish and reflects accurately |
| Diagnosis | Launches rebuttal | Asks leading or stacked questions | Asks one neutral question and confirms |
| Accuracy | Invents feature, price, result, customer, roadmap, legal or security fact | Uses vague or overbroad language | Uses approved claim with material limits |
| Evidence | Assertion or irrelevant testimonial | Names evidence without source | Offers current, attributable, relevant proof or verification |
| Buyer autonomy | Pressures after no or bypasses contact | Ambiguous permission | Offers choices and honors stop/contact preference |
| Next step | Vague chase or forced meeting | Date without decision job | Owner, artifact, date, decision and stop condition |
| CRM capture | Records motive as fact | Partial note | Records buyer words, diagnosis as hypothesis, evidence, owner and permission |
Score 0–14, but use hard fails: fabricated material claim, undisclosed limitation, prohibited legal or security advice, contact after a clear stop, bypassing the contact without permission, disparaging a competitor, or logging an inferred motive as fact. A rep cannot average out an integrity failure with fluent delivery.
Escalate rather than answer when the objection concerns contract interpretation, regulatory requirements, security architecture, privacy, data processing, insurance, financial condition, roadmap commitment, custom pricing authority, clinical or safety claim, guaranteed outcome, customer disclosure, or a feature the rep cannot verify. Say: “I do not want to guess. I will bring the owner and current document by [agreed time].”
The FTC’s advertising guidance says claims must be truthful, nondeceptive, and evidence-based; its advertising FAQ explains that both express and implied claims require a reasonable basis. Regulated sellers can face stricter rules: the SEC’s investment adviser marketing guide, for example, addresses substantiation, balanced benefits and risks, testimonials, ratings, and performance for covered advisers. Sales enablement and counsel should translate applicable rules into the approved-claim library.
For call QA, sample ordinary calls across stages and reps. Calibrate two reviewers on the same recordings, reconcile disagreements, then review independently. Track diagnosis accuracy, unsupported claims, escalation compliance, next-step clarity, correction, and repeat coaching themes. Do not claim that the rubric improves win rate unless a valid evaluation proves it.