INT-10 · SEC. 09 Competitive Intelligence

Incumbent Switching-Cost Teardown

Map exactly what makes it hard to leave a specific incumbent, and which costs are real vs. perceived.

FORMAT: workflow
DIFFICULTY: intermediate
TIME: 12 min
TOOLS: universal
MODELS: any
COPIES: 0 so far

When to use this

You're trying to win customers off a specific, named incumbent and keep hearing "switching is too much work" as an objection. Use this to find out precisely what that means so sales and onboarding can address the real cost, not a vague fear of it.

The pattern

Pastes as plain text

The incumbent we're displacing and my product are named at the bottom of this prompt.

Research the incumbent's public data export docs, API docs, integration marketplace, and contract/terms page if available. Then map switching cost across these categories:

1. Data portability: can a customer export their data in a usable format without contacting support? Note any format, size, or plan-tier restrictions on export.
2. Contract lock-in: stated contract length, auto-renewal terms, and any early-termination penalty mentioned publicly.
3. Integration dependency: how many third-party tools commonly connect to this incumbent (check their integration/marketplace page) that a switcher would need to reconnect elsewhere.
4. Retraining cost: how different is the incumbent's core workflow or UI from category norms — is this a tool with unusual terminology or a highly custom workflow that takes real time to unlearn?
5. Migration tooling: does the incumbent, or any third party, offer an import tool or migration service, or is this fully manual today?

For each category, classify the cost as "real" (structurally hard to avoid, e.g. a 12-month contract with a penalty) or "perceived" (sounds hard but is actually low-effort, e.g. a clean CSV export in one click). For every "real" cost, write one sentence on how my product or onboarding process should address it directly.

Incumbent (name and URL):
My product (one line):

Real example output

1. Data portability: CSV export available self-serve on all tiers, no restrictions found. Classified perceived — customers likely assume lock-in here but the actual export is low-friction.
2. Contract lock-in: Terms page states a 12-month minimum with auto-renewal and a stated early-termination fee. Classified real. Response: offer to cover or waive the customer's remaining contract cost as a switch incentive, since this is the one hard structural cost found.
3. Integration dependency: Marketplace lists 40+ integrations; no way to tell from public pages how many any given customer actually uses. Classified unclear — flag for sales to ask directly rather than assume.
4. Retraining cost: Incumbent uses non-standard terminology unlike most tools in this category. Classified real, but moderate. Response: ship a terminology-mapping guide in onboarding so switching users aren't relearning the mental model from zero.
5. Migration tooling: No official import tool found; several third-party threads mention manual re-mapping as the common path. Classified real. Response: build or promote a one-click importer for this specific incumbent's export format as a direct answer to the biggest friction point found.

Why it works

Splitting "real" from "perceived" switching costs stops sales from over-promising on things that are actually easy (data export) while under-preparing for the one that's genuinely hard (the contract term). Tying each real cost to a specific product or onboarding response turns a research doc into an actual sales enablement asset.