The five outbound objections worth having an answer to
Most replies are not yes or no. They are five recurring objections — and how you answer them decides whether the thread ends or turns into a meeting.
Teams write a great opener and then improvise everything after it. That is backwards: the opener decides whether you get a reply, but the reply handling decides whether you get a meeting.
Across the threads we see, almost every non-positive response is one of five things. Each has an answer that works and an answer that kills the thread.
1. “We already use [competitor]”
Kills it: a feature comparison. You are now asking them to relitigate a decision they already made and defend in public.
Works: accept the decision and ask a narrow question about the edges.
Makes sense — most teams your size are on something by now. Out of curiosity, is it covering the follow-up after the first reply, or is that still landing on the AEs?
You are not attacking the incumbent. You are looking for the part of the job it does not do, which is where you actually sell.
2. “Not the right person”
Kills it: apologising and disappearing.
Works: treat it as the referral it is, and make forwarding trivial.
Thanks for flagging — who owns outbound pipeline these days? Happy to go direct so this stops landing in your inbox.
Give them one question with a one-word answer. Do not attach anything they would have to read before forwarding.
3. “Send me some info”
Usually a polite exit. Occasionally genuine. The way to tell is what you send.
Kills it: a 20-page deck and a “let me know your thoughts”. Nobody reads it and there is no next step.
Works: something short and specific, plus a decision point.
Sending a two-minute overview rather than a deck. If the ramp-time part is relevant I’ll grab 15 minutes; if not, I’ll close the loop and leave you alone.
Offering the exit explicitly is what makes the yes meaningful.
4. “No budget” / “Not this quarter”
Kills it: discounting. You have just told them the price was arbitrary.
Works: separate the timing from the fit, and get a real date.
Understood. Is it worth a conversation now so it is scoped for when budget opens, or should I come back after planning — and when is that?
Either answer is useful. A date is a qualified follow-up. A vague deflection tells you it was fit, not budget.
5. Silence after an initial reply
The most common and least handled. Someone engaged, then stopped.
Kills it: “just bumping this to the top of your inbox.” It adds nothing and signals you have nothing to add.
Works: one nudge that carries new information — a relevant result, a change at their company, a specific question — and then a clean close.
Last one from me: [specific, relevant thing]. If the timing is off just say so and I’ll stop.
The explicit close reliably produces replies, because not answering starts to feel ruder than a quick no.
Why this is worth writing down
Two reasons. First, objection handling is where new reps lose deals they had already won. Second, if you are going to hand outbound to software, this is exactly the part that has to be encoded — a tool that branches on keywords will send the wrong one of these five answers with total confidence.
Related: how VSDR handles replies in context, and pricing if the budget objection is yours.
