Skip to main content
Steady at the Top
← All articles

Why buyers stay with a supplier they say they dislike

Buyers stay with suppliers they dislike when switching appears to create more work, uncertainty, or professional exposure than staying. Diagnose those costs before treating the decision as irrational loyalty. A better offer must make the transition credible as well as make the destination attractive.

Status quo bias is a disproportionate preference for the existing option, as examined by Samuelson and Zeckhauser in their 1988 decision research. Staying can also be a sound decision. The practical task is to separate preference for the familiar from costs your proposal has failed to address.

That distinction changes the conversation. You stop asking why the buyer cannot see your value. You start asking what your proposed change requires of the people who must approve, implement, and defend it. This is an application of ethical customer persuasion: help the customer inspect a decision rather than make resistance embarrassing.

Dissatisfaction is not a transition plan

A customer can dislike response times while valuing the incumbent’s knowledge of an old installation. The incumbent may have poor reporting yet know which local manager can authorize an emergency workaround. A new supplier can offer a better product while requiring the customer to reconstruct that knowledge.

Burnham, Frels, and Mahajan’s 2003 switching-cost typology separates procedural, financial, and relational costs. Their research concerned consumers, so it does not establish the causes of any specific enterprise decision. It does provide useful categories for questions about effort, money, and relationships.

Ask the operations leader what must happen before the first order moves. Ask finance when costs overlap. Ask the technical lead what cannot be tested outside production. Record their answers separately. A sales presentation that bundles these into an undefined implementation fee can hide the largest obstacle.

There is also a difference between switching cost and switching risk. Cost is a burden you expect to incur. Risk concerns uncertain outcomes. Training may take a known amount of staff time, while the chance of missed deliveries remains uncertain. Paying for training does not resolve the delivery concern.

The supplier-change burden review

The following proposed method produces a usable transition assessment. It is a management tool, not a validated psychological instrument.

  1. Write the customer’s stay option. Describe what happens if no switch occurs this cycle. Include current shortcomings and available remedies. Do not compare your ideal future with an exaggerated incumbent failure. The buyer may renegotiate service, narrow scope, or add a backup supplier without replacing the incumbent.
  2. List the work of changing. Name data migration, approvals, process changes, training, and the staff member responsible for each. Ask those owners to correct the list. Distinguish work your company will perform from work your customer must absorb. A promise to help does not assign capacity.
  3. Expose the personal accountability. Ask who signs off and who answers if the transition fails. Use role questions rather than guesses about motives. A proposed question is: “Which outcomes would your approval group expect you to explain after implementation?” The answer may reveal a missing acceptance test.
  4. Attach evidence to uncertain claims. Use a representative test, relevant reference, or documented technical review. State what the evidence cannot establish. A successful demonstration in a clean environment does not prove compatibility with every legacy system. Evidence should narrow an uncertainty you have named.
  5. Offer a bounded next commitment. Propose a next step that matches what has been learned. This might be a technical assessment rather than a contract. Define its cost, owner, output, and exit condition. Avoid using a small step as a disguised commitment to the full purchase.
  6. Ask for an explicit decision. Invite the customer to choose among staying, investigating, and switching. Record the reason and the event that would justify reopening the question. An honest decision to stay is more useful than a pipeline entry supported by repeated polite meetings.

Put the social exposure into ordinary language

Do not tell a buyer that they are protecting their status. That is an interpretation, and it may be wrong. Ask how the decision will be reviewed. A buyer might need a defensible procurement comparison, security approval, or a credible explanation for retiring a tool they previously selected.

Mayer, Davis, and Schoorman’s 1995 organizational trust model treats risk as part of understanding trust. Applied here, confidence in your salesperson and confidence in the proposed change require different evidence. Rapport can support a working relationship while leaving operational exposure unresolved.

Make the buyer’s reasoning easier to inspect. Give them the assumptions behind your estimate and identify where their team must supply information. If you cannot state the basis of a proposed saving, leave it out. If savings depend on retiring an incumbent system, say whether the retirement is feasible and who has confirmed it.

