Handling objections in the selling process means keeping a customer’s concerns visible until they are answered, accepted as a limitation or become a reason to stop. A good conversation can still leave work for a technical, delivery or commercial colleague.
Give each open concern an owner and a clear next action. This article covers that workflow. For a definition and a simple exchange, see what handling objections means.
Capture the concern in the customer’s terms
Record the issue, who raised it and when. Include the situation that makes it matter. “Setup concern” is less useful than “Customer cannot allocate its reporting specialist until November.”
Check that your note reflects what the customer meant. Do not replace their statement with an assumed hidden motive. If an interpretation might be useful, label it as a question to investigate.
Decide who can answer it
A seller can answer some questions from approved material. Others need a specialist to verify compatibility, scope or delivery effort. Identify the right owner before promising an answer.
Distinguish a request for information from a request to change the offer. Confirming an existing capability is different from promising custom work. A commercial change may require separate approval even when it appears easy to deliver.
For price concerns, use the price objection guide to establish what the customer is comparing and which costs matter.
Agree the action and timing
State what you will provide, who will provide it and when. If the answer depends on customer information, explain what is needed. Keep the next step proportionate to the question.
For a fictional example, a buyer asks whether an export will work with its reporting system. The action could be to obtain a sample format, have a specialist check it and return a result. Scheduling another general product demonstration would not necessarily answer that question.
If the work cannot be completed by the requested date, say so before the deadline. A realistic update is more useful than leaving the buyer to chase an answer.
Check the answer with the customer
Share the result with its limits. If a test covered one file format, do not imply that every possible export has been validated. Explain any requirement the buyer would need to meet.
Ask whether the answer addresses the concern. Record the response, including any new question. “Answer sent” and “customer confirmed this is acceptable” are different states.
It is possible for the customer to understand the answer and still reject the offer. Do not mark the concern resolved in a way that hides that decision.
Keep the opportunity record consistent
Review what the open issue means for the next step and expected timetable. If a required capability is still unverified, the opportunity record should show that dependency. An unanswered question should not disappear because the seller wants to advance the stage.
Where the issue establishes poor fit, update the opportunity accordingly. Where the customer wants more time, agree whether and when contact would be useful. Respect a request to stop.
Review repeated concerns across the team
Examine a sample of the actual notes before grouping issues under a category. Several “implementation” objections may concern different things: access, resources or an unsupported connection.
Use the findings to improve the relevant material or ownership. The answer may be a clearer product page, an earlier qualification question or better access to technical help. More rebuttal training is not automatically the right response.
If concerns repeatedly lose owners or return unanswered, bring those records to a discovery meeting with The Sales Arc. They provide a practical starting point for reviewing the sales process.
