--- title: "Naming competitors in cold email: when it works, when it backfires" description: "Naming a rival in cold email can lift replies or kill the deal. Here is the decision framework, the wording rules, and the legal line." date: "2026-08-14" tags: "cold email copy, competitive positioning, outbound strategy" readTime: "14 min read" slug: "naming-competitors-in-cold-email" canonical: "https://firstsales.io/blog/naming-competitors-in-cold-email/" --- # Naming competitors in cold email: when it works, when it backfires **TL;DR:** Naming a competitor works when the prospect is already using that tool, already frustrated with it, and your email gives them a specific, verifiable reason to look elsewhere. It backfires when you name a rival the prospect has no relationship with, when the comparison reads as an attack, or when you cannot back the claim with a fact. Use the switch trigger, not the brand name, as the actual reason to write the email. --- ## Table of contents - [The instinct to name names](#the-instinct-to-name-names) - [When naming a competitor actually helps](#when-naming-a-competitor-actually-helps) - [When it kills the reply](#when-it-kills-the-reply) - [The decision framework](#the-decision-framework) - [Named vs unnamed vs category framing](#named-vs-unnamed-vs-category-framing) - [How to phrase it without sounding like an attack](#how-to-phrase-it-without-sounding-like-an-attack) - [The legal and factual line](#the-legal-and-factual-line) - [Competitor mentions inside a sequence, not just the opener](#competitor-mentions-inside-a-sequence-not-just-the-opener) - [Where AI drafting helps and where it does not](#where-ai-drafting-helps-and-where-it-does-not) - [What to check before you send](#what-to-check-before-you-send) - [FAQ](#faq) - [Conclusion](#conclusion) ## The instinct to name names Every sales team eventually writes the email that names a rival by brand. It feels efficient. The prospect already knows the other product, so you skip the education step and go straight to the pitch. Sometimes that works. More often it reads as a swipe, and the prospect files the email under "vendor trash-talking me" instead of "someone who understands my problem." The difference between those two outcomes is not the boldness of the writer. It is whether the email is actually about the prospect's situation, with the competitor as a supporting fact, or whether the competitor's name is doing the work that a real insight should be doing. Reply rates on cold email overall have been sliding, from about 5.1% in 2024 to roughly 3.43% in 2026 across the platform. Generic sends without a real trigger now land in the 1 to 3% range. A named competitor is not a trigger by itself. It only becomes one when it is tied to something the prospect is actually experiencing right now. ## When naming a competitor actually helps Naming a rival helps in a narrow set of situations, and they share a common thread: the prospect's relationship with that competitor is already a live, current fact, not something you are guessing at. **The prospect is a public, verifiable user of the competitor.** Case studies, a logo on the competitor's website, a G2 review under the prospect's name, or a job posting that lists the tool by name. If you cannot point to where you learned this, do not write the email as if you know it. **The competitor has a known, dated failure.** A public outage, a pricing change that a segment of customers is visibly complaining about, a feature deprecation, an acquisition that changes the product roadmap. These are facts, not opinions, and they give the prospect a real reason the email exists right now instead of any other week. **You are running a structured switch campaign.** Teams that build [competitor switch campaigns](/blog/competitor-switch-campaigns) around a specific, dated event, a price hike, an outage, a policy change, get a much higher hit rate than teams sending "hey, tired of [Competitor]?" cold with no trigger at all. The trigger is the reason to write, the competitor name is just the label on the trigger. **The prospect brought it up first.** If a prospect's public post, review, or forum comment already names the competitor and complains about a specific thing, quoting that complaint back to them respectfully is not an attack. It is proof you read what they wrote. ## When it kills the reply The failure mode is almost always the same: the sender assumes a relationship with the competitor that does not exist, or uses the name as a rhetorical weapon instead of a shared fact. **No confirmed relationship.** If you are guessing the prospect uses a specific competitor based on company size or industry alone, you will be wrong often enough that the email reads as spam, not personalization. **Negative framing with no specifics.** "Everyone knows [Competitor] has terrible support" is an opinion, not a fact, and it puts the prospect in the position of defending a purchase decision they made. People do not like defending decisions to strangers, so they stop reading. **Naming a competitor the prospect has never used.** This is the most common self-inflicted wound. The prospect uses neither tool, has no context for the comparison, and now reads your email as a stranger trashing a company they have no opinion about. **Making a claim you cannot support.** If the competitor could point to your email and dispute the claim in public, do not send it. This is not just a tone problem, it is a real legal exposure covered later in this piece. **Doing it in the subject line.** Competitor names in subject lines get flagged by spam filters more often and read as combative before the prospect has any context. Save the name for the body, after you have earned a sentence or two of goodwill. ## The decision framework Before naming any competitor, run the situation through a short filter. ```mermaid flowchart TD A[Considering naming a competitor] --> B{Confirmed the prospect uses or evaluated it?} B -->|No| C[Do not name it. Use category language instead] B -->|Yes| D{Is there a dated, verifiable trigger?} D -->|No| E[Wait for a real trigger or skip the mention] D -->|Yes| F{Can every claim survive the competitor reading it?} F -->|No| G[Rewrite until every claim is a fact, not an opinion] F -->|Yes| H[Name it once, tie it to the trigger, move to the ask] ``` If the answer at any gate is no, the safer move is to drop the brand name and write about the underlying problem instead. The problem is what earns the reply. The brand name is just a shortcut, and shortcuts fail the moment they are wrong. ## Named vs unnamed vs category framing Three ways to write the same email, and how each one tends to land. | Approach | ✓ Works when | ✗ Fails when | |---|---|---| | Named competitor, specific trigger | Prospect is a confirmed user, trigger is dated and factual | Trigger is vague or unverified | | Named competitor, general complaint | Almost never on a cold first touch | No confirmed relationship, no specific proof | | Category language, no brand name | Prospect's tool is unknown, or the point is about a category-wide gap | You actually do know the tool and are hiding behind vagueness | | Prospect named it first | You are quoting their own public words back respectfully | You misquote or exaggerate what they actually said | | Feature comparison chart, no cold-email framing | Landing pages, comparison content, mid-funnel nurture | First cold touch, no relationship established yet | The category-language row deserves a second look. Writing "the tool you're on today" instead of a brand name is not weaker, it is often stronger, because it works whether or not your guess about the specific vendor is correct. ## How to phrase it without sounding like an attack The wording matters as much as the decision to name the competitor at all. Three patterns hold up better than the rest. **State the fact, let the prospect draw the conclusion.** "[Competitor] shut down its free tier last month" is a fact. "So you're probably stuck paying full price for something you don't need" is an assumption, and it sounds like you are speaking for them. Cut the second sentence and let the first one do the work. **Reference the trigger, not the company's character.** "The pricing change affects teams your size" targets the event. "They've always overcharged smaller teams" targets the company's motives, which you cannot actually know and which reads as bitter. **Keep it to one mention.** One clean reference to the competitor, tied to the trigger, followed immediately by your actual point. Repeating the brand name three times in one email turns a factual reference into a rant, and rants do not get replies. This is closely related to writing with a real stance instead of a generic pitch, which our piece on [point of view cold email](/blog/point-of-view-cold-email) covers in more depth. Taking a position is good. Taking a swing at a named competitor's character is a different thing entirely, and prospects can tell the two apart instantly. ## The legal and factual line This is the part teams skip until legal gets involved. Do not make disparaging factual claims about a real competitor that you cannot substantiate with a public, dated source. That includes claims about security incidents, financial trouble, customer counts, or quality, unless you can point to where the claim came from and it is still accurate at send time. Comparative advertising law varies by jurisdiction, but the common thread across most of them is the same: factual claims must be true, verifiable, and not misleading by omission. An opinion framed as a fact ("everyone knows their support is bad") is exactly the kind of statement that creates exposure, because it implies a factual basis you do not have. If a claim would embarrass you in a deposition, it does not belong in a cold email. This sits next to the broader compliance picture covered in [cold email compliance penalties](/blog/cold-email-compliance-penalties) and the current legal landscape in [is cold email legal in 2026](/blog/is-cold-email-legal-2026). Naming a competitor does not change your consent or CAN-SPAM obligations, but it does add a second layer of risk on top of them. ## Competitor mentions inside a sequence, not just the opener Most of the guidance above focuses on the first email, but competitor context can also earn a place later in a sequence, where the risk profile changes. By the third or fourth touch, if the prospect has opened every email but never replied, referencing a [buying signal](/blog/buying-signals-for-cold-email) tied to their current stack, a renewal date, a contract term ending, a tool sunset, is lower risk than doing it cold on touch one. The prospect has already seen your name a few times by then, so the mention reads as informed timing rather than a stranger guessing. This only works if the trigger is still real at send time. A renewal date from six months ago is stale information, not a signal, and using it anyway is the kind of guesswork that erodes trust the way generic [custom pain points](/blog/custom-pain-points) do when they are copied across every send instead of built from something true about the account. ## Where AI drafting helps and where it does not ![A branching decision path for whether to name a competitor in a cold email](/images/blog/naming-competitors-in-cold-email/inline-1.webp) AI can draft the competitor-aware version of an email quickly once you feed it the trigger and the confirmed relationship. What it cannot do reliably on its own is verify that the trigger is still accurate, that the prospect really uses the tool you are naming, or that a specific sentence crosses from fact into unsupported opinion. That verification step is exactly where a human needs to sit between the draft and the send button. FirstSales builds its drafting flow around that checkpoint: the AI proposes the email using research it has gathered on the account, and a person approves or edits it before anything goes out, rather than letting a model send competitor-related claims unsupervised. That review step matters more here than almost anywhere else in cold email copy, because a wrong guess about a rival costs more than a wrong guess about a job title. ![FirstSales draft approval screen showing an AI-drafted email awaiting human review before sending](/images/blog/shared/app-ai-draft-approval.webp) The same discipline applies to any AI-assisted outbound stack, not just this one. If your tool lets AI send competitor-naming emails without a human checking the underlying claim, you are one wrong guess away from an email you cannot take back. ## What to check before you send Run this list on any draft that names a competitor before it leaves the queue. - Confirm the prospect's relationship with the named competitor from a real, current source. - Confirm the trigger event is dated and still accurate today, not from months ago. - Read every sentence and ask whether it states a fact or implies an opinion. - Cut any sentence that speaks for the prospect's feelings about the competitor. - Limit the brand name to one mention in the body, never the subject line. - Check that the ask in the email stands on its own even if the competitor reference were deleted. That last check is the most useful filter. If the email falls apart without the competitor's name in it, the name is propping up a weak offer, and a stronger [offer](/blog/cold-email-offer-clarity) beats a sharper jab every time. ## FAQ ### Is it legal to name a competitor in a cold email? Generally yes, as long as every claim you make about the competitor is factual, verifiable, and not misleading. Opinions framed as facts, or claims you cannot support with a public source, are where the legal risk starts. ### Does naming a competitor increase reply rates? It can, but only when the prospect has a confirmed relationship with that competitor and there is a real, dated trigger behind the mention. Without both of those, naming a rival tends to read as a guess and lowers trust rather than raising it. ### Should I ever name a competitor in the subject line? Avoid it. Subject lines with a competitor's brand name are more likely to trip spam filters and set a combative tone before the prospect has any context for the comparison. ### What counts as a safe trigger for a competitor mention? A dated, public, verifiable event: a price change, an outage, a feature deprecation, an acquisition, or a policy shift the prospect could confirm independently. ### What if I am not sure the prospect actually uses the competitor? Do not guess. Use category language instead, "the tool you're on today" or "your current process," which works whether or not your assumption about the specific vendor is correct. ### Can I quote a prospect's own complaint about a competitor back to them? Yes, if you quote it accurately and respectfully, and it is clearly their own public words, not your interpretation of what they probably think. ### How is this different from a comparison landing page? A landing page is opt-in content the prospect chooses to read when comparing vendors. A cold email is unsolicited, so the bar for restraint and accuracy is higher because the prospect did not ask for the comparison. ### Does this apply to LinkedIn messages the same way it applies to email? Yes. The same rules on verifiable relationships, factual claims, and single mentions apply to any outbound channel, since the legal and trust risks are not email specific. ### What is the single biggest mistake teams make with competitor mentions? Naming a competitor the prospect has never used, based on an assumption from company size or industry rather than a confirmed fact. ### Should competitor mentions go in the first email or later in the sequence? Later touches carry less risk, since the prospect has already seen your name and the mention reads as informed timing rather than a cold guess. ### Can AI safely write competitor-naming emails on its own? AI can draft the email, but it should not verify the underlying claim or send it unsupervised. A human needs to confirm the trigger is real and current before the email goes out. ### What happens if a competitor disputes a claim I made about them? If the claim was factual and sourced, you can defend it. If it was an opinion framed as fact, you likely cannot, which is why the sourcing check matters before send, not after a complaint. ### Is it better to name the competitor or describe the pain point they cause? Describing the pain point is safer and often just as effective, since it does not depend on your guess about which vendor the prospect actually uses. ### Do enterprise buyers react differently to competitor mentions than SMB buyers? Enterprise buyers are more likely to already have a documented, procurement-visible relationship with a competitor, which makes a factual mention safer. SMB buyers are harder to verify, so category language is usually the better default there. ### Should sales reps get competitor claims approved before sending? Yes, particularly any claim about a named competitor's product quality, pricing, security, or financial standing. A short internal review step catches most of the risk before it reaches a prospect's inbox. ### Can I use a competitor's name in a follow-up if the first email got no reply? Only if a new, real trigger has appeared since the first email. Repeating the same competitor mention without new information reads as nagging, not persistence. ### Does mentioning a competitor work better for switch campaigns than cold outbound in general? Yes. Dedicated [competitor switch campaigns](/blog/competitor-switch-campaigns) built around one specific trigger event consistently outperform ad hoc competitor mentions dropped into a generic sequence. ### What is the risk of over-relying on competitor mentions across a whole campaign? If every email in a campaign leans on a competitor's name instead of a real insight about the account, replies drop once the novelty wears off and prospects start comparing notes. ### How do I know if my draft crossed the line from factual to disparaging? Read it as if the competitor's own marketing team will see it. If a sentence would require you to defend an opinion rather than point to a source, it has crossed the line. ## Conclusion Naming a competitor is a tool, not a strategy. It works when it rides on a confirmed relationship and a real, dated trigger, and it fails the moment it becomes a substitute for actually knowing something true about the account. The safest version of this tactic reads less like a jab and more like a fact the prospect already half knew, delivered at the right moment. If you are not confident enough in the relationship or the trigger to say it out loud in a room with the competitor present, it does not belong in the email either. Build the habit of running every draft through the fact check before the name goes in, and the tactic will earn replies instead of complaints.