Competitive Displacement Strategy: Find the Change First

Most competitive displacement campaigns start the same way. Someone pulls a technographic export of every company running the competitor, the list lands in a sequencer, and the reps get a talk track about why our product is better. Six weeks later the reply rate is flat, the few meetings that happened went nowhere, and the team concludes that the incumbent is too entrenched to move.

The incumbent was entrenched. That part is true. But the campaign did not fail because the product comparison was weak. It failed because it treated every account running the competitor as equally ready to switch, when almost none of them were. A company that signed a three year contract last spring, rolled the tool out to every team, and has the same leader who championed it is not a displacement target. It is a name on a list.

The list told you who runs the competitor. It did not tell you which of those accounts has a reason to leave this quarter. That reason is what a displacement strategy is actually for, and it is the part most playbooks skip.

Why displacement is a timing problem, not a pitch problem

An incumbent vendor has one structural advantage over you: doing nothing is free. Nobody gets fired for renewing. The buyer already did the work of choosing, integrating and training, and every one of those costs comes back if they switch. Your pitch has to beat not only the competitor's product but the buyer's preference for the decision they already made.

Research on lost deals makes the size of that preference plain. Matt Dixon and Ted McKenna analysed roughly 2.5 million recorded sales conversations for their work on buyer indecision, and Dixon summarised the finding in an interview with CustomerThink: "anywhere between 40 and 60% of all deals are actually lost to the customer doing nothing." In a displacement deal, doing nothing has a name. It is the incumbent.

So the question is not "how do we make a better argument than the competitor?" Every vendor in the category has a better argument on paper. The question is "at which accounts has something changed that makes staying put cost more than leaving?" Before that change, your best pitch lands on a buyer who has no reason to act. After it, a decent pitch lands on a buyer who is already looking.

There is evidence that the window does open, often. Gartner surveyed 1,503 technology buyers from February to March 2023 and found that 60% of buyers involved in renew or expand decisions regret nearly every purchase they make. Regret is not the same as intent to switch. But it means that inside most of the accounts on your technographic list, someone has a complaint. The work is finding which accounts have a complaint plus a moment to act on it.

The changes that open a displacement window

A displacement window opens when an event raises the cost of staying or lowers the cost of leaving. In practice, a short list of events does most of the work. Each one is observable from outside the account if you know where to look.

Change	Why it opens the window	Where you see it
A contract cycle coming up	The renewal forces a decision the buyer has avoided all year. Switching cost is lowest just before it.	Original purchase date in public announcements, procurement notices for public sector buyers, a rep you lost to telling you when they signed
A new leader over the function	New leaders inherit the stack and owe it nothing. They were not in the room when the incumbent was chosen.	Leadership announcements, LinkedIn job changes, press releases
A job post that names the problem	A posting asking for someone to "migrate", "consolidate" or "evaluate replacements" is the company saying out loud that the current setup is under review.	The company's careers page and job boards
Public frustration with the incumbent	A review, forum thread or community post from a user at the account shows the pain is real and named.	Review sites, user communities, social posts from the team
A structural change the incumbent does not fit	An acquisition, a new region, a new product line or a jump in headcount can outgrow the tool that fit last year.	Press releases, funding news, expansion announcements
A change at the incumbent	A price increase, a product sunset, an acquisition of the vendor or a support cut gives every one of their customers a reason to look at once.	The competitor's own announcements and changelog

Two things about this table matter more than the rows. First, most of these events are about the account, not the competitor. The technographic list only knows which vendor is installed. The reason to call lives in what happened at the buyer. Second, the last row is the only one that applies to every account on your list at once, which is why competitor price increases produce the rare displacement campaigns that do work at volume. Everything else has to be found one account at a time.

If you want a fuller catalogue of events beyond the competitive case, the guide to trigger events in sales walks through how to tie each one to a specific product line.

The reason test for displacement targets

Here is the method, and you can run it by hand on your own list this afternoon. A displacement target is worth a call when you can answer three questions about it in one sentence each:

1. What changed? Not "they use the competitor." Something at the account moved: a new VP, a job post, a renewal coming up, a public complaint.
2. Where did you see it? A link you can open. A job post, a press release, a review, an announcement. If you cannot point at it, you are guessing.
3. When did it happen? A date. A new leader from eighteen months ago has already decided whether to keep the stack. One from six weeks ago is still deciding.

