A content management system (CMS) is sold as the ability to edit. Open it, change it, save it. But if that were the whole product, a plain text file would have replaced it long ago. It sells something else, and the people who named it best weren't critics. They were the vendors themselves.
Susan in marketing
The CMS company DatoCMS wrote a sentence on their blog worth framing: "What AI can't do is give Susan in marketing a usable interface to update the homepage without writing up a Jira ticket."
There's the product. Not editing. A way to skip another department's queue. When marketing wants to change the headline and the dev team has its own backlog two weeks deep, a CMS is the door Susan walks through without waiting. It's an organizational purchase, not a technical one.
And that's exactly why it evaporates in a one-person business. If the owner, the marketing department, and the "dev team" are all you, there's no queue to skip. The door leads to the same room.
The same company that sells CMS software writes, in that same post: "if it's your own website and you write all the content and know how to code, just hard code it. A CMS is overhead you don't need." They throw in internal tools, prototypes, and sites that "genuinely rarely change" too. A vendor conceding an entire slice of the small-project market without a fight. That tells you which market they already consider lost.
Not just them
Squarespace, a platform that lives on monthly subscriptions, published a guide on when it's worth building a site with AI instead of Squarespace. Their conditions: you only need a simple site, and you're not scared of maintaining code. Their counter-argument is honest and worth noting: adding features, keeping things running, and security "become your responsibility." In other words, the platform isn't selling pages. It's selling a person who answers when something breaks.
Joost de Valk built Yoast, the world's most popular WordPress SEO plugin. He moved his own blog off WordPress onto a static generator and wrote: "people never wanted a CMS. They want a website." His next line is even better, because it comes from the person who used to sell those exact features: the SEO features a plugin provides "aren't magic. They're HTML output." On one of his pages the code dropped from 1,400 lines to 180.
The restaurant and the Word document
A story from Hacker News, told by a former agency employee. A restaurant used to manage its menu online by typing it up in a Word document and saving it as HTML. The agency laughed about it internally, then sold them WordPress.
Years later, that same person admitted: the WordPress site was "arguably less useful," and the Word trick was "actually genius, when you have a million more important things to do at your restaurant."
The story leaves us with a test we apply to ourselves: does the new system actually outperform what the client is already doing, or does it just look more professional. Often, the answer is the second one.
Why CMS still wins on the sales floor
If all this is true, why does a content system still get sold to everyone? One comment on that same Hacker News thread explains it better than any analysis could: "A marketing site SHOULD be optimized for the editor."
The platform gets chosen by whoever controls the budget and whose daily work depends on it. Not the visitor. Visitor speed, site cost, and simplicity lose that conversation every time, because the visitor isn't sitting at the table. Another commenter put it even more bluntly: "I don't understand why their requirements should be met over, say, the readers'."
That's not malice, it's structure. But the next time you read another proposal with a CMS line item, it's worth asking whose convenience it's really there for.
What this means for you
If your business has a Susan, a dev queue, and an approval chain, you need a CMS, and we'll point you to webflow.lt, where the same team builds sites like that with Webflow.
If Susan is you, you need a website. Simple, fast, with no doors that lead to the same room.