When Failure Renews the Contract

After a supplier’s software update shuts down your system, the emergency support number still belongs to the supplier.

A breakdown can strengthen the operator who caused it when that operator controls the fastest route to repair.

Before the outage, changing suppliers was a project you could schedule. During it, a newcomer’s investigation may prolong the disruption. A more competent firm can still be slower if it must obtain access and reconstruct undocumented dependencies. Your right to replace the supplier survives. The damage you risk while exercising it increases. A workable fallback limits this leverage by making a slower replacement bearable.

Merely keeping the job is not necessarily a gain in power. Nor is a larger payment: restoration has legitimate costs. The gain appears when urgency lets the supplier secure terms you would otherwise refuse, such as an exclusive contract extension that the repair does not require.

A troubled building project can produce the same advantage. A replacement contractor may have to open finished walls to discover what the incumbent already knows. Poor documentation can do two jobs at once: justify dismissal and raise the cost of dismissing its author.

No sabotage is required. Specialization, convenience, or neglect can concentrate essential knowledge in one firm. Agreement about responsibility does not make a replacement ready. The people dependent on the system bear the cost of waiting.

Dependence on expertise need not preserve the authority of those responsible. A supplier’s owners, or a legally empowered administrator, may replace its managers while retaining technical staff. The customer ordinarily has no such power. Where records and access let another firm restore service promptly, repair need not depend on keeping the incumbent in control.

An outage can end while the concessions secured during it remain. The supplier may emerge with less credibility and a longer contract.