Deletability

Deletability is the ability to remove or replace a system through a documented, tested exit path without losing access to business data or continuity of the process it served: data exported in open formats, integrations redirected, a documented fallback for the workflow. At Syndicai we use a one-week removal exercise as the demanding design test — if the system could not be gone in about a week, it carries coupling nobody agreed to.

Why it matters

Switching cost is a defect from the buyer's side, not a vendor asset. A vendor who says "you should stay, because leaving would be hard" is selling the solution to a problem they created. Deletability is also a forcing function: designing for it produces modular architecture, clean documentation, and a neutral data store — the same properties that make a system operable at all.

Common confusion

Deletability is not an anti-retainer position — a retainer is legitimate when chosen for its value rather than enforced by exit cost. And it does not promise zero disruption: a manual fallback is itself an impact. The point is that the impact is bounded, known, and rehearsed, instead of discovered during a dispute.

Where we use it

The exit clause in What to check before you sign, and the sequencing argument in One app or four?.