Bigmind

Move deals forward

Win the case for change

Understand the incumbent, find the opening, and make switching feel worthwhile.

Understand the cost of staying and switching

Replacing an incumbent requires more than demonstrating a better feature. Learn what works in the current arrangement, what does not, and what a transition would require. Existing integrations, user habits, training, procurement, and internal ownership can all influence the decision. Acknowledge those constraints openly. Dismissing the current supplier can make it harder for the buyer to discuss the tradeoffs honestly.

Create a fair comparison

Agree on a small number of criteria tied to the customer’s desired outcome. Include the option of keeping the current approach. For each criterion, identify evidence that can be collected during an evaluation rather than relying on a vendor claim. If your product has a limitation, document it and discuss whether it matters to the use case. A credible comparison helps the customer make a defensible decision, including when the right answer is not to switch.

Plan the transition before the signature

If the customer sees enough value to proceed, identify the first practical migration step, the people responsible, and the conditions for a safe rollout. Consider data, training, support, and parallel operation where relevant. Avoid assuming that enthusiasm from one stakeholder means the organization is ready to change. Use the playbook to surface those dependencies early and keep the business case connected to the real effort required. Review the comparison when new information appears rather than defending an outdated argument.

Overview

Displacing an incumbent is harder than winning a greenfield deal. The prospect already has a working (if imperfect) solution, established workflows, and switching costs. This playbook helps your team run a methodical displacement motion — turning dissatisfaction into action.

💡 Displacement reality check

Prospects don't switch because your product is better. They switch because the pain of staying exceeds the pain of switching. Your job is to help them quantify both sides of that equation.


Stage 1 — Trigger Identification

Goal: Identify accounts where the incumbent is vulnerable and switching motivation is high.

Key Triggers to Monitor

  • Contract renewal approaching: The 3–6 month window before renewal is the prime displacement window. After renewal, you're locked out for 12+ months.
  • Pricing increase: When the incumbent raises prices, customers re-evaluate. This is your opening.
  • Feature gaps: New requirements (compliance, integrations, scale) that the incumbent can't meet.
  • Leadership change: New CTO, VP Eng, or Head of Payments often brings fresh evaluation of the tech stack.
  • Outages or incidents: Service reliability issues create urgency. Monitor public status pages and social media.

Stage 2 — Switching Cost Analysis

Goal: Help the prospect objectively evaluate the total cost of switching vs. staying.

Key Activities

  • Map the total cost of the incumbent: License fees, integration maintenance, workarounds, manual processes, lost opportunity cost. The true cost is always higher than the invoice.
  • Quantify switching costs honestly: Migration effort, retraining, integration rework, temporary parallel running costs. Don't hide these — address them head-on.
  • Build the ROI model: Show the breakeven point. "Migration takes 6 weeks, but you'll recover the investment in 4 months through [specific savings]."
  • Offer migration support: Dedicated migration team, API compatibility layers, data migration tools, parallel running period — reduce the perceived risk.

⚠️ Never badmouth the incumbent

Criticizing the current vendor makes you look unprofessional. Instead, ask questions that help the prospect articulate their own frustrations: "What would you change about your current setup if you could?" Let them sell themselves on switching.


Stage 3 — Parallel Evaluation & Migration

Goal: De-risk the switch with a structured pilot and migration plan.

Key Activities

  • Run a side-by-side pilot: Process a subset of transactions, data, or workflows through both systems. Let the results speak for themselves.
  • Define clear success criteria: Performance benchmarks, uptime targets, integration verification, user satisfaction scores — agreed in advance.
  • Plan the migration in phases: Never propose a "big bang" migration. Start with a low-risk segment, prove value, then expand.
  • Assign a migration project manager: Own the timeline, coordinate with their engineering team, and proactively surface blockers.

💡 Displacement timeline expectations

  • SMB: 30–60 days from first contact to go-live
  • Mid-Market: 60–120 days including pilot and migration
  • Enterprise: 4–9 months including procurement, pilot, phased migration

Set realistic expectations. Rushed migrations create integration debt and churn risk.

Zet het in de library van je team, waar elke agent het vindt, en maak er je eigen kopie van.

Vorm
Playbook
Lengte
10 min read
Status
Free
Thema
dealssales

Meer zoals dit