Publishers rebuilding their content stacks used to be a story about speed and SEO. Increasingly, it is a story about whether the stack can be read by an AI agent at all, and TIME’s newsroom just became the latest proof point.
TIME announced on July 9 that it has moved its digital publishing platform, more than 100 years of archive included, from WordPress onto Contentstack’s Agentic Experience Platform, closing out a four month migration. Michael Mraz, TIME’s General Manager of B2C and Chief Product Officer, said the goal was a system that worked for engineering and editorial teams without forcing either side to compromise: developers keep an API-first architecture while newsroom staff get a publishing workflow built around how stories actually get produced.
The result is not just a faster CMS. TIME has already shipped a chatbot, TIME AI Agent, that answers reader questions from its reporting archive using Scale AI, along with a partnership with TollBit to generate markdown versions of its content that large language models can parse directly, plus in-house workflow agents that handle tasks like content tagging automatically. Contentstack CEO Neha Sampat framed the underlying problem bluntly: organizations rushed to adopt AI without fixing the content infrastructure underneath it first.
That is the industry shift worth naming. The competitive question for publishers and content-heavy brands is no longer which CMS renders pages fastest; it is whether the content layer is structured well enough for an AI agent, whether an internal orchestration tool or an external answer engine, to retrieve and act on it correctly. That is the same infrastructure logic driving the fight over verified data layers underneath AI agents more broadly, and it echoes how customer data platforms are being rearchitected around agentic orchestration rather than simple storage.
Marketing and content leaders auditing their own stack should treat “can an AI agent parse and cite this correctly” as a real technical requirement for any CMS or DAM evaluation now underway, not a future nice-to-have.
Source: Contentstack
