What to do when a prospect says they already use a competitor

The second most common reply in outbound is a gift

"We already use a competitor" arrives constantly — and it gets the worst handling of any reply type, because it sounds final. So reps do one of two things: argue (a feature-by-feature defence of a decision the prospect already made) or file it as a loss (a polite "totally understand!" and a record marked dead). Both responses throw away the same thing.

Because look at what the reply actually tells you. They have the problem — badly enough to have paid for a solution. They have budget. They know the category, so you skip the entire education phase. And they've told you exactly who you're compared against, which means every future conversation can be specific instead of generic. A cold prospect is a stranger; a competitor's customer is a qualified lead with a contract end date.

The failure mode is invisible, as usual. Nothing breaks loudly. The rep sends a gracious reply, feels fine about it, and logs nothing. The renewal window opens the following spring — the one moment the account is genuinely in play — and nobody calls, because the fact that there was a window lived in an email thread nobody re-opened.

The by-hand routine (how teams do it today)

Teams that handle this well without tooling all do a version of the same five steps. It works — the cost is discipline at inbox speed:

1. Read for the four facts. The competitor's name, how long they've used it, the gripe they volunteered, and any timing — "locked in until spring", "up for renewal in Q2", "we review it at the end of the year". The gripe and the timing are the two that pay you back.

2. Reply with grace and one question. Thank them for the straight answer, ask "if you could change one thing about it, what would it be?", and stop. No comparison chart, no "we're different because". The answer to that question is your positioning when the window opens — people will tell you exactly how to win their account if you ask without pitching.

3. Log the competitor on the record. Create a "Competitor in place" property (Settings → Properties) and set it — on the contact, and on the company if you sell at that level. Put the gripe in a note or property in their words. This is the step everyone skips, and it's the step everything else depends on: a property is filterable, a memory is not.

4. Create the renewal-timed task. Open the contact record and create a task (contact record → create task) dated a few weeks before the window opens — before it, not on it, because switching decisions get made before renewal dates. If they gave no timing, assume an annual contract and note that it's assumed.

5. Keep them warm, lightly. A long-cycle nurture — one useful, no-ask touch every month or two — so the renewal call isn't from a stranger. Don't leave them in the sequence that provoked the reply; that's not nurture, it's noise.

Done properly that's ten minutes per reply. Its failure mode isn't refusal — it's that step 3 feels like admin on a busy day, so the intel stays in the thread, and spring arrives unnoticed.

Why arguing loses twice

The urge to defend is understandable — you know where you're stronger. But a competitor reply is not an invitation to a comparison; it's a status update. The prospect made a decision, possibly championed it internally, and a takedown of that decision lands as a critique of their judgement. You don't just lose the argument — you lose the right to have the next conversation.

The math is also against it. Today, switching costs them a migration, retraining, and admitting the original choice was wrong — an enormous price to pay for a marginally better tool. At renewal, the same switch costs almost nothing. Arguing fights the battle at the moment you're weakest; the graceful reply banks the relationship for the moment you're strongest.

There's one exception that isn't really an exception: when they answer your one question with a real complaint ("honestly, the reporting is a let-down"), you've been invited to be specific — next time, not this time. Acknowledge it, log it verbatim, and let it become the opening line of the renewal-window follow-up: "You mentioned the reporting was letting you down — here's what that looks like on our side."

What ReplyCircuit does with a competitor reply

ReplyCircuit reads the reply the moment it lands and classifies it as a competitor mention — which means it treats the message as intel to capture, not a loss to file. It extracts the competitor's name, the gripe in the prospect's own words, and any renewal or contract timing, and it gets the contact out of the active sequence so no further steps fire at someone who already answered.

It then prepares the HubSpot work: the competitor logged on the record and a follow-up task dated to land before the window opens. The review card shows the competitor, gripe, timing, record update, and task in one place. ReplyCircuit does not write or send the email response; that stays with your team.

The compounding effect is the real product. Every competitor reply your sequences generate becomes a structured, dated, filterable future opportunity. Six months in, you can pull a list of every Procore account with a renewal approaching — which is a pipeline your competitors don't know exists, built from replies they would have filed as losses.

What to expect afterwards

The first change is that renewal windows stop being surprises. The follow-up arrives a few weeks before the contract decision, opens with the prospect's own words about what's letting them down, and finds someone who is, for a short window, genuinely allowed to consider alternatives. That conversation converts at a rate cold outreach never touches.

The second change is market intelligence. When every competitor mention lands in a property, you can finally see who you're losing to, where, and why — which competitors come up, which gripes repeat, which segments you're competitive in. Most teams pay research firms for a worse version of this data while it sits unread in their own inbox.