How to Handle Objections in Sales: Questions, Responses, and When to Stop

Let the buyer finish, reflect the concern accurately, ask a focused question, and respond to the answer. Keep the response short enough for the buyer to correct your understanding before you explain further.

HubSpot’s objection-handling guide recommends preparing for likely concerns before the meeting, then using listen, acknowledge, explore, and respond during the conversation. It attributes that live sequence, known as LAER, to Carew International. Use it as a conversation structure rather than a promise that every objection can be resolved.

1. Listen for the condition behind the words. If the buyer says implementation will overwhelm the team, hear the staffing concern before explaining your product. Wait until they finish describing it.
2. Acknowledge the specific difficulty. Say: Your team is already committed to another rollout, so taking on additional work would be difficult. Acknowledgment does not require agreeing with an inaccurate claim about your offer.
3. Explore what needs to be established. Ask: Which part would create the most work for your team? Follow their answer rather than running through a prepared questionnaire.
4. Respond, then check. Explain the relevant scope or show appropriate evidence. Ask: Does that address the workload concern, or is there another part we need to examine?

Example: A buyer says, “Your service would be hard to introduce.” You ask which team would own the introduction. They explain that no one can maintain the proposed process. You can now discuss responsibility and actual service scope; a longer list of benefits would have missed the issue.

Choose the next action from the answer. Continue when the concern can be examined and the buyer wants to examine it. Pause when information is missing. Stop when a mandatory condition cannot be met or the buyer declines further discussion. A resolved objection is permission to consider the next question, not an automatic agreement to buy.

First establish what “too high” refers to: available funds, an uncertain benefit, or a competing offer. Each calls for different work. Use an open question first; offer those categories if the buyer needs help explaining the concern.

Example: A supplier discussing a maintenance service proposal.

Buyer: Your price is too high.

Seller: You need the cost to make sense before taking this further. What makes the quote feel too high for the work you need?

Buyer: We have another quote for less, and I cannot explain the difference to finance.

Seller: Let’s compare the service scope. Which visits, response commitments, and exclusions does that proposal include? We can review the documents together.

Buyer: Their quote lists scheduled visits. Yours also lists additional work, but I do not know whether we need it.

Seller: Our proposal includes [listed additional scope]. Here is the written scope and the relevant service description. Which of those items addresses a requirement your team has actually identified?

Buyer: The extra inspections might matter, but I need our facilities lead to check.

Seller: Then the open question is whether those inspections belong in your requirements. Would a scope review with the facilities lead help? I can bring the itemized proposal so we can separate required work from additions.

Buyer: Yes, send that first. We may still be over budget.

Seller: I will send it. If the required scope remains above the approved budget, we can check whether an authorized alternative is available or pause. Who should confirm the requirement before we arrange the review?

The conversation ends with a scope decision, not a discount commitment. If the buyer instead reveals a fixed spending limit, ask whether a smaller scope would still meet the essential need. If it would not, say so and pause the proposal.

If the concern is value, ask what result would justify consideration and what evidence the buyer needs. Show relevant deliverables, a demonstration, or documented results with their conditions. Do not turn a hoped-for benefit into a promised return on investment. If competing proposals have equivalent scope, address the remaining price difference directly and explain what, if anything, your team is authorized to change.

Ask what makes the timing difficult and what would need to change. Distinguish a calendar constraint from a project that has no internal priority. A follow-up date is useful only if both sides know what it is waiting for.

Example:

Buyer: We like the proposal, but this is not the right time.

Seller: What is competing with this project at the moment?

Buyer: Our operations team is moving premises. They cannot review another service until that is complete.

Seller: Understood. Is there a milestone after the move when a review would become practical, or would you prefer to leave the project paused?

Buyer: We could reconsider once the new site is operating. I cannot commit to a meeting yet.

Seller: Let’s leave it paused. Would you like a short scope summary to keep, and should I wait for you to contact me?

If the buyer welcomes a later check-in, agree on the trigger and preferred contact method. Record “after the site opens” if that is all they can commit to; do not invent a scheduled evaluation.

For an internal priority objection, ask what outcome currently takes precedence. A useful question is: What would have to be true for this project to receive attention? Their answer might reveal a prerequisite you can help evaluate, or confirm that the project should close for now.

Avoid creating urgency from your own sales deadline. Use the buyer’s actual constraints when discussing timing. Your next step should resolve a dependency or respect the pause, rather than repeat the same pitch on a later date.

Find out what the current supplier does well, what the buyer wants to change, and what switching would require. An existing relationship is part of the decision. Do not assume that dissatisfaction with one detail justifies replacing the whole arrangement.

Example:

Buyer: We already have a supplier, and changing would create too much work.

Seller: Which part of the change concerns you most?

Buyer: Our team knows their ordering process. Retraining everyone would be disruptive.

Seller: Then we should assess the ordering workflow before discussing a replacement. What steps must remain workable for the team?

Buyer: Managers need to approve orders before they are placed.

Seller: Let’s make that an evaluation requirement. We can review [available process documentation] and arrange [an agreed demonstration] covering that approval step. If it does not meet the requirement, we should stop the comparison there.

