You send out 500 cold emails. 30 people reply. 15 of those replies are objections - "we're happy with our current vendor," "this isn't in the budget," "send me info and I'll look at it." You panic. You respond with the wrong thing. The conversation dies.

The problem isn't that objections kill deals. It's that you don't have a repeatable, tested system for handling them. You're improvising every single time.

A battlecard fixes this. It's a one-page reference guide that shows exactly how to respond to the 5-7 objections you'll actually get, with specific language that works. No guessing. No wasting time thinking about what to say. Just go down the list, find your objection, use the response.

What Goes Into a Cold Email Objection Battlecard

A functional battlecard has three columns: the objection, the underlying concern it represents, and your response framework.

Most people mess this up by jumping straight from "they said X" to "say Y." That's backwards. You need to understand what they actually mean first, because the objection they state and the objection they're really making are almost never the same thing.

Here's how it breaks down:

Column 1: The Exact Objection They Use

Write down the actual words. "We're happy with our current solution." "This doesn't fit our timeline." "We're not ready yet." Not paraphrases - the real language people use. This is your trigger for which response to deploy.

Column 2: What They're Actually Saying

This is the translation layer. "We're happy with our current solution" usually means "I don't see a clear reason to make a change right now" or "switching costs more than staying put." "We're not ready yet" means "I don't have budget allocated" or "someone else controls this decision and hasn't approved exploration."

Knowing the real objection tells you which response category to use. This is the part that separates people who convert objections from people who get blocked by them.

Column 3: Your Response Framework

This is where the actual language lives. Not a full email template - a framework you adapt based on the conversation. Something like: "Validate - ask a clarifying question - reframe - next step offer."

The 7 Objections That Actually Matter

If you're running cold email at scale, you'll see roughly the same 7-8 objections repeatedly. Build your battlecard around these.

1. "We're happy with our current solution"

What they mean: "I don't know your solution well enough to justify switching, and my current one is adequate."

Your response framework: Acknowledge the vendor relationship exists. Reframe from "replace" to "comparison." Ask a specific question about a pain point you know their current solution doesn't handle well.

An example response:

I get it - most companies we work with felt the same way before they realized [specific vendor] doesn't handle [specific workflow]. When was the last time you evaluated whether there was something better for that process?

The specificity matters here. "Better" means nothing. "Doesn't handle X workflow" gives them something concrete to consider. For a more detailed dive into this one, see our guide on happy with current solution objections.

2. "This is too expensive"

What they mean: "I don't see enough value to justify the cost" or "I don't have budget allocated for this category."

Your response framework: Don't lower your price. Ask what they're currently spending on the problem you solve, then compare. Most prospects don't know.

Example:

What are you currently paying in [labor/software/overhead] for [the problem you solve]? Most companies are surprised when they add it up.

You're not negotiating. You're making the math visible. There's a full breakdown on handling expense objections worth reading.

3. "Send me information and I'll look at it"

What they mean: "I'm not interested enough to talk, but I don't want to be rude."

Your response framework: Don't send a brochure. That email goes into a folder and never surfaces again. Instead, ask one more clarifying question. Offer a 15-minute call. Make it impossible to say yes to without committing to a conversation.

Example:

Rather than me sending a generic overview, it'd be more valuable if I understood your situation first. What's your biggest bottleneck with [specific problem]? Then I can send exactly what's relevant.

This works because you're not asking them to commit to a meeting - you're just asking a question. They answer, and you've now got them in a conversation. For more on this, check out our guide on the "send me info" objection.

4. "We're using an internal solution for this"

What they mean: "We've built something, it works okay, and we don't want to depend on outside vendors."

Your response framework: Validate the decision. Ask about maintenance cost and opportunity cost. Show examples of companies that built something similar and regretted the time investment.

5. "We're not at the right stage for this yet"

What they mean: "We don't have budget, or the person who decides this stuff isn't convinced we need it yet."

Your response framework: Ask what stage they need to hit first. Get specific. "When you're doing $X revenue" or "when you have Y team members." Then stay in touch on a specific timeline - not vaguely, but with actual dates.

6. "We just signed a contract with someone else"

What they mean: "The decision was already made, but I didn't know you existed."

Your response framework: Lock in a re-evaluation date. Most contracts have escape clauses or come up for renewal. Stay in their world until then.

7. "I'm not the decision maker"

What they mean: "You need to talk to someone else, but I'm not going to introduce you."

Your response framework: Ask for the introduction by name. "Would you mind introducing me to [specific person] so I can understand how [problem] affects the broader team?" Make it easy for them to say yes.

How to Build Your Own Battlecard

Start by looking at your actual email replies from the last month. Pull every objection. Group them. You'll probably see 5-7 repeat. Those are your battlecard priorities.

For each objection, write three things: 1) What they literally said, 2) What that usually means, 3) Your response in 1-3 sentences.

Keep it on a single page. Make it a Google Doc. Share it with your team. Every time someone responds to an email, they should check the battlecard first. Not to copy-paste - to get the framework and adapt it to the specific conversation.

Update it monthly based on what's actually working. If you find a response that converts objections consistently, lock it into the battlecard. If one doesn't work, replace it.

The Missing Piece

Knowing the framework is one thing. Executing it consistently across your team, tracking which responses actually work, and updating the battlecard based on real data is another. Most people build a battlecard and then never touch it again - so it gets stale, your team uses it inconsistently, and you lose track of what's actually converting. That's the gap between "I know what to do" and "this actually works at scale."

Related Guides