A vendor tool creates lock-in. Is that automatically a bad choice?
Unexamined exit trade-offLock-in is a trade-off to evaluate, not a label that settles the decision. Compare benefits with portability, data access, switching cost, and continuity requirements.
What to do now
- Identify what would be difficult to move
- Assess exit and migration options
- Compare the dependency with expected value
- Record the decision and safeguards
When to escalate
Escalate when
Essential data or operations cannot be recovered on acceptable terms.
Who decides
The authorized procurement or commercial owner
Example
A proprietary service is chosen with verified export capability and a documented transition approach.
Mistake to avoid
Assuming open-source software or a contract automatically eliminates dependency.
Prevent a repeat
Compare supplier evidence with agreed obligations; refer contract interpretation and remedies to qualified owners.
Suggested ApprovedFlow setup
- Vendors
- Documents
- Tasks
- Approvals
Keep supplier commitments and evidence linked to the project, assign follow-up work, and route commercial decisions to authorized owners. See the platform
Related cases
- The vendor wants full payment before handover. What should we review?Payment-handover misalignment
- The vendor refuses to share progress evidence. What should we do?Unverifiable supplier delivery
- Our utilization is high, but delivery is slow. Why?Utilization-flow trade-off
- How do we assess a new urgent project without derailing everything?Urgent intake trade-off