TechCrunch reported on September 20 that AI leaders were arguing over whether the industry could “pace the frontier.” Anthropic CEO Dario Amodei called for slowing capability growth by one to two years so safety work could catch up. OpenAI, Anthropic, and Google had also been discussing an industry-funded standards body for powerful AI systems.
For a business already using those systems, the debate raises a practical issue: the cost of changing course when a vendor becomes risky, expensive, or misaligned with company standards. A useful AI system can become embedded in daily work, making replacement a migration project.
Find the dependencies before renewal
In the TechCrunch discussion, Sean O’Kane argued that consumer choice exerted limited pressure on the market. His example was companies being unlikely to switch from OpenAI’s Codex to Anthropic’s Claude Code over disagreement with OpenAI’s conduct. That is an attributed market judgment, worth examining against your own ability to switch.
Prompts, work history, automations, and employee habits can tie a workflow to a vendor. Consider a team spending six months building around a model-specific feature while leaving the process undocumented. A pricing or policy change would then require reconstructing both the integration and the way people use it.
Start a dependency map with the systems used in daily operations. Record the process each supports, the data it touches, the outputs it influences, its owner, and the difficulty of replacement in 30 days. The map should distinguish inconvenience from a workflow that would stop functioning.
Test an exit path
Before renewal, check whether work products, prompts, evaluation history, and audit logs can be exported in a usable format. Try the export. Choose a representative task and determine what another system would need to complete it, including human review and permissions.
Document which parts of the process transfer and which depend on the vendor’s interface or model-specific behavior. Sensitive tasks may need a backup procedure that people can run while a replacement is evaluated. Name the person with authority to pause, restrict, or replace the tool if risk changes.
A hard-to-replace tool deserves closer review because a decision to leave may take time to execute. An agent that can change records or send messages also needs clear limits during any transition. Keep those limits attached to the assignment so that they survive a vendor change.
Nvidia’s Jensen Huang has argued for continued rapid development, countering Amodei’s proposed slowdown. A business can plan for vendor changes under either approach. Your team can already check its exports, document its dependencies, and rehearse a replacement for one important workflow. That produces evidence about how much freedom the business actually has.