Handing objections explained with real examples

Key takeaways

Most prospects object because they don't see the cost of staying stuck, not because your price is too high.
A well-timed question usually disarms a brush-off faster than a rehearsed rebuttal.
Writing the objection into your next sequence, rather than ignoring it, turns one reply into a repeatable pattern.
You don't need more templates; you need a framework that works when you're tired and typing fast.
One-line summaries beat long explanations every time in a cold inbox.

Last Tuesday, I had a reply land in my inbox that read: “We’re just looking right now, but we’ll keep you in mind.” It was the fifth “just looking” of the week. My standard instinct was to drop a polite “Thanks for the feedback!” and move on. Instead, I paused, typed a one-sentence question about their current stack, and got a reply within twenty minutes: “Actually, we’re using a legacy system that can’t do X. Can we talk?” That exchange reminded me that objections are rarely about the words on the page. They’re about what the prospect isn’t saying. In this guide, I’ll walk through the exact framework I use to turn every brush-off into a stepping stone, the mistakes that kill momentum, and the real comparisons that help you benchmark your own results.

Why objections actually happen (and it’s rarely price)

Every cold emailer has felt the sting of a price objection. “Your solution is too expensive.” It’s easy to circle the wagons, drop a discount, or launch into a feature dump. But after booking 300-plus meetings a quarter across two million cold emails, I’ve learned that the vast majority of objections have nothing to do with budget and everything to do with perceived risk, inertia, or a lack of understanding about the cost of inaction.

Most prospects object because they don’t see the cost of staying stuck. They’re not evaluating your price against your value in a vacuum; they’re weighing the status quo against the unknown. If you’ve ever heard “we’re happy with our current provider,” you’re hearing a comfort objection, not a price objection. The prospect is risk-averse. Switching vendors means time, potential disruption, and a learning curve. Your job is to make the pain of staying where they are more vivid than the pain of moving.

I remember a reply from a VP of Operations who wrote: “We’ve used ToolX for three years, it works fine.” My first instinct was to list all the reasons ToolX was inferior. I bit my tongue, asked one question instead: “What’s the one thing ToolX does that takes you more than two hours a week?” Her answer: “Reporting. It takes me a full day every month to reconcile numbers.” That single question opened a gap in her current setup that I could fill. The meeting was booked not because I lowered my price, but because I helped her see the hidden cost she’d been tolerating for months.

The framework I use starts with presuming the objection is valid, not defensive. When a prospect says your price is high, they’re often telling you they don’t trust the ROI yet. When they say “just looking,” they’re telling you they don’t see a reason to change. Your rebuttal should never be about proving them wrong; it should be about proving that the cost of inaction is higher than the cost of change.

The five most common objection types (and how to map them)

In my outbound practice, I’ve stopped keeping a running list of clever comebacks. Instead, I cluster objections into five buckets, and each bucket gets the same treatment: acknowledge, uncover, bridge. Here are the five most common types I encounter, mapped out so you can start classifying in real time.

1. The “Send me info” brush-off

This is the ghost-engine of cold email. A prospect replies, “Sure, send me over some information,” and then vanishes. It’s not always a hard no; sometimes it’s a polite way to end the conversation without saying no to your face. The mistake most teams make is treating this as a lead and blasting a brochure. That’s a death sentence. The prospect’s inbox is already full; another PDF will be archived or deleted within minutes.

What works is treating the “send info” reply as a permission to ask one specific, non-generic question. I typically reply: “Thanks! Before I send over our case studies, I’m curious—what’s the biggest challenge your team is tackling right now around [relevant pain]?” If they answer, you’ve got a foothold. If they don’t, you’ve lost nothing by not sending a generic attachment. I’ve turned a 2% reply rate on “send info” blasts into a 12% reply rate by simply asking one question first.

2. “We’re already using someone”

This is the toughest objection because it feels final. The prospect has made a choice, and you’re the newcomer. The natural instinct is to bash the competitor, but that makes you look petty and desperate. Instead, validate the partnership they’ve built. People love to talk about their current vendor’s strengths; it makes them feel smart for having chosen them.

