Your model already has a retirement date

AI vendors publish model retirement schedules and they differ: 6 months, 60 days, or 2 weeks. What to check before you sign an enterprise AI contract.

By DellonUpdated on: September 13, 20268 min read

The model you signed for has a retirement date, and in most cases the vendor has already published it.

That's the part of AI procurement most contract reviews miss. Teams negotiate seats, usage tiers, and termination language, then discover the underlying model is on a lifecycle schedule that sits outside the contract entirely and moves on the vendor's timetable.

Traditional software licensing assumes the product you bought will still exist next year. AI licensing assumes it won't, and publishes the date.

The market moved to buying

Start with the scale, because it explains why this matters more than it did two years ago.

Menlo Ventures' 2025 State of Generative AI in the Enterprise, published 9 December 2025, put enterprise spending on generative AI at \$37 billion in 2025, up from \$11.5 billion in 2024, a 3.2x increase it describes as the fastest-scaling software category in history.

The composition shifted at the same time. In 2024 enterprises split roughly evenly, 47 percent building internally and 53 percent buying. By 2025, 76 percent of AI use cases were acquired rather than developed in house.

So more organizations are dependent on vendor terms than were a year ago, and the dependency arrived faster than most procurement functions adapted.

The retirement clock is published

The most useful thing a buyer can do costs nothing and takes ten minutes. Read the vendor's deprecation policy before the contract, because the major providers publish theirs and the terms differ materially.

Editorial evidence panel

Evidence panel

Editorial context panel

Context panel

OpenAI's deprecation documentation sets tiered minimum notice. Generally available models get at least 6 months before retirement. Specialized variants get at least 3 months.

Preview models can get as little as 2 weeks, and the documentation states outright that they aren't recommended for production use. Faster timelines apply if safety or compliance concerns require them.

Anthropic's model deprecation policy commits to at least 60 days' notice before retirement for publicly released models, with a four-stage lifecycle of active, legacy, deprecated, and retired. Deprecated models keep working and stop being recommended. Retired models fail.

Those are different planning horizons for the same class of dependency. Six months lets you test, migrate, and validate on a normal release cycle.

Sixty days is a quarter's notice for a migration that may touch prompts, evaluation criteria, and downstream reporting. Two weeks on a preview model is not a production commitment at all, which the documentation says plainly and which buyers routinely ignore.

Same model, different clock

Here is the detail that catches multi-vendor buyers, and it is not in any sales deck.

Anthropic's policy states that its published dates apply to Anthropic-operated platforms, and that partner-operated platforms including Amazon Bedrock and Google Cloud set their own retirement schedules, so a model's lifecycle status and dates can differ.

Read that carefully. The same model, bought through a different channel, can carry a different retirement date. An organization running the model directly and through a cloud marketplace has two clocks on one dependency, and the procurement team that negotiated the marketplace agreement may never have seen the direct policy.

The practical step is to write the channel into the record. Which platform, which model identifier, which published retirement date, and who watches it. That's four fields and it prevents the most avoidable version of this failure.

What that does to a contract

Now put the two together, because the interaction is where cost appears.

A multi-year agreement priced against a specific capability assumes that capability persists for the term. If the underlying model retires inside the term, the buyer migrates on the vendor's schedule regardless of what the contract says about price. The commercial terms survive. The technical foundation does not.

That's the honest version of the "model versioning" problem, and it's more manageable than the usual framing suggests, because the dates are published rather than hidden. The failure is that buyers never look the schedule up, then treat the migration as a surprise.

Two contract provisions follow from that. Ask what happens commercially if the contracted capability is retired mid-term, and get the answer in writing. Ask whether migration support is included or billed as professional services, because that is where the unbudgeted cost usually lands.

Exit terms are regulated in one market and contractual in the rest

Data portability is the other clause worth attention, and the legal backdrop is uneven by geography.

The European Union's Data Act entered into force on 11 January 2024 and became applicable on 12 September 2025, establishing a framework for customers to switch between providers of data processing services. Switching and portability are regulated obligations there rather than negotiated favors.

In the United States there's no equivalent, which means exit terms are whatever the contract says. A buyer who wants structured export in an open format, within a defined window, at no additional charge, has to write it in. Nobody will offer it.

