Claude as a CMS: how we manage websites through conversation

We don't use a CMS. Not in the way you're thinking.

No WordPress. No Sanity. No Contentful. No Webflow. No admin panel with a left sidebar and a WYSIWYG editor that kind of works. Our content lives in a database — Supabase, specifically — and we manage it entirely through Claude.

I tell Claude what I want changed. Claude changes it. That's the CMS.

This probably sounds like a tech experiment. It's not. It's how we run multiple production websites right now, including the one you're reading. And the teams using this system aren't developers. They're business owners, marketing leads, and operations people who talk to Claude the same way they'd talk to a colleague.

What "Claude as a CMS" actually means

A CMS — content management system — is supposed to let you manage content. Most CMSes accomplish this by giving you a web application with forms, fields, buttons, and a preview pane. You log in, click around, type into boxes, hit publish.

We replaced all of that with a conversation.

Want to update the homepage headline? Open Claude, say "update the homepage headline to [new headline]." Done. Claude calls the underlying tools, updates the database, triggers a rebuild, and your site is live with the change in under 60 seconds.

Want to publish a blog post? Tell Claude the topic. Claude writes a draft, you review it together in the chat, make edits conversationally — "make the intro shorter," "add a section about pricing," "that stat doesn't sound right, find a better one" — and when you're happy, Claude publishes it. Title, slug, meta description, tags, publish date — all handled.

Want to see what's on the site? "Show me all our blog posts" or "what's on the services page right now?" Claude reads the content and shows you, right in the conversation.

The headless CMS market is projected to reach $2.55 billion in 2026, growing at 20.8% year over year (Research and Markets, 2026). That growth is driven by the same frustration everyone feels: traditional CMSes are bloated, confusing, and slow. We just took a different exit off that highway.

Why we don't miss the dashboard

Every CMS admin panel is a compromise. It has to be generic enough to handle any content type, which means it's optimized for none of them. You get 47 fields when you need 5. You get a rich text editor that produces messy HTML. You get a media library that turns into a junk drawer by month three.

And then there's the real problem: people break things.

Give a marketing lead access to a WYSIWYG editor and within a month someone has bolded a random word in the middle of a paragraph, tripled the size of a heading, pasted in content from a Word doc that brought along 200 lines of invisible formatting, and uploaded a 14MB hero image that tanks the page load time.

This isn't a knock on marketing teams. It's a knock on the tool. WYSIWYG editors invite fiddling. They put design decisions in the hands of people whose job isn't design, and then everyone wonders why the site looks inconsistent six months after launch.

Claude doesn't have a "make this heading bigger" button. When a team member tells Claude to update content, Claude writes clean, properly formatted content that fits within the design system. The structure is enforced. The branding stays intact. The site looks exactly as designed, every time, because nobody can accidentally break the layout by dragging a text box three pixels to the left.

In 2026, 93% of web designers report using AI tools in their workflow (FixNHour, 2026). The gap we're bridging is: why stop at the design phase? If AI can design it, AI can manage the content that lives inside it — and do it without breaking the design in the process.

You don't need to be a developer

I need to be direct about this because every "Supabase as a CMS" article on the internet is written for developers, and that's not who this is for.

I'm not a developer. I can't write a React component from scratch. I don't know what a webhook does at the protocol level. I built this agency — and this website infrastructure — by working with Claude, not by writing code myself.

The system we use daily:

• Updating content: I open Claude and say what I want changed. In plain English. "Update the about page to mention our new case study." "Change the contact form headline." "Add a FAQ about pricing to the services page."
• Publishing posts: I describe what I want to write, or I paste in notes, and Claude and I shape it into a post together. Claude handles the formatting, the SEO metadata, the publication — I focus on the ideas and the voice.
• Reviewing the site: "What pages do we have?" "Show me the current meta description for the home page." "When was the last time we updated the case studies page?" Claude reads it all and reports back instantly.
• Schema and structure changes: When we need to add a new field to a page — say, an FAQ section that didn't exist before — Claude handles the database change too. I say "add FAQ support to the services pages," and Claude updates the data model, adds the content, and triggers a rebuild. No migration files. No terminal commands. Just a conversation.

The technical setup — database, API, hosting, deployment pipeline — is built once by someone who knows what they're doing (that's the service we provide). After that, day-to-day content management is entirely conversational. If you can describe what you want in words, you can manage your website.

The real power: Claude doesn't just manage content — it works on it

Here's where this goes from "convenient" to "transformative."

A traditional CMS is a filing cabinet. It stores your content and lets you rearrange it. It doesn't have opinions. It doesn't notice problems. It doesn't improve things while you sleep.