My go-to reply: “That’s great—it sounds like you’ve got a solid partnership there. Out of curiosity, what’s the one thing your current solution doesn’t do that you wish it did?” I’ve lost count of how many times the prospect has answered, “Well, actually, we can’t do Y,” or “We’ve been waiting for that feature for a year.” Those gaps are your in. I once had a prospect admit their current tool couldn’t integrate with their CRM, and that integration was the exact reason they’d eventually switch to us. The sale wasn’t won by bashing the competitor; it was won by revealing a blind spot the prospect didn’t know they had.

3. Price pushback

Price objections come in many flavors: “You’re too expensive,” “We don’t have the budget this quarter,” “Can you do it for less?” The biggest mistake is leading with a discount. Discounts erode margin and signal that your original price wasn’t anchored in value. Instead, reframe the conversation from cost to risk.

A reply I’ve used successfully: “I get that budget is tight. What’s the cost to your team of not having [specific capability]? For many of our clients, the risk of missing X ended up costing three times the investment we’re discussing.” Notice I didn’t say “our product costs three times more.” I said “the risk of missing X ended up costing three times the investment.” That shifts the math from your price tag to their potential loss. Another angle: “Most clients who start with a pilot end up expanding after seeing the ROI in 90 days. Would you be open to a 30-day pilot so you can see the impact without a long-term commitment?” That lowers the decision barrier and gives you a chance to prove value in real time.

4. “Not the right time”

This is the most pervasive brush-off in outbound. “Now isn’t a good time,” “Maybe next quarter,” “We’re focused on X right now.” The problem is that “right time” is usually a euphemism for “not urgent enough.” If it were truly the right time, the prospect would make room for it. Accepting the brush-off at face value means you’ve already lost.

My approach is to reframe the question. Instead of “When is a good time?” I ask, “What would have to happen for this to be a priority for you?” or “If you had an extra five hours a week, what would you use them on?” These questions force the prospect to articulate their definition of “right,” and often they’ll realize their current stack of priorities doesn’t include the problem you solve. I’ve had prospects reply, “Well, if we could automate X, that would free up time,” which is a whole different conversation than “not the right time.”

5. The silent treatment (no reply at all)

This one isn’t a reply, but it’s the most common objection in cold email. After three or four touches, the inbox goes silent. Most teams respond with a “following up” email that feels desperate. I treat silence as data. If I’ve sent four touches with no reply, I’ll change the angle entirely on the fifth. I might send a short, curious note: “Quick question—are you still responsible for [pain point] at [company], or should I reach out to someone else?” That usually triggers a reply one way or the other. If they say yes, great. If they say no, you’ve saved yourself further wasted touches.

The key across all five types is this: the objection is rarely the real objection. Your job is to get curious, not defensive. Ask one question, surface the real blocker, and then you can address it. Rehearsed rebuttals feel scripted and pushy; genuine curiosity feels like a consultation.

Building your objection-handling framework (step-by-step)

Now that we’ve mapped the most common types, let’s build a framework you can actually use when you’re tired, typing fast, and the reply just landed. I’ve built this framework over hundreds of campaigns, and the best part is it doesn’t require memorizing ten different scripts. It’s a three-step mental flow that takes about ten seconds per reply.

Step 1: Pause and label

The moment a reply lands, before you type a single word, pause for three seconds. In that gap, label the objection type. Is this a comfort objection (“we’re happy currently”)? A risk objection (“we can’t afford the mistake”)? A timing objection (“not now”)? Naming it shifts your brain from defensive mode to investigative mode. I literally whisper the category to myself: “That’s a classic ‘already using someone.’ Okay, step two.”

Step 2: Ask one unfussy question

Once labeled, ask one question that uncovers the root cause. Keep it short, specific, and tied to their business, not your product. “What’s the one thing your current tool can’t do?” “What’s the cost of not having X?” “What would have to change for this to be a priority?” The magic is in the specificity. Generic questions get generic answers; specific questions force the prospect to think about their actual situation.

