Sales
Objection Handling: Diagnose the Concern Before Drafting a Reply
Handle sales objections by identifying the real concern, asking a useful question and responding with evidence instead of a memorized rebuttal.
What you will learn
- Separate uncertainty, fit, timing, authority and a clear refusal.
- Choose a clarifying question before drafting a response.
- Use a truthful answer or a respectful stop condition.
Objection handling starts with understanding what the buyer means. “Too expensive” could describe a budget constraint, an unclear benefit or a polite refusal. Ask one useful question, respond to the actual concern and respect a clear no. A persuasive answer should not require an invented claim.
What is objection handling?
Pete Kazanjy's Founding Sales chapter on pitching includes objections alongside demonstrations and follow-up. That is useful context: an objection belongs in the wider buying conversation, not in an isolated collection of comeback lines.
Do not assume every concern is a hidden yes. Some buyers lack the need, timing or permission to proceed. Some are telling you that the offer does not fit. Your job is to understand the decision, not win an argument.
Record the buyer's words separately from your interpretation. “We cannot allocate an implementation owner this quarter” is evidence. “They are not serious” is an interpretation. Keeping the two apart makes the next conversation more useful.
An original concern-diagnosis practice set
The statements and replies below are fictional. They are prompts for understanding, not scripts to repeat regardless of context.
| Buyer statement | Possible concern | Clarifying question | Useful response or boundary |
|---|---|---|---|
| “It costs more than we expected.” | Budget, scope or unclear value | “Which comparison or budget assumption are you using?” | Compare the same scope; do not invent a discount or ROI. |
| “We already use a spreadsheet.” | Current method may be sufficient | “What works well, and is there a specific gap you want to address?” | Acknowledge that no change may be needed. |
| “We cannot take this on now.” | Timing or operating capacity | “Is there a known event that would make reviewing it useful?” | Agree a relevant re-entry condition only if invited. |
| “Security will need to review it.” | Required evidence and approval | “Which reviewer and questions should we prepare for?” | Route approved evidence; do not improvise compliance claims. |
| “This is not a priority. Please stop contacting us.” | Clear refusal | No further persuasion question is needed | Respect the request and follow the applicable suppression process. |
The same words can have different causes. Keep the diagnosis provisional until the buyer clarifies it. If they do not want to elaborate, you do not have permission to keep probing indefinitely.
Copyable AI prompt
Try this with Aurora AI in Finta, Codex, or Claude. Use only material you are authorized to share, and review the draft before using it.
Review [authorized buyer statements] and [verified offer facts]. Separate exact statement, possible interpretation, clarifying question, supported response and stop condition. Include alternatives such as no fit, no timing and a clear refusal. Do not invent discounts, compliance claims, ROI or hidden buying intent. Draft short responses for human review only; do not send or schedule follow-up.Write a response with one job
Use a short structure: acknowledge the stated issue, check your understanding, provide the relevant supported fact and propose a proportionate next step. If the answer is unknown, name who can verify it and do not promise their response before checking.
For example: “It sounds like the concern is implementation time, not the feature itself. The proposed scope currently requires a customer reviewer and two input files. I can separate that work from the optional rollout tasks so you can judge the commitment. Would that clarify the decision?” This is a fictional draft, not proof of a particular product's implementation requirements.
Keep a source beside claims about price, capability, security and customer outcomes. If a claim cannot be supported, remove it rather than adding confident language.
Review patterns without erasing context
Group repeated concerns so the team can improve its offer or materials, but preserve meaningful differences. A missing feature, a delivery constraint and a buyer with no active project should not become one generic “price” loss reason.
Use the discovery guide to ask better questions and the B2B sales guide for the wider process. Explore Finta's Sales Call Coach with authorized notes when preparing a conversation. Keep the real relationship, approved claims and decision to continue with the responsible seller.