In this post we explain what AI won't do when you build a site with AI tools.
Home/Blog/What you need to know when building a site
You can now describe a website to an AI tool and have something on screen in minutes. That is genuinely useful, and we use AI-assisted tooling ourselves. But a page appearing on screen and a website doing its job are two different things, and the gap between them is where most people get caught.
Here is what the tools will not do for you.
An AI tool answers the question you ask it. If you ask for "a website for my business", you get a website for a business, with the usual sections in the usual order. It will not stop and ask who is coming to the site, what you want them to do, or what has to happen when they do it.
That decision is the most important part of the whole project, and it is the one that stays with you. A site with no clear job looks fine and produces nothing.
The tool does not know your prices, your service area, your qualifications or what you actually promise customers. When it fills a gap it writes something plausible, and plausible is not the same as true.
Every claim on your site needs to come from you or be checked by you. Opening hours, guarantees, "trusted by hundreds of customers": if the tool wrote it and you did not verify it, you are publishing it under your own name.
This is the one that surprises people most. A site can look finished and still be broken in ways you will not see for weeks.
Does the enquiry form actually reach your inbox, or does it fail quietly? Do old links redirect, or do visitors land on an error page? Does every page work on a small phone, not just in a desktop preview? Is it fast on a normal mobile connection? Can someone using a screen reader or a keyboard use it? Someone has to test all of this, page by page, and the tool will not do it unless it is told exactly what to look for.
A website is not a document you finish. Software needs updating, hosting needs paying for and watching, forms break after a change somewhere else, and contact details go stale.
The tool that built the site is not monitoring it. If something stops working on a Friday evening, nobody is going to notice unless you have arranged for someone to. Keep control of your domain name too, registered in your name, because that is what you will need the day you want to move.
If your site collects names and email addresses, you have obligations around privacy, and your site needs proper privacy and cookie pages. If it makes promises about price or results, you are held to them. If it breaks the law or someone's rights, the answer is not that the AI wrote it.
A human has to own the result. That is not a reason to avoid the tools. It is a reason to know who that human is.
They are good at speed. First drafts, rough layouts, repetitive code, trying three directions in an afternoon instead of three weeks. Used by someone who knows what a good result looks like, they make good work faster.
That is how we use them, and we say more about it in how we actually build. The tool does the typing. The decisions, the checking and the accountability stay with a person.
Whether it is an agency, a freelancer or you with an AI tool, a handful of questions tell you most of what you need to know. Who decided what the site is for? Who checked the forms, the redirects and the mobile layout? Who looks after it after launch, and what does that cost? Whose name is the domain registered in? And if something goes wrong, who do you call?
If the honest answer to any of those is "nobody", you have found the real cost of the cheap option. We cover the wider picture in custom-coded vs template, and our own prices are on the pricing page. If you would rather just talk it through, tell us what you are building.
Tell us what you are building and we will come back with a plain answer on what it needs and what it would cost.