Absolutely. The best BDR objection scripts don’t try to “beat” the objection. They acknowledge it, ask one smart question, and either earn another 20–30 seconds or establish a concrete next step. That pattern shows up consistently in current sales-training guidance.

1. “Just send me an email.”

Best default:

“Absolutely. I can do that. Just so I don’t send you something generic, what’s the biggest thing you’d want to know about [problem/solution]?” If they answer, follow with:

“Got it. I’ll keep it focused on that. If it looks relevant, would it be crazy to spend 10 minutes on it next week?” This is stronger than simply saying “sure” because you're converting the email request into a specific need + agreed next step.

If you think it's clearly a brush-off

“Happy to. And I know you’re probably busy, so let me make it easy—give me 20 seconds on why I called, and you can decide whether the email is even worth sending. Fair?” Then give one sentence of relevance, not a product pitch.

---

2. “I’m not interested.”

Don't immediately launch into another pitch.

“Totally fair—you weren’t expecting my call. Can I ask you one quick question before I let you go?” Then:

“How are you currently handling [specific problem]?” If they have it solved, move on. If there's friction, you've earned the conversation.

The key is recognizing that an early “not interested” often reflects resistance to the interruption rather than an informed evaluation of your offering.

---

3. “We already have a solution/vendor.”

Don't attack the incumbent.

“That makes sense. Most companies we speak with already have something in place. Out of curiosity, what do you like most about your current solution?” Then:

“And if you could change one thing about it, what would it be?” That second question is the money question. If they're completely happy, don't manufacture a problem. But if they identify a weakness, you've uncovered a reason to continue.

---

4. “We’re not looking right now.”

Try:

“Understood. Is that because [problem] isn't a priority, or because you already have it covered?” This separates “not a priority” from “not interested in your solution.”

If it's timing:

“Got it. When does that typically become a priority for you?” Now you have potentially useful timing information instead of a dead-end “follow up sometime.”

---

5. “I’m too busy.”

Don't respond with a five-minute pitch.

“I figured I probably caught you at a bad time. Give me 20 seconds to tell you why I called, and you can tell me if it's worth continuing. Fair?” Or, if they genuinely sound rushed:

“No problem. Is later today better, or would tomorrow be easier?” The important distinction is busy ≠ uninterested.

---

6. “How much does it cost?”

Avoid immediately throwing out a number if pricing depends on their situation.

“It depends a bit on what you're trying to accomplish. Before I give you a number that may be meaningless, can I ask how you're handling [problem] today?” If there is a standard price:

“Plans start around $X. The bigger question is whether there's enough value there for you—can I ask how you're currently handling [problem]?”

---

7. “We don't have budget.”

Try:

“I understand. Is the issue that there's genuinely no budget allocated, or that this isn't high enough priority to spend budget on?” That's a much better question than immediately defending your price.

If there's no budget:

“Makes sense. When does budgeting typically happen for this?” If it's a priority issue:

“What would have to change for it to become worth funding?”

---

8. “Call me next quarter.”

Don't just say “sure.”

“Happy to. So I don't call you at the wrong time, what's likely to be different next quarter?” Then:

“Makes sense. Why don't we put 10 minutes on the calendar for [specific week], and if the priority hasn't changed, we'll leave it there?” You're respecting their timing while preventing the vague “I'll call you sometime later” trap.

---

9. “We’re happy with what we have.”

Use curiosity rather than confrontation:

“That's good to hear. What would you say is the one thing your current provider does exceptionally well?” Then:

“And is there anything you wish they did better?” If they can't identify a gap, that's useful information. If they can, you've got your opening.

---

10. “I’m not the right person.”

Don't immediately hang up.

“Got it. Who typically owns [specific problem] on your side?” If they give you a name:

“Perfect. And just so I approach them intelligently, what tends to matter most to them around [problem]?” Now your referral comes with context, rather than being a blind introduction.

---

The BDR objection framework I'd actually train

Rather than memorizing 30 responses, teach reps this:

Acknowledge → Question → Advance

Example

Prospect: “Just send me an email.”

BDR: Acknowledge: “Absolutely.”

Question: “Just so I send something relevant, what's the biggest thing you'd want to know about [X]?”

Advance: “Got it. I'll send that over. If it looks relevant, let's take 10 minutes next week—Tuesday or Wednesday better?”

That's essentially the common thread across modern objection-handling recommendations: don't argue, don't over-explain, and don't surrender the conversation immediately.

One important rule

Don't use the same script mechanically. “Send me an email” from a genuinely interested but busy prospect should be handled differently from a prospect who is obviously trying to get you off the phone. Current guidance specifically recommends distinguishing between a real information request and a reflexive brush-off.

If you're building a BDR call playbook, I can also give you a one-page objection-handling cheat sheet with 15 objections, exact word-for-word responses, and when not to push back.

The best way for a Business Development Representative (BDR) to handle the "just send me an email" objection is to pivot. Do not simply agree to send the email, as it usually results in a ghosted thread. Instead, use the request to build value, narrow down their interest, or secure a brief conversation.

Here are the best scripts to handle this and other common BDR objections.

📧 Objection: "Just send me an email"

Strategy: Agree to send it, but ask a targeted question to customize the content and keep the conversation going.

• The "Tailored Content" Pivot:
  • "I'd be happy to do that. So I don't flood your inbox with generic info, are you more focused on [Pain Point A] or [Pain Point B] right now?"
