Sales rebuttals are responses to a customer’s concern. Their purpose is to help the customer assess the offer, not to find a clever way around a refusal. First check whether the person wants an answer. A clear request to end contact should end the conversation.
The examples below are fictional wording for practice. Adapt them to what the customer has said and the evidence you can provide. For the broader process of listening, clarifying and checking an answer, see the guide to handling sales objections.
When the customer says the price is too high
Ask what the price is being compared with. The concern may be an available budget, a competing offer or uncertainty about the scope. Do not assume the salesperson has failed to explain value.
One possible question is: “Is the concern the total amount, the payment timing, or what is included?” Use the answer to decide what information would help.
If the comparison is with another supplier, compare equivalent scope and terms. If the budget is fixed, discuss a smaller scope only when you can actually offer one. An ROI calculation is useful only when its assumptions are relevant and visible; it does not create budget or prove that the purchase is affordable.
When the customer needs time to think
There may be a real decision to work through. Ask whether there is an unanswered question before proposing another call.
For example: “Is there anything you still need to assess, or would it help to have some time without a follow-up?” That leaves room for the customer to ask for information or decline further contact.
If they identify an open issue, agree who will provide the answer. A follow-up date should reflect their decision process. Do not manufacture urgency or describe a pause as a hidden objection without evidence.
When the current supplier is working well
A satisfied customer may have no reason to change. Acknowledge that before asking whether a comparison is useful.
Possible wording: “It sounds as though the current arrangement is meeting your needs. Is there anything you expect to review, or should we leave it there?”
If there is a genuine review, discuss the criteria the customer will use. Provide evidence of your own capabilities and limits. Avoid implying that the incumbent has a problem you have not established, or offering a pilot whose scope and cost have not been agreed.
When other people need to be involved
An internal discussion is part of many buying decisions. It does not establish that your contact lacks authority or influence.
Ask: “What will the team need to assess, and would a written summary or a joint discussion be more useful?” Keep your contact involved rather than trying to bypass them.
A useful summary distinguishes confirmed requirements, open questions and proposed terms. Include implementation responsibilities where they affect the decision. Leave unsupported claims and invented customer examples out of it.
When implementation looks difficult
Do not turn a practical concern into a reason to buy without investigating it. Find out whether the difficulty concerns data, integration, internal capacity or a deadline.
For example: “Which part of the setup looks hardest with your current resources?” Then identify the person who can verify the answer. If you do not know whether a connector or migration is supported, say so and return with a checked response.
It may turn out that the offer is a poor fit. A documented limitation is more useful than a promise the delivery team cannot meet.
Check whether the response helped
After answering, ask whether the information addressed the concern. Give the customer room to disagree. One answered question does not mean every issue is resolved or that a purchase should follow.
Record the concern in the customer’s terms, the evidence supplied and any agreed action. Keep interpretation separate. “Customer requested an integration review” is more precise than “technical objection overcome” when the review has not happened.
Practise answers against actual evidence
In a coaching session, use an anonymised concern from a real conversation. Ask the salesperson to clarify it and locate an answer in approved material. Check whether they distinguish a known capability from something still to be verified.
Review repeated concerns for product, targeting or message problems as well as skill gaps. Where a customer has declined, use the separate guide to handling sales rejection to review the outcome without assuming another rebuttal is needed.
If your team records concerns inconsistently or cannot find reliable answers, bring examples to a discovery meeting with The Sales Arc. That provides a starting point for discussing the process and coaching work required.
