A value proposition should explain why changing is worth the disruption, not only why the new offer is better. Identify the customer’s migration, learning, process, integration, contractual and confidence costs. Reduce what you can, make the remaining work visible and show a credible transition. Compare value over the relevant period, while acknowledging when staying with the current approach is reasonable.

Treat the current approach as a real competitor

Customers do not compare two feature lists in a vacuum. The current tool, supplier or manual process is familiar and already embedded. Even an imperfect approach may have trained users, connected systems and accepted workarounds.

Use How to Identify Competitive Alternatives to document why people keep the status quo. “Resistance to change” is not an explanation. A customer may be protecting delivery continuity, previous investment, team confidence or scarce implementation capacity.

Map the whole switching burden

Interview recent adopters, lost prospects, implementers and support teams. Capture costs in six groups:

  1. Discovery: evaluating options and building approval.
  2. Commercial: contract exit, overlap and procurement.
  3. Technical: data, integrations, configuration and testing.
  4. Operational: revised processes, temporary slowdown and contingency work.
  5. Learning: training, documentation and new habits.
  6. Confidence: fear of loss, error, reputational harm or regret.

Record who bears each cost and when. A benefit for the buyer may create work for users or administrators, so research the full buying group.

Separate reducible costs from unavoidable work

Mark each switching cost as:

  • remove: redesign the offer so the task disappears;
  • reduce: provide tools, defaults, training or staged adoption;
  • transfer: perform a task for the customer, with clear responsibility;
  • explain: make necessary work predictable;
  • accept: acknowledge that the offer is not suitable under some conditions.

Do not call a migration “seamless” merely because your team manages it. The customer may still need to clean data, approve mappings, test exceptions and support users.

Build transition into the value proposition

A complete working proposition answers four questions:

  1. What valuable change makes switching worthwhile?
  2. Why can this offer create that change?
  3. What will the transition require from the customer?
  4. How does the approach reduce or control the risk?

The result may be longer than a headline. Use the concise promise at the top of a page, then provide a migration path, responsibilities, proof and exceptions. The objection-messaging guide can help place answers where buyers encounter doubt.

Illustrative example

Illustrative example: imagine a client portal for small accountancy practices. Its message promises “all client files in one place”, but prospects worry about moving years of documents and retraining clients.

A stronger proposition might add: “Start with active engagements, import the agreed folder structure and invite clients in phases. Historical archives can remain read-only in the current system until retention requirements are reviewed.”

This hypothetical message reduces the size of the first move and states a boundary. It does not claim that every archive can be imported or that the old contract can end immediately. Those facts depend on systems, policy and customer choices.

Show proof for the transition

Useful evidence can include:

  • a current migration specification;
  • a sample responsibility map;
  • an accessible training plan;
  • product demonstrations of import and export;
  • documented rollback or exception handling;
  • verified customer evidence with context and permission.

Match proof to the claim. A customer quote about friendly support does not prove data completeness. Follow Proof Points for a Value Proposition to record scope, limitations and review dates.

Where personal data is involved, portability rights and responsibilities can affect the process. The UK Information Commissioner’s Office explains the right to data portability, including its scope and technical considerations. Obtain appropriate privacy and legal guidance for the actual service.

Compare value across a realistic period

Switching often creates an early cost and later value. Show both. A useful comparison can include setup effort, overlap period, steady-state cost, operational improvement and conditions for adoption.

Avoid using a long time horizon simply to make a weak case look positive. Let the customer adjust assumptions and identify the break-even condition without promising that every customer will reach it.

Limitations and trade-offs

Reducing friction can require provider labour, product development or lower initial revenue. A phased rollout controls risk but delays full value and can prolong dual systems. Done-for-you migration reduces customer effort while increasing the need for access, governance and clear accountability.

Some switching costs should not be minimised. Security review, accessibility testing, records management and user training may be necessary safeguards. Position around making them controlled and intelligible, not bypassing them.

Use this switching-cost checklist

  • Map every affected role, not only the buyer.
  • Capture financial and non-financial costs.
  • Identify dependencies and irreducible safeguards.
  • Decide what to remove, reduce, transfer or explain.
  • Show stages, responsibilities and exception paths.
  • Match transition claims to current evidence.
  • Compare cost and value over a fair period.
  • State when switching is not sensible.

Use the core value proposition guide to keep this transition logic connected to customer, problem, outcome and relevant difference.

Frequently asked questions

Should switching incentives be part of the proposition?

They can reduce an initial barrier, but a discount does not remove operational or confidence costs. Explain the transition and enduring value rather than relying on a temporary incentive.

Is “no migration required” a strong claim?

Only when it is literally accurate for the intended use. Check whether setup, connection, mapping, user change or parallel operation still creates work, and qualify the message accordingly.

What if switching costs are higher than the likely benefit?

Say so for that situation. The responsible next step may be to wait, change a smaller part of the process or serve a different segment with a stronger value case.

Your useful next step

Interview one new customer and one prospect who stayed with the status quo. Draw a timeline from evaluation to stable use, marking effort, risk and responsibility at each stage. Choose the largest avoidable burden and change the offer or message to address it explicitly.

Publication note: This guide is published by To-Do Growth and reviewed under our Editorial Policy. Illustrative examples are labelled and are not presented as customer case studies.