Claude and ChatGPT Make the Headless CMS Obsolete for Independent Publishers
For a few years the headless CMS was the grown-up choice for a serious publisher. Keep the words and images in one structured store. Send them out by API to the website, the app, the newsletter, the partner feed. Let the front end change every season while the archive stays put. We covered the case for it in What Is a Headless CMS? A Publisher’s Guide and walked through one of the better tools in Sanity CMS for Publishers.
That case has fallen apart, and fast. The reason sits in the chat window most editors already have open: Claude and ChatGPT, wired straight into the places where content lives.
What publishers were paying for
Strip away the vendor language and a headless CMS sold a small press three things.
A clean content model. Every article broken into typed fields, so a headline, a pull quote and a byline could travel anywhere without dragging page layout along.
An API. One endpoint that a website, an app or a syndication partner could pull from.
An editor. A friendly screen where a writer or a copy desk could work without touching code, priced by the seat.
Each one cost money, and the API layer cost developer time on top. For a five-person magazine or a one-person imprint that bill was the whole argument. You paid for the plumbing so the work could go everywhere.
The assistant is now the channel and the editor
Anthropic’s Model Context Protocol gave AI assistants a standard way to plug into outside systems, and OpenAI adopted it too. A publisher can now connect Claude to a plain WordPress install, a Git repo of Markdown files, Google Drive or a database, and the assistant reads, edits and publishes there directly.
Run the three things through that.
The content model matters less. Language models read prose, messy HTML and scanned PDFs and pull out what they need. A ten-year archive of WordPress posts with inconsistent categories is perfectly usable by an assistant. Nobody has to remodel it into typed fields first.
The API is no longer scarce. Anything with an MCP connector is reachable, and connectors exist for nearly everything a small publisher already runs. The headless vendors know this, which is why Contentful, Sanity, Storyblok, Strapi and the rest all shipped MCP servers of their own. Once your premium content platform and your free WordPress site answer the same plug, the premium is hard to defend.
The editor is a chat box. An editor asks for every book review from 2019 to get a fresh summary paragraph, or the spring catalogue copy in German, or the dead links fixed across a whole section. The assistant does it through the connector. Seat pricing for an editing screen stops making sense when the screen is barely used.
And the developer glue went cheap. Coding agents write a static front end, a content schema and a deployment pipeline in an afternoon. The integration work that used to justify an agency retainer is now the easy part.
The vendors are being folded into bigger platforms
The business side tells the same story. Salesforce bought Contentful, the category leader, and closed the deal on September 1, 2026, for about half of what Contentful was valued at in 2021. It wanted a content layer for its own AI agents. Figma bought Payload in 2025 to power Figma Sites, and Payload’s hosted cloud stopped taking new projects. The independents still standing have renamed themselves as content platforms for the AI era.
For a publisher choosing tools that is the important part. The standalone headless CMS you sign up with today may run on somebody else’s roadmap next year.
What a small publisher should do instead
Keep the content somewhere boring and portable. WordPress, a Hugo site built from Markdown, a well-organised folder in Git. These formats outlive vendors, and an assistant can work with all of them. We made a similar point in Choosing a CMS Is an Editorial Decision: the tool should follow how you edit, not the other way round.
Hold on to the controls that protect the work. Drafts, revision history, roles and the ability to roll back a bad change matter more now, because an assistant can edit a hundred posts in a minute. WordPress already has these. A Git repo has them by design.
Spend the money you save on writers.
That’s where a publisher’s value always was. The plumbing was never the product, and now it costs almost nothing.
There’s a market-side version of this argument on Market Research Media: Claude and ChatGPT Integrations Killed the Headless CMS Market.