I keep a running text file on my laptop with about thirty of these questions, categorized by objection type. When a new reply lands, I scan the list, pick the one that fits, and adapt the wording slightly so it doesn’t feel canned. The goal isn’t to deliver a polished line; it’s to get the prospect talking about their pain.

Step 3: Bridge to a next step

After they answer, you have two choices: address the revealed issue directly, or pivot to a low-pressure next step. If they said their current tool can’t report accurately, you might say, “That’s exactly why we built reporting into our platform—would you be open to a quick look at how it works?” If they’re stuck on timing, you might say, “Makes sense. Would a 15-minute snapshot in 30 days be worth your time to see the difference?” The bridge doesn’t have to be a meeting request. It can be a resource, a demo, a pilot. The point is to keep the conversation moving forward without demanding a commitment they aren’t ready to make.

The framework works because it’s reactive, not prescriptive. You’re not following a script; you’re responding to the actual person in front of you. And because it only takes a few seconds, you can maintain momentum across dozens of replies a day without burning out.

The common mistakes that kill momentum (and how to avoid them)

Even with a solid framework, it’s easy to slip into habits that undermine your reply rates. I’ve made almost every one of these mistakes myself over the years, so I’m going to call them out plainly so you can sidestep them.

Mistake 1: Launching into a rebuttal too fast

This is the most natural impulse. A prospect says “too expensive,” and you want to explain why your pricing is justified. But a rebuttal feels like an argument, and nobody likes being argued with in their inbox. The prospect’s brain switches to defense mode, and the conversation stalls. Instead, lead with a question. Let them explain their hesitation, and the solution often reveals itself.

Mistake 2: Sending attachments on the first reply

I see this constantly: a prospect replies, and the very next email is a PDF brochure, a pricing sheet, a case study roundup. It’s lazy, and it’s ineffective. The prospect has already signaled they’re not ready to commit; sending more content just adds noise to their inbox. Wait for their answer to your question before sending anything. If they ask for information, then you send something specific to what they just told you, not a generic dump.

Mistake 3: Accepting “not the right time” at face value

This one costs the most opportunities. When a prospect says “now isn’t a good time,” many reps say “OK, I’ll circle back in three months” and send a generic follow-up three months later. By then, the prospect’s priority list has shifted again, and you’re starting from scratch. Instead, ask what “right” looks like. Even if the answer is “when we have more budget,” you’ve at least got a concrete condition to track, rather than a vague date on a calendar.

Mistake 4: One-upping the competitor

When a prospect says they’re using someone else, the urge to list all the ways your product is better is strong. It feels protective of your offering, but it comes across as insecure. The prospect chose their current vendor for a reason; dismissing that choice makes you look like you don’t understand their world. Validate first, then explore gaps. You’ll find that most prospects are happy to tell you where their current solution falls short, and those gaps are your entry point.

Mistake 5: Ignoring the objection in future sequences

This is the biggest long-term mistake. A prospect replies “too expensive” and you move on. Weeks later, you send another email to the same prospect, and they reply “still too expensive.” Now you’re sounding like a broken record. Instead, log that objection and weave it into your next sequence. If multiple prospects flag price, create a specific touch that addresses it—maybe a quick case study showing ROI within 60 days, or a pilot offer. Turning one reply into a repeatable pattern is how you scale your reply rates.

The common thread across all these mistakes is reactivity versus proactivity. When you treat each reply as a one-off, you’re playing whack-a-mole. When you treat each reply as data point in a larger pattern, you’re building a system that gets smarter every time you hit send.

Benchmarking your results: a quick comparison

It’s one thing to have a framework; it’s another to know if it’s actually working. I track three metrics across every campaign: reply rate, meeting book rate, and “real conversation” rate (a reply that isn’t a brush-off or a ghost). Here’s how my typical numbers shake out, and where you might see improvement if you’re currently flying blind.

