The CMS Is Dying. AI Just Made It Obvious.
Why are we still building web pages on request? Flat HTML is faster, cheaper, and harder to hack, and AI just removed the last good reason most small business sites needed a CMS.
I have built on WordPress. I have built on Drupal. I have built on more content management systems than I can name, going back to the first dot-com run. They paid a lot of my bills.
And I'm starting to think the CMS is dying.
Not tomorrow. Not for every site. But for a lot of the websites I see every day, the CMS is a heavy machine doing a light job. AI is about to make that very obvious.
What actually happens when someone loads your page
Here's what a typical WordPress site does when a homeowner clicks your link.
The server wakes up. It runs PHP. It loads a pile of plugins. It asks a database for your page. It stitches a header, a footer, a sidebar, and your content together. Then it sends the result.
For a page that hasn't changed since Tuesday.
It does that for every visitor, every time. We bolt on caching plugins to skip some of that work, which is a fix for a problem we chose to have.
Why are we still building pages on request?
Flat HTML is faster, cheaper, and harder to break
A flat HTML page is already built. The server just hands it over. No PHP. No database. No plugins waking up.
That gets you three things.
Speed. There is nothing to assemble, so there is nothing to wait for. You can serve it from a network of servers close to the visitor. Fast pages rank better and convert better. Every SEO I know has been chasing that for a decade.
Security. A flat file has no login page to brute-force, no plugin to exploit, no database to inject. WordPress had 11,334 new vulnerabilities reported in 2025, up 42% from the year before, according to Patchstack. A folder of HTML files has a much smaller attack surface. When I think about protecting a contractor's business, that matters more than anything else on this list.
Cost. Static hosting is cheap, often free. No plugin licenses. No database server. No emergency calls because an update broke the theme.
None of this is new. HTML is still HTML. It's the same thing I was writing in the 90s. The fundamentals never left.
So why did we all use a CMS?
One reason: editing.
The business owner needed to change their hours. The office manager needed to post a seasonal special. Nobody wanted to call a developer for a one-line change, and nobody should have to. The CMS gave non-technical people a login and a text box.
That was a good trade for twenty years. You accepted the weight of the system in exchange for the ability to make your own edits.
That trade is changing.
What AI changes
Here's how I can run a site now. The whole site lives in GitHub as plain files. When something needs to change, I ask Claude to make the change. It edits the page. I look at what changed, line by line. If it looks right, I publish it.
That workflow gives you things a CMS never did well.
- Every edit has a history. Who changed what, when, and why.
- Every mistake has a rollback. One step back and the old page is live again.
- You review before it goes live. Not after a customer spots the typo.
- There's no lock-in. It's just files. Move them anywhere.
The editor used to be a login screen. Now the editor is a conversation.
The numbers are starting to move
I'm not the only one seeing it. According to W3Techs, WordPress ran 43.6% of all websites at its peak in January 2025. As of October 2026, it's down to 40.2%. That's the first real decline in its history.
And here's the part that caught my eye. The biggest winner isn't Shopify or Wix. It's websites with no CMS at all. Sites with no detectable CMS absorbed roughly 90% of the share WordPress lost.
That's a lot of people quietly deciding they don't need the machine anymore.
Where a CMS still earns its keep
I'm not going to pretend this fits every site. That would be its own kind of hype.
A CMS still makes sense when:
- You have a big team of non-technical people publishing every day
- You run real e-commerce with inventory, checkout, and accounts
- You have members, logins, or content behind a paywall
- Your content truly changes by the minute
And to be fair, this blog runs on Ghost. That's a CMS. It's a lean one, and it's on my list to rethink too.
But most small business sites don't look like that list. A contractor's site is a homepage, a set of service pages, service areas, reviews, and a contact form. That content changes a few times a month, not a few times a minute. The contact form still needs somewhere to send leads, and that's a solved problem. Everything else can be flat.
The catch nobody talks about
Here's the part I want to be clear on. AI didn't remove the need for someone who understands the code. It made that person more important.
When Claude edits a page, somebody still has to read the change. Somebody has to know whether that schema markup is right, whether the form still posts, whether the page still works on a phone. AI can write the code in seconds. Understanding what got built is still the job.
That's why I don't think this is a do-it-yourself story for most contractors. It's a story about what your web partner should be doing. Simpler sites. Faster sites. Fewer things to hack. And a real person checking every change before it goes live.
Where I land
For a long time, the CMS was the price of letting regular people edit their own websites. AI is lowering that price to almost nothing.
When you don't need the machine to make edits, you have to ask what else it's doing for you. For a lot of sites, the honest answer is: slowing them down and giving attackers something to aim at.
Keep it simple. Make it look beautiful. Have it work.
Turns out flat HTML was good at all three the whole time.