• The "Calendar Value" Pivot:
  • "I can definitely do that. Honestly, our platform is highly visual, and an email won't do it justice. Can we take just 3 minutes right now to see if it’s even relevant to you?"
• The "Upfront Agreement" Pivot:
  • "Will do. If you like what you see in the email, what is the best way for us to connect next week? If you don't like it, you can just reply 'no thanks' and I'll stop reaching out. Fair enough?"

🛑 Objection: "We already use a competitor / [Competitor Name]"

Strategy: Validate their choice, don't insult the competitor, and position your solution as a distinct alternative or a strong backup plan.

• The "Complementary Solution" Script:
  • "[Competitor] is a great platform. Many of our current clients used them too before finding that we integrate perfectly to handle [specific gap/feature]. How is that specific piece working for you today?"
• The "Keep Us in Mind" Script:
  • "That makes sense—they are a major player. Contracts always come up for renewal eventually. Can we take 5 minutes next Tuesday just so you can see how we differ, in case you ever need a backup plan?"

⏳ Objection: "I don't have time / Bad time"

Strategy: Respect their time immediately, but don't just hang up. Attempt to lock in a specific, ultra-short alternative window.

• The "20-Second Flash" Script:
  • "I completely understand, I'll be brief. I'm calling because we help [industry] companies solve [major problem]. If I promise to catch you at a better time, do you have 30 seconds to schedule a quick call for Thursday morning?"
• The "Direct Alternative" Script:
  • "Got it, sounds like you are swamped. Would it be better if I called you back tomorrow at 10:00 AM, or is later this afternoon preferred?"

💰 Objection: "We don't have the budget"

Strategy: Shift the focus away from cost and toward value. A BDR's goal is to see if there is a problem worth solving, not to close a financial contract on a cold call.

• The "No Cost Exploration" Script:
  • "That's completely fine. I'm not looking to sell you anything today. I just want to show you how we've helped companies like yours save [X amount of time/money], so you have the data when budget opens back up. Worth a look?"
• The "ROI Pivot" Script:
  • "Understood. Most companies we talk to don't have a specific line item for this until they see how much money they are losing by doing [process] manually. If we could change that, would it be worth a brief look?"

To tailor these further, let me know:

• What product or service are you selling?
• Who is your target persona (e.g., HR Managers, CTOs, Sales VPs)?
• What other objections do you hear most often?

The best way for a Business Development Representative (BDR) to handle the "just send me an email" objection is to pivot. Do not simply agree to send the email, as it usually results in a ghosted thread. Instead, use the request to build value, narrow down their interest, or secure a brief conversation.

Here are the best scripts to handle this and other common BDR objections.

📧 Objection: "Just send me an email"

Strategy: Agree to send it, but ask a targeted question to customize the content and keep the conversation going.

• The "Tailored Content" Pivot:
  • "I'd be happy to do that. So I don't flood your inbox with generic info, are you more focused on [Pain Point A] or [Pain Point B] right now?"
• The "Calendar Value" Pivot:
  • "I can definitely do that. Honestly, our platform is highly visual, and an email won't do it justice. Can we take just 3 minutes right now to see if it’s even relevant to you?"
• The "Upfront Agreement" Pivot:
  • "Will do. If you like what you see in the email, what is the best way for us to connect next week? If you don't like it, you can just reply 'no thanks' and I'll stop reaching out. Fair enough?"

🛑 Objection: "We already use a competitor / [Competitor Name]"

Strategy: Validate their choice, don't insult the competitor, and position your solution as a distinct alternative or a strong backup plan.

• The "Complementary Solution" Script:
  • "[Competitor] is a great platform. Many of our current clients used them too before finding that we integrate perfectly to handle [specific gap/feature]. How is that specific piece working for you today?"
• The "Keep Us in Mind" Script:
  • "That makes sense—they are a major player. Contracts always come up for renewal eventually. Can we take 5 minutes next Tuesday just so you can see how we differ, in case you ever need a backup plan?"

⏳ Objection: "I don't have time / Bad time"

Strategy: Respect their time immediately, but don't just hang up. Attempt to lock in a specific, ultra-short alternative window.

• The "20-Second Flash" Script:
  • "I completely understand, I'll be brief. I'm calling because we help [industry] companies solve [major problem]. If I promise to catch you at a better time, do you have 30 seconds to schedule a quick call for Thursday morning?"
• The "Direct Alternative" Script:
  • "Got it, sounds like you are swamped. Would it be better if I called you back tomorrow at 10:00 AM, or is later this afternoon preferred?"

💰 Objection: "We don't have the budget"

Strategy: Shift the focus away from cost and toward value. A BDR's goal is to see if there is a problem worth solving, not to close a financial contract on a cold call.

• The "No Cost Exploration" Script:
  • "That's completely fine. I'm not looking to sell you anything today. I just want to show you how we've helped companies like yours save [X amount of time/money], so you have the data when budget opens back up. Worth a look?"
• The "ROI Pivot" Script:
  • "Understood. Most companies we talk to don't have a specific line item for this until they see how much money they are losing by doing [process] manually. If we could change that, would it be worth a brief look?"

To tailor these further, let me know:

• What product or service are you selling?
• Who is your target persona (e.g., HR Managers, CTOs, Sales VPs)?
• What other objections do you hear most often?

A good BDR objection response usually follows a simple pattern:

1. Acknowledge the objection (don’t fight it).
2. Lower the pressure (show you respect their time).
3. Ask a question that uncovers the real reason.
4. Earn the next step (don’t jump straight into pitching).

