| Forced AI SKU migration |
The underlying product is required, an as-is or AI-free path exists, and the premium is not the price of staying. |
The old tier still exists or a credible as-is path is available, and nobody uses the AI. |
The old SKU is being deleted. Demand a separable AI line, an as-is quote in writing, and migration-proof price protection. |
Only if another product clears Year-1 net economics and risk before the notice window closes. |
| Metered AI credits |
Named owners, a forecast you can defend, a hard ceiling, and unused-credit treatment in writing. |
No forecast, no owner, or the vendor will not cap consumption. |
Split seats from credits. Cap monthly burn. Notify before the ceiling. Price the credit line separately. |
Only after replacement operating, AI/API, and switching costs still beat the current stack on a net basis. |
| Outcome-based fees |
The unit is defined, auditable, and tied to a workflow you already run. |
The vendor owns the definition and you cannot verify the count. |
Pilot with audit rights, a volume cap, and a walk-back to seats if the unit fails. |
Same net-economics gate. Subtract switching cost before calling a cheaper outcome fee a saving. |