Free as in broken: What the $0 website comparison actually proves

I saw a LinkedIn post last week comparing a $5,000 WordPress build to a static site generated with Claude and served through Cloudflare. Fraction of the cost. Same outcome. WordPress is dead. Long live the AI king.

The framing was not dishonest, exactly. A Claude-generated static site does exist. It loads. It can look decent. Those things are true. The problem is what the comparison treats as equivalent: a product built for longevity, content management, team access, and campaign readiness versus something that works as long as the person who prompted it is still around to fix it. That is not a price comparison. It is two different categories being stacked against each other as though the only meaningful axis is the invoice.

I have had this conversation with clients. Not because they saw this specific post, but because the framing is everywhere and it works on exactly the people it is designed to work on: business owners who do not yet know what the expensive option is actually buying them.

What the invoice does not include

A client came to us running a Wix site she had built herself. It loaded. In a screenshot it looked passable. But there was no structure underneath it: no consistent buttons or fonts from one page to the next, no content model, nothing that resembled an architecture, because nobody had ever designed one. She had assembled a site. She had not built one.

We moved her to WordPress, but the platform swap was not the work. The work was two months spent figuring out an architecture that had never existed: real content types, navigational paths that led somewhere on purpose, a clear call to action on every page instead of whichever one felt right in the moment. Nobody had done that exercise before, not because it was hard to justify but because a $0 build gives you no reason to do it.

The clinic, a laser and skin practice, now averages one to two new leads a day. That number did not come from a nicer template sitting on top of the same content. It came from someone finally answering the question the free version never asked: what is a visitor supposed to do on this page, and does the page make that obvious.

The $5,000 WordPress site is not overpriced for what it is. It is priced for a system a team can own and operate without the person who built it in the room. That is a different product. It costs more because it does more, not because someone is extracting margin from a buyer who does not know better.

The Golf and the Porsche

Nobody cross-shopping a Porsche is looking at Golfs. They are not competing for the same buyer, which means they are not actually competing. The only person who frames them as alternatives is someone selling Golfs, or running a course about how to get a Porsche experience on a Golf budget.

The $0 website post follows the same shape. Here is a cheaper tool doing something that resembles the outcome you want. Why would you pay more? The answer, which the post does not address, is that the outcome you want and the outcome the cheap tool produces are not the same outcome. They look similar in a screenshot. They diverge immediately in use.

This matters because the framing is not neutral. It is designed to make the expensive option look irrational. And if you are a small business owner who does not know what the expensive option is actually buying you, the framing works. That is exactly who these posts are written for.

The tell is in the close

There is a pattern to posts like this. They open with a specific use case: something concrete and legitimate. A static portfolio site. A landing page prototype. A simple brochure build. Then the conclusion expands to cover everything. This replaces your developer. WordPress is dead. Just talk to Claude. The specific case dissolves and the general claim takes its place.

The tell is usually near the end. A course. A workflow template. A "comment Claude" or "follow for more" hanging off the bottom. The post is not a public service announcement about what AI can do. It is a top-of-funnel for something else. That does not make the underlying point wrong, but it does explain why the argument stops exactly where the nuance would start.

What $0 actually costs

A $0 website built without understanding what the business needs from it is not a savings. It is a deferred expense. At some point the business grows, or a campaign demands more than a static page can deliver, or the team realizes nobody can touch the thing without starting over. What looked like a smart shortcut turns out to be a dead end with a clean design.

The cost of a website is not the build. It is the time and opportunity lost when the thing you built cannot do what you actually need. That math does not appear in the post comparing invoice amounts, because it would ruin the comparison.

The businesses that get this right do not buy the most expensive option by default. They buy the right one for where they are going, not just where they are. The difference between those two questions is exactly what the LinkedIn post was designed to make you stop asking.