Here are practical scripts for common BDR objections.

1. “Just send me an email.”

Goal: Keep the conversation alive without refusing their request.

Script A — The personalization pivot

“Absolutely, happy to send something over. So I don’t just send you another generic sales email, what would be most useful for you to see — how we help with [problem], examples from companies like yours, or something else?” Script B — The 20-second permission ask

“Sure, I’ll send that over. Before I do, can I ask one quick question so I make it relevant? How are you currently handling [problem area] today?” Script C — The meeting bridge

“Happy to. Usually the email only gives the high-level overview, though. If it looks relevant, would it make sense to grab 15 minutes next week to see if there’s a fit?” The mistake is simply saying “Sure, what’s your email?” and ending the call. The better move is to agree while using the moment to qualify interest.

---

2. “I’m not interested.”

Script A — The curiosity check

“Totally fair. Usually when I hear that, it’s because either this isn’t a priority or you already have a solution in place. Which one is closer for you?” Script B — The 30-second reset

“I understand. You weren’t expecting my call. Can I take 30 seconds to explain why I reached out, and you can tell me if it’s worth continuing?”

---

3. “We already have a vendor.”

Script A — Find the gap

“That makes sense. Most companies I speak with already have something in place. Out of curiosity, what made you choose your current solution?” Script B — Competitive differentiation

“Got it. If you could change one thing about your current setup, what would it be?”

---

4. “We don’t have budget.”

Script A — Separate budget from priority

“Understood. Is the challenge that there’s no budget allocated right now, or that solving this problem isn’t a priority at the moment?” Script B — Low-pressure discovery

“Makes sense. I’m not asking you to buy anything today — I’m just trying to understand if this is a problem worth solving. Is it something your team is looking at?”

---

5. “I don’t have time.”

Script A — Respect + value

“I get it. I’ll be brief — the reason I called is [specific outcome]. If it’s irrelevant, I’ll let you go. Fair?” Script B — Reschedule

“No problem. Is there a better time this week when I can take two minutes and see if this is worth a conversation?”

---

6. “Call me back later.”

Script A — Lock in context

“Happy to. Before I let you go, what should I make sure we cover when I call back?” Script B — Avoid the vague follow-up

“Sure. When you say later, are we talking next week, next month, or after a specific event?”

---

7. “How much does it cost?”

Script A — Don’t price dump

“It depends on what you’re looking to solve and the scope. To make sure I’m not giving you a meaningless number, can I ask how you’re currently handling this?” Script B — Qualify

“Is budget the main factor you’re evaluating, or are you trying to understand whether there’s a fit first?”

---

A simple BDR cheat-code formula

When you hear almost any objection:

“Totally understand. A lot of people I speak with initially say that. Just so I don’t waste your time — [one diagnostic question]?” Examples:

• “Just send me an email” → “What would you want me to include so it’s actually useful?”
• “Not interested” → “Is that because timing is off, or because this isn’t a problem you’re focused on?”
• “Already have a solution” → “What’s working well, and what would you improve?”

The best objection handlers don’t try to “win” the objection — they turn it into a discovery question.

Script A — The personalization pivot

“Absolutely, happy to send something over. So I don’t just send you another generic sales email, what would be most useful for you to see — how we help with [problem], examples from companies like yours, or something else?” Script B — The 20-second permission ask

“Sure, I’ll send that over. Before I do, can I ask one quick question so I make it relevant? How are you currently handling [problem area] today?” Script C — The meeting bridge

“Happy to. Usually the email only gives the high-level overview, though. If it looks relevant, would it make sense to grab 15 minutes next week to see if there’s a fit?” The mistake is simply saying “Sure, what’s your email?” and ending the call. The better move is to agree while using the moment to qualify interest.

---

2. “I’m not interested.”

Script A — The curiosity check

“Totally fair. Usually when I hear that, it’s because either this isn’t a priority or you already have a solution in place. Which one is closer for you?” Script B — The 30-second reset

“I understand. You weren’t expecting my call. Can I take 30 seconds to explain why I reached out, and you can tell me if it’s worth continuing?”

---

3. “We already have a vendor.”

Script A — Find the gap

“That makes sense. Most companies I speak with already have something in place. Out of curiosity, what made you choose your current solution?” Script B — Competitive differentiation

“Got it. If you could change one thing about your current setup, what would it be?”

---

4. “We don’t have budget.”

Script A — Separate budget from priority

“Understood. Is the challenge that there’s no budget allocated right now, or that solving this problem isn’t a priority at the moment?” Script B — Low-pressure discovery

“Makes sense. I’m not asking you to buy anything today — I’m just trying to understand if this is a problem worth solving. Is it something your team is looking at?”

---

5. “I don’t have time.”

Script A — Respect + value

“I get it. I’ll be brief — the reason I called is [specific outcome]. If it’s irrelevant, I’ll let you go. Fair?” Script B — Reschedule

“No problem. Is there a better time this week when I can take two minutes and see if this is worth a conversation?”

---

6. “Call me back later.”

Script A — Lock in context

“Happy to. Before I let you go, what should I make sure we cover when I call back?” Script B — Avoid the vague follow-up

“Sure. When you say later, are we talking next week, next month, or after a specific event?”

---

7. “How much does it cost?”

Script A — Don’t price dump

“It depends on what you’re looking to solve and the scope. To make sure I’m not giving you a meaningless number, can I ask how you’re currently handling this?” Script B — Qualify

“Is budget the main factor you’re evaluating, or are you trying to understand whether there’s a fit first?”

