Buyer-Led Competitive Displacement

An incumbent is not merely a product to beat. It is part of the buyer's current operation: contracts, data, integrations, training, controls and work people already know how to perform. A responsible displacement process therefore has to answer a harder question than “is the alternative better?”:

Do the forward-looking benefits of change justify its cost and risk when compared with improving or retaining the current approach?

The answer may be no. A credible evaluation keeps that option open.

Establish why an evaluation exists

Start with buyer-confirmed facts, not public clues treated as private intent. Ask:

• What requirement or operating condition has changed?
• Does the current approach meet that requirement, and what evidence supports that view?
• What has already been tried with the incumbent?
• What would a satisfactory no-change or improvement plan look like?
• Which contract, data, security, implementation and people constraints must any alternative respect?

A leadership change, acquisition, review, job post or public complaint does not prove dissatisfaction, budget or authority. Use public facts only for the limited claim they support, check that they are current and ask the buyer whether they are relevant.

If the group cannot state a material requirement that the current approach fails to meet, a replacement exercise may be unnecessary. Record that instead of trying to manufacture a “fracture.”

Compare requirements, not reputations

Build the criteria with the buyer before scoring any option. For each requirement, record the current evidence, an incumbent improvement option, the alternative option, remaining unknowns and a named owner. Apply that structure to at least these areas:

• Required workflow: use a buyer demonstration or documented process for the current state; compare a confirmed configuration or service change with a demonstrated alternative capability.
• Data and security: use the current architecture and approved assessment; compare verified remediation with verified controls and migration design.
• Commercial terms: use actual authorised contract information; compare an incumbent renewal or amendment supplied by the buyer with a written proposal. The buyer should first confirm that its agreement permits sharing those terms with a competing supplier.
• Implementation capacity: name the people and available time; compare the work needed to improve in place with the work needed to change.

Do not use a stopwatch demonstration, selective workflow or roadmap rumour as a substitute for like-for-like evidence. Product capabilities, prices and public roadmaps change. Attribute each claim to a current primary source, written proposal or buyer-verified demonstration and record the checked date.

Keep the language neutral. “The incumbent does not support this requirement in the configuration we verified” is testable. “Their platform is outdated” is not. The same standard applies to your own product.

Use forward-looking economics

Past spending should not be silently counted as a future benefit of staying or as a future cost of changing. Arkes and Blumer's 1985 study found that prior investment can affect willingness to continue an endeavour in its study settings. It does not establish that a particular B2B buyer is trapped by sunk cost, nor does it justify diagnosing someone's motives.

Build the model from the decision date forward. Include, where applicable:

Staying or improving the incumbent

• remaining committed fees and renewal terms supplied by the buyer;
• internal administration and workaround time;
• configuration, service or integration improvements;
• expected operational impact of unresolved gaps; and
• the risk and cost of making no change.

Switching

• new subscription or service fees;
• migration, validation, security and legal work;
• integration rebuilding and data-quality remediation;
• training, dual running and temporary productivity effects;
• termination or overlap costs confirmed from authorised terms; and
• ongoing operating cost after transition;
• the risk that the alternative does not deliver the expected improvement; and
• the cost and practical feasibility of reversing the change.

Show every input, unit, period and formula. Use ranges where the input is uncertain, and run at least a low, central and high scenario. Do not bring an invented “fully loaded” cost into the meeting and present it as the buyer's number. Let the accountable owner supply or approve it.

For example, suppose the buyer supplies central estimates for the same twelve-month period. Staying might include £120,000 in fees, £30,000 of administration and £20,000 of agreed remediation: £170,000 in total. Switching might include £90,000 in fees, £35,000 of migration, £25,000 of integration and training, and £20,000 of dual running: also £170,000. Those illustrative totals do not decide the recommendation. The group still needs to compare requirement fit, uncertainty and the low and high scenarios using its own approved inputs.

Past investment still matters operationally when it created assets that must be migrated, replaced or abandoned. That is a future switching consequence, not a reason to speculate about the career exposure of whoever selected the current vendor.

Give the original decision fair context

The buyer does not need a story that declares the original purchase a mistake. Ask what the tool was selected to do and what has changed since. A defensible internal explanation might be:

The original decision addressed the requirements documented at the time. We are reassessing because these named requirements, constraints or volumes have changed.

That statement only works when the changes are real and recorded. Do not invent market shifts, competitor strategy or internal politics to provide a convenient narrative.

Design a transition that can be challenged

A replacement recommendation is incomplete without an implementation plan. At minimum, identify:

1. scope and out-of-scope workflows;
2. data owners, migration method, validation and rollback;
3. integration dependencies and test environments;
4. security, privacy, legal and procurement approvals;
5. training and accessible support;
6. dual-running or cutover criteria;
7. operational acceptance measures; and
8. the conditions under which the buyer pauses or abandons the switch.

Dates should come from named work and capacity, not a universal “week three” rule. Security material must be current and authorised. A migration plan should state unknowns rather than using specificity to create false confidence.

If the recommendation is a pilot, record the requirement being tested, its scope and cost, the acceptance measure and the decision date. The scope must be large enough to test the disputed requirement without quietly becoming an open-ended rollout.

Handle incumbent responses without prediction

The incumbent may discount, propose a service change, explain a roadmap or challenge the transition plan. Treat each response as new evidence:

• compare total terms and obligations, not just headline price;
• request written scope, ownership and timing for promised changes;
• validate roadmap statements through authorised, current sources;
• add legitimate transition risks to the model; and
• update the recommendation if the incumbent option now best meets the agreed criteria.

Do not tell a champion that a particular counteroffer is certain to arrive or use it as proof that previous pricing was unfair. Do not encourage disclosure of confidential competitor information. The goal is an accurate decision, not a performance in which your prediction must come true.

Ask the internal advocate to explain the proposed decision in one sentence without disparaging the incumbent. If the sentence cannot identify a verified, forward-looking reason to change, the case needs more work; it does not prove the incumbent is weak or the advocate lacks influence.

Know when to pause or withdraw

Pause the evaluation when the buyer cannot confirm a material unmet requirement, accountable owners will not approve the economic inputs, or the implementation constraints cannot be assessed fairly. Record the unresolved condition and remove the opportunity from the active forecast rather than manufacturing urgency. The forecasting guide explains how to separate evidence from upside assumptions.

Revisit only when the buyer identifies a relevant change, such as a documented requirement, renewal decision or available implementation capacity. A pause is a valid decision, not a cue to invent a trigger event.

Use an explicit decision record

End the evaluation with a short record containing:

• the criteria and their owners;
• evidence for each option;
• unresolved unknowns;
• forward-looking scenario results;
• implementation and no-change risks;
• conflicts or limitations in the evidence; and
• the recommendation, including stay, improve, switch, pilot or defer.

Ask the group to correct it. A buyer-approved record is more useful than a seller-authored “cost of staying” slide because it shows which assumptions the organisation is actually prepared to own.

Qualification checklist

• Is the changed requirement confirmed by the buyer?
• Has the incumbent been assessed against the same current criteria?
• Are competitor and self-product claims sourced and dated?
• Are all economic inputs visible and buyer-approved?
• Does the plan include migration, people, data and control costs?
• Can the group choose to stay or make no decision without being punished?
• Is the recommendation based on future consequences rather than inferred psychology or reputational pressure?

Competitive displacement earns trust when the analysis is fair enough to recommend the incumbent when the evidence points that way.

Sourcing note: the linked Arkes and Blumer paper supports the narrow description of its sunk-cost findings only. The evaluation structure above is SalesTap editorial guidance, not measured claims about displacement outcomes.