Every sales conversation eventually hits objections. "It's too expensive." "We already have something." "Not right now." Most founders — especially non-sales founders — react to these badly. They either fold immediately (offering discounts, dropping the pitch), get defensive (over-explaining why the customer is wrong), or panic-close (adding urgency the customer sees through).
The founders who close consistently understand a different reality: objections aren't rejections. They're the buyer's way of saying "I need more information to feel comfortable saying yes." Every objection is an invitation to help them get past a specific concern.
Here are the 12 most common sales objections, plus the exact language for each. This is the playbook I actually use — and teach founders to use — for turning "no" into a real conversation.
First: understand what objections MEAN
A prospect who says "it's too expensive" almost never means "I have no budget." They usually mean:
- I don't yet see enough value to justify this price
- I have budget, but not for this specific thing (priority issue)
- I'm testing whether you'll discount (negotiation)
- Something else about the deal makes me uncomfortable and price is easier to say
A prospect who says "we already have something" usually means:
- What we have is imperfect but I don't want to explain the details
- I'm not the person who'd make the switch decision
- I'm shopping but you haven't yet shown me why to move
- I'm politely deflecting
A prospect who says "not right now" usually means:
- The timing genuinely isn't right (rare)
- I don't yet believe this will produce results (common)
- Other priorities are ahead of this (common)
- I want to but need approval I haven't gotten yet
The rule: never take an objection at face value. Every objection is a symptom. Your job is to diagnose the underlying concern, then address that.
The 3 principles of handling objections well
Before the specific templates:
Principle 1: Acknowledge before addressing
Never dive straight into a counter-argument. Acknowledge first.
Bad: "But actually, our pricing is very competitive because..." Good: "I hear you — price is a real factor in this decision. Can I ask what you're comparing to?"
The acknowledgment does two things: shows you actually listened, and buys time to think.
Principle 2: Ask, don't tell
Most founders answer objections with more information (features, testimonials, case studies). This rarely works.
What works: asking questions that let the prospect reveal what they actually need to hear.
Bad: "Let me show you three case studies of similar customers who saw ROI within 90 days..." Good: "What specifically about the price feels off? Is it the total, the monthly commitment, or something else?"
Questions surface the real concern. Information overwhelms.
Principle 3: Never argue
If a prospect says "we don't need this" and you spend 10 minutes explaining why they DO need it, you'll lose the deal — even if you're right. Nobody buys because they lost an argument.
Instead: understand their perspective, restate it back, and let THEM come to a new conclusion.
The 12 most common objections and how to handle them
Objection 1: "It's too expensive"
What they might mean: value isn't clear yet, no budget for this priority, testing for discount, or comparing to a cheaper alternative.
Bad response: "We offer a 20% discount for annual." (immediately negotiating)
Good response: > "I understand — that's a fair concern. Can I ask what you're comparing it to? If it's [Competitor X], they price differently but end up costing more with the add-ons most customers need. If it's the cost of doing nothing, the math usually looks like [specific calculation]. What's the comparison you're making?"
Why it works: you ask for the real basis of "expensive" instead of just discounting. Often the prospect can't actually articulate what they're comparing to, which reveals price is a stand-in for another concern.
Objection 2: "We already have something for this"
What they might mean: don't want to switch, don't see enough differentiation, or actually satisfied with current solution.
Bad response: "But ours is different because we have [feature X]." (arguing on features)
Good response: > "That makes sense — most companies your size have something in place. What I'm curious about: is there anything about your current setup that's less than ideal, or that you'd change if you could?"
Why it works: you're inviting them to identify gaps in what they have, rather than trying to convince them their current thing is bad. Often they'll tell you exactly what would make them consider switching.
Objection 3: "Not right now" / "Let's revisit in Q3"
What they might mean: they're not the decision-maker, other priorities are ahead, or they're politely declining.
Bad response: "OK, let's put a calendar reminder for Q3." (which never converts)
Good response: > "Understood. I want to respect your priorities. Two quick questions: > 1) What would need to be true in Q3 for this to become a priority? > 2) In the meantime, is there anything specific that would make you change the timing?"
Why it works: you learn whether the delay is real or an excuse. Real delays have specific triggers ("we're moving offices" / "our fiscal year starts"). Excuses don't have specific answers.
Objection 4: "I need to talk to my team/boss/spouse"
What they might mean: they don't have authority to decide alone, they're deflecting, or they genuinely need buy-in.
Bad response: "OK, let me know what they say." (loses control of the deal)
Good response: > "That makes sense. Can I ask: what's your recommendation going to be to them? Because that's the actual conversation that matters. And what specifically would they want to know before making a decision?"
Why it works: two effects. First, you make them articulate whether they're personally on board (usually the answer reveals it). Second, you learn what the decision-maker needs, so you can prepare them (or offer to join the conversation).
Objection 5: "Send me some more information"
What they might mean: they want to end the call politely, they need info to sell internally, or they're doing due diligence.
Bad response: "Sure, I'll email over our full deck." (deck gets forgotten in inbox)
Good response: > "Happy to. So I can send the RIGHT information: what specifically would help you? Case studies of similar customers? Detailed pricing? A technical spec? Or is there a specific question I could answer right now?"
Why it works: if they're deflecting, they'll say "just send the general stuff" (a signal). If they're serious, they'll name specific things, giving you both a follow-up hook and information about their concerns.
Objection 6: "We don't have budget for this"
What they might mean: literally no budget, or "not important enough to reallocate budget for."
Bad response: "Well, when is budget being planned for next year?" (kicks the can)
Good response: > "That's fair. Two things I'm curious about: > 1) If budget were available, is this something you'd move forward on? > 2) Because in my experience, budget is often less about 'available' and more about priorities. Are there current line items that this would replace, or that would be cheaper by moving to us?"
Why it works: the first question separates real budget constraint from priority ("no we still wouldn't buy" = it's not budget, it's value). The second surfaces potential ROI framing.
Objection 7: "Your product doesn't do [X]"
What they might mean: it's a genuine dealbreaker, or they think it's a dealbreaker but might not be.
Bad response: "Actually we do have that on our roadmap for Q3." (over-promising)
Good response: > "You're right — we don't do [X]. Can I ask: is that something you actively need today, or a nice-to-have? And are you currently doing [X] through another tool that would keep working alongside us?"
Why it works: many "must-have" features turn out to be nice-to-haves when the prospect articulates their actual usage. Others are already handled by tools that don't need to be replaced. Rarely is it a genuine dealbreaker.
Objection 8: "I need to think about it"
What they might mean: they're not ready to decide, they have specific concerns they haven't voiced, or they're being polite.
Bad response: "Sure! I'll check back next week." (usually no reply)
Good response: > "Of course. What are you thinking about specifically? Because sometimes when I hear 'let me think,' there's actually a specific concern that surfaces in the thinking — and if I can address it now, we can save you some cycles."
Why it works: you're not pressuring them to buy; you're inviting them to share the underlying concern. Most people appreciate this — it's easier for them to voice the concern in the moment than to have to explain themselves in a follow-up email.
Objection 9: "Send me a proposal"
What they might mean: they're serious and need a document, or they're using it as a soft rejection.
Bad response: Immediately promise a 20-page proposal. (delays the decision)
Good response: > "Happy to. Before I put together a proposal, let me confirm a few things so it's specific to your situation: is [pricing range] the right ballpark? Are we solving for [problem A] or also [problem B]? Who else needs to see this before you can make a decision?"
Why it works: proposal writing is expensive time. Confirming basics upfront ensures the proposal actually leads somewhere. Also often reveals the objection was really "I'm not ready to decide" in disguise — in which case, don't write the proposal.
Objection 10: "We're going with [competitor]"
What they might mean: they've made the decision, or they're testing whether you'll respond with a better offer.
Bad response: Immediate 30% discount to save the deal. (signals your prices were made up)
Good response: > "I understand — [competitor] is a legitimate choice. Can I ask: what specifically was the deciding factor? Because I want to know for future prospects, and if it's something I could have addressed, I'd rather know now than not."
Why it works: you often learn something valuable (positioning gap, feature you don't emphasize, price presentation issue). Occasionally the prospect reveals that the decision wasn't actually final, opening the door back up.
Objection 11: "It sounds too good to be true"
What they might mean: they're skeptical of the specific claims you're making.
Bad response: "It's actually true — we can prove it." (defensive)
Good response: > "That's a healthy skepticism. Which specific claim feels off? Because sometimes marketing language sounds punchier than the reality — and I'd rather tell you the specific number than the marketing version."
Why it works: shows you're honest, invites specificity, and often the specific reality is impressive enough to close the deal (or at least remove the skepticism).
Objection 12: Silence / ghosting after a good meeting
What they might mean: priority changed, hit an internal blocker, or lost interest.
Bad response: "Just following up on my last email!" (four times in a row)
Good response (one specific follow-up, then move on): > "Hey [name] — haven't heard back on [thing]. Totally understand if timing shifted or if the priority moved. Two options for you: > 1) If we should reconnect in [specific timeframe based on their situation], say the word and I'll circle back then. > 2) If it's not going to happen, I'd appreciate a quick 'no' so I can stop bothering you and go help someone else. > Either is fine — just want to close the loop."
Why it works: gives them the graceful out to say "no thanks," which they usually take. Better to close the loop than pester indefinitely.
The 4 traps that kill deals
Trap 1: The immediate discount. The moment a prospect mentions price, offering a discount. This teaches them your prices are made up and they should always ask for more.
Trap 2: The over-explanation. Instead of asking questions, dumping information on them. Overwhelms rather than persuades.
Trap 3: The fake urgency. "This offer expires Friday!" when it doesn't. Sophisticated buyers see through this and lose trust.
Trap 4: The competitor bash. "Well, competitor X is fine but they don't do..." Everyone can see through this. Speak positively about competitors and let your own strength speak for itself.
The one meta-objection: "I don't trust you yet"
Most objections, underneath, are versions of one thing: "I don't yet trust you enough to say yes."
Trust is built through:
- Specific relevant examples (not generic case studies — SPECIFIC to their situation)
- Realistic promises (what you say will happen matches what actually happens)
- Willingness to say no (declining a bad-fit deal builds trust with the deals you do close)
- Continuity (consistent behavior across every touch point)
If you find yourself facing objection after objection, the underlying issue is usually trust, not features or pricing. Address that (be more specific, more honest, more willing to walk away) and the individual objections often resolve.
A specific example
I worked with a founder whose close rate was ~10%. She was getting good discovery meetings but losing most of them at the objection phase.
What we found in review:
- She was answering "it's too expensive" by immediately mentioning payment plans (before understanding the real concern)
- She was answering "we already have something" by attacking the competitor (defensive)
- She was answering "let me think" with "sure, I'll follow up next week" (killing momentum)
What we changed:
- For each of the 12 objections, she pre-wrote her response using the templates above
- Practiced them out loud until they were natural
- On calls: asked one question before answering ANY objection
Result over 90 days:
- Close rate went from 10% to 25%
- Average deal size went UP (she stopped discounting reflexively)
- Sales cycle SHORTENED (better questions surfaced real objections earlier)
No new product features. No new marketing. Just better objection handling. That's the leverage in this skill.
What to do this week
If you're doing sales calls:
- Pick the 3 objections you hear most often
- Write out (or memorize) the responses using the templates above
- Practice them out loud before your next call — hearing yourself say them makes them stick
If you're getting a lot of "let me think about it":
- Your discovery isn't surfacing real objections during the call
- Ask better questions earlier: "What would need to be true for you to move forward?"
If your close rate is under 15%:
- Record your next 5 calls (with permission)
- Listen back specifically for how you handle objections
- Look for patterns: are you over-explaining? Discounting too fast? Missing chances to ask questions?
If you're not doing sales calls yet:
- The templates above apply to email too — same principles
- Every "no" via email is an opportunity to ask ONE question that surfaces the real concern
If sales is a struggle broadly, related reads:
- How to get your first 10 customers — sometimes the objections you face are downstream of targeting the wrong prospects
- How to write cold emails that get replies — the same "acknowledge first, ask questions" approach applies to written outreach
- Customer discovery interview guide — sometimes objections in sales calls reveal you haven't done enough discovery work
Objection handling is the single most trainable sales skill. Most founders never train it because they don't view themselves as "salespeople." But every founder IS in sales, whether they call it that or not. Getting good at objections is where the biggest close-rate gains live.
---
If you have a specific objection you keep failing at, reach out via the contact page with the objection and the language you're currently using. I'll give you a rewrite.