What's a CMS in the Era of Agents?

The session shows exactly how the migration worked, where the agents needed correcting, and what it would take for your team to make the same move. Ben Hofferber, SVP of Agentic Product Engineering, leads the walkthrough.

Rangle is the team behind Nike's personalized AI shopping assistant and Sanofi's Elements Design System, and the system in the session publishes the very page you're reading: rangle.io has run on agent-published content since May.

What's in the recording#

• Three checks to run before you leave your CMS: can an agent already edit your content faster than your CMS UI, is your team fluent enough to work this way, and how much of the feature set you pay for do you actually use.
• The real cost breakdown: what the migration actually cost in time, tokens, and engineering hours, and how that compares to the three months and three developers our last migration took. The numbers, not the pitch.
• The gotchas and the checks that catch them: schema drift, redirect debt, content quality when agents write, and the validation gates that keep each one out of production.

Who it's for#

You manage a content platform for a mid-to-large organization. Your CMS contract is up for renewal, or you're evaluating a migration. You've heard the AI hype and you want production evidence before you make a call. Engineering leads, heads of marketing, technical founders: what you have in common is that you're the person who has to live with the decision.

You'll leave with a clear framework for deciding whether an agent-based content architecture is right for your team, including the cost model, the timeline, and the checks that keep agent-written content production-safe.