Win the merchant who just uninstalled a competitor

There is no colder lead than a merchant who has never heard of you, and no warmer one than a merchant who just removed the app they used to solve the exact problem you solve. A competitor uninstall is the highest-intent signal in the Shopify ecosystem, because the decision has already been made: the old tool is out, and something has to replace it.

The catch is timing. That replacement window is measured in days, not weeks. Whoever reaches the merchant first, with a message that acknowledges the switch, usually wins the slot. This is the discipline Jeb Blount built Fanatical Prospecting around: the deals you close next quarter are made by the outreach you do today, and speed to a fresh signal is a compounding advantage. Here's how to run the play.

Why an uninstall beats every other signal

Most prospecting works off proxies for intent, like company size, funding, or a job title. An uninstall is not a proxy. It's the event itself. The merchant has already gone into their admin, made a decision, and pulled a tool out of their stack. Three things are now true at once:

• They have budget. They were already paying for a tool in your category, so the line item exists.
• They have a live problem. Something the old app did is now unhandled, and every day it stays unhandled costs them.
• They're in motion. A stack change is the moment stores re-evaluate everything nearby, so the door is open wider than just your category.

Compare that to a store that has run the same apps for two years. There's no opening, no urgency, no reason to reply. The uninstall manufactures all three.

The pipeline gap, and why most sellers miss this

Blount's core warning is the pipeline gap: reps who only prospect when they're desperate ride a feast-or-famine cycle, because pipeline built today doesn't pay off for weeks. Competitor uninstalls are the antidote, but only if you work them consistently. The reason most app sellers never touch this signal is that it's invisible by default. Shopify doesn't publish a feed of who uninstalled what. By the time you learn a former user churned, from a failed billing webhook or a support ticket, the replacement decision is usually already made. You end up learning about switches after they've closed, not while they're open. That's the whole reason App Moves exists: to surface install and uninstall events across the storefront base as they happen, so the switch is a lead you act on, not a fact you discover late.

The play, step by step

1. Watch the apps you compete with, not just your own. Track the specific competitors a merchant might leave. When one of their customers drops them, that's your alert, and it's worth more than a hundred cold names.

2. Qualify in ten seconds. Pull the merchant's profile: revenue band, vertical, current stack, and what else they run. A switch is only worth chasing if they fit your ICP, so filter before you write. Blount is blunt about this: activity without qualification is just noise.

3. Lead with the switch, never with your pitch. The opener that works names the transition, not your feature list. "Saw you moved off [competitor] this week, most teams do that because of X, here's how we handle it" beats any cold template, because you're opening a loop the merchant already has open in their own head. Blount's rule for a prospecting message: bridge from something relevant to them, ask for a small next step, and get out.

4. Reach a human, not an inbox. A generic support@ address gets you nowhere. Get to the person who owns the stack, the founder at a small store, the ops or retention lead at a bigger one, and reach them by email and LinkedIn, not one channel.

5. Move the same day. The value of this signal decays fast. A lead worked the day of the uninstall converts far better than the same lead worked two weeks later, when three other vendors have already emailed.

Handling the "we just switched, we're set" reply

You'll hear it: "We already picked a replacement." That's not a dead end, it's information. Blount teaches that most first objections are reflexes, not final answers. If they've chosen a tool but haven't fully rolled it out, there's a window. Acknowledge the choice, plant one specific reason teams like theirs come back to re-evaluate, and ask to be the backup they call if the new tool disappoints. A surprising number of "we're set" replies convert within 60 days, because switches made under time pressure often don't stick.

What "good" looks like

Run this consistently and your pipeline stops depending on volume. Instead of blasting a list and hoping, you work a smaller number of merchants who are provably in-market right now, each with a specific reason to talk to you. Reply rates go up because every message is relevant. Cycles shorten because the budget and the problem already exist. And you spend your hours on stores that are actually shopping, not on the 99% who aren't. The uninstall was always happening. The only question was whether you found out in time to do something about it.