Switching-Cost Audit¶
Audit — instantiates Structural Constraint Identification and Lock-In
Itemizes the full cost of leaving the current arrangement — migration, retraining, integration rework, exit penalties, and the commitments already sunk into it — to measure how much of the lock-in is exit friction rather than genuine preference.
Staying with something can look like a preference when it is really a toll. Switching-Cost Audit measures that toll. It itemizes everything that would have to be paid to move off the current arrangement — the data migration, the retraining, the integration rework, the parallel-running, the contractual exit penalties — and separately accounts for the commitments already poured in that make leaving feel wasteful. Its distinguishing purpose is quantitative and forward-looking on the exit side: it does not ask what forces reproduce the path (that is a lock-in map) or who can block a change (that is a veto review); it asks how expensive is the door? By separating real forward switching costs from already-spent sunk commitments, it exposes how much of the lock-in is genuine friction to leaving versus a psychological reluctance to abandon what has already been paid.
Example¶
A mid-size manufacturer runs its whole operation on an aging ERP system and keeps renewing it, insisting the platform is "too embedded to replace." A Switching-Cost Audit tests that claim by pricing the door. On the forward side it itemizes the true cost of moving to an alternative: migrating fifteen years of master data and cleaning its accumulated errors, rebuilding the custom integrations to the shop-floor machines and the logistics carrier, retraining four hundred users, running both systems in parallel through a fiscal close, and paying the remaining term on the current license. Each line gets a range and an uncertainty tag; the switching-cost profile totals to a large but finite and knowable number.
Then it builds the sunk-commitment ledger separately: the millions already spent over the years customizing the incumbent. Those dollars are gone whether the company stays or leaves — they belong on a different page precisely so they cannot inflate the case for staying. The audit's punchline is the contrast: the forward cost of switching is real and substantial, but a chunk of what everyone felt as lock-in was actually reluctance to walk away from sunk customization. That reframes the decision from "we can't move" to "moving costs X, and here is the honest X."
How it works¶
The audit's discipline is a strict forward/sunk separation. The switching-cost profile counts only costs incurred by leaving, going forward: one-time transition costs (migration, integration rebuild, retraining, dual-running) and any recurring differences after the move. The sunk-commitment ledger counts what has already been spent and cannot be recovered — and it is kept off the switching decision on purpose, because sunk cost is irrelevant to whether leaving is worth it now.[1] Each switching-cost line is estimated with a range and its basis (a vendor quote, an analog migration, an internal estimate), and the profile distinguishes hard costs (contractual penalties, licenses) from soft ones (lost productivity, morale, risk during cutover) since the soft ones are the most under-counted and the most decision-relevant. The output is a defensible exit price with its uncertainty attached, plus an explicit ledger of what to ignore.
Tuning parameters¶
- Forward/sunk strictness — how rigidly already-spent costs are excluded from the switching total. Loose bookkeeping lets sunk cost masquerade as switching cost and over-states lock-in.
- Cost-category breadth — whether only hard, contractual costs are counted or soft costs (productivity dip, risk, morale) too. Broader is truer but harder to defend line-by-line.
- Estimation rigor per line — a quick internal guess versus a vendor quote or a pilot migration. More rigor narrows the range but spends time; match it to how consequential the exit decision is.
- Recovery/salvage accounting — how much of a sunk commitment is treated as still recoverable (reusable data, transferable skills). Generous salvage shrinks the apparent sunk pile but can be wishful.
- Time-phasing — whether switching costs are summed as a lump or spread across a staged migration, which changes how affordable the exit looks.
When it helps, and when it misleads¶
Its strength is that it turns "we're locked in" into a number you can argue with, and its forward/sunk split is a direct antidote to the most common lock-in illusion — mistaking money already spent for a reason to stay. A finite, itemized exit price also enables staging: if the total is dominated by one line, that line becomes the thing to attack first.
Its failure mode is the sunk-cost fallacy running the other direction — decision-makers quietly fold the sunk ledger back into the switching case to justify staying, which is exactly the error the separation exists to prevent. The audit also systematically under-counts soft and hidden switching costs (the productivity trough, the cutover risk, the tacit workflows no one documented), so a tidy hard-cost total can understate the real friction. The guarding discipline is to keep the sunk ledger visibly quarantined from the switching decision, to force every soft cost onto the profile even when it can only be ranged, and to carry the uncertainty forward rather than reporting a false single figure.
How it implements the components¶
switching_cost_profile— its primary output: the itemized, ranged inventory of forward costs to leave, split into hard and soft, that quantifies how expensive the exit actually is.sunk_commitment_ledger— a separate accounting of what has already been irrecoverably invested, kept explicitly apart so it informs how the lock-in formed without contaminating the should-we-leave calculation.
It does not map the self-reinforcing loops that make staying attractive in the first place (lock_in_mechanism_map and network_effect_register, from Lock-In Map, its nearest twin — that map explains why the path reproduces itself; this audit prices the door out of it), nor does it identify the institutional_rule_map of who could veto a switch (see Institutional Veto-Point Review).
Related¶
- Instantiates: Structural Constraint Identification and Lock-In — supplies the exit-cost layer: how much of the constraint is priced friction versus preference.
- Sibling mechanisms: Comparative Case Constraint Check · Counterfactual Breakpoint Analysis · Feasibility Envelope Diagram · Institutional Veto-Point Review · Lock-In Map · Threshold and Hysteresis Assessment · Dependency Graph
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Switching-Cost Audit operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it itemizes the full cost of leaving the current arrangement — migration, retraining, integration rework, exit penalties, and the commitments already sunk into it — to measure how much of the lock-in is exit friction rather than genuine preference.
Independent corroboration: The frozen evidence defines Switching-Cost Audit as 'Itemizes the full cost of leaving the current arrangement — migration, retraining, integration rework, exit penalties, and the commitments already sunk into it — to measure how much of the lock-in is exit friction rather than genuine preference', so its operative form is Assessment, Review & Assurance.
Nearest alternative: Analysis, Modeling & Optimization — Switching-Cost Audit includes features of an analytical, modeling, inference, comparison, or optimization procedure that derives insight or a solution, but its defining operation is a bounded evaluation of existing evidence or work that produces a finding or disposition.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Economics & Finance
Origin pattern: Single lineage
Present-day reach: Universal
Rationale: Switching costs are an industrial-organization concept for frictions that lock users into suppliers or choices.
Related originating lineages:
- Computer Science & Software Engineering — Computer science and software-engineering practice supplies a parallel or contributing lineage for the mechanism's defining operation: itemizes the full cost of leaving the current arrangement — migration, retraining, integration rework, exit penalties, and the commitments already sunk into it — to measure how much….
- Organizational & Management Science — Process audits expose retraining, migration, and coordination burdens.
Review resolution: The blind reviewers agree that economics_finance is the primary origin and differ only on alternate origin disagreement, encyclopedia synthesis disagreement. I preserve every independently explained alternate from both records rather than imposing a numeric cap. I retain single_lineage because the combined evidence shows one traceable formative lineage. The broader reach of universal records portability separately from historical provenance; encyclopedia_synthesis=true preserves the affirmative synthesis judgment where either reviewer identified one.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
References¶
[1] Arkes, H. R., & Blumer, C. "The Psychology of Sunk Cost". Organizational Behavior and Human Decision Processes 35(1), 124–140 (1985). Treats irrecoverable past expenditure as sunk and therefore irrelevant to the present continue-or-leave decision. registry ↩