---

A simple BDR cheat-code formula

When you hear almost any objection:

“Totally understand. A lot of people I speak with initially say that. Just so I don’t waste your time — [one diagnostic question]?” Examples:

The best way to handle the "just send me an email" objection is to pivot the conversation immediately to uncover a specific pain point, rather than giving up or sending a generic message.

Here are the best high-utility BDR scripts to handle this and other common objections.

1. "Just send me an email"

Goal: Agree to send the email, but use it as a bridge to ask a qualifying question.

• The "What to include" pivot:
  "I'd love to. So I don't waste your time with a generic brochure, are you currently more focused on [Problem A] or [Problem B]?"
• The "Open calendar" check:
  "Can do. Usually, people ask for an email because they are running into a meeting. Are you in the middle of something, or can I take 30 seconds to show you why I called?"
• The "Filter the noise" approach:
  "I will absolutely do that. Our platform covers a lot of ground, from [Feature X] to [Feature Y] . Which of those is most relevant to your team right now so I can send the right info?"

2. "We already use a competitor"

Goal: Do not attack the competitor; focus on gaps, contracts, or future evaluation.

• The compliment and contrast: "[Competitor Name] is a great platform. Most companies we work with use them too. They usually switch to us because they need stronger [Unique Value Proposition] . How has your experience been with their [Specific Feature]?"
• The timeline check:
  "That makes sense, they are huge in this space. I'm not looking to replace them today. When does your current contract with them come up for renewal?"
• The benchmark offer:
  "Glad to hear you have that covered. Even if you don't switch, it might be worth seeing how your current setup benchmarks against the market. Would you be open to a peer review next week?"

3. "We don't have the budget"

Goal: Shift the focus from price to value or timing.

• The "No cost to look" shift:
  "I completely understand. Budgeting is tight everywhere right now. I'm not asking you to buy anything today. I just want to show you how we typically save teams [X]% on their current spend so you have it in mind for next quarter."
• The ROI challenge:
  "That’s exactly why I called. Most of our clients felt the same way until they saw that our tool actually pays for itself within [X] months by reducing [Specific Waste/Cost]."

4. "I'm not the right person"

Goal: Turn a rejection into a warm internal referral.

• The direct guidance request:
  "Thanks for letting me know. Usually, the person managing [Specific Responsibility] handles this. Who on your team is currently driving that initiative?"
• The clean hand-off:
  "Got it. I appreciate your honesty. If I reach out to [Name of likely persona from LinkedIn] , should I mention that we spoke briefly?"

5. "We are handling this internally"

Goal: Acknowledge their expertise, then introduce a perspective they might lack.

• The resource relief angle:
  "That's great, building it yourself gives you total control. Many teams we partner with started out doing it internally too, but found it was draining too much engineering time away from their core product. How much time is your team spending maintaining that system?"

To tailor these further, let me know:

• What product or service are you selling?
• Who is your target persona (e.g., CFO, VP of Sales, IT Manager)?
• What is your biggest value proposition?

I can build customized, word-for-word scripts based on your specific market.

The best BDR objection handling is not a clever comeback. It’s a short pattern: acknowledge → probe → give a relevant reason → ask for the next step. That aligns with current guidance from HubSpot and Salesforce, both of which emphasize curiosity and diagnosis before responding.

Here’s a practical talk track you can actually use on cold calls.

1. “Just send me an email.”

Best default:

“Absolutely, happy to. Just so I don’t send you something generic—what would be most useful: how we solve [problem], results we’ve gotten for companies like yours, or pricing?” Then:

“Got it. I’ll send that over. And rather than have you read a five-page email and guess whether it’s relevant, why don’t we take 10 minutes next week and see if it actually applies?” More direct version:

“Happy to. Usually when someone asks me to send information, it’s because they’re either curious but busy, or they’re not sure this is relevant. Which is it for you?” That second version is particularly useful because it turns a vague brush-off into a real conversation. HubSpot similarly recommends using the request for information as an opening to qualify rather than simply ending the call.

2. “I’m not interested.”

“Totally fair. Usually when I hear that, it’s because what I’m offering isn't a priority, you already have something in place, or you don't see the value yet. Which is closest for you?” If they answer, stop selling and investigate that answer.

For example:

“We already have a solution.”

“Makes sense. What do you like most about what you're using today?” Then:

“And if you could change one thing about it, what would that be?” That's much stronger than immediately saying, “We're better than your current provider.”

3. “We already use [Competitor].”

“Got it. And I'm not looking to convince you to rip something out that's working. What do you like most about [Competitor]?” Then:

“Where do you wish it worked better?” If they identify a weakness:

“That's actually where we tend to help companies like yours. Would it be unreasonable to spend 15 minutes showing you how we approach that?”

4. “We don't have budget.”

Don't immediately defend your price.

“I understand. Is the issue that there's literally no budget allocated, or that this isn't currently high enough on the priority list to justify spending?” Those are two completely different objections.

If it's priority:

“What would have to happen for this to become a priority?” If it's genuinely no budget:

“Understood. When does budgeting typically happen for something like this?” Now you've learned something useful instead of arguing about price.

5. “We're too busy.”

“I completely understand. That's actually why I'm calling rather than sending you a long pitch. Give me 30 seconds to explain why I reached out, and you can tell me if it's worth another conversation.” Then give a 20–30 second value proposition, not a product dump. HubSpot specifically recommends keeping the initial value proposition concise and selling the next step rather than trying to conduct the entire sales process on the prospecting call.

