Handbook
/
Sales
Handling Sales Objections
Objections aren't rejections—they're requests for more information. Here's how to handle the most common ones.
Objections are part of every sale. They’re not rejection—they’re engagement. A prospect with no objections is either not paying attention or not serious about buying.
Your job is to address objections clearly and confidently, turning them into reasons to buy.
Understanding Objections
Why Prospects Object
Objections come from:
Genuine concerns (risk, uncertainty)
Need for more information
Testing you (can you handle pushback?)
Negotiating (trying to improve terms)
Habit (always push back on salespeople)
The real reason matters for how you respond.
Surface vs. Real Objections
Sometimes the stated objection isn’t the real issue.
"It’s too expensive" might mean:
They don’t understand the value
Budget is genuinely limited
Another stakeholder has concerns
They’re comparing to wrong alternatives
They want a discount
Dig to find the real objection.
The Objection Handling Framework
1. Listen Fully
Let them finish. Don’t interrupt or rush to respond.
Show you understand: “I hear you saying…”
2. Clarify
Make sure you understand the objection.
“When you say [objection], what specifically concerns you?”
“Can you help me understand more about that?”
3. Validate
Acknowledge their concern is reasonable.
“That’s a fair concern.”
“I understand why that would give you pause.”
Don’t be dismissive.
4. Respond
Address the objection directly.
Use evidence: data, case studies, demonstrations.
5. Confirm
Check if you’ve addressed their concern.
“Does that address your concern?”
“What other questions does that raise?”
6. Move Forward
If addressed, continue the conversation.
“Given that, shall we discuss next steps?”
Common Objections and Responses
“It’s Too Expensive”
Dig deeper: “Compared to what?” / “What were you expecting?” / “Help me understand your budget constraints.”
Value reframe: “Let’s look at the cost of the problem you’re solving. You mentioned [problem] costs [impact]. This solution eliminates that.”
ROI focus: “If this saves your team [X hours/dollars], when does it pay for itself?”
If truly budget-limited: “What is the budget? Let’s see if there’s a way to start smaller.”
“I Need to Think About It”
Dig deeper: “Of course. What specifically do you need to think through?”
Uncover blockers: “Is there information I can provide that would help you decide?”
Set next step: “When would be a good time to reconnect? I’ll send you [relevant resource] in the meantime.”
“We’re Looking at Other Options”
Understand the landscape: “Which others are you considering? I can help clarify how we compare.”
Highlight differentiation: “Here’s where we’re typically different from [competitor]…”
Add value: “Would it help if I put together a comparison for you?”
“We Don’t Have Time to Implement”
Understand their concern: “What specifically about implementation concerns you?”
Reduce perceived effort: “Most customers are up and running in [time frame]. Here’s what that looks like…”
Offer support: “We handle [X, Y, Z] for you. Your team would only need to [minimal effort].”
“We’re Happy with Current Solution”
Dig into satisfaction: “What’s working well? And if you could change anything, what would it be?”
Find the gap: “How does it handle [area where you’re stronger]?”
Plant seed: “Makes sense to stick with what works. Can I check back in [time frame] to see if needs have changed?”
“The Timing Isn’t Right”
Understand the timing: “What’s driving the timing concern? Is there something changing that would make this better later?”
Calculate cost of delay: “If you wait [time period], that’s [continued impact of problem]. Worth considering whether it makes sense to start now.”
Offer flexibility: “We can start with a smaller scope now and expand when timing is better.”
“I Need to Talk to [Someone Else]”
Offer to help: “Would it help if I joined that conversation? I can answer any questions they have.”
Prepare them: “What do you think their main concerns will be? Let me help you address those.”
Set next step: “When are you meeting with them? Let’s schedule a follow-up for right after.”
“Can You Send Me Information?”
Clarify what they need: “Happy to. What specifically would be most helpful?”
Set expectations: “I’ll send that over. Can we schedule a call for [date] to discuss after you’ve reviewed it?”
Don’t let it become an escape hatch.
“Your Company Is Too Small/New”
Acknowledge and reframe: “We are newer, which means you get [more attention, more flexibility, better pricing, direct access to founders].”
Provide proof: “Here are similar companies who’ve trusted us. Would you like to speak with them?”
Reduce risk: “We can start with a pilot so you can see the results before a bigger commitment.”
Advanced Objection Handling
Feel, Felt, Found
Classic framework:
“I understand how you feel. Other customers have felt the same way. What they found was…”
Example: “I understand how you feel about the price. Other customers felt the same way initially. What they found was that the time savings paid for it within three months.”
Isolate the Objection
“If we could address [objection], is there anything else that would prevent you from moving forward?”
This reveals if there are multiple objections or just one.
Turn Objection into Advantage
Reframe the objection as a benefit.
“We’re too small” → “Because we’re smaller, you get direct access to our engineering team and faster response times.”
Walk Away
Sometimes the right response is to acknowledge poor fit.
“Based on what you’re describing, we might not be the best fit for you right now. Here’s what might work better…”
Walking away builds trust and sometimes brings them back.
When You Can’t Overcome
Signs They’re Not Buying
No engagement with your responses
Vague next steps
Can’t articulate the value
New objections keep emerging
What to Do
Acknowledge reality: “It sounds like this might not be the right fit/timing. Is that fair?”
Leave door open: “If things change, I’d be happy to revisit. I’ll check in [time frame].”
Learn from it: “Would you mind sharing what would have made this a better fit? It helps us improve.”
Preventing Objections
Good Discovery Prevents Objections
The best objection handling happens before objections arise.
Uncover concerns early
Address in demo/proposal
Pre-handle anticipated objections
Build Value Throughout
If value is clear, price objections decrease.
If fit is demonstrated, timing objections decrease.
If success stories are shared, risk objections decrease.
Key Takeaways
Objections are engagement, not rejection—welcome them
Surface objections often hide the real concern—dig deeper
Use the framework: listen, clarify, validate, respond, confirm, move forward
Price objection often means unclear value—reframe to ROI
“Need to think about it” means there’s a blocker—find it
Isolate objections: “If we solve this, is there anything else?”
Sometimes walking away is the right move—it builds trust
The best objection handling is prevention through good discovery
Never be dismissive—validate their concern before addressing it
Always end with a clear next step, even if the objection isn’t fully resolved
AIMake has access to all of this
Our AI has access to the entire Startup Handbook. Ask it anything about building your startup.
Get started
Previous
Finding Your First 10 Customers
Next
Hiring Your First Salesperson