How to Win Deals When They Already Pay Someone Else [2026]
Status quo is your real competitor
In displacement deals, the logo on the contract beats your product until you make staying more painful than switching. Buyers lie politely: “We are evaluating options” often means “my boss will not sign another change this year.” Your job is to surface the cost of that lie — in dollars, hours, and missed quarters.
Ask directly: What breaks if you do nothing for twelve more months? If the answer is nothing, you are not in a displacement deal — you are in a hobby. Log it and move on.
Find the bleeding — not the feature gap
Incumbent weakness hides in operations, not RFP checklists:
- Renewal invoice shock — seat creep, marketing hub they never use, per-seat automation tax.
- RevOps as human API — exports, Zapier fixes, “why doesn’t Mail match CRM?”
- Adoption theater — licenses bought; reps live in Gmail and Notion.
- Parallel stacks — CRM plus Slack plus Zoom plus a BI export nobody trusts.
Document quotes from discovery on the opportunity in Momentum. When procurement pushes back, you are not selling — you are reading their own words back to them.
Displacement playbook (four moves)
- Quantify stay vs leave — line-item current spend (licenses, integrations, contractor hours). Compare to one Salestrics subscription and migration time. No fantasy 90% savings — credible 30–40% with fewer logins wins trust.
- Name the migration owner — if nobody internal owns cutover, you lose post-pilot. Require a named admin or ops lead before proposal.
- Phase the rip — CRM + Mail week one; docs week two; retire old tools on a calendar date. Big-bang cutovers scare champions.
- Give political cover — champion kit for the sponsor: risk of staying, risk of switching (honest), and why peers switched. See champion enablement.
Competitive talk that backfires
| Do not | Do instead |
|---|---|
| Mock the incumbent in the room | Ask what they wish worked differently today |
| 50-tab feature matrix | Three workflows side-by-side on their data |
| “We are cheaper” without scope | Total cost of ownership over 12 months |
| Assume IT wants change | Ask what security needs to see before pilot |
Compare positioning on HubSpot, Pipedrive, or Salesforce when buyers name names — then get back to their migration story.
Pilot design for displacement
Pilots fail when they run parallel forever. Set:
- One team, one motion — inbound, outbound, or CS; not all three.
- Exit criteria — e.g. 80% of team logs in daily, mail sent from platform, one closed deal logged end-to-end.
- Decision date — on the calendar before pilot starts. See pilot-to-paid conversion.
- Data import plan — what moves, what stays read-only, what dies.
Run the pilot on live records in Salestrics — not a sandbox with fake Acme Corp. Sandboxes let buyers nod and never commit.
When to walk
Walk when: no executive sponsor, renewal is 18 months out and they feel no pain, or they want you to replicate every custom Salesforce object before trial. Politely disqualify. Your quarter is shorter than their inertia.
Internal alignment before you pitch displacement
Your own team can sabotage displacement deals. CS promises features you have not shipped. Founders offer discounts that signal desperation. RevOps quotes migration as “two weeks” when data cleanup is two months. Align internally on:
- Minimum viable migration — what must move day one vs later.
- Support capacity — white-glove onboarding for displacement, not self-serve docs only.
- Reference customers — one similar switch beats ten logos in unrelated industries.
Log the displacement plan on the opportunity in Workspace. When the champion asks “how did [peer company] switch?” you send one doc — not a scramble across Notion and Gmail.
Displacement is a discipline — fewer deals, higher intent, migration plans that scare you a little. That is how you beat an incumbent without out-spending them.