6. “Call me back next quarter.”

“Happy to. Just so I don't randomly call you in three months—what do you expect will be different next quarter?” If they say, “Budget should open up.”

“Got it. Is budget the only thing holding this back, or are there other pieces we should figure out first?” If they genuinely have a future initiative:

“Makes sense. Why don't we spend 10 minutes now understanding what you're planning? That way, when the budget opens up, we'll already know whether we're a fit.”

7. “I'm not the person who handles this.”

Don't just say “Who is?”

“No problem. Just so I point myself in the right direction, who typically owns [problem/initiative]?” Then:

“And would it make sense for you to introduce us, or should I reach out directly?” This is particularly important for BDRs because an objection can actually reveal that you've reached the wrong persona.

8. “We don't need it.”

“Fair enough. What are you currently doing for [problem]?” Then:

“And is that working exactly the way you'd like?” If yes, don't force it.

If no:

“What isn't working?” Now you've converted “we don't need it” into discovery.

9. “Send me pricing.”

“Absolutely. Pricing depends a little on how you're using it. Can I ask you two quick questions so I don't send you a number that's completely irrelevant?” If they agree, qualify.

If they insist:

“I can send you a range. Before I do, what are you comparing it against?” That tells you whether they're actually evaluating or simply trying to end the call.

10. “We're happy with what we have.”

“That's good to hear. What would have to change for you to consider switching?” This is one of my favorites because you're not challenging their current decision.

You are learning their switching criteria.

The BDR cheat code: don't rebut too quickly

When you hear an objection, mentally run:

Pause → Acknowledge → Question → Listen → Respond → Advance

For example:

Prospect: “Just send me an email.”

Weak BDR:

“Sure, what's your email?” Better BDR:

“Absolutely. What would you like me to include?” Great BDR:

“Absolutely. What would be most relevant to you?” Elite BDR:

“Absolutely. Usually when someone asks for an email, they're either interested but don't have time right now, or they're not convinced it's relevant. Which is it for you?” The last version isn't about beating the objection. It's about finding the real objection.

That's the recurring theme in modern objection-handling guidance: don't answer the prospect's first sentence as though it's necessarily the real problem. Listen, acknowledge, explore, and only then respond.

A simple BDR formula to memorize

“Totally fair. [Question that diagnoses the objection]. If [relevant condition], would it make sense to [small next step]?” Examples:

• “Totally fair. Is it timing, priority, or that you already have a solution?”
• “Makes sense. What would need to be different for this to become a priority?”
• “Absolutely. What would you want to know before deciding whether it's worth exploring?”
• “I hear you. If we could solve [specific problem], would it be worth a 15-minute conversation?”

One important rule: don't fight every objection. If someone clearly isn't interested and has no relevant problem, thank them and move on. Good objection handling is about earning another conversation, not trapping someone on the phone. HubSpot and Salesforce both caution against defensive or overly aggressive responses.

If you're building a BDR team, I’d turn these into a one-page objection cheat sheet with the top 15 objections, exact scripts, and follow-up questions so reps can keep it beside their dialer.

Then:

“Got it. I’ll send that over. And rather than have you read a five-page email and guess whether it’s relevant, why don’t we take 10 minutes next week and see if it actually applies?” More direct version:

“Happy to. Usually when someone asks me to send information, it’s because they’re either curious but busy, or they’re not sure this is relevant. Which is it for you?” That second version is particularly useful because it turns a vague brush-off into a real conversation. HubSpot similarly recommends using the request for information as an opening to qualify rather than simply ending the call.

2. “I’m not interested.”

“Totally fair. Usually when I hear that, it’s because what I’m offering isn't a priority, you already have something in place, or you don't see the value yet. Which is closest for you?” If they answer, stop selling and investigate that answer.

For example:

“We already have a solution.”

“Makes sense. What do you like most about what you're using today?” Then:

“And if you could change one thing about it, what would that be?” That's much stronger than immediately saying, “We're better than your current provider.”

3. “We already use [Competitor].”

“Got it. And I'm not looking to convince you to rip something out that's working. What do you like most about [Competitor]?” Then:

“Where do you wish it worked better?” If they identify a weakness:

“That's actually where we tend to help companies like yours. Would it be unreasonable to spend 15 minutes showing you how we approach that?”

4. “We don't have budget.”

Don't immediately defend your price.

“I understand. Is the issue that there's literally no budget allocated, or that this isn't currently high enough on the priority list to justify spending?” Those are two completely different objections.

If it's priority:

“What would have to happen for this to become a priority?” If it's genuinely no budget:

“Understood. When does budgeting typically happen for something like this?” Now you've learned something useful instead of arguing about price.

5. “We're too busy.”

“I completely understand. That's actually why I'm calling rather than sending you a long pitch. Give me 30 seconds to explain why I reached out, and you can tell me if it's worth another conversation.” Then give a 20–30 second value proposition, not a product dump. HubSpot specifically recommends keeping the initial value proposition concise and selling the next step rather than trying to conduct the entire sales process on the prospecting call.

6. “Call me back next quarter.”

“Happy to. Just so I don't randomly call you in three months—what do you expect will be different next quarter?” If they say, “Budget should open up.”

“Got it. Is budget the only thing holding this back, or are there other pieces we should figure out first?” If they genuinely have a future initiative:

“Makes sense. Why don't we spend 10 minutes now understanding what you're planning? That way, when the budget opens up, we'll already know whether we're a fit.”

7. “I'm not the person who handles this.”

