Competitor-mention cold email template
Prospects on a competitor are already educated buyers, which makes them valuable. The trick is respect: name a real gap without bashing their choice.
Lead with their outcome, not your feature war.
Short answer
A competitor-mention cold email acknowledges the tool the prospect already uses, names a gap that tool commonly leaves, and offers a low-risk comparison. Never trash the competitor; frame the gap around the prospect's outcome. The template below is ready to personalize.
Key takeaways
- Acknowledge the competitor's strengths; never bash.
- Name a real, specific gap tied to an outcome.
- Use a switch story from a peer as proof.
- Offer a comparison, not a demand to replace.
The competitor-mention template
Acknowledge, then differentiate on outcome.
- Subject: a gap {competitor} tends to leave
- Hi {First}, I know a lot of {industry} teams run {competitor}, and it does {thing} well. Where teams tell us it falls short is {specific gap}, which quietly costs them {consequence}.
- We built for exactly that. {Peer} switched and {result}. Not saying rip and replace, but worth a 15-minute look to compare?
Draft and send this with Ardovo
You do not have to start from a blank page. Tell Rook, Ardovo's AI operator, what you need (for example, "competitor-mention cold email template") and it drafts a version grounded in your real pipeline data, personalizes it for the specific contact or deal, and can send it or enroll it in a sequence in one step. Every template lives in one shared library, so your whole team stays on message and nothing gets rewritten from scratch.
Frequently asked questions
Should I mention a competitor in a cold email?
Yes, when you know the prospect uses one and you can name a real gap. It signals you understand their world. Just stay respectful; trashing their current choice insults their judgment and kills the reply.
How do I position against a competitor without bashing?
Acknowledge what the competitor does well, then name one specific gap framed around the prospect's outcome, not your feature list. "Great at X, but teams lose Y" is credible; "they are terrible" is not.
What if I do not know which competitor they use?
Reference the category instead: "most {industry} teams run a legacy tool that leaves {gap}." You keep the relevance without guessing wrong, and the prospect fills in the name.