The seven AI vendor exit clauses that decide whether you can leave

ABBY

This is Agent Mode AI. I'm Abby. Two of the largest standalone enterprise agentic AI vendors moved into platform parents in eight weeks at the end of 2025. ServiceNow completed its Moveworks acquisition in December 2025 against the originally-announced two point eight five billion dollar consideration. Automation Anywhere closed its Aisera acquisition on the eleventh of November 2025. Today we're walking AM-145. Switching AI vendors in 2026 is a contracts problem before it is a tech problem, and seven clause families repeatedly create the lock-in most enterprises only discover at year two of the relationship.

AVERY

I'm Avery. Why is the contract layer the binding one in 2026.

ABBY

Three forces converged. Vendor consolidation accelerated. ServiceNow and Moveworks, Automation Anywhere and Aisera, and the broader pattern across the second half of 2025 placed existing customers on the acquirer's renewal calendar with the acquirer's master service agreement template waiting on the other side. Model deprecations became a recurring contract event. OpenAI retired the GPT-4 base model in mid-2024 and has continued a quarterly deprecation cadence. Anthropic publishes a model lifecycle policy that puts most production model versions on a twelve-month observable horizon. Google Vertex AI tracks similar cadence. And the first wave of multi-year enterprise agentic AI contracts is approaching renewal. Deals signed in 2024 are hitting their first renewal cycle through 2026 and 2027. Some of those customers have learned the optimistic adoption deck Klarna walked back on the eighth of May 2025, reverting from seven-hundred-agent automation to human agents in customer service, is the modal trajectory rather than the exception.

AVERY

Clause one. Data-portability scope.

ABBY

Most enterprise master service agreements commit to exporting customer data on termination. The procurement question is what the contract defines as customer data. Common scope language includes prompts, completions, and uploaded documents. Common exclusions, sometimes explicit and sometimes by silence, include derived embeddings, retrieval indices, fine-tuned model weights, persistent agent memory, conversation traces, and intermediate planning state. The exclusions are precisely the categories that took the most operational effort to build, and they are the categories that make the agent useful on day one of the successor platform. The redline language defines customer data to include all customer-specific state produced by the system during operation, including derived, embedded, indexed, and intermediate forms.

AVERY

Clause two. Model-deprecation rights.

ABBY

Vendor terms commonly reserve the right to retire underlying models with advance notice. The notice period varies. Microsoft's Azure OpenAI model retirement policy commits to specific timelines and at least one alternative model during transition. Many smaller vendors are silent. Without a contractual minimum, ninety-day notice is operationally sufficient for the vendor and operationally inadequate for an enterprise running a regression suite, security review, and governance sign-off against the deprecated model. The redline asks for a contractual minimum notice period. Twelve months is the asking number; six months is the floor. Plus parallel availability of the deprecated and successor model for a stated overlap window, and a documented mapping of deprecation-driven prompt changes the vendor will provide rather than push to the customer.

AVERY

Clause three. Sub-processor expansion.

ABBY

Vendor master service agreements typically include a sub-processor list that may be updated by the vendor during the term. The customer's recourse on disagreement is usually a termination right with limited compensation. Agentic AI sub-processor lists include not just infrastructure providers but model providers, vector database providers, and increasingly third-party Model Context Protocol server operators. A vendor that adds a new model provider mid-term has materially changed the system the customer signed for. The redline. Sub-processor changes affecting model providers, jurisdictions outside the term-period commitments, or categories of processing not covered by the original assessment require customer consent rather than just notification. For lower-impact changes, a documented objection-and-cure period before changes take effect.

AVERY

Clause four. Output-ownership ambiguity.

ABBY

Who owns the agent's output, and who is on the hook for intellectual-property infringement claims arising from it. Vendor terms differ. Microsoft's Customer Copyright Commitment indemnifies customers against third-party copyright claims arising from the output of certain Copilot products under specified conditions. Google's generative AI indemnification for Vertex AI is similar in shape. Smaller vendors and platform parents that have absorbed agentic-AI startups are commonly silent or carve out broader exceptions. The redline. Explicit ownership of customer-derived output by the customer, vendor indemnification against third-party intellectual-property claims subject to documented use within the agreed parameters, and a defined notification-and-defense protocol when claims arise.