Don't just say “Who is?”

“No problem. Just so I point myself in the right direction, who typically owns [problem/initiative]?” Then:

“And would it make sense for you to introduce us, or should I reach out directly?” This is particularly important for BDRs because an objection can actually reveal that you've reached the wrong persona.

8. “We don't need it.”

“Fair enough. What are you currently doing for [problem]?” Then:

“And is that working exactly the way you'd like?” If yes, don't force it.

If no:

“What isn't working?” Now you've converted “we don't need it” into discovery.

9. “Send me pricing.”

“Absolutely. Pricing depends a little on how you're using it. Can I ask you two quick questions so I don't send you a number that's completely irrelevant?” If they agree, qualify.

If they insist:

“I can send you a range. Before I do, what are you comparing it against?” That tells you whether they're actually evaluating or simply trying to end the call.

10. “We're happy with what we have.”

“That's good to hear. What would have to change for you to consider switching?” This is one of my favorites because you're not challenging their current decision.

You are learning their switching criteria.

The BDR cheat code: don't rebut too quickly

When you hear an objection, mentally run:

Pause → Acknowledge → Question → Listen → Respond → Advance

For example:

Prospect: “Just send me an email.”

Weak BDR:

“Sure, what's your email?” Better BDR:

“Absolutely. What would you like me to include?” Great BDR:

“Absolutely. What would be most relevant to you?” Elite BDR:

“Absolutely. Usually when someone asks for an email, they're either interested but don't have time right now, or they're not convinced it's relevant. Which is it for you?” The last version isn't about beating the objection. It's about finding the real objection.

That's the recurring theme in modern objection-handling guidance: don't answer the prospect's first sentence as though it's necessarily the real problem. Listen, acknowledge, explore, and only then respond.

A simple BDR formula to memorize

The best BDR objection scripts don’t try to “overcome” the prospect. They acknowledge the objection, ask one smart question, and either earn another 20–30 seconds or get a clean next step. That lines up with Gong’s research on objection handling: validate → clarify/isolate → reframe → advance.

1. “Just send me an email.”

Best default:

“Absolutely. So I don’t send you a generic deck—what’s the one thing you’d want to know about [problem]?” If they answer:

“Got it. I’ll send that specifically. And if it looks relevant, would it be crazy to take 15 minutes next week?” If you suspect it’s a brush-off:

“Happy to. Before I do, just so I don’t waste your inbox—is [problem] actually something you’re looking at, or is it just not a priority?” That distinction matters: “send me an email” is often a dismissive reflex rather than a genuine request for information.

If they're genuinely busy:

“Of course. What would be most useful—pricing, a case study, or a quick overview? And when would be a reasonable time for me to circle back?” The key is don't say “sure, I'll send something” and hang up. You want to turn the email request into either a qualification question or a defined follow-up.

2. “I’m not interested.”

“Totally fair—you don’t know enough about what I’m calling about yet. Can I take 20 seconds to explain why I reached out, and you can tell me if I’m completely off base?” If they say yes, actually take 20 seconds. Don't turn it into a three-minute pitch.

A softer version:

“Fair enough. Is that because [problem] isn't a priority, or because you already have it handled?” That gets you from a vague rejection to a real reason.

3. “We already have a solution.”

“Makes sense. Most companies I speak with already have something in place. Out of curiosity, what do you like most about your current solution?” Then:

“And if you could change one thing about it, what would it be?” This avoids the rookie mistake of immediately trashing their incumbent.

4. “We don’t have budget.”

“Understood. Is the issue that there’s genuinely no budget allocated, or that this isn't high enough on the priority list to get budget?” Those are two completely different objections.

If it's priority:

“Got it. What would need to happen for this to become a priority?” If it's genuinely no budget:

“Makes sense. When does budget typically get planned for something like this?” Now you're qualifying timing instead of arguing about price.

5. “We’re too busy right now.”

“I figured I might be catching you at a bad time. Is it the topic that's not a priority, or literally just bad timing today?” If it's timing:

“No problem. Would [specific day] be better?” Gong specifically recommends acknowledging the interruption rather than steamrolling through it, then making a secondary ask.

6. “Can you call me back next quarter?”

“Absolutely. So I don't randomly call you in three months—what's likely to change by then?” That's a fantastic qualification question.

If nothing will change:

“Got it. Then would it make more sense to look at this now, or should I close the loop altogether?”

7. “I’m not the right person.”

“Got it. Who usually owns [specific problem]?” Then:

“And would it make sense for you to introduce us, or should I reach out directly?” Don't immediately accept “not my area” as a dead end. You may have just found the path to the actual buyer.

8. “We’re happy with what we have.”

“That's good to hear. I'm curious—what would have to be true for you to ever consider switching?” If they give you something:

“Interesting. How are you handling [that issue] today?” Now you're discovering a potential gap without attacking their existing vendor.

9. “Send me pricing.”

This one is particularly important for BDRs:

“Happy to. Pricing depends a little on [X]. Can I ask you two quick questions so I don't send you a completely irrelevant number?” If they agree, qualify.

If they refuse:

“No problem. I can send a range. Just so I put the right context around it, are you evaluating this for [use case A] or [use case B]?”

The framework I'd actually train a BDR on

Rather than memorizing 25 scripts, I'd teach this:

Acknowledge → Question → Connect → Advance

For example:

Prospect: “Just send me an email.”

BDR: “Absolutely.” ← Acknowledge

BDR: “So I send the right thing, what's most important to you—reducing [X] or improving [Y]?” ← Question

