How Do You Write an Outbound Email to a Competitor's Customer?

How do you write an outbound email to a company that already uses your competitor?

Do not ask them to switch. Acknowledge the tool they use, name one specific gap or situation where teams like theirs outgrow it, and offer something small and useful, such as a comparison or a short audit. The goal of the first email is a conversation about fit, not a migration decision.

Competitor customers are some of the best prospects you have. They already believe the problem is worth paying to solve, they have budget for it, and they understand the category. The hard part is that they have already chosen, and nobody likes being told their choice was wrong.

This article is for B2B teams running outbound to accounts that use a rival product. I will cover how I would find the right moment, what to say, what never to say, and how to follow up without becoming annoying.

Why are a competitor's customers worth targeting?

They have already proven the need and the budget. A company paying for a rival product has a problem your product solves, an internal owner for that problem, and a line in the budget. You skip the hardest part of selling, which is convincing someone the category matters. What remains is a question of fit and timing.

Compare that with a cold account that has never bought anything in your category. You must explain the problem, justify the spend, and find an owner. With a competitor customer, those pieces already exist. Your job is to show why your approach might fit better now.

The catch is switching cost. Moving tools takes time, data migration, retraining, and political capital. Your email has to respect that cost rather than pretend it does not exist.

When is the right moment to reach out?

The best moments are when switching costs drop or frustration rises. Common signals include an approaching renewal, a new leader in the team that owns the tool, rapid growth that strains the current setup, a public pricing change by the competitor, or job posts that mention problems your product solves. Timing matters more than wording here.

A new leader is often the strongest signal. New heads of a function frequently review the tools they inherited, and they have not personally invested in the current choice. A short, respectful note in their first few months can land well.

Growth is another. A tool that worked for a small team can strain at a larger size. If an account is hiring heavily in the function your product serves, that is worth a note. I explain how to time outreach around events like these in writing an outbound email for a trigger event.

What should the first email say?

Open by showing you know their situation, including the tool they use, without judging it. Name one specific scenario where teams like theirs hit limits with that kind of setup. Offer something low effort and useful. Keep it short, plain, and easy to answer with a yes or a polite not now.

A good structure is three short parts. First, context: a line showing you understand their team and their current approach. Second, the gap: one specific situation where your approach tends to fit better, framed as a pattern rather than an attack. Third, the offer: a small next step, like a two minute comparison video or a list of questions to evaluate their current setup.

Specific beats broad. Saying you are better than the competitor means nothing. Saying that teams who add a second region often find routing rules hard to maintain in their current tool, and that your product handles that differently, gives the reader something to check against their own experience.

What should you never say about a competitor?

Never insult the competitor, never make claims about their product you cannot back with their own public documentation, and never imply the buyer made a bad decision. Negative claims make you look insecure, can be factually wrong, and put the buyer on the defensive. Let the buyer draw the comparison from facts and their own experience.

Accuracy matters for more than manners. Competitors change their products. A limitation you heard about last year may be fixed. If you state it as fact and you are wrong, you lose credibility instantly with someone who uses the tool every day. Check claims against the competitor's current docs or leave them out.

Your sales team needs a shared, accurate view of the competition so emails and calls stay consistent. My guide on writing a competitor battlecard in a Google Doc shows a simple way to keep that view current.

What offer works best for a competitor's customer?

The best offers help them evaluate their current setup, whether or not they switch. A short checklist for reviewing their tool, a side by side of approaches, or a brief audit of one workflow all work. These offers give value even if the answer is no, which makes a reply feel low risk.

Avoid leading with a demo request. A demo asks for thirty minutes and implies they are shopping. Most competitor customers are not shopping yet. A lighter offer meets them where they are.

Migration help is a strong second step, not a first one. Once someone is curious, explaining how you would move their data and how long it takes removes the biggest fear. In the first email, it can feel presumptuous.

How should you handle the reply that says they are happy with their tool?

Accept it, thank them, and ask one light question about what would make them revisit the decision, such as a renewal date or a future need. Then note the answer in your CRM and set a reminder. A respectful exit keeps the door open, and many of these accounts become ready later.

Do not argue. If they are happy, pushing harder confirms their choice and makes you the vendor they avoid. Instead, plant a small marker. Asking when their renewal comes up, or what would need to change for them to look again, gives you a future reason to reach out.

This reply is so common that it deserves its own playbook. I go deeper in handling the already use a competitor objection.

How many follow ups should you send?

Send a small number of follow ups spaced out over a few weeks, each adding something new, such as a relevant example or a short resource. Stop when the sequence ends or they ask you to. With competitor customers, patience beats volume, because the right moment may be months away at their next renewal.

Each follow up should stand on its own. A message that only says checking in gives them nothing to respond to. A message that shares how a similar team handled a specific problem gives them a reason to read.

When the sequence ends without a reply, move the account to a longer cycle tied to signals. A renewal date or a leadership change is a far better trigger for the next email than an arbitrary date on your calendar.

What should you do next?

Build a list of accounts using your main competitor, add the signals that make switching likely, and write one three part email: context, specific gap, small offer. Check every claim about the competitor against their current public docs. Then send to a small batch, read the replies, and refine before scaling.

Competitor customers reward respect. They know their tool better than you do, and they will notice any exaggeration. Specific, accurate, low pressure outreach is what earns the second conversation.

If you want help building an outbound system that finds competitor customers and reaches them at the right moment, reach out. I build outbound and enrichment systems in Clay, Apollo, and HubSpot for B2B teams. Let's chat.