Claude is a colleague. It reads your content, understands your business, and actively works to make things better.

Automated SEO optimization. We run a scheduled task — three times a week — where Claude reviews our site's search performance, checks if our content is being cited by AI search engines like ChatGPT and Perplexity, identifies pages that need freshness updates, and pushes minor improvements automatically. Meta descriptions get tightened. Dates get refreshed. Internal links get added between related content. FAQ schema gets added to pages that should have it. All without anyone asking.

95% of ChatGPT's citations come from content updated within the last 10 months (Storyblok CMS Statistics, 2025). With Claude as your CMS, content freshness isn't a quarterly chore — it's automatic.

Content co-creation. When we write a new blog post, Claude isn't just the publishing mechanism — it's the writing partner. It researches the topic, finds current statistics, drafts sections, and formats everything for both human readers and AI search engines. The human brings the voice, the opinion, the experience. Claude brings the research, the structure, and the tireless attention to detail.

Competitive intelligence that acts on itself. Claude monitors what competitors publish, checks whether our content is showing up in AI-generated answers, and flags when we need to respond. When it finds a gap — a question people are asking that we haven't answered — it can draft the content and queue it for review. The CMS isn't waiting for instructions. It's identifying the work that needs doing.

51% of enterprises already have AI agents running in production, and 85% plan to by end of 2026 (Warmly, citing enterprise surveys). Most of those agents do one narrow task. Ours manages the entire content lifecycle — creation, optimization, publication, monitoring, and improvement.

What this looks like for a client

Here's the actual experience when we set this up for a business:

Week 1-2: We build the infrastructure. Database, content schema, website templates, deployment pipeline, MCP connections. This is the technical work — we handle all of it. The client doesn't touch a terminal or write a line of code.

Week 3: We populate content together. Working with the client in Claude, we create all the initial page content, write the first blog posts, set up the SEO foundations. The client sees immediately how the conversational workflow works because they're doing it with us from day one.

Week 4+: The client manages their own content. They open Claude, tell it what they want to change, and it happens. Need to add a team member to the about page? Tell Claude. Want to announce a new service? Tell Claude. Got a blog post idea at 11pm? Start a conversation with Claude, shape it together, publish it before bed.

Ongoing: Claude works in the background. If the client opts into our SEO service, Claude runs automated working sessions — monitoring search performance, refreshing content, optimizing for AI citations, drafting new content ideas. The client gets a Slack summary of what was done and what needs attention. The site gets better every week without the client lifting a finger.

Compare this to the traditional model: hire a web agency to build a WordPress site ($10,000-30,000), then pay a content manager ($4,000-6,000/month) or agency retainer ($2,000-5,000/month) to keep it updated, plus an SEO specialist ($1,500-3,000/month) to optimize it. Our approach collapses all of that into the initial build plus a Claude subscription.

How the technology works (without the jargon)

If you're curious about the system underneath — or if you're the person in the meeting who asks "but where does the data actually live?" — here's the simplified version.

Your website content lives in Supabase, which is a database service used by over 7 million developers, valued at $5 billion, and trusted by roughly 40% of Y Combinator startups (TechCrunch, 2025). It's not a startup experiment — it's serious infrastructure.

Supabase stores your content as structured data: page headlines, body text, images, SEO metadata, FAQ content — each piece in its own field, organized and queryable. Think of it like a very organized spreadsheet that your website reads from.

Your website is hosted on Vercel, which builds static HTML pages from your Supabase content and serves them from servers around the world. The result: your pages load in under half a second, anywhere. No WordPress plugins slowing things down. No database queries when someone visits your site. Just fast, clean HTML.

The bridge between Claude and Supabase is an MCP server — a small piece of software that translates Claude's conversational commands into database operations. When you tell Claude "update the homepage headline," the MCP server handles the technical translation. You never see it. You just see the result.

Total hosting cost for a typical business website: $0/month. Supabase free tier. Vercel free tier. The only ongoing cost is your Claude subscription, which you're probably already paying for.

