---
id: "prereq-saas-lock-in"
type: "prereq"
source_timestamps: ["00:16:10"]
tags: ["business-context"]
related: ["framework-eras-of-lock-in", "concept-behavioral-lock-in"]
sources: ["s51-512k-leaked-code"]
sourceVaultSlug: "s51-512k-leaked-code"
originDay: 51
---
# Familiarity with SaaS Vendor Lock-In

## Prerequisite

**Topic:** SaaS vendor lock-in patterns (especially Salesforce, Slack, Oracle migrations).

## Why It's Required

The speaker's core thesis relies on **comparing the new [[concept-behavioral-lock-in|behavioral lock-in]] to historical examples** of database and cloud/SaaS lock-in to illustrate its unprecedented severity. Without this baseline, the argument that the new lock-in is *categorically worse* is hard to evaluate.

## Minimum Knowledge Needed

- Why migrating off Salesforce or Slack is operationally painful (not technically impossible).
- Database lock-in: Oracle/SQL migrations historically taking 6–12 months.
- The role of GDPR/CCPA in mandating data portability.

## Where It's Used

- [[framework-eras-of-lock-in]] — eras 1 and 2 frame era 3.
- [[claim-agent-lock-in-severity]] — quantitative comparison (20–30% SaaS dip vs. 50%+ agent dip).