From Headless to Agent-Native: The New Way for Content Sites<br>This site works best with JavaScript enabled.<br>all posts
On this page<br>Where this all came from<br>What was promised, and what was actually delivered<br>The partner market and the reality of audits<br>Vendor lock-in that goes by another name<br>When AI arrived: imitation instead of integration<br>A signal worth noticing<br>Why headless CMS is still here<br>What happens next<br>What we're building in response<br>*]:m-0 [&>*+*]:mt-6 [&_p]:text-text-primary [&_strong]:font-semibold [&_strong]:text-text-primary [&_em]:italic [&_a]:text-text-primary [&_a]:border-b [&_a]:border-text-tertiary [&_a]:pb-px [&_a]:no-underline hover:[&_a]:border-text-primary [&_h2]:font-display [&_h2]:font-semibold [&_h2]:text-text-primary [&_h2]:!text-[28px] [&_h2]:!leading-[1.2] [&_h2]:!tracking-[-0.025em] [&_h2]:mt-14 [&_h2]:scroll-mt-24 [&_h2]:[text-wrap:balance] [&_h3]:font-display [&_h3]:font-semibold [&_h3]:text-text-primary [&_h3]:!text-[20px] [&_h3]:!leading-[1.3] [&_h3]:!tracking-[-0.018em] [&_h3]:mt-10 [&_ul]:list-disc [&_ul]:pl-[22px] [&_ol]:list-decimal [&_ol]:pl-[22px] [&_li]:m-0 [&_li]:pl-1.5 [&_li+li]:mt-2 [&_blockquote]:my-8 [&_blockquote]:pl-[22px] [&_blockquote]:border-l-2 [&_blockquote]:border-text-primary [&_blockquote]:font-display [&_blockquote]:italic [&_blockquote]:!text-[21px] [&_blockquote]:font-medium [&_blockquote]:!leading-[1.45] [&_blockquote]:text-text-primary [&_blockquote]:tracking-[-0.015em] [&_blockquote_p]:m-0 [&_blockquote_p]:text-inherit [&_code]:font-mono [&_code]:text-[0.86em] [&_code]:font-medium [&_code]:px-1.5 [&_code]:py-px [&_code]:bg-bg-secondary [&_code]:border [&_code]:border-border-primary [&_code]:rounded-sm [&_code]:text-text-primary [&_pre]:my-7 [&_pre]:bg-bg-secondary [&_pre]:border [&_pre]:border-border-primary [&_pre]:rounded [&_pre]:overflow-x-auto [&_pre]:px-[18px] [&_pre]:py-4 [&_pre]:font-mono [&_pre]:text-[13.5px] [&_pre]:leading-[1.7] [&_pre_code]:bg-transparent [&_pre_code]:p-0 [&_pre_code]:border-0 [&_pre_code]:text-text-secondary [&_hr]:my-10 [&_hr]:border-0 [&_hr]:border-t [&_hr]:border-border-primary ">We're living in an interesting time. That deserves its own conversation, but today I'm focused on delivering maximum signal per unit of time for anyone whose work intersects with headless CMS.
Over the last five years, I've been involved in 30+ projects in this space — building, advising, reviewing. Beyond that, I regularly audit other teams' projects already running in production. This text is written for those familiar with the domain: specific products and mechanics named, no foundational explanations. For those unfamiliar, well, we now have LLMs.
The main thesis of this text is simple. The problems with headless CMS are old, documented, and largely unchanged. What's new is the alternative. Start with an honest map of the market. Most content sites never reach for a headless CMS at all — they run on WordPress, on a site builder, or now on something like Lovable. Plenty of them never needed a CMS in the first place. The headless world is the slice above that: teams whose site outgrew a builder's ceiling and who got pushed onto Contentful, Sanity, or Storyblok because that looked like the only serious option left. Inside that slice, a minority genuinely need what headless offers, and for them it should stay. The rest inherited an architecture built for someone else's scenario — and for the first time, there's a third option between the no-code ceiling and full headless complexity. The numbers below carry the argument; I'll keep my thumb off the scale.<br>Where this all came from
The headless CMS concept appeared earlier than most think. Directus was created in 2004 — by founder Ben Haynes's own account, long before the term 'headless CMS' even existed. The term itself only entered circulation around 2014. But the essence was already clear: separate the content editing layer from the rendering layer.
The idea is correct. Monolithic CMS platforms like WordPress held us hostage to their architecture. Templates, plugins, themes, all fused together. Headless promised stack freedom: pick any frontend, render where you want, scale how you need.
When Contentful arrived in 2013, then Sanity and Storyblok in 2017, they landed in the right place at the right time. The agency market was migrating to Next.js, companies wanted to escape WordPress, and here was a ready solution with a clean dashboard and an API. It sold well. The headless CMS market is estimated at roughly $817M in 2024 and projected to reach $7.1B by 2035 , a 22.6% CAGR according to Future Market Insights.
For its time, it worked.<br>What was promised, and what was actually delivered
The standard sales deck for any headless CMS between 2018 and 2022 looked roughly the same. Omnichannel, developer freedom, scalability, SEO boost, performance, and editors who would never bother developers again.
Let's go through this honestly.
Omnichannel. This is one of the central marketing claims...