{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Beyond the CMS - A Content Management Podcast","title":"Beyond The CMS #42 - Chris Bryce (Dotfusion) with Joel Varty (Agility CMS)","html":"","width":"100%","height":180,"duration":2434,"description":"\nIn 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.\n\nThe 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.\n\nKey topics include:\nWhy 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.\nHeadless 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.\nMCP: 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...","thumbnail_url":"https://img.transistorcdn.com/FO-MfURcPdfZAybU3p1Sq0_mV2DxhS0owOU508deeIY/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9lNjcx/M2I0M2FjODk0Yjg4/ODdjZDJkMDM1NWE3/ZGE0ZS5wbmc.webp","thumbnail_width":300,"thumbnail_height":300}