In Episode 42 of Beyond the CMS, host Chris Bryce, founder of Dotfusion, is joined by Joel Varty, CTO at Agility CMS. Joel recently celebrated his 21st anniversary at Agility — a bootstrapped, Canadian headless CMS that has never taken a dollar of venture capital and still counts customers from nearly its founding days. That long arc gives him a uniquely grounded perspective on where the CMS industry has been and where it is actually going, as opposed to where investors want it to go.

The conversation opens on a question that sounds simple but isn't: what is headless, really? From there, Joel walks through why enterprises are finally abandoning monolithic DXP platforms en masse, why the composable model the MACH Alliance promotes is different from those platforms trying to rebundle the same features under a new name, and why the best AI workflows are being built around headless systems right now. He also shares a live demonstration of publishing a personal blog post directly from Claude on his phone, straight into Agility CMS, using an MCP server connection and a pre-built skill — no copy-paste required.

Key topics include:

• Why bootstrapped beats venture-funded for CMS longevity: Agility has never taken outside capital, which means product decisions are driven by customer needs rather than growth-at-all-costs mandates. Joel argues this is directly why their average customer lifetime exceeds 15 years.
• Headless as the AI-ready architecture: Adding AI onto an API-first, headless system is dramatically easier than retrofitting it onto a monolithic DXP. Every headless CMS has been able to take advantage of MCP servers and AI agents specifically because content and code are already separated.
• MCP: the layer that teaches AI how to use your tools: The Model Context Protocol is not just a wrapper on an API. It contains human-readable instructions that explain what every field type actually means — so AI agents can act on your CMS without a developer interpreting the API for them.
• Skills as the next standard for AI agents: Joel predicts that Claude-style "skills" — pre-configured prompt contexts scoped to a specific task like "create blog post" — will become a universal standard. His team has already built org-wide skills that pull simultaneously from Jira, Figma, and Agility MCP servers.
• Content Operations, redefined: The content operations pipeline has always been idea to draft to CMS to publish. What's changed is that AEO (Answer Engine Optimization) and GEO have replaced the SEO ranking game as the reason content quality matters. AI models cite based on truth and structure, not keyword density.
• Why DXPs are creating the problem headless was built to solve: Several major DXP vendors are now acquiring personalization, search, and analytics tools to capture more revenue — which is exactly the monolithic bloat that composable architecture was designed to escape. Joel says Agility is staying focused: content, done exceptionally well.
• Data sovereignty as an enterprise buying signal: Canadian government websites, Scotiabank's Latin American properties, and Cineplex are all on Agility in part because of data residency control. With CFOs and legal teams now actively asking where AI tools process their data, this is becoming a board-level conversation, not just an IT checkbox.
• The CMS as a diamond: Agility's product philosophy is subtraction. Their director of product frames the CMS as a diamond — and the job is to keep chipping edges off. Every recent update removes steps rather than adding features. Joel's example: a locales update that reduced the number of clicks for multi-locale teams, which sounds minor until you manage 30 locales like Epson does.
• Stop making marketers fill out fields: The long-form piece is the only thing a marketer should have to write. AI should handle field population, metadata, and content model mapping automatically. When publishing is that frictionless, teams actually produce more content — Joel went from occasional to blogging two or three times a week.

Joel's bottom line is that the CMS is not where AI should live. AI should live in the agents your teams already use — Claude, ChatGPT, Gemini — and those agents should connect to your CMS through MCP. The CMS is the foundation. The cleaner and more structured that foundation is, the more powerful every AI workflow built on top of it becomes.

🎧 Listen now and join the conversation!