An AI website builder takes a description of a business, what it offers and who it is for, and returns a site: a home page, a few inner pages, a contact form and somewhere to host it. The result is usually good to look at, and it arrives in minutes rather than weeks.
That changes who can have a website and what the first draft costs. It does not change what a website has to do once it exists. It still has to be found, load quickly on the phones its visitors actually carry, work for people who do not use a mouse, and be changed by someone when the business changes. The builder does the first draft of the look. The rest is still somebody's job.
What it is for
A site whose work is to explain, reassure and take an enquiry. A small business that needs to look credible this week. A landing page for an idea, so you can test whether the message lands before anything is built behind it. A portfolio, an event page, a page for one product.
It is also a fast way to explore a direction. Three generated versions of a home page will settle an argument about layout that a written brief would not.
Who it suits
- Owners of small businesses, and founders, who need a presence and have no developer.
- Freelancers and small agencies who sell websites. For them a builder is two things at once: a faster way to produce the first draft, and a threat to the cheapest end of the work, because a client can now get that draft without them.
- Anyone testing a message, where the page is an experiment with a life measured in weeks.
How to tell this is your category
- What you describe is pages and what is on them, not what a visitor can do.
- The finished thing is judged by how it looks and reads. Nobody signs in.
- You start from words. If you start from a picture of the screen you want, that is screenshot to app, which has costs of its own.
- If you find yourself describing accounts, saved data or payments, you have left this category. That work sits on the Prompt to app rung.
What it costs you later
The layer page covers what every tool on this rung shares: the rebuild when you need behaviour, the export question and the change request in month six. These are the costs particular to a site built from a description.
- Copy that fits the layout and says nothing. A generated site comes with words, shaped to the design rather than to the business. They describe a business like yours, not yours, because nothing in a short description says what makes this one different. Replacing them is the work that makes the site worth visiting, and the builder cannot do it for you, because it does not know what you know.
- Search is structure, not tags. A builder can fill in a title and a description for every page. That is not the same as being found. Search rewards one clear subject per page, headings that say what the page covers, a description written for that page rather than for the template, and pages fast enough that people stay on them. Those are decisions about content, and a builder will not make them for you.
- Weight you cannot see in the preview. The preview runs on a fast connection and a large screen. Your visitors may be on a mid-range phone, on metered data, somewhere the connection drops. A full-width hero image or an embedded video can leave a page blank for seconds before anything shows. Load every page on a real phone over a slow connection, and measure it. Core Web Vitals explained covers what to measure.
- Access belongs to the owner, not the tool. Where a site has an accessibility obligation, it falls on whoever owns the site, whatever made it. Tab through every page. Check that images carry text alternatives that say what they show, that headings run in order, and that text has enough contrast with its background. An automated checker catches part of this, never all of it.
- The quote has to name the work the tool does not do. For anyone building sites for clients, the visible part of the job is now cheap, and the client knows it. What is left, the copy, search, speed, accessibility and handover, is still real work, and it is invisible unless the proposal names it. A quote that prices only the build is pricing the part the client could have done themselves.
- The account is the site. If the builder hosts the site, the site lasts as long as the subscription is paid, and whoever holds the login holds the site. On client work, settle before launch whose account it lives in, whose card pays for it, who controls the domain, and how the client takes the site with them if they leave. Writing that into the handover takes ten minutes. Untangling it after a falling-out takes much longer.
After the first draft
The builder's part is done when the preview looks right. Yours starts there.
- Rewrite the copy, page by page, in your words or the client's.
- Write each page's title and description for that page alone.
- Load every page on a mid-range phone over a throttled connection, and fix what is slow.
- Go through each page with the keyboard alone, then run an automated accessibility check.
- Write the handover: whose account, whose domain, how to export, and who makes changes.