Outbound Plays

The competitor displacement play

The repeatable motion to win competitor customers, run only when they have a real reason to switch.

Using a competitor is not a buying signal. A reason to leave one is.

By Rahul · Updated June 2026 · 8 min read

Book a Fit Check

Play Snapshot

Signal-driven

Outcome

Switched logos won from an incumbent vendor

When to run it

A competitor account hits a real switch trigger

Signals it uses

Competitor usage, tool sunset, tech-stack fit

Channel mix

Email + LinkedIn, gap-led, with a migration offer

Trigger, not title Timed to the window

Competitor displacement outbound is the play for winning accounts that already run a competitor, but only the ones with a real reason to switch. The fact that they use someone else is not the opening. A renewal, a price hike, a tool being sunset, or a capability they keep missing is, and the play rides that trigger, not the logo.

When to run it

Run it only on a real switch trigger

A happy customer with no reason to move will not move. So this play starts with the trigger, not the target list. Here are the four that open a window worth working.

1

A renewal in view

The incumbent contract is coming up. This is the strongest trigger, because the buyer is already weighing whether to re-sign or look around.

2

A price or plan change

The competitor raised prices, killed a tier, or moved a feature behind a higher plan. A fresh cost makes the switching math worth a second look.

3

A sunset or a gap

The tool is being shut down or end-of-lifed, or it is missing a capability the account keeps hitting. A forced decision, or a felt pain, is a real opening.

4

A new leader with a mandate

A new exec arrives to rebuild the stack. New leaders re-evaluate inherited tools fast, so the inherited vendor is suddenly up for debate.

Gartner found that 99% of B2B purchases happen in the context of an organizational change. That is exactly what these triggers are. Without one, you are asking a satisfied buyer to take on risk and work for no reason, and they will not.

The signals it uses

This is a signal-driven play, and it reads three signals together. One tells you who runs a competitor, the others tell you whether a switch window is actually open.

Primary

Competitor usage

Who already runs a competitor, and how to read whether that usage is happy and locked in or quietly looking for the exit.

Read the competitor usage signal

The trigger

Tool sunset and migration

A vendor shutting down or being dropped forces a replacement decision on a clock. The strongest displacement trigger there is.

Read the tool sunset signal

Qualifier

Tech-stack fit

What else is in the stack tells you how deep the integration moat runs and whether you can actually slot in cleanly.

Read the tech-stack signal

The read

Read in isolation, competitor usage is weak: it tells you they bought a category, not that they want to leave it. Stacked with a sunset, a price change, or a renewal date, it becomes a window. To find the accounts and the trigger dates, you need clean technographic and signal data, which is what the signal and intent tools guide and the B2B data tools guide walk through.

Sitting on a list of accounts that run your competitor?

Book a Fit Check

The sequence

How we run it, touch by touch

Five touches over two to three weeks, built around the gap and the migration, never around the competitor's flaws. Each touch earns the next.

Step	Channel	Timing	Goal
1 Name the gap	Email	Days 1 to 2	Open on the specific pain the trigger created. No mention of the competitor by name, no pitch.
2 Show the proof	LinkedIn	Days 3 to 5	Connect, and share one concrete way you close that exact gap. Evidence, not claims.
3 Lower the switch cost	Email	Days 6 to 9	Name the switching cost out loud and shrink it. Offer a migration plan and a small parallel pilot.
4 Make the case	Email	Days 10 to 14	A short cost-of-staying versus cost-of-switching note they can forward internally. One clear ask.
5 The break	Email or LinkedIn	Days 16 to 21	One last light touch, then stop. Re-enter at the renewal date with a fresh reason.

The one rule

Never trash the incumbent. The buyer chose it, so attacking it attacks their judgment and makes them defend the status quo. Lead with the gap they already feel and the cost of staying, and let the comparison make itself.

Where it wins, and when it fails

A play is only useful if you know when not to run it. Here is the honest read on both.

Where it wins

✓The buyer already gets the category, so you skip the education
✓The pain is concrete and known, which sharpens the opener
✓Renewal dates give you a real clock to time outreach to
✓A switched customer tends to stick, having chosen you on purpose