Prospect: “Probably reducing X.”

BDR: “Got it. That's actually why I called—we've been helping [similar companies] with X.” ← Connect

BDR: “I'll send something specific. If it looks relevant, are you opposed to taking 15 minutes Tuesday?” ← Advance

That structure is much more useful than trying to memorize clever comebacks. Gong's research similarly emphasizes validating first, then using a question to uncover the real objection before reframing.

One rule I'd drill into every BDR

Never fight the objection.

Bad:

“But that's exactly why you need to talk to us…” Better:

“Totally fair. Can I ask one quick question?” The goal isn't to win the objection. It's to determine whether there's enough legitimate interest to continue. If there isn't, a clean “no” is actually better than forcing a meeting.

If you're building a BDR playbook, the “send me an email,” “not interested,” “too busy,” “already have a vendor,” “no budget,” and “call me next quarter” objections are the five I'd drill until they're automatic. Gong's analysis of 300M+ cold calls found that the top five objections account for roughly 74% of objections.

The best way to handle the "just send me an email" objection is to pivot the conversation immediately to uncover a specific pain point, rather than giving up or sending a generic message.

Here are the best high-utility BDR scripts to handle this and other common objections.

1. "Just send me an email"

Goal: Agree to send the email, but use it as a bridge to ask a qualifying question.

• The "What to include" pivot:
  "I'd love to. So I don't waste your time with a generic brochure, are you currently more focused on [Problem A] or [Problem B]?"
• The "Open calendar" check:
  "Can do. Usually, people ask for an email because they are running into a meeting. Are you in the middle of something, or can I take 30 seconds to show you why I called?"
• The "Filter the noise" approach:
  "I will absolutely do that. Our platform covers a lot of ground, from [Feature X] to [Feature Y] . Which of those is most relevant to your team right now so I can send the right info?"

2. "We already use a competitor"

Goal: Do not attack the competitor; focus on gaps, contracts, or future evaluation.

• The compliment and contrast: "[Competitor Name] is a great platform. Most companies we work with use them too. They usually switch to us because they need stronger [Unique Value Proposition] . How has your experience been with their [Specific Feature]?"
• The timeline check:
  "That makes sense, they are huge in this space. I'm not looking to replace them today. When does your current contract with them come up for renewal?"
• The benchmark offer:
  "Glad to hear you have that covered. Even if you don't switch, it might be worth seeing how your current setup benchmarks against the market. Would you be open to a peer review next week?"

3. "We don't have the budget"

Goal: Shift the focus from price to value or timing.

• The "No cost to look" shift:
  "I completely understand. Budgeting is tight everywhere right now. I'm not asking you to buy anything today. I just want to show you how we typically save teams [X]% on their current spend so you have it in mind for next quarter."
• The ROI challenge:
  "That’s exactly why I called. Most of our clients felt the same way until they saw that our tool actually pays for itself within [X] months by reducing [Specific Waste/Cost]."

4. "I'm not the right person"

Goal: Turn a rejection into a warm internal referral.

• The direct guidance request:
  "Thanks for letting me know. Usually, the person managing [Specific Responsibility] handles this. Who on your team is currently driving that initiative?"
• The clean hand-off:
  "Got it. I appreciate your honesty. If I reach out to [Name of likely persona from LinkedIn] , should I mention that we spoke briefly?"

5. "We are handling this internally"

Goal: Acknowledge their expertise, then introduce a perspective they might lack.

• The resource relief angle:
  "That's great, building it yourself gives you total control. Many teams we partner with started out doing it internally too, but found it was draining too much engineering time away from their core product. How much time is your team spending maintaining that system?"

To tailor these further, let me know:

• What product or service are you selling?
• Who is your target persona (e.g., CFO, VP of Sales, IT Manager)?
• What is your biggest value proposition?

I can build customized, word-for-word scripts based on your specific market.

Handling the classic "just send me an email" brush-off is all about lowering friction, regaining control, and calling out the elephant in the room with a smile. Here are the top scripts organized by strategy, designed to pivot that polite rejection into a real conversation.

The "Permission & Hook" Strategy

Acknowledge their request, but ask a quick qualifying question first so you can actually send something relevant instead of a generic brochure.

• The Tailored Info Approach: "Happy to. To make sure I don't send you a generic PDF you'll delete in 3 seconds, what's the one thing on your plate right now regarding [pain point]?"
• The Value Drop Approach: "I can do that. Just so I send the right context—are you guys currently struggling with [Problem A] or [Problem B]?"
• The Quick Pitch + Choice: "I'll send it over right after this. But just so I know what to highlight: is your team focused more on saving time or cutting costs with [solution category] right now?"

The "Pattern Interrupt" Strategy

Politely push back by highlighting that email isn't usually the best place for a first glance, using gentle humor or candor.

• The Honest Truth: "I’d love to, but honestly, my emails usually end up in the digital graveyard. Let's do this: I'll send it, but let's put 5 minutes on the calendar for [Day] just to see if it even makes sense. If not, we cancel. Fair?"
• The Low-Pressure Check: "I can, but usually when people say that, it's a polite way of saying 'not interested.' If that's the case, just tell me straight—is the timing just completely off?"
• The Calendar Anchor: "Will do. But since my calendar fills up fast, what does your Thursday look like for a quick 2-minute reality check on whether this is even relevant for you?"

Would you like me to tailor these for a specific industry/product , or do you need scripts for another common objection (like "we already use a competitor" or "we have no budget")?

