Score exit readiness before you need to leave.

Exit is part of buying

Renewal season arrives. Switching cost is “too high” because export is unclear, identities will not map, runbooks only exist inside the vendor’s head, and dual-run was never possible. The SLA still looks fine. You renew by inertia.

Exit readiness should be scored while you still have leverage—before signature and before renewal—not during a forced migration.

This note gives you the TWIMCO Vendor Exit Readiness Scorecard. Partnerships that stay inspectable, like Sutton|Place, make ongoing ownership legible; exit scoring extends that habit to portability. Scope under web applications.

Exit readiness is easiest to ignore while the product works. That is exactly when to score it. Waiting until dissatisfaction peaks means you score under time pressure with less leverage.

Include subprocessors in the conversation: if your data lives in a vendor’s vendor, export and identity questions multiply.

Four dimensions 0–2

1. Export. Can you extract your data in documented, usable formats on a known cadence—without a heroic professional-services project?

• 0 — No practical export; or export is screenshots and CSVs that omit critical relations.
• 1 — Export exists with gaps; lead time or completeness unclear.
• 2 — Documented export, tested sample, relations preserved enough to rehydrate elsewhere.

2. Identity. Can users, roles, and object ids map to a successor system without losing audit trails?

• 0 — Opaque ids; no mapping story.
• 1 — Partial mapping; manual pain accepted.
• 2 — Stable external keys; mapping approach written and sampled.

3. Runbooks. Can your team operate critical paths using artifacts you control if the vendor disappears tomorrow?

• 0 — Knowledge only in vendor staff.
• 1 — Some docs; critical paths still tribal.
• 2 — Runbooks you hold; dry-run or tabletop evidence.

4. Dual-run. Can old and new run together long enough to cut over safely?

• 0 — Hard cut only; no overlap path.
• 1 — Dual-run theoretically possible; untested.
• 2 — Dual-run path described; compare approach named.

Optional fifth: Contractual exit assistance (hours, fees, data destruction proof).

Test export with a restore exercise into a neutral store (even a staging database you control). “We downloaded files” is not the same as “we can rehydrate.” Score Export on rehydrate evidence when stakes are high.

Identity scoring should include SSO and SCIM realities: can accounts be remapped without breaking audit? Sample one role mapping end-to-end.

Operating details that keep the artifact honest

Involve security and privacy in Export and Identity scoring. Portability that violates retention or redaction rules is not a 2. Exit must be lawful as well as technical.

Price the exit assistance line item before you need it. Emergency professional services during a forced migration are a different market than contracted exit hours.

For critical systems, run a miniature dual-run drill annually even if you are not leaving—prove the path still exists. Skills and exports rot.

Document where exported data will land (successor vendor, internal warehouse). Exit to nowhere is not readiness.

Tell leadership the Fail dimensions in plain language: “We cannot currently leave Vendor X without data loss risk.” Clarity creates budget for remediation.

Pass rule

Pass — no zeros; Export ≠ 0; at least two dimensions = 2. Conditional — no zeros on Export/Identity; remediation dated before renewal. Fail — Export or Identity = 0: do not claim you can leave.

Score at RFP, at go-live+90 days, and before each renewal. Keep evidence lines (sample export files, mapping sheets).

Use Conditional scores as renewal leverage: fee credits, exit assistance hours, or dual-run commitments dated in the order form. A score without commercial consequences becomes a diary entry.

Fail on Export should block “strategic platform” language in internal memos until remediated. Words matter for future you.

Failure modes

Export theater. One CSV without relations.

Identity prison. Ids that only mean something inside the vendor.

Runbook mirage. Vendor wiki you cannot take with you.

Cliff cutover. No dual-run; migration is a weekend prayer.

The unreproducible asset is your scored sheet—the TWIMCO Vendor Exit Readiness Scorecard—with evidence.

Revisit after M&A on either side. Ownership and export postures change when companies combine. Schedule a re-score within 90 days of material ownership change.

How this fits beside related operating habits

This note’s unreproducible asset—the TWIMCO Vendor Exit Readiness Scorecard—is meant to sit beside other TWIMCO operating sheets, not replace them. Use it when the job in front of you matches the title; reach for sister artifacts when the job is adjacent.

Keep the sheet short enough to fill in a working meeting. Long frameworks that never leave the drive do not change go-live behavior. Dated, named, evidenced lines do.

When you socialize the artifact, bring one real case—not a hypothetical. Real cases expose missing owners and blank cells faster than abstract agreement. Update the sheet when roles, systems, or policies change; stale operating paper is how teams relearn the same incident.

If two documents disagree under pressure (for example a boundary spec and a source-of-truth map), treat the disagreement as a defect to fix in daylight. Do not leave on-call to invent a merger of conflicting instructions at night.

Finally, resist metric theater. These sheets ask for evidence you can open—runbooks, recordings, fixtures, named roles—not for invented industry benchmarks. Your filled evidence is the moat; empty templates are not.

Teach the vocabulary on the sheet in standups and incident reviews until the words feel ordinary. Ordinary vocabulary is the goal: exception path, owner, rollback, SoT, fallback, done-means. When those words are shared, debates get shorter and decisions get written down.

Put this into practice

1. Score your top vendor this month.
2. Attach Conditional remediations to renewal negotiations.
3. Demand a sample export as buying evidence—like an SLA pack.
4. Re-score after major data model changes.
5. Reference Sutton|Place; scope under web applications.

Buy the exit while you still can.

Revisit the filled artifact on a fixed cadence—after major releases, before renewals, or after incidents that touched the same surface. A scorecard or checklist that is never re-opened becomes folklore. Folklore is how teams argue from memory instead of from evidence.

When you hand the sheet to a vendor or an internal partner, keep a copy you control. Shared drives that only the counterparty edits are not your operating record. Your dated copy is what you bring to the next steering meeting.

Keep a short changelog on the artifact itself: date, editor, what cell changed. Changelogs make re-onboarding faster and show auditors that the operating sheet is alive. If nobody has edited the sheet in six months, schedule a review—even if the answer is “still correct.”