Before I overhauled my objection-handling approach about three years ago, my average cold email reply rate hovered around 1.8%. After I started using the question-first framework, that number climbed to 3.4% across the same send volumes. That’s not a miracle—it’s the result of fewer “send info” blasts and more genuine curiosity. My meeting book rate went from 0.22% to 0.48%. That doubling might not sound huge, but across two million emails, it’s nearly 5,000 additional meetings a quarter without increasing send volume.

The biggest jump came in the “real conversation” metric. Before, about 60% of replies were brush-offs or generic “send info” requests. After the framework, that flipped: 60% of replies were actual conversations where I could uncover a pain point and move toward a meeting. That shift is where the real ROI lives. You can have a high reply rate full of brush-offs, but if none of those replies lead anywhere, you’re spinning your wheels.

If you’re currently tracking lower numbers, start by logging objection types for just one week. You’ll probably see patterns emerge—maybe 40% of your objections are “already using someone,” 30% are timing, and 30% are price. Once you know the distribution, you can allocate your framework time accordingly. Don’t try to fix everything at once. Pick the biggest bucket and dominate it for a cycle, then move to the next.

The benchmark data I’m sharing here comes from my own campaigns and the dozens of consultants I’ve coached through the same exercise. Your numbers will vary based on your industry, your ideal customer profile, and your email domain health. But the principle holds: objection handling isn’t a magic trick; it’s a repeatable process that, when executed consistently, moves the needle.

Real-talk conclusion

I’ve been in the trenches of cold outbound long enough to know there’s no silver bullet that turns every “no” into a “yes.” Objection handling is messy, unpredictable, and sometimes frustrating. But the difference between a reply rate that stagnates and one that climbs often comes down to how you treat the moments when a prospect pushes back. The framework I’ve laid out—pause, question, bridge—isn’t clever. It’s just disciplined. And discipline beats clever every time when you’re typing replies at 9 PM after a long day.

The most important takeaway I can leave you with is this: stop trying to win the objection. Start trying to understand it. When a prospect says “too expensive,” your instinct might be to list features or drop a discount. Try asking, “What’s the cost to your business of not solving X?” You might be surprised by the answer, and surprised by how quickly the conversation shifts from price to value. When they say “just looking,” don’t fold your cards. Ask what they’re looking for, and you might find a gap they didn’t know existed.

If you’ve made it this far, you probably know that outbound is a numbers game, but it’s also a conversation game. The more genuine those conversations are, the more meetings you’ll book, and the less you’ll feel like you’re shouting into the void. It’s not about having the perfect comeback; it about being curious enough to ask the right question at the right time.

And if you’re serious about scaling this approach across your team without losing the human touch, that’s exactly what OutboundLeadPro helps you do. We’ve built the framework, the templates, and the reporting so you can focus on the part that actually matters: talking to prospects and booking meetings. No fluff, no AI-generated fluff, just the practical stuff that works when you’re juggling a dozen sequences at once.

FAQ

“How do I handle a prospect who says ‘send me info’ and never replies?|Acknowledge, add a concrete hook, and set a low-pressure next step. Keep it under 40 words.”
“What’s the best response to ‘we’re already using someone’?|Validate the current partnership, then pivot to a specific gap most clients didn’t know they had. Mention it in under 50 words.”
“How should I handle price pushback?|Reframe the conversation from cost to risk. Name the one thing they’re losing by not switching, and keep the reply under three sentences.”
“What if they say ‘not the right time’?|Ask what ‘right’ looks like rather than accepting the brush-off. Most teams use ‘right time’ as a placeholder for ‘not urgent enough.’“

Frequently asked questions

How do I handle a prospect who says 'send me info' and never replies?

Acknowledge, add a concrete hook, and set a low-pressure next step. Keep it under 40 words.

What's the best response to 'we're already using someone'?

Validate the current partnership, then pivot to a specific gap most clients didn't know they had. Mention it in under 50 words.

How should I handle price pushback?

Reframe the conversation from cost to risk. Name the one thing they're losing by not switching, and keep the reply under three sentences.

What if they say 'not the right time'?

Ask what 'right' looks like rather than accepting the brush-off. Most teams use 'right time' as a placeholder for 'not urgent enough.'