← All lessons
Day 85 of 90

Platform Lock-In Risk with LLM Providers

8 min read

Key Concepts

  • 1Building deeply on one LLM provider creates lock-in: prompts, fine-tunes, and features tuned to one model can be costly to migrate if pricing, terms, or quality change
  • 2Provider risk is real: price hikes, deprecations, rate-limit changes, outages, and policy shifts are all outside your control and can hit the business
  • 3Abstraction layers reduce lock-in: routing agent calls through a provider-agnostic interface makes switching or multi-provider strategies feasible
  • 4But abstraction has a cost: providers differ in capabilities and prompt behavior, so a lowest-common-denominator abstraction can forfeit a provider's best features
  • 5Multi-provider strategies add resilience (failover, negotiating leverage, best-model-per-task) at the cost of complexity and maintenance
  • 6Fine-tuning deepens lock-in because a tuned model is provider-specific and must be re-created elsewhere — a factor in the fine-tune-vs-prompt decision
  • 7The PM tradeoff: depth of integration and best-model performance vs portability and negotiating leverage, weighed against the provider's strategic importance

Why It Matters for PMs

Strategic risk management: Deep single-provider dependence exposes the business to price, deprecation, and policy changes. Managing lock-in is a strategic PM concern.
Portability vs performance: Abstraction reduces lock-in but can forfeit best-in-class features. PMs must weigh portability against performance deliberately.
Leverage and resilience: Multi-provider capability provides failover and negotiating leverage, at a real complexity cost the PM must justify.

Test Your Understanding

Question 1 (Multiple Choice)

Why is deep single-LLM-provider dependence a risk?

Question 2 (Multiple Choice)

What is the cost of a provider-agnostic abstraction layer?

Question 3 (Multiple Choice)

Why does fine-tuning deepen lock-in?

Question 4 (Short Answer)

How would you reduce LLM provider lock-in without forfeiting too much performance?

Think about your answer before revealing the explanation.

Question 5 (Short Answer)

What's the tradeoff between deep single-provider integration and a multi-provider strategy?

Think about your answer before revealing the explanation.