The Sales Arc

Product

Sales43

Solutions

Overview Revenue leaders Sales managers Sales professionals Enablement & RevOps Individuals Small and mid-sized businesses Enterprises

Services

Overview Training & coaching Implementation & advisory The Sales Arc Framework

Company

About Insights
Request access

Handling Sales Objections: Listen, Clarify and Respond

Handle sales objections by understanding the concern before responding. Use questions, evidence and a clear next step to assess whether the issue is resolved.

Sales Skills & Tactics By RK
Two people having a discussion across a desk

Handling sales objections starts with understanding what the buyer is concerned about. A price objection may concern affordability, uncertain value or a comparison with another option. You need to know which issue you are answering before choosing a response.

The purpose is to help the buyer make an informed decision. Sometimes the concern can be resolved. Sometimes it reveals a poor fit, a requirement you cannot meet or a reason to stop the sale.

A process for handling sales objections

Listen before preparing your answer

Let the buyer finish. Note the specific concern and ask about anything unclear. Do not assume that a familiar phrase means the same thing in every conversation.

For example, “implementation looks difficult” could refer to staff availability, a previous failed project or a missing integration. Each calls for a different discussion.

Check your understanding

Summarise the concern in plain language and ask whether you have understood it correctly. A useful response might be: “You are concerned that your team cannot support the setup work this quarter. Have I understood that?”

Acknowledge the issue without pretending to agree with an unsupported conclusion. Avoid stock empathy phrases if you cannot explain what you have heard.

Ask what would resolve the concern

Find out what information or change the buyer needs. If the price seems high, ask what they are comparing it with and which costs they have included. If they doubt a capability, ask what they need the product to do.

Check whether other concerns would remain if this one were addressed. Give the buyer room to explain them; do not turn the question into pressure for a commitment.

Respond with relevant evidence

Answer the issue directly. Use a demonstration for a workflow question, a written scope for an implementation concern or a cost breakdown for a budget discussion. State any limitation that affects the decision.

A customer example can help when it is real, relevant and approved for use. Do not invent another customer’s experience or promise that the buyer will achieve the same result. If the evidence is not available, say what you will check and when you will respond.

Confirm what happens next

Ask whether the response addressed the concern. If it did not, find out what remains unresolved. If it did, agree an appropriate next step with an owner and a date.

A next step could be a technical review, a revised proposal or a decision not to proceed. Agreement that an answer makes sense is not the same as agreement to buy.

Work through a price objection

Consider this fictional example. A buyer says, “Your proposal costs more than the alternative.” The salesperson asks which alternative they are comparing and whether both proposals cover the same work.

The comparison reveals that one quote excludes implementation. The salesperson shows the cost breakdown and asks the buyer to compare the total scope. If the proposal is still too expensive, they discuss whether a smaller scope would meet the buyer’s needs.

This example illustrates a way to investigate the objection. It does not establish that a higher price is justified or that a buyer should accept it.

Prepare the team without scripting every answer

Keep a record of recurring objections, the questions that clarified them and the evidence used in response. Include cases where the product was not a fit. A useful playbook helps a salesperson investigate; it should not supply a rebuttal for every possible concern.

Practise with realistic situations. Ask the observer to identify where the salesperson made an assumption, missed a question or offered a claim without evidence. Where recording is permitted and participants have agreed, a call review can provide specific examples.

Review your objection-handling approach when requirements, pricing or the product change. Remove answers that no longer apply.

Improve the next conversation

Choose one recent objection and examine what the team knew at the time. Identify the question that was missing or the evidence that would have helped. Use that finding in the next practice session.

The Sales Arc’s training and coaching can help teams examine these conversations and practise clearer responses.

See how Sales43 would work for your team

Request access and The Sales Arc will arrange a walkthrough.