A meaningful share of the companies who could buy from you already pay someone else for a version of the same job. Most outbound advice, and most outbound founders write, ignores this completely and pitches as though the recipient has never solved the problem before. That message gets deleted by someone who solved it eighteen months ago and has an opinion about it already. Reaching a buyer who already bought is a different discipline, with different timing, a different message, and a different objection sitting in the way.
The message cannot be "why software like this"
They already know why. They bought it. Explaining the category's value to someone already inside the category reads as either condescending or, worse, irrelevant, because it answers a question they resolved a long time ago. The only message worth sending names something specific: a pattern that tends to show up six or eight months into using a tool in this category, described concretely enough that someone living through it right now recognizes their own week in it. That has to come from real conversations with people who actually switched, or from what your own customers told you when they described leaving something else. It cannot be invented from a guess about what a competitor probably does poorly.
Never build the pitch on attacking what they chose
Naming a specific product by name in an honest comparison is fair. Trashing the choice a buyer already made is not just against the rules here, it does not work as persuasion either. A person who chose a tool has already justified that choice to themselves, out loud, probably to their own boss. An email that attacks the choice puts them in a position of defending it rather than reconsidering it, which is the opposite of what you want. Describe the specific situation instead, and let the reader recognize themselves in it. Recognition moves people. Being told they were wrong makes them dig in.
Timing does most of the actual work
A buyer's switching cost feels fixed right up until a specific moment when it stops feeling that way. A contract renewal window is the clearest one: nobody wants to evaluate an alternative mid-contract, but everyone is at least willing to look in the ninety days before a renewal decision. A public price increase from the incumbent is another. So is a champion leaving the company, since their replacement inherits a tool they did not choose and has no loyalty to. Build your target list around these moments specifically, rather than a flat firmographic list of everyone who might conceivably use something in the category, and the same message performs enormously better simply because it arrives when the door happens to be open.
The real objection is the move, not the merits
With a greenfield buyer, the conversation is about whether your product solves the problem. With a buyer who already has something working well enough to keep paying for, the conversation is almost entirely about the cost of switching: migrating data, retraining a team, the risk that something breaks during the transition. Lead with that directly instead of only pitching what your product does better. A buyer who is quietly convinced your product is superior will still say no if nobody has addressed how painful the actual move is going to be. Answering that question early, specifically, and honestly is usually what moves a skeptical reply into a real conversation.
Where to actually build this list
A displacement list is not built the same way a greenfield one is. Firmographics alone, company size, industry, headcount, tell you almost nothing about whether now is a good moment to reach someone who already bought. Look instead for the trigger itself: public news of a price change, a role change on a team that touches the tool in question, review sites where people describe what made them look elsewhere, or your own customers who switched and can tell you, specifically, what the breaking point was for them. That last source is the most underused one. Every customer who displaced an incumbent to reach you already lived through the exact decision you are trying to trigger in the next one, and their account of it is more reliable than any guess.
Why the reply-reading matters more here than anywhere else
Displacement replies read differently than greenfield ones. They are often defensive, sometimes a little annoyed, and frequently full of specific, technical objections about the switch rather than open curiosity about the category. Rocketship's worker can be pointed at exactly this kind of list, using a plain-English description that includes what category of tool the target company already runs, and it reads what comes back closely enough to answer the actual objection rather than repeating the pitch. A fair number of these prospects skip email entirely and call to ask a migration question directly, since a decision that big often gets a phone call instead of a reply, and having your line picked up at any hour, through the receptionist add-on available on top of a plan, catches that moment instead of losing it to voicemail.
What the pricing conversation actually needs to answer
A displaced buyer will do the arithmetic on cost whether you invite them to or not, so save them the trouble and do it with them directly: what they pay today, what they'd pay with you, and what the move itself costs in time and disruption on top of either number. Skipping this and hoping the product's merits alone carry the decision ignores the actual shape of the objection. It is rarely "is this better." It is "is this better by enough to justify doing anything about it right now," and that second question only gets answered with real numbers on the table, not a features list.
Slower, but it holds better once won
Displacement deals close less often and take longer than deals with someone who has no solution yet. They are also, once won, some of the most durable customers you will have, because you can point to the exact day they decided the disruption of switching was worth it, and a decision made that deliberately does not reverse easily. It is worth running as its own list, with its own timing and its own message, rather than folding it into the same generic outbound everyone else gets.