Absolutely. The best BDR objection handling is not about winning an argument—it’s about lowering resistance, figuring out whether there’s a real objection underneath, and earning the next 10–30 seconds. Gong’s analysis of 300M+ cold calls similarly recommends agreeing with the objection, incentivizing a little more conversation, and selling the next small step rather than immediately selling the product.

The core formula

Use this simple pattern:

Acknowledge → Clarify → Reframe → Small CTA

For example:

“Totally fair. Just so I don't send you something irrelevant—what are you currently doing for [problem]?” The important part is asking a question instead of launching into a rebuttal. Gong's research specifically finds that strong objection handling starts with clarification and validation rather than a long monologue.

1. “Just send me an email.”

Best default:

“Absolutely, happy to. Just so I send you something relevant and not a generic brochure—what’s the biggest priority around [problem] right now?” If they answer:

“Got it. I’ll keep it focused on that. And if it looks relevant, would it be crazy to spend 10 minutes on it together rather than make you figure it out from an email?” More direct version:

“Happy to. Usually when people ask me to email, it’s because they’re either interested but busy, or it’s not a priority. Which is it for you?” Permission-based version:

“Of course. Before I let you go, can I take 20 seconds to explain why I called? Then you can decide whether the email is even worth opening.” This is particularly useful because “send me an email” can be a genuine preference or simply a polite exit. The trick is to avoid treating it as an objection you need to defeat.

2. “I’m not interested.”

Don't respond with “Why not?” That can put the prospect on the defensive. Instead:

“Totally fair—you weren't expecting my call. Just so I don't bother you unnecessarily, is [problem] simply not a priority right now?” Or:

“Fair enough. Is that because you already have [solution/process] handled, or because it isn't something you're focused on?” This turns a vague rejection into something you can actually qualify.

3. “We already use [competitor].”

“Makes sense. Most companies I speak with already have something in place. Out of curiosity, what do you like most about [competitor]?” Then:

“Got it. And is there anything you wish it did better?” You're not attacking the competitor. You're looking for a gap.

If they say everything is great:

“That's good to hear. Sounds like there's probably not a reason to change right now. Would it be useful if I sent over a quick comparison so you have it if that ever changes?”

4. “We don't have budget.”

Don't immediately discount or defend your price.

“Understood. Is the issue that there's genuinely no budget allocated for this, or that the problem isn't painful enough to justify spending on?” If there's no budget:

“Makes sense. When does that typically get revisited?” Now you've potentially uncovered timing rather than a dead opportunity.

5. “We're too busy right now.”

“I figured that might be the case. Is it more that this isn't a priority, or that you actually don't have bandwidth to look at it?” If bandwidth is the issue:

“Totally understand. What would need to change for this to become worth looking at?” That gets you a trigger event instead of a vague “call me later.”

6. “Call me back in a few months.”

Don't simply say “Sure.”

“Happy to. So I don't call you at the wrong time again, what changes in a few months?” Then:

“Got it. And assuming that happens, would [month] be a reasonable time to reconnect?” Now you have both reason + timeline.

7. “I'm not the right person.”

This is actually a valuable objection.

“Got it. Who normally owns [specific problem]?” Then:

“And would you mind if I mentioned you pointed me their way?” If they're hesitant:

“No problem. What would you recommend I say when I reach out?” That can give you valuable account intelligence even if you don't book the meeting.

8. “We're happy with what we're doing.”

Try:

“That's great. What would have to happen for you to consider changing it?” Or:

“Makes sense. What do you like most about your current setup?” Then:

“And what's the one thing you'd improve if you could?” You're looking for dissatisfaction without forcing them to admit they're unhappy.

9. “How much does it cost?”

If you're early in the conversation:

“It depends a bit on what you're trying to accomplish. Before I throw a number at you, can I ask one quick question about how you're handling [problem] today?” If they insist:

“Fair question. We're typically in the range of [range]. If that's roughly where you'd expect it to land, does it make sense to spend a few minutes seeing whether it's actually a fit?” The goal is to prevent price from becoming a substitute for understanding value.

10. “I need to think about it.”

For a true sales conversation:

“Absolutely. When someone tells me they need to think about it, it's usually because I either haven't answered something or there's a concern we haven't uncovered. Which one feels closer to what's happening?” That approach is consistent with Gong's research on “I need to think about it”: use the statement to uncover the underlying uncertainty rather than immediately pushing for a close.

The 5 scripts I'd memorize

If you're training a new BDR, I'd actually have them memorize only these:

“Send me an email.”

“Happy to. So I send something relevant rather than generic, what's the biggest priority around [X] right now?” “Not interested.”

“Totally fair. Is that because [X] isn't a priority, or because you already have it handled?” “Too busy.”

“I get it. Is it bad timing, or is this just not important enough to spend time on right now?” “We already have a solution.”

“Makes sense. What do you like most about it—and what would you change if you could?” “Call me later.”

“Happy to. What changes between now and then that would make this more relevant?”

One rule I'd drill into every BDR

Don't rebut the objection before understanding it.

The weakest response is:

Prospect: “Just send me an email.” BDR: “Absolutely, but the reason I called is that our platform can increase your productivity by 37%…” The prospect asked to get off the phone, and the rep responded by talking more.

A better response is:

“Absolutely. Before I do, can I ask one quick question?” Then listen.

That's the fundamental difference between objection handling and objection arguing. Gong's call analysis repeatedly emphasizes pausing, validating, asking questions, and earning permission before reframing.