When a customer rejects an offer, acknowledge the decision and establish whether any further contact is welcome. Then record what is known and decide whether there is something useful to change. You do not need to turn every refusal into another sales conversation.
This guide covers the work after a rejection. If a customer is still evaluating the offer and wants a concern answered, the sales rebuttals guide provides example responses.
Accept the decision before asking for feedback
A brief acknowledgement is enough. If the situation allows, ask whether the customer is willing to share a reason. Make that optional rather than a condition of ending the conversation.
For example, this fictional response leaves the choice with the customer: “Thanks for letting me know. If you are willing to share what drove the decision, it would help us review the proposal. No problem if you would rather leave it there.”
If the customer asks for no further contact, record that request and follow it. Do not place them into another follow-up sequence simply because the CRM makes it easy.
Separate the customer’s words from your interpretation
Record the reason as accurately as the available evidence allows. If the customer says the project was postponed, that is different from saying a competitor won. If they give no reason, record it as unknown.
A useful note includes the decision, its date and the source of the information. Add any agreed follow-up separately. Avoid filling gaps with labels such as “no budget” or “poor fit” unless the conversation supports them.
For instance, “customer postponed the project until its internal review” is a reported fact. “The proposal was too expensive” is an interpretation unless the customer said so or other evidence establishes it.
Review the work you could influence
Read the opportunity record and the material shared with the customer. Check whether the stated requirements were addressed, open questions received answers and agreed actions happened on time. Look for a specific gap before prescribing more calls or better closing skills.
You may find that the team proposed an unsupported feature, missed a decision date or misunderstood the purchasing process. Those findings suggest concrete changes. You may also find that the work was sound and the customer chose a different priority.
Keep the scale of the conclusion proportionate to the evidence. One lost deal cannot establish that a whole market rejects the offer or that one salesperson is incapable.
Choose a next action that fits the reason
If an important question went unanswered, improve how the team finds and verifies that answer. If the offer could not meet a requirement, update qualification guidance so the limit is recognised earlier. A genuine product gap belongs with the people responsible for the product.
When the customer has agreed to a later discussion, record the reason for it and the agreed timing. A postponed project is not automatically an active opportunity for the current forecast. Review its status against your team’s evidence requirements.
If there is no useful action and no permission to continue, close the opportunity and move on to other work. Keeping it open does not make the forecast more accurate.
Look for patterns across comparable deals
Group lost opportunities only when the comparison makes sense. Consider the offer, customer type and stage reached. A first-contact refusal and a loss after a formal evaluation reveal different things.
Check the underlying notes before accepting a report of repeated “price” losses. Some records may describe a fixed budget, others a cheaper alternative, and others an unverified assumption. Those situations need different responses.
Use a small set of complete records in a team review. Agree one change to test and the evidence that would show whether it helped. Do not treat a change in win rate alone as proof; the mix and number of opportunities may also have changed.
Make the review useful for the salesperson
A manager can examine the work without turning the outcome into a judgement of someone’s worth. Be precise about what was handled well, what was missed and what support is needed. Vague instructions to be more resilient do not explain what to do differently.
Repeated rejection can be discouraging. Leave room for a colleague to say that the workload or conversations are difficult, and discuss practical support. Ask what support would help rather than assuming the same response suits everyone.
If lost-deal records are too vague to support these discussions, The Sales Arc can review the qualification and follow-up process with you in a discovery meeting. Bring examples of the records and decisions you want to improve.
