Part of: this research — view all 7 rows
As of November 2026, no qualifying statement has been made by a large enterprise. While analysts and commentators are increasingly discussing "memory lock-in"—such as Oliver Wyman's framing of agent memory as a non-portable "book of business" How to avoid vendor lock-in with agentic AI—surveys attribute existing switching friction to agentic workflows, embedded application logic, and provider-tuned prompts, rather than accumulated model context The Switching Cost You Can't See: Why AI Lock-In Moved ... When AI model choices become a switching problem. Resolving this question does not strictly require the arrival of weight-updating continual learning, which remains undeployed at the frontier; persistent context layers and workspace personalization are sufficient if a large buyer explicitly cites them as the reason they will not switch.
The conditions for such a statement are steadily assembling. Vendors are actively deploying personalized agent systems and have a strong incentive to publish case studies highlighting their stickiness. OpenAI, for example, pitches its Frontier platform as building memories from past interactions and lists adopters like State Farm—which alone boasts over $130 billion in annual revenue https://openai.com/index/introducing-openai-frontier/ State Farm® Reports 2025 Financial Results. Anecdotal evidence of memory lock-in is already appearing below the $1 billion revenue threshold, such as Jason Calacanis reporting that he had to restore employees' OpenAI accounts following an attempted migration due to objections over lost accumulated memory Switching AI providers sounds easy. It's not. I canceled my .... Given the thousands of eligible enterprises, it only takes one executive quote in a vendor testimonial or conference talk to trigger resolution.
However, several forces push against an imminent statement. First, enterprise IT leaders are culturally averse to publicly admitting lock-in, typically preferring to project optionality and multi-model flexibility. Indeed, multi-homing is rising, with 37% of enterprises running five or more models in production, and executives at major firms like JPMorgan explicitly advocate avoiding single-provider dependence Banks to AI labs: 'It's complicated' | Banking Brief. Second, labs are actively mitigating lock-in to capture market share from incumbents: Anthropic and Google offer cross-provider memory import tools, and Anthropic's developer memory is designed to live entirely in customer-controlled storage https://platform.claude.com/docs/en/agents-and-tools/tool-use/memory-tool. These bring-your-own-database memory solutions directly undercut the accumulation of non-portable personalization.
Consequently, while the hazard rate is currently low, it is expected to rise steadily through 2027 and 2028 as enterprise agents with persistent memories diffuse and vendors seek out customer testimonials. A median of September 15, 2028 balances the growing deployment of these personalized systems against corporate reluctance to admit lock-in and the ongoing development of memory portability tools. This timing also aligns with the expected timeline of adapter-based personalization costs , while allowing persistent context alone to produce an earlier qualifying statement. I assign a 10% probability of occurrence by March 15, 2027 and 25% by October 15, 2027. The long right tail accounts for the strict resolution criteria—borderline statements citing "integration" or "context" may be rejected as generic switching costs—and the possibility that multi-homing and portable memory architectures prevent this specific form of lock-in from ever materializing. Those constraints put the 75th percentile at September 15, 2030 and the 90th percentile at January 1, 2034.
Set against related questions, the median was held in late 2028 to align with the expected timeline of adapter-based personalization costs , balancing multi-homing against rising memory lock-in.
Ask a followup
Sign in to run · $20 free credit, no card · every claim cited