Switching costs are real strategy—not a dirty trick by default. I'd use them to reward continued value, not to trap unhappy customers.
Levers I'd consider
- Data gravity: history, workflows, integrations that get better over time
- Network effects: value rises with participants
- Learning curves: mastery the user doesn't want to re-earn elsewhere
- Contracts/procurement: honest enterprise reality—not dark patterns
- Ecosystem: apps, partners, templates
Ethical line I won't cross
| Healthy | Sketchy |
|---|---|
| Export exists; staying is still better | Hostage data formats |
| Habit from value | Punitive cancellation mazes |
| Integrations deepen outcomes | Compatibility sabotage |
High switching costs with low satisfaction is churn debt. I'd rather earn retention.
Technical and platform PMs hit this often—Technical PM Certification helps frame platform bets.
More in the newsletter.