Only offer documentation or a demonstration your team can actually provide. Check a claim such as “an easy transition” against the work involved: ownership, training, continuity, contractual obligations, and any required transfer of information. Leave technical or contractual questions with the person qualified to answer them.

Ask the buyer how they want the options compared. They may care most about continuity, a specific service gap, or the workload of managing the relationship. Put the same requirement beside each option and identify what remains unknown.

If the buyer confirms that the present supplier meets their needs and they do not want an evaluation, close respectfully: It sounds like the current arrangement works for you. I will leave the proposal here. That is a complete outcome; you do not need to manufacture a switching problem.

Ask how the decision will be evaluated and what each person needs to assess. “I need to discuss this internally” may identify a real approval step. It does not tell you who has authority, whether funds exist, or which concerns remain.

Example:

Buyer: I need to take this to the team before I can answer.

Seller: What will the team need to decide, and what information would help them do that?

Buyer: Operations needs to confirm the workload, and purchasing needs to review the terms.

Seller: I can separate those questions in the proposal. Would you prefer to circulate it yourself, or would a joint review help?

Buyer: Send it to me first. Purchasing may have its own requirements.

Seller: I will send the scope, responsibilities, and proposed terms. Please let me know which purchasing questions need a response and who should handle that discussion with us.

Respect the buyer’s chosen route through their organization. Request an introduction when useful, without treating your contact as an obstacle to bypass.

For your notes, establish the following as information becomes available:

• Evaluation: Which requirements must the team assess?
• Participation: Who reviews fit, cost, workload, and terms?
• Process: What documents or reviews are required before approval?
• Uncertainty: Which questions have no answer or owner yet?

If the buyer cannot describe the process, offer a concise requirements summary they can use internally. Ask permission before arranging meetings with other people. End by confirming what you will send and what response, if any, you have agreed to wait for. Do not describe an internal discussion as purchase approval.

Acknowledge a limitation as soon as it affects a required condition. Separate a capability you know is absent from a question you still need a specialist to investigate. Both deserve a direct answer, but the next steps differ.

Missing requirement: The buyer needs [required capability], and your offer does not provide it. Say: That requirement is outside our current offer. If it is mandatory, this proposal is not a fit. Would you like me to close it here? Do not sell a future possibility as something available now.

Unanswered technical question: Say: I cannot confirm that compatibility. With your agreement, I will ask [responsible specialist] to review [specific requirement] and return an answer before we proceed. Record the question precisely so the specialist investigates the actual condition.

Unproven outcome: If a buyer asks for a guaranteed saving you cannot substantiate, say: I cannot promise that result. We can examine [available evidence] and agree on a suitable evaluation, but you should not approve the proposal on that guarantee. If a guarantee is essential, accept that the sale may end.

Wrong scope: Say: We have been discussing [offered work], while your essential need is [different work]. I suggest we stop this proposal and clarify whether there is a relevant team or provider to approach. Offer a referral only when you have a sound basis for it and permission to make an introduction.

When a buyer gives a clear refusal, acknowledge it and close. When they leave an issue unresolved, ask whether they want a defined check or a pause. The useful distinction is between an answer still being investigated and a condition your offer cannot meet. Repeating benefits does not resolve either one.

SayNow AI offers professional conversation practice with feedback on delivery, structure, clarity, and persuasiveness through its speaking coaching approach. Use the Sales Pitch scenario to rehearse how you explain an answer when a buyer raises a concern.

Choose a concern from this guide and keep a brief cue beside you, such as “price difference, scope unclear.” Speak your acknowledgment, clarifying question, evidence-based response, and confirmation question aloud. Treat these as your rehearsal prompts; use only offer details you can support.

Review the structure and clarity feedback, then select a specific revision. You might shorten the acknowledgment, replace a vague benefit with a concrete scope detail, or ask a question that lets the buyer explain the concern. Speak the revised response again and check whether it still answers the original issue.

For the next round, change the concern in your own preparation notes and rehearse a pause or exit response. Keep the goal specific: a clear explanation and an appropriate next step. Practice your objection response in the Sales Pitch scenario.

Record the buyer’s concern, the evidence discussed, and the agreed next action while the details are fresh. Separate what the buyer confirmed from your interpretation. “Purchasing will review the terms” is different from “the buyer is ready to purchase.”

Use these short review prompts:

• Concern: What did the buyer say, in their own terms?
• Clarification: What did your question establish about the cause?
• Evidence: What did you show, and what remains unconfirmed?
• Decision: Is the concern resolved, open, paused, or a reason to stop?
• Next action: Who agreed to do what, and when or after which trigger?

If a confirmation is useful, send a short message: You raised [concern]. We reviewed [material]. The open point is [question]. I will [action], and we agreed [buyer action or pause]. Please correct anything I have misunderstood. Do not add a buyer commitment that was never made.

Build your judgment about how to handle objections in sales by reviewing the moment when your question changed the conversation. Keep the wording that clarified the issue, replace the answer that missed it, and rehearse the next response against the evidence you actually have. Your measure of a useful conversation is a clearer decision and an accurate next step.