No reason, no call. The account stays on the list, and you check it again next month. That rule feels wasteful the first time you apply it, because it shrinks a list of four hundred competitor accounts down to maybe a few dozen. But the four hundred were never all live. You were going to spend the same hours either way. The test decides whether those hours go to accounts where something happened or to accounts where nothing did.

Run it on ten accounts first. Take the first ten names off your competitor list, give yourself ten minutes per account, and write down the three answers or "nothing found." If two or three of the ten have a real reason, those two or three are your campaign. The rest are next month's list.

Write the switching argument from the change

Once you have the change, the argument to switch writes itself in a different way. You stop saying "we are better than the incumbent" and start saying "this thing changed, and here is what it means for the tool you have."

• New leader: "You inherited a setup built for a team half this size. Here is what teams at your current size usually hit in the first year." The argument is about the leader's new mandate, not the old vendor's flaws.
• Job post naming a migration: "Your posting for a systems lead mentions consolidating tools. If the evaluation is open, here is what moving from your current platform looks like and how long it takes." You are answering a question they already asked in public.
• Renewal coming up: "Before the renewal is signed, it is worth pricing out what the next three years cost on each side, including migration." You give them something useful to bring to the renewal conversation even if they stay.
• Public complaint: "One of your team wrote about the reporting gap in the current tool. That gap is the first thing we built around." Quote the gap, not the person, and never lead with "I saw you complained."

Each of these is honest about switching cost. Displacement messaging that pretends migration is painless loses the buyer's trust the moment their own team estimates the work. Say how long it takes. Say what breaks. The buyer already knows it costs something, and the vendor who admits it reads as the one telling the truth.

Who to talk to inside a displacement account

An incumbent usually has a champion: the person who chose it, defended it in budget meetings and trained the team on it. Going to that person first asks them to admit their decision was wrong. Most of the time, they will not.

The change you found tells you who to talk to instead. A new leader is the obvious one, because they owe the old decision nothing. A hiring manager on a migration posting is another, because their job description says the evaluation exists. The daily users who wrote the public complaint are a third, though they rarely sign the contract. The people who live with the tool's gaps and the people who approve its budget are usually not the same people, and a displacement deal needs both.

This is where account mapping earns its keep: you need to know who chose the incumbent, who inherited it and who feels its limits before you decide where to start. A good sales battlecard handles the comparison once you are in the conversation. It does not tell you which conversation to start.

Where displacement campaigns usually break

Most failed displacement campaigns fail in one of four places, and every one of them traces back to treating the list as the strategy.

• Same message to every account running the competitor. The technographic list is a starting set, not a target list. A message that only says "we beat your vendor" gives the buyer no reason to act now, so they do not.
• Calling the champion first. You are asking the person who made the decision to undo it. Start with the person the change affected.
• Attacking the incumbent. Criticising a tool the buyer chose criticises the buyer. Talk about what changed for them, not what is wrong with the vendor.
• Giving up after one quarter. An account with no reason this quarter may have one next quarter. Displacement is a standing watch on the list, not a campaign with an end date. The accounts you parked go back through the reason test every month.

The last point is the expensive one. Running the reason test once by hand is an afternoon. Running it every month across hundreds of competitor accounts is a job nobody on the team has time for, which is why most teams quietly go back to sending the same message to the whole list.

Running the reason test across the whole list

The method above does not need software. It needs someone to open each account, look for what changed, write down where they saw it and when, and decide. That labour is the bottleneck, and it is exactly the part PitchSmart does. You tell it what you sell and which changes matter for a displacement (a new leader over the function, a job post naming a migration, a public complaint about the incumbent), and it researches every lead on your list against those questions. Each lead comes back with who to contact, what to pitch, why now, and what to say, with a source link on every claim, so you can check the reason before you act on it.

The accounts with no reason come back saying so. That matters as much as the ones with a reason, because it is the difference between a list of four hundred names and a short list of accounts you can call this week. If you are already using competitive intelligence tools to track what the competitor is doing, this is the other half: tracking what changed at each of their customers.

Whether you do it by hand or not, the rule is the same. Your competitor list is not the problem. The missing reason is. Find what changed, where you saw it and when, and call the accounts where you can answer all three.