AVERY

Clause five. Pricing-tier rebalancing.

ABBY

Most agentic AI commercial contracts in 2026 are token-metered with enterprise minimum commits and discount tiers layered on top. The risk is not the published rate. It is the vendor's reserved right to revise the rate-card on advance notice, and the fair-use definitions that reset on renewal. A pilot's token-per-action profile understates production by a wide margin, and adoption-volume forecasts built on pilot data routinely miss by five-to-ten-times at scale. Source: our-estimate. Once volume deviates, the vendor's rate-revision right turns the contract into a metered one without a renegotiation event. The redline. Rate-card stability for the contract term, a usage-cap notification protocol that triggers escalation rather than invoice surprise, and a fair-use definition fixed at signature rather than reset on renewal.

AVERY

Clause six. Agent-uptime service-level definitions.

ABBY

Standard software-as-a-service service-level agreements define uptime as the application programming interface responding within latency bounds. For an agentic system, the operational question is not whether the model interface is up. It is whether the agent, including its retrieval, tool integrations, planning loop, and approval-gate execution, is functioning. A ninety-nine point nine percent model-availability service-level can coexist with frequent agent failures driven by retrieval timeouts, tool-call errors, or context-window limits the service-level does not cover. The redline. Agent-level service-level definitions that measure successful task completion, not just model interface uptime. Where the vendor argues the customer's tools and integrations are out of scope, separate the vendor-controlled portion of the agent stack from the customer-controlled portion and write service-levels against each.

AVERY

Clause seven. Audit-evidence retention.

ABBY

Article 16 of the EU AI Act, applicable to deployers of high-risk AI systems from the second of August 2026, requires deployers to operate the system in accordance with the provider's instructions and to retain logs for at least six months. The deployer cannot satisfy the retention obligation if the vendor terminates access to the audit substrate at contract end, or if the export format does not satisfy the Article 12 record-keeping structural requirements. The redline. A contractual audit-log retention obligation that extends past contract termination by at least the regulatory floor — six months for Article 16, longer for sector retention such as the six-year Health Insurance Portability and Accountability Act requirement and the seven-year Sarbanes-Oxley requirement — in a documented machine-readable format compatible with the fourteen-field Article 12 audit substrate. The export must include provenance, the planned-versus-executed action distinction, and policy version stamps that bare prompt-and-response export does not.

AVERY

The procurement playbook.

ABBY

Three artefacts run in parallel during a live procurement. The sixty-question agentic AI request-for-proposal surfaces the vendor's posture before contract drafting begins. Section five asks the exit-and-lock-in questions whose verbal answers should appear later as contract language. The eight-provision exit-clause framework translates the verbal commitments into binding contract language. And the AI master service agreement red-team checklist, RES-005, walks the seven clauses against vendor paper before signature, with the redline language for each clause and the priority order the procurement team should ask in. The seven clauses in this episode are the procurement-side red flags. The eight provisions are the legal-side enforceable form. They map to each other.

AVERY

Change of control.

ABBY

Two questions before signature. Does your master service agreement require notification on change of control. Does it grant termination-for-convenience rights at preserved pricing on change of control. Without the first, you can be moved onto the acquirer's terms without a contract event you control. Without the second, the acquirer can repaper you at their pricing on the next renewal. The Moveworks-ServiceNow and Aisera-Automation Anywhere deals from late 2025 are working examples; existing customers landed on the acquirer's renewal calendar with the acquirer's template waiting on the other side.

AVERY

Final word.

ABBY

The technical team will get blamed for what is, in fact, a procurement-and-legal failure that occurred before the first agent was deployed. The seven clauses are the procurement-deck checklist; the redline language for each is in RES-005, the AI master service agreement red-team checklist. The Moveworks and Aisera announcements, the OpenAI and Anthropic and Google Vertex deprecation pages, the Microsoft Azure model retirement policy, the Microsoft Customer Copyright Commitment, the Bloomberg Klarna reversal, and the EU AI Act Articles 12 and 16 are linked at agentmodeai dot com slash holding slash question mark claim equals A-M one four five. AM-145 is Holding. The next review is on the sixth of July 2026.

AVERY

Holding-up. See you next Sunday.