What AI website builders do well, and where they leave you
We build one of these. Here is the part the demonstration does not show.
Describe your business in a few sentences, wait, and a working website appears. The first time you see it happen it is genuinely startling — and the startle is the problem, because it makes the next question hard to ask: what is this good at, and what is it not?
We build one of these, so treat what follows as interested testimony. We have also watched enough people get stuck to know where the floor gives way.
What these tools are genuinely good at
Getting from nothing to something. The hardest version of a website is the first one, and that is exactly the part this removes. A business that has put off a site for two years can have one this afternoon.
The boring pages, done consistently. Service pages, a contact page, legal text, the same information formatted the same way in three languages. This is work that humans do worse as they get more tired, and software does identically at page forty.
Changes small enough that nobody would schedule them. A price, a phone number, an opening hour. On a traditional build these accumulate into a quarterly batch, because each one costs more in coordination than in work.
Where people actually get stuck
Not where they expect. The failures are rarely "the AI made an ugly page".
The second change. The first version arrives and it is good. Then you want something specific — this section above that one, this word not that word — and you discover how precisely you are able to say it. People who can describe what they want get what they want. People who cannot, accept what they were given. That is a communication skill, and it is unevenly distributed.
The thing with rules. A site that displays information is one problem. A site that decides something — availability, pricing that varies, stock, anything with a rule underneath — is a different problem. Ask for it in a sentence and you get something that looks right and is wrong in the third case you try. Software with rules needs a specification, and a specification is not a description.
Ownership of the strange parts. Every business has something unusual: the booking that has to skip Wednesdays, the customer group that pays differently, the certification that must appear on one page only. These are individually small and collectively the reason your business is not a template.
Nobody owning the result. This is the one that actually bites. With an agency there is a person accountable for whether the site works. Generate a site alone at midnight and the accountable party is you, holding something you did not build and cannot fully inspect.
How to tell in advance which side you are on
Three questions, answerable before you start.
Is your site mostly nouns or mostly verbs? Nouns — who you are, what you offer, where to find you — are what these tools do well. Verbs — book, calculate, reserve, compare, pay-if-then — are where rules hide.
Could you brief it in one page? If yes, you will get a good result. If your description keeps sprouting exceptions, those exceptions are the project, and they need someone to own them.
What happens when it is wrong? A wrong opening hour is a correction. A wrong price on an order is a refund and an apology. The higher that cost, the more you want a human in the loop — whichever tool builds the page.
Where we are the wrong answer. If the exact arrangement of the page is what you sell, or your site has to run rules that change per customer, a subscription that builds from a description is not your best option — and a demonstration will look fine right up until it isn't. What ChatBuild Web actually covers.
Five questions to ask before you commit
Ask these of any tool or supplier, ours included. The answers take a minute and they are the difference between choosing and hoping.
Can I export my content? If the answer is a screenshot or a support ticket, your text lives in someone else's product.
Is the domain registered in my name? Not pointed at them — registered to you. This is the single hardest thing to undo later.
What does a change cost, in money and in days? Every route can make a first version. They differ almost entirely on the second one.
Who is accountable if the site is wrong? Not who fixes it: who is responsible for noticing. On a self-serve tool that person is you, which is fine as long as you know it.
What happens to the parts with rules? If your business has availability, variable pricing or stock, ask specifically how those are handled rather than whether they are supported.
A supplier who answers all five plainly is worth more than one with a better demonstration.
The honest summary
AI website builders have compressed the part of web work that was mostly typing, and left almost untouched the part that was mostly deciding. The first version is nearly free. Knowing what should be on it is not, and never was.
That is not a reason to avoid them. It is a reason to spend the time you saved on the thing that still needs you: the paragraph about what your business does, the prices you are willing to publish, and the sentence explaining why someone should choose you rather than the identical business two streets away.
The copy is where this shows up first — see what to keep and what to rewrite in AI-written website text. And if everything ends up built the same way, being recognisable stops being a design preference and becomes the point.
Frequently asked
- Can an AI-built website rank in Google?
- Ranking depends on what the page says, how fast it loads and whether other sites reference it, not on which tool produced the HTML. An AI-built page with thin, generic copy will struggle for the same reason a hand-built one would.
- What happens if I outgrow an AI website builder?
- Ask before you start, not after: can you export your content, and is the domain registered to you? Those two answers decide whether outgrowing a tool is a migration or a rebuild.
Sjors Hooijen Builds ChatBuild and writes about getting a business online without turning it into a project. Questions about this article? Email hi@chatbuild.com.