When is an AI-built site enough?
Site builders have reached the point where an introductory website really can be put together with them. The question is how far they take you.
Let me start at the end, because that is the honest way round: if an introductory site is what you need, do not pay more for it. A few pages, text, images, a way to get in touch — a site builder handles that faster than a developer would, and afterwards you can edit it yourself. There is nothing for me to do there.
The limit is not where most people look for it. Not in the appearance, and not in the text — a site builder does both properly. The limit is where the site no longer just has to appear, but has to do something.
What a site builder genuinely solves
The surface: layout, colours, type, where the images sit. A form that sends an email. Pages you create yourself. A responsive display that works on a phone. Hosting you never have to think about.
That list is longer than many assume, and for a business it is often exactly what is needed. For a trade business, a holiday rental or a service provider who arranges things over the phone, the job of the website is that people find it and call.
Where it stops
When money moves through it. Payment itself can be wired in, but the chain that follows cannot: issuing the invoice, opening the access, sending the notification, and making sure all of it holds even when one step stalls. That is not a button, it is behaviour.
When something already running has to be connected. The accounting software, the booking tool, the mail system, the stock list — separate systems with their own rules. Connecting them is not a settings question.
When the content has a complicated shape. Twenty staff, a hundred priced services, changing opening hours — entering that once is not the problem; keeping it current is. What is needed there is not a page but an editing screen that follows your logic, not a generic template's.
When it would have to be moved. Text and images can usually be exported; the structure rarely can, because it lives in the platform's own format. There is a separate piece on that, going through who your website is tied to.
- WHAT A SITE BUILDER SOLVES
- Layout · Text, images · A form · Hosting
- THIS IS WHERE IT ENDS
- WHAT RUNS BELOW THE SURFACE: The chain after payment · Existing systems · An editing screen · Getting the data out
- The difference
- The top row is about appearance, the bottom one about behaviour. A site builder solves the first — the second cannot be clicked together.
The question that settles it
Not which option is more modern, and not which is cheaper. This one: what happens when somebody uses the site?
If the answer is that they read it and call — a site builder is enough. If the answer is that they pay, book, log in, or start something that another system then has to act on — the site is only the surface, and most of the work sits underneath.
My own work is the second kind, and I take on introductory sites when something will be needed underneath them later. If nothing will be, I say so — the page on automated systems covers where that line runs. One thing I will say here too: if your site does not have to do anything, do not pay for it to be able to.
Questions on this
Is a site builder enough for an introductory website?
Often yes. If the job of the site is to introduce you, list the services and give a way to get in touch, a site builder handles that, and faster than a developer would. There is no reason to pay more for it.
When is it not enough?
When something has to happen below the surface. Card payments, automatic invoicing, granting and revoking access, handing data to a system you already run — none of these are about appearance, and none can be clicked together. At that point the site is only the surface; most of the work sits underneath.
Can such a site be moved later?
Partly. Text and images can usually be exported; the structure rarely can, because it lives in the platform's own format. Moving means the content comes along and the structure gets rebuilt. Worth checking at the start, not when it becomes urgent.
How much more expensive is custom development?
By an order of magnitude — which is exactly why it is not worth starting if a site builder solves the job. The question is what is needed. For an introductory site custom work is wasted money; for a payment chain a site builder is not an answer.