Who this is for (and who it isn't)

This works exceptionally well for:

Professional services firms — law firms, accounting practices, consultancies, medical practices — who need a polished website that stays current but don't want to hire a webmaster or fight with WordPress. Your office manager can update the site by talking to Claude.

Founders and small business owners who want to control their own content without learning a CMS platform. If you can write an email describing what you want, you can manage your website.

Growing companies that want AI-powered content — not just AI-managed, but AI-optimized. The same system that publishes your content also monitors its search performance and improves it over time. This is the setup for businesses that want to take SEO seriously without hiring an SEO team.

Agencies and studios managing multiple client sites who want a unified, low-cost content layer. We run several sites from a single Supabase project, all managed through Claude.

This isn't the right fit for:

Large organizations with complex editorial workflows — if you need 12 people to approve a blog post through a formal review chain, you need a CMS with workflow management features. Claude can be part of that process, but it shouldn't replace purpose-built approval software at that scale.

E-commerce businesses with thousands of product SKUs — Shopify, BigCommerce, and similar platforms exist for a reason. Product catalog management is a specialized problem. (Though Claude works great for the content marketing around an e-commerce store.)

The design protection nobody talks about

This might be the most underrated benefit, and it's the one our clients mention most after a few months.

When you launch a beautiful website, the clock starts ticking on how long it stays beautiful. With a traditional CMS, every person with edit access is a potential source of visual entropy. Someone pastes from Google Docs and imports hidden styles. Someone changes a font size "just on this one page." Someone uploads an image that's the wrong aspect ratio and the layout breaks on mobile.

With Claude as the CMS, content goes through an intelligent layer that understands your design system. Claude formats text correctly. Claude sizes images properly. Claude maintains heading hierarchy. Claude doesn't let someone accidentally override the CSS.

Your site looks exactly as designed on day one, and it still looks that way on day 365. Not because you locked everyone out, but because the content management interface is smart enough to enforce consistency while remaining completely flexible about what content you publish.

WordPress powers roughly 61.7% of all CMS-based websites (CMS Knowledge Base, 2026). Visit a random WordPress site that's been live for a year and you'll see the visual entropy in action. That's not WordPress's fault — it's what happens when a dumb editor meets a busy team.

What we automated (and what we didn't)

Automation is the word people get nervous about, so let me be specific about what's automated and what still requires a human.

Automated (Claude handles these independently):

• SEO metadata improvements (title tags, meta descriptions)
• Content freshness updates (dates, minor edits for recency)
• Internal link additions between related content
• Schema markup (FAQ, Article, Organization structured data)
• Performance monitoring and reporting
• Competitive content monitoring

Co-created (Claude drafts, human reviews):

• Blog posts and articles
• Page copy changes
• New service or feature announcements
• Content strategy recommendations

Human only:

• Brand voice and editorial judgment
• Business strategy decisions
• Client relationship context
• Anything involving "should we?" rather than "how do we?"

The result is a content operation that runs with maybe 2-3 hours of human attention per week — mostly reviewing drafts and approving strategic recommendations — while the site continuously improves in the background. Compare that to the industry average of 16-20 hours per week for content management at a small business.

Frequently asked questions

Do I need to know how to code to use this?

No. The person who built and manages the Automaton website — the one you're reading right now — is not a developer. Day-to-day content management is entirely conversational. You tell Claude what you want in plain English, and Claude handles the technical execution. The initial setup requires technical expertise (that's our job), but ongoing use requires only the ability to describe what you want.

What happens if Claude makes a mistake?

Claude shows you what it's about to do before it does it. For content changes, you review the text in the conversation before it publishes. For automated updates (meta tags, dates, schema), those are low-risk changes that improve SEO — and Claude reports what it changed in a Slack summary so nothing happens invisibly. The database also supports point-in-time recovery, so any change can be reversed.

Can my whole team use this, or just one person?

Anyone with a Claude account can manage the site — they just need access to the workspace. Team members can update content, publish posts, and review the site independently. Claude keeps things consistent because the design rules are built into the system, not dependent on individual discipline.

How is this different from using AI to write content in WordPress?

Using ChatGPT to write a blog post and then pasting it into WordPress is AI-assisted content creation. What we're describing is AI-native content management — Claude doesn't just write the content, it manages the entire infrastructure: publishing, SEO optimization, performance monitoring, competitive analysis, and continuous improvement. The CMS isn't a place you paste AI-generated text into. The AI is the CMS.

What does this cost?

The initial setup (database, website, deployment pipeline, MCP connections) is a one-time build project — typically part of a website engagement. After that, ongoing infrastructure costs are $0 (Supabase and Vercel free tiers). Your only recurring cost is your Claude subscription, which most businesses are already paying for. If you want the automated SEO and content optimization service (Claude working sessions), that's a separate retainer — but still a fraction of what a traditional SEO agency charges.

Is our content safe? Where does it live?

Your content lives in Supabase, a database platform used by over 7 million developers and valued at $5 billion. Your data is in a Postgres database that you own — not locked inside a proprietary CMS. You can export everything at any time as standard SQL or JSON. If you ever want to move to a different system, your content comes with you. There's zero vendor lock-in.

Published: February 2026. Last updated: April 2026. This system powers automatonagency.com and multiple client production sites.

Related: The five-layer framework for business systems · The creative technologist is the new agency · How we work