The competitive displacement playbook

Displacement is the highest-conviction motion in B2B sales and the worst-executed. The conviction is easy to explain: a company already paying a competitor has a budget line, an internal owner, a renewal date, and — critically — has already been through the argument about whether this category is worth buying. You are not selling the category. You are selling the swap.

The execution failure is usually upstream of the sequence. Most displacement lists are assembled from review-site scrapes, conference attendee lists, and rep intuition, which means a meaningful share of the accounts on the list don't actually use the competitor. Reps discover this on call one, lose credibility, and stop trusting the list. Everything downstream is then theatre.

This playbook starts by fixing the list.

Phase 1 — build the list from evidence

The reverse lookup returns entities whose public web presence names a given vendor, ten per page:

curl "https://api.vendorstacks.com/v1/prospect?vendor=Twilio&category=sms_messaging&page=1" \
  -H "Authorization: Bearer $VENDORSTACKS_KEY"

Paginate through until you have as much of the list as you want. Pricing is 1 credit per result returned — and a page that returns no results costs nothing, so walking off the end of the list is free.

What makes this list different from a scraped one is that every row carries the source: a page on the company's own site where the competitor is named. Your rep is never guessing. If a prospect says "where did you get that?", the answer is a URL on their own domain.

A caveat to state plainly to your team: this list is companies with public evidence of using the vendor. It is not every company that uses the vendor. Absence from the list means nothing. Presence on it means something specific and verifiable, which is the property you actually need.

Phase 2 — enrich and segment

A competitor match is one bit of information. Sequencing off one bit produces generic email. Pull the full stack for each domain so you can segment:

curl "https://api.vendorstacks.com/v1/company/meridian-fleet.com" \
  -H "Authorization: Bearer $VENDORSTACKS_KEY"

Use /v1/company rather than /v1/check for this pass — it reads the index only, never triggers a scan, and returns instantly, which matters when you're doing 500 of them. Same 1 credit either way.

Then segment on stack shape, not firmographics:

• Tier A — competitor plus complementary stack. They run your competitor and the tools that make your product better. This is where the personalized sequence goes, quoting the source line. Typically 15–25% of the list.
• Tier B — competitor plus mature but neutral stack. Real company, real budget, no particular affinity signal. Standard sequence with a stack-aware first line.
• Tier C — competitor plus thin stack. Either small, or they don't publish much. Low-touch nurture; re-check next quarter.
• Tier D — competitor plus a platform you can't coexist with. Route these out before a rep spends forty minutes finding out on a call. Negative signals save more hours than positive ones.

Phase 3 — design the sequence around the evidence

The single most common mistake is putting the competitor mention in every email. Use it once, precisely, and then move on to the argument.

Touch 1 — the sourced observation. Name what you saw and where. One inference about what it implies, phrased as a question they can correct. No pitch. The outbound research post has the message structure in detail.

Touch 2 — the specific difference. Not "we're better". One concrete thing that is different about how you solve the problem they have given their stack. This is where the enrichment pays off: a company running your competitor alongside Snowflake and Segment has a different pain surface than one running it alone.

Touch 3 — the low-friction proof. A teardown, a benchmark, a migration guide. Something they can consume without talking to anyone.

Touch 4 — the timing question. Renewal cycles are the actual constraint. Asking directly when their contract comes up is less presumptuous than most reps assume, and the answer determines whether this account is a this-quarter conversation or a calendar entry for month nine.

Phase 4 — objection handling

Displacement provokes a predictable set of responses. Prepare them.

"How do you know what we use?" Answer honestly and immediately: their company publishes it, here's the URL. This is a moment that either builds credibility or destroys it, and the only way to build it is to have the source ready. Never imply you have inside information. You don't; you read a public page.

"We're happy with them." Usually true and usually irrelevant — happiness is measured against alternatives they haven't evaluated. Don't argue. Ask what would have to be true for them to look, and put a reminder in for the renewal window.

"Switching is too painful." The real objection most of the time. Answer it with migration specifics, not reassurance. If you don't have a migration story, you don't have a displacement motion.

"That page is out of date." Occasionally true, and it's a gift — they've just told you they changed vendors recently, which is the single most useful piece of information in the conversation. Ask what they moved to and why.

The credit math for 500 accounts

• Building the list: 500 reverse-lookup results at 1 credit each = 500 credits.
• Enriching for segmentation: 500 lookups at 1 credit = up to 500 credits, less in practice since misses cost nothing.
• Total: ~1,000 credits, about $9 at the $10/1,100 pack, or roughly $8.30 at the $50/6,000 rate.
• Quarterly refresh: the same ~1,000 credits. Diff the stacks and you find the accounts that dropped the competitor — or added a second one, which is a company mid-evaluation and the best-timed call you'll make that quarter.

Nine dollars to build a 500-account list where every row has a verifiable citation. The expensive part of displacement was never the data; it was the rep hours spent on accounts that turned out not to use the competitor at all.

See the pricing page for the packs and the API reference for the full response shape. Start with 25 free credits — enough to pull two pages of a competitor's user list and check whether the evidence holds up against accounts your team already knows.