TL;DR: Silence from a prospect is not agreement. Founders lose deals when they let prospects leave without surfacing hidden concerns. The hardest part of sales objection handling is extracting the objection in the first place. You must explicitly ask what might prevent the deal, diagnose the real issue, and secure a concrete next step before hanging up.
You end a first sales call for a $2,000 pilot without securing a next commitment or surfacing any objections. The prospect leaves the call, and you assume everything went well.
The mistake here is treating their exit as an answer. Prospects often do not state their real objections directly. If you let them leave without uncovering their concerns, you lose the chance to solve the problem.
Sales objection handling is the process of identifying, diagnosing, and resolving the concerns that stop prospects from buying. While founders often look for common sales objections and rebuttals, the hardest part is not reciting a script. It is extracting the objection in the first place.
The Problem With Scripts
Founders tend to overcomplicate sales objection handling by memorizing polished responses for every scenario. They treat "too expensive" as a complete explanation.
When someone says a product costs too much, they are rarely talking about the absolute dollar amount. Instead, the objection comes from concrete drivers:
How often they plan to use the product
What alternative they compare you with
The perceived monetary value of the outcome
If you answer with a standard discount, you miss the root cause. You need to diagnose the actual constraint before you try to solve it. To see how other teams script their responses, you can review these sales objections scripts. But remember that a script only works if you uncover the real issue first.
The Objection Framework
Before reviewing examples, separate the four distinct steps of objection handling. This discovery process mirrors the principles of customer development:
Surfacing: Getting the prospect to voice their unstated concern.
Diagnosing: Finding the root cause behind the stated concern.
Responding: Addressing the real issue based on your diagnosis.
Securing the next step: Agreeing on an action that moves the deal forward.
The End-of-Call Checkpoint
Do not assume prospects will volunteer what is stopping them. Build an objection check into your process.
Before ending any call — even a first call for a $2,000 offer — surface the hidden objection or secure a concrete further commitment. Frame this as a standard process check, not a high-pressure sales tactic.
Practical Framework: The Extraction Check
Use these checks to draw out concerns before the call ends:
Acknowledge the silence: If they have not raised a concern, assume they are holding one back.
Ask about the alternative: Find out what they use right now, and ask why it might be easier to stay with that option.
Check the perceived value: Ask how your solution compares to their current workflow in terms of outcomes.
Establish a concrete next step: Never leave the call without scheduling a follow-up meeting or clarifying exactly what needs to happen next.
Practical Scenarios and Examples
Sourced Company Case: Gong
Gong's data on sales objections shows that top-performing reps pause before responding to objections.
Stated Objection: "Your price is too high."
Likely Underlying Issue: They may not understand the return on investment, or they compare you to a cheaper, mismatched category.
Diagnostic Question: "How are you currently measuring the cost of not solving this problem?"
Response Principle: Clarify the category and demonstrate value before discussing price.
Next Commitment: Agree to review a business case together.
Illustrative Scenario: The Competitor Comparison
As HubSpot recommends, the best approach to competitor objections is probing rather than arguing.
Stated Objection: "We already have a vendor for this."
Likely Underlying Issue: They might feel that switching is risky, or they want to avoid the procurement process.
Diagnostic Question: "What is the one thing you wish your current vendor did better?"
Response Principle: Investigate their relationship with the vendor instead of listing features.
Next Commitment: Schedule a short follow-up to show how you handle that specific gap.
Illustrative Scenario: The Timing Delay
When a prospect stalls, investigating their underlying concerns leads to better outcomes.
Stated Objection: "Call me back next quarter."
Likely Underlying Issue: They might not see immediate value, or they lack the authority to buy.
Diagnostic Question: "What changes for your team next quarter?"
Response Principle: Uncover the missing urgency or authority barrier.
Next Commitment: Set a firm calendar invite for next quarter with an agenda based on their answer.
Illustrative Scenario: The Feature Request
Reframing the conversation often works better than defending your product.
Stated Objection: "We need it to do X."
Likely Underlying Issue: The feature might be a dealbreaker, or it is a polite excuse to avoid saying no.
Diagnostic Question: "How does your team handle X today without our software?"
Response Principle: Determine if the feature is a core requirement or a distraction.
Next Commitment: Agree to map out a workflow showing how to achieve the outcome without the specific feature.
FAQ
What if the prospect gives me no objection — does that mean they are convinced?
No. Prospects often hide the real objection or never state it directly. You must extract it. Do not ask "What do you think?" or "How do you like it?" — these questions invite polite answers. As a discovery technique, ask about their past decisions and behavior to investigate why they acted that way. The useful objection is the concrete constraint behind their prior inaction.
How do I handle price objections?
Price objections are rarely about the exact dollar amount. They are usually about perceived value, category framing, or frequency of use. Diagnose the root cause by asking what alternative they are comparing you to before defending the price.
What should I do when they say "call me next quarter"?
Do not accept the delay. Ask what specifically changes next quarter. This helps you uncover whether the issue is a lack of budget, lack of authority, or a polite way to say no.
How should I respond to an objection about existing vendors?
Do not argue features. Ask what they wish their current vendor did better. This shifts the conversation from a defensive comparison to an exploration of their unmet needs.
When is an objection a firm no?
An objection is a firm no when you have diagnosed the root cause and found an immovable constraint — like an absolute lack of budget or no relevant use case — that your product cannot solve.