That asymmetry is worth knowing even for a domestic operator, because vendors selling into both markets often already have the capability built to satisfy the European requirement. Asking for it is asking them to extend something that exists rather than build something new, which is a materially easier negotiation.

Where the negotiating room actually is

Most of the advice circulating about AI contract negotiation is generic procurement advice with the word AI attached. The provisions that actually matter are narrower.

Name the model and the channel in the contract, not the product category. A commitment to a vendor's platform is not a commitment to the capability you evaluated.

Get the retirement position in writing. What notice applies, whose schedule governs given how you're buying, and what happens to pricing if the capability retires inside your term.

Separate the compliance layer from the vendor. Organizations that kept regulated workflows in systems they controlled, and used AI vendors for content and personalization, absorbed vendor strategy changes without rebuilding.

That separation is the single most durable structural decision available, and it's covered from the input side in AI marketing inputs and from the records side in the marketing source-of-truth problem.

Define export concretely. Structured, machine-readable, complete, within a stated window, at no charge. Vague portability language is unenforceable at the moment you need it.

Prefer shorter terms while the category moves this fast. Enterprise spend tripled in a year and the buy-versus-build ratio inverted in the same period. A three-year commitment prices a market that changed shape twice during the term.

The governance record that makes this routine

None of this needs new software, and a short record turns a recurring scramble into a scheduled task.

The NIST AI Risk Management Framework, released as version 1.0 on 26 January 2023 and currently under revision, organizes around govern, map, measure, and manage. Applied to vendor dependencies that means a named owner, documentation of what you depend on, monitoring for changes, and a defined response.

Six fields per dependency is enough: the vendor, the model identifier, the purchase channel, the published retirement date, the renewal date, and the export right as written. Anthropic's policy notes that customers can export a usage audit from the console broken down by API key and model, which means the second and third fields are discoverable rather than guesswork for anyone already running workloads.

Review it quarterly against the vendors' published pages. That's the whole discipline, and it converts the version of this problem that arrives as an emergency into one that arrives as a calendar entry.

The adjacent exposures are covered in AI vendor lock-in and the agentic budget black hole.

Editorial field diagram for ai-licensing-trap-enterprise-overpayment-2026
Field diagram
Editorial field diagram for ai-licensing-trap-enterprise-overpayment-2026
Field diagram

FAQ

It varies by vendor and by model tier, and the policies are public. OpenAI's deprecation documentation sets a minimum of at least 6 months for generally available models, at least 3 months for specialized variants, and as little as 2 weeks for preview models it states are not recommended for production. Anthropic commits to at least 60 days' notice before retirement for publicly released models. Both allow faster timelines where safety or compliance requires.

Yes, depending on how you buy it. Anthropic's policy states its published dates apply to Anthropic-operated platforms and that partner-operated platforms including Amazon Bedrock and Google Cloud set their own retirement schedules, so lifecycle status and dates can differ. An organization buying the same model directly and through a cloud marketplace is managing two timelines on one dependency.

That depends entirely on what the contract says, which is why it's worth asking before signing. The commercial terms generally survive a model retirement while the technical foundation does not, so the buyer migrates on the vendor's published schedule. Get the answer in writing on two points: what happens to pricing if the contracted capability retires mid-term, and whether migration support is included or billed as professional services.

In the European Union there is a regulatory framework. The EU Data Act entered into force on 11 January 2024 and became applicable on 12 September 2025, establishing rules for customers to switch between providers of data processing services. In the United States there is no equivalent, so export terms are whatever the contract specifies. Define it concretely: structured, machine-readable, complete, within a stated window, at no additional charge.

Treat long terms with more caution than in other software categories, because the market is still reshaping. Menlo Ventures measured enterprise generative AI spend rising from \$11.5 billion in 2024 to \$37 billion in 2025, and the share of use cases bought rather than built moving from 53 percent to 76 percent in the same period. A three-year commitment prices a market that changed shape twice inside the term.

Six fields per dependency: the vendor, the model identifier, the purchase channel, the published retirement date, the renewal date, and the export right as written in the contract. Most of that is already published by the vendor. Anthropic's documentation notes customers can export a usage audit from the console broken down by API key and model, which makes the model and channel fields discoverable for anything already running. Review quarterly against the vendors' published pages.

Jamie

Online

Jamie: Hi, I’m Jamie. What are you working on?