A proposed question is: “If your colleagues rejected this change, what concern would you consider legitimate?” This permits disagreement without demanding that the buyer defend your offer. The answer can be technical, financial, or organizational. Each needs its own response.

A hypothetical composite: the renewal nobody likes

In this hypothetical composite, a founder hears the same complaint about a supplier during every operating review. At home, the founder repeatedly delays changing the family’s unreliable service provider because transferring accounts would consume a weekend. The parallel is about work left unassigned, not a diagnosis of decision-making ability.

At the company, the purchasing manager says the incumbent is difficult. Sales interprets that statement as an invitation to replace it. The proposed replacement offers a lower unit price and expects a quick decision. The purchasing manager keeps asking for another meeting.

A burden review reveals that the production lead would have to qualify materials during an already crowded schedule. Finance has not budgeted the overlap. The purchasing manager also needs the quality team to approve traceability before committing. None of this makes the dissatisfaction false.

The next proposal changes. It includes a limited qualification batch, named responsibilities, and a decision after the quality review. It leaves the incumbent in place during testing. The hypothetical buyer still might decline, but the conversation now concerns a workable change rather than an attractive promise.

For leaders carrying persistent stress or symptoms that affect daily life, a licensed clinician is the right professional to consult. A commercial transition method does not assess or treat those symptoms.

Design relief that reaches the real burden

A discount addresses a price difference. It does not automatically provide implementation time or restore a strained internal relationship. Before adding another concession, ask which obstacle it removes. If no one can name the obstacle, the concession may reduce your margin without improving the customer’s ability to proceed.

Use risk reversal carefully. A refund clause may be irrelevant when the feared loss is disrupted operations. A rollback plan might matter more, provided it is technically feasible and contractually clear. Have appropriate advisers review obligations, liability, and any material transition terms.

Do not promise that the switch is effortless. State the effort you can remove and the effort that remains. A customer who discovers hidden implementation work after signing has a different reason to distrust the new supplier. Accurate limits belong in the proposal before the contract closes.

Improve discovery as well. Questions that avoid leading the customer can separate a complaint from a purchase requirement. “How much better would our service be?” invites endorsement. “What would have to be true before you changed?” invites conditions you can investigate.

Make staying visible in your own decisions

CEOs can create the same problem internally by announcing that the new supplier is plainly superior. Staff then have to carry transition costs while appearing resistant if they identify them. Ask for a written case for staying before authorizing a switch. Require the same quality of evidence on both sides.

An incumbent should not receive automatic credit for familiarity. Record recurring failures, internal workarounds, and the cost of monitoring them. Otherwise, the stay option will look inexpensive because its burdens have become ordinary. Keep historical sunk expenditure separate from future obligations that a switch would trigger.

A useful decision record names the future service standard, the evidence, and the unresolved issue. It also states who can accept residual risk. Do not leave that responsibility with a junior employee while senior leaders claim the commercial benefit.

The last review question is practical: can the customer execute the change with the people, time, and authority available? If the answer is uncertain, use the supplier-switch negotiation process to assign those burdens before seeking commitment. Preference can change when the change itself becomes credible.

Compare the next year, not the last argument

Put the stay option and the switch option on the same time horizon. For each, write the service standard, future work, contractual commitments, and unresolved dependencies. If your proposal includes a transition period, include the incumbent’s likely performance over that period rather than assuming an immediate replacement.

Ask which burdens are already funded. A new supplier may appear expensive because its implementation work is explicit, while staff time spent managing the incumbent remains hidden. The reverse can also occur. A replacement can look inexpensive because the proposal assumes customer effort that nobody has priced or scheduled.

Do not force every consequence into a speculative monetary estimate. Some issues should remain conditions, such as a required qualification test or approval from a specific operating owner. Record the evidence needed to clear each condition. A false number is less useful than an honest unresolved requirement.

Review the decision after the agreed event, even if the customer stays. Did the incumbent remedy the problem? Did the transition work become easier? Did a promised capability fail to appear? Updating the record prevents the next conversation from repeating a stale sales argument. It also shows the customer that their decision can be revisited on evidence without being treated as a failure of courage.

Sources

Steady at the Top