Skip to main content
AI Biz Hub

AI economics

LLM Vendor Lock-In Cost

How much does it really cost to migrate off your current LLM provider? Engineering hours, downtime, and payback at a new vendor's price.

Your numbers

Start from an example

$
Prompt complexity (1–10)

1 = a few plain prompts, 10 = heavily tuned chains with few-shot examples (about 4 h per point).

Test cases to migrate and recalibrate (about 0.5 h each).

hr
d
$

Monthly revenue that stops while the feature is down; drives the downtime cost.

$
New vendor discount

Result

Total switching cost
$16,133
Engineering hours
104 hr
Months of current spend
2 mo
Payback months
6.7 mo

Switching cost breakdown

Engineering hours and downtime add up to total cost-of-migration.

Engineering cost
$15,600
Downtime cost
$533.33
Total switching cost
$16,133

General business information, not legal, tax or financial advice. The result comes only from your inputs and the published method. How we check our numbers.

How to use it

  1. Enter your current monthly LLM spend, your prompt complexity on a 1-10 scale, the size of your eval suite, the engineering hours you expect retraining and reintegration to take, the days of downtime during the switch, the monthly revenue that stops while the feature is down, your hourly engineering cost, and any discount the new vendor offers. Prompt complexity (about 4 hours per point) and eval-suite size (about half an hour per test) drive the rewrite estimate, because the more your prompts are tuned to one model's quirks, the more engineering it takes to make them work on another.
  2. Read the total switching cost, the engineering hours behind it, how many months of current LLM spend it equals, and the payback period at the new vendor's discount; the chart splits the total into engineering cost and downtime cost. The total switching cost is the real price of the migration, and the months-of-spend figure puts it in terms you already understand.
  3. Use the payback period as the decision gate. If a 30% discount takes years to repay the switching cost, the lock-in is effectively permanent and the discount is a distraction; if it pays back in a few months, the migration is worth scheduling. This reframes vendor choice from a sticker-price comparison into a real return-on-investment question.
  4. Treat the engineering and downtime estimates as the part most teams underestimate. Prompts that were tuned over months, evals that encode hard-won edge cases, and the revenue lost during a cutover are all real costs that a headline price-per-token comparison ignores entirely. Model a pessimistic case with more rewrite hours and an extra day of downtime to see how quickly the payback period stretches.
  5. Re-run whenever a vendor changes pricing or a new model makes switching tempting, and use the output to negotiate. Knowing your true switching cost is leverage with your current vendor, since the discount a competitor must offer to clear your payback hurdle is exactly the number your incumbent has to beat to keep you.

The same numbers as a table

  • Make the call Build vs Buy Decision Engine

    Compare building infrastructure yourself versus buying managed services with per-component build/buy verdicts.

  • Make the call One-Person SaaS Valuation

    Estimate what your solo SaaS is worth using indie/micro-SaaS multiples with key valuation factors.

  • Make the call Ship-or-Kill Decision Score

    Get a brutally honest SHIP, ITERATE, or KILL verdict on your side project based on traction and market signal.

  • Make the call Pricing Model Picker

    Flat monthly, per-seat, usage-based, or hybrid? Compare projected revenue side-by-side.

All articles

More in AI product economics

Understand the costs, margins, and pricing of building AI-powered products.

The AI product economics guide

Use it from code

The same calculation as a JavaScript module you can import. It runs where you import it, with no request, key or rate limit.

import { compute } from "https://aibizhub.io/engines/llm-vendor-lock-in-cost.js";

Input and output contract, TypeScript types and the guide for agents.