How to handle sales objections: 10 diagnostic scripts
Your buyer says the proposal is too expensive, and you’re about to defend the price before knowing what they mean. Use the sequence and conditional scripts below to identify the concern, answer what you can verify, and recognize when to stop.
Handle sales objections by listening without interrupting, acknowledging the concern, clarifying its cause, answering with verified evidence, and checking what remains. If the buyer declines or the requirement cannot be met, agree to pause or stop. An objection is a stated concern, not permission to argue.
Should you answer, verify, or stop?
Our answer–verify–stop method separates a supported answer from a bounded check or an honest exit. It is a working method, not a tested performance claim.
Objection handling is addressing a buyer’s stated purchasing concern, not defeating the buyer; see Salesforce.
- Answer: You understand the requirement and have relevant evidence. Expect a remaining condition or permission to discuss next steps.
- Verify: The requirement is clear, but evidence is missing. Expect permission for a specific check, not a purchase commitment.
- Stop: The buyer declines, or a mandatory requirement cannot be met. Accept the mismatch.
What should you say to common sales objections?
A buyer’s phrase is a diagnostic starting point, not proof of its cause. Choose a branch only after the buyer confirms the concern.
All scripts are suggested wording.
| When they say | Say this |
|---|---|
| “It’s too expensive.” | “Is the concern funding, the amount, or expected value?” |
| If value is uncertain | “Which result would you need to verify?” |
| If the ceiling is firm | “Would approved scope changes help, or should we stop?” |
| Investment check | “What remains unresolved about the investment?” |
| “We don’t have budget.” | “Is funding unavailable, or does this require approval?” |
| If approval is possible | “What would that approval require?” |
| If funding is unavailable | “Would future contact help, or should we stop?” |
| “Let’s revisit next quarter.” | “What changes next quarter?” |
| If an event matters | “Would you like to reconnect after that event, or leave it here?” |
| If nothing changes | “Shall we leave it here?” |
| “We already use another provider.” | “What works today, and what needs improvement?” |
| If a gap exists | “Would comparing that requirement be useful?” |
| If nothing needs changing | “Understood. We can leave it here.” |
| “I need to talk to my boss.” | “What will your boss need to evaluate before deciding?” |
| If evidence is needed | “Would a joint call or evidence summary help?” |
| Approval check | “Does that cover what your boss needs?” |
| “I need to think about it.” | “What part would you like to think through?” |
| If a question remains | “Address that now, or would you prefer time?” |
| If they prefer time | “Would you like further contact, or not?” |
| “Send me some information.” | “What question should the information help you answer?” |
| If relevant material exists | “I’ll send material addressing that question.” |
| Review check | “Would a review conversation help, or just the material?” |
| “You don’t have the feature we need.” | “What must that feature enable?” |
| If support is verified | “May I show you the documented approach?” |
| If unsupported | “We cannot meet that requirement today.” |
| Fit check | “Is that requirement mandatory?” |
| “Implementation will be too much work.” | “Which part of the rollout concerns you most?” |
| If effort is unverified | “Let me verify the work involved with the right person.” |
| Verification check | “What evidence, owner, and delivery date would work?” |
| “We’re not interested.” | “Understood. I’ll leave it there.” |
Require an approved reciprocal commitment for any discount; never discount merely to end silence. Use the price-objection playbook for negotiation.
How does a complete objection conversation sound?
For example: Maria is considering a proposal; CSV exports are mandatory, but their availability is unverified.
The moment: Opening the concern.
“Maria, what would you need to verify before deciding?”
When they say: “Can we export CSV files?”
“I cannot confirm CSV exports yet. Would checking the documentation help you decide whether to continue?”
When they say: “Yes. Send proof Monday; I’ll review it then.”
“I’ll verify CSV exports and send what I find Monday. What, if anything, is still unresolved?”
When they say: “Nothing else for now. I’ll review it Monday.”
The commitment is verification, not a purchase or another meeting. RAIN Group advises verifying missing information rather than improvising.
How do you confirm the concern is resolved?
A resolution check needs an explicit answer: RAIN Group warns that a buyer’s nod does not establish agreement.
- If a concern remains, clarify again rather than repeating the pitch.
- Record the concern, evidence, unresolved items, and actual commitments. Salesloft recommends confirming resolution rather than leaving it implicit.
How should you prepare for your next call?
Prepare by separating verified proof from unanswered questions, then rehearse the concern you are least ready to handle.
- Review requirements, alternatives, funding approval, evaluators, timing, and rollout constraints using the discovery guide.
- Gather documented capabilities, approved commercial options, and relevant references.
- Have a partner vary one concern’s cause. Check diagnosis, unsupported promises, and explicit answers using the sales roleplay guide.
For rehearsal, see the NextSay Sales overview and how it works.
Frequently asked questions
What are the 5 steps of objection handling?
The five conversational actions are listen, acknowledge, clarify, respond with evidence, and confirm what remains. Acknowledgment recognizes the concern without accepting the buyer’s conclusion.
What are the 5 major objections in sales?
Use five practical groups: fit or need, timing, money, decision authority, and trust or delivery risk. These are working categories, not universal labels. When concerns overlap, ask which condition must be addressed first.
How do you handle objections in sales examples?
Match the evidence to the confirmed question. A customer reference can address delivery confidence, but it cannot establish that your product supports a required feature.
What should I say when I cannot answer an objection?
Say you do not know yet, then identify what needs verification. If verification changes an earlier answer, correct that answer before asking the buyer for another decision.
When should I stop trying to overcome an objection?
End the discussion after an explicit refusal or an unmet mandatory requirement. Permission to verify one issue does not authorize another proposal or a standing follow-up sequence.
Sources
- 7 Winning Steps for Effective Objection Handling | Salesforce salesforce.com
- How To Handle Sales Objections at Every Deal Stage | Salesloft salesloft.com
- 4 Steps to Handle Sales Objections rainsalestraining.com
Rehearse the concern you least want to hear on your next call.
NextSay Sales is a real-time AI call assistant for B2B sales reps and account executives: it guides the live sales call with the next move and Key Signals, and prepares, researches and rehearses each call and writes the record and follow-up. The button opens NextSay on NextSay Sales, with no account needed to try it.
Where your state or theirs requires it, tell the other person the call is being transcribed and get their consent.