When it fails

!The customer is happy and locked in with no trigger
!The integration moat is deep and migration is too costly
!You are not actually better for their specific use case
!You lead by badmouthing, and the buyer digs in

Common mistakes

What kills the play

Four ways teams turn a viable switch into a closed door. Each one is avoidable, and each one is common.

✕

Trashing the competitor

Attacking the incumbent attacks the buyer's past choice, so they defend it. Name the gap they feel, not the rival's faults.

✕

"You use X, try us"

Usage alone is not a reason to switch. Without a trigger and a gap, this is just cold outreach wearing a competitor's name.

✕

Ignoring the switching cost

The buyer is already doing the migration math in their head. Skip it and you lose. Name it, then shrink it with a real plan.

✕

Bad timing, no window

A switch pitch one month before renewal has no time to land. Reach in 120 to 180 days early, or wait for the next window.

Want this play set up and run for you?

Book a Fit Check

How we would run it

The play in motion

An illustrative walkthrough of the method, not a specific client result. We report real numbers only when they are real.

1

The trigger

A sunset surfaces

A competitor announces it is end-of-lifing a product line. We pull the accounts running it, which now face a forced decision.
2

The read

Find the real gap

We read public reviews and threads for the exact frustration the sunset leaves behind, then match it to where we are genuinely stronger.
3

The touches

Gap, proof, migration

We open on the gap, show one concrete way we close it, then lead with a migration plan that makes the move feel small.
4

The meeting

A pilot, not a pitch

A call framed as scoping a small parallel pilot before the deadline, so the buyer validates with control rather than ripping and replacing.

Plays like this fed pipeline we've built inside these companies

Palm.ai

Alcméon

Mindflow

CEF.AI

Boolee

CoachHub

Inrō

Buster.AI

Palm.ai

Alcméon

Mindflow

CEF.AI

Boolee

CoachHub

Inrō

Buster.AI

FAQ

Questions founders ask

What is competitor displacement outbound?

Competitor displacement outbound is targeting accounts that already run a competitor and reaching them with a real reason to switch, not a generic pitch. The reason is a trigger: a renewal coming up, a price hike, a tool being sunset, a missing capability they keep hitting, or a new leader rebuilding the stack. Without a trigger, a happy customer has no reason to move, and the play does not work.

How do you win competitor customers without trashing the competitor?

You name the gap they already feel, not the competitor's flaws. Mine real one-star to three-star reviews and support threads for the specific frustration that matches your strength, then lead with that pain and how you close it. Badmouthing the incumbent makes the buyer defensive, because it implies they made a bad choice. Respect the past decision, focus on what changed, and let the gap speak for itself.

When is the best time to run a displacement campaign?

Time it to the trigger, and the strongest one is the renewal window. Most teams need 120 to 180 days before a renewal to evaluate, migrate, and decide, so a switch conversation one month out has no real chance of landing. Other strong moments are a competitor price change, a tool sunset or end-of-life notice, a public outage, and a new executive arriving with a mandate to rebuild the stack.

Why does competitor displacement fail?

It fails when the customer is happy and locked in with no trigger, when the switching cost or integration depth is too high to justify the move, when you are not actually better for their use case, or when you lead by trashing the incumbent. In each case the reason to switch is missing or the cost of switching swamps it, so the account stays put. Displacement needs a real opening, not just the fact that they use someone else.

How do you handle switching costs in a displacement play?

You name the switching cost out loud and shrink it, because the buyer is already thinking about it. Bring a concrete migration plan: timeline, who moves the data, what training looks like, and a way to run a small slice in parallel before committing. Framing it as validate-with-control rather than rip-and-replace lowers the perceived risk, which is usually the real blocker, not the price.

How is the displacement play different from the signal that feeds it?

The competitor usage signal tells you who runs a competitor and how to read whether a switch window is open. This play is the repeatable motion you run once a real trigger fires: who to target, the sequence, the angle, and the migration offer that closes it. The signal is the read, the play is the move. Knowing they use a competitor is not enough on its own, you need the trigger and the sequence around it.

Keep going