AI-built websites by use case: what each kind needs

An AI assistant will give you a website in an hour. It will look like a website, it will open on your phone, and it will be wrong in a way that depends entirely on what you asked it to do. A plumber's page needs the phone number to be right. A store needs a payment gateway in your name and tax rates for every place you ship to. The chat knows neither, so the gap between "a website appeared" and "a website that works" is a different gap for every kind of site.

This is a requirements guide, not a ranking: ten rows, each a kind of site people actually ask for, with what the AI has to produce, what it reliably forgets, and what the result then needs from a server. Then the three routes to a finished site.

How to read the ten rows

Find your row by what a visitor must be able to do on the site, not by what industry you are in. A hair salon and a law firm are the same row if both only need to be found and contacted; add online booking to one and a document sale to the other and they split, because a booking engine and a checkout are different machines.

The kind of site decides what the AI output must contain: a brochure site needs facts and a form, a store needs payments and tax, a course site needs accounts, an app needs a backend. That is the article in one line, and the rows are its detail.

The hosting question is separate from the build question, and smaller. Every Flashcloud plan includes the domain, SSL, mailboxes and daily backups, so once you know your row the hosting answer is usually "a shared plan" and the open question is only who builds the thing. Shared hosting starts at $2.79 a month on an annual term with all of that included.

And the heavier your row, the less of it an assistant finishes. The tools are not writing bad pages. They are writing pages. A store is not a page.

The needs table

Nine of those ten rows end in "a shared plan", which is the quiet finding of the table. The exception is the app MVP, and only because it needs a runtime: Node and Express servers run on Flashcloud shared hosting through cPanel's Setup Node.js App, with NPM install and environment variables set from the panel, and Flask, Django and FastAPI run through Setup Python App. So even that row is often a shared plan. Which runtime fits what an AI builder produced is the subject of hosting AI-built apps from Lovable, Bolt, v0 and Cursor.

Four rows worth more than a table row

A store is the row where people lose the most time. Installing WooCommerce takes five minutes; a first real order takes longer, because products need inventory data, payments need a live gateway rather than cash on delivery, shipping needs rates that match what you charge, and tax is per jurisdiction. The knowledgebase walks that sequence in setting up your first WooCommerce store. An assistant can write every product page you need. It cannot open a Stripe account for you. Whether to build a store with an AI tool at all or go straight to WooCommerce gets its own piece.

A course or membership site is the row where AI output sits furthest from the requirement. "Members only" is four systems: accounts, payments, content locking and email. On WordPress that is an LMS plugin; for real coursework it is often Moodle, installed through Softaculous in cPanel, with its own cron job and raised PHP upload limits because course files are large. Installing Moodle has that sequence, including why the cron job is not optional. A piece comparing AI tools with a real LMS is coming.

An app MVP is the row where the demo is honest and the production version is not built yet. A Lovable or Bolt project gives you screens and often a backend you do not own. Production needs the keys out of the code and into environment variables, the data somewhere that gets backed up, and a plan for the night it crashes. That row gets its own piece.

A client site built for someone else is the row where the hosting question is a business question: separation per client, backups you can show a client, and a handover that does not depend on you remembering a password. That handover problem is the one clubs and committees have, which we wrote up in hosting for clubs and associations: whoever holds the domain holds the website, so register it to the organisation, not to a person who might move on. Building client sites with AI as a freelancer or agency gets its own piece.

The three things AI always forgets

The same three gaps turn up in all ten rows. They are worth naming separately because they are not bugs in the output: they are things no chat window has access to.

Facts

An assistant that does not know your opening hours will write opening hours. It will write a founding year, a team size, a service area, a price. Every one of those is a guess shaped like a fact, and it is the most common reason an AI-built site embarrasses its owner in week one.

The fix is mechanical. Before you accept the pages, check every number, name, date, address and price against something authoritative: your till system, your calendar, your registration document. Fix the source file rather than the live page, so the next regeneration does not reinstate the invention. That consistency matters more now that assistants read sites to answer questions, which is the subject of how AI assistants find, read and cite your website. Put the facts where a machine can read them too: hours and address as text rather than inside a hero image, and the phone number as a real link.

Forms

The contact form the assistant drew is a picture of a contact form. A static HTML page cannot send mail on its own, because nothing on the page can talk to a mail server. Press submit on a fresh AI-built site and, at best, nothing happens.

You need a handler: a form plugin if the site is WordPress, a small server-side script, or a third-party form service that posts to its own endpoint. On WordPress the usual route is creating a contact form in WordPress, sending through SMTP so the messages do not land in spam. Then test it from a phone on mobile data, not from the laptop you built it on.

Every row in the table has a form somewhere, which makes this the most-forgotten component in AI-built sites. The landing page row is the extreme case: a waitlist with a dead form collects nothing while looking like it works.

Email on your own domain

Nobody asks about this until the first enquiry does not arrive. An assistant cannot create a mailbox, and the publish links the assistants offer carry no mail at your name at all. A site at your own domain with a contact address at gmail.com reads as temporary to a cautious customer.

Mailboxes come with the hosting, so the work is five minutes in creating email accounts on your domain and then adding the address to your phone. Clubs and committees should use role addresses, treasurer@ and secretary@, so the inbox survives the person holding it.

The free route

If your row is the brochure site, and for most small businesses it is, one route costs nothing extra and involves no chat window.

Every Flashcloud plan includes a free handcrafted website of up to five pages, built by the Flashcloud team, usually ready in one to two working days, with one free revision. It is designed by people rather than generated from a template, you do not have to supply content (if you have colours, a logo, images or text we use them, and if you do not, we create them), and the revision can be a complete redesign rather than a tweak. You pick the domain, tell us what the business is, choose single-page or multi-page, and choose whether we deploy it live, to a staging subdomain for review, or as a placeholder to hand over later. The request flow is in get a free website built for you.

What it is not: a store, a custom integration, logo work, or ongoing content production. It is a starter site, and we say so. If your row is the store, the course site or the app, the free build covers the brochure part and the rest is a project.

The second free thing applies where you already built something with AI. Flashcloud moves an AI-built site onto the customer's domain for free with every plan: the customer sends the files and Flashcloud sets up the domain, SSL and email. So "the assistant made it and I cannot work out how to put it online" is not a reason to abandon the site. That move, from chat window to your own domain, is in how to host a website built with ChatGPT, Claude or Gemini.

The AI route

This route works best when you treat the assistant as a fast drafter working to your spec rather than as a web agency. Give it your row's requirement list, from the table above, as the prompt. Name the pages, name the facts, say what the visitor must be able to do, and name the hosting target: a static site on shared hosting with cPanel, or WordPress. That one sentence about the target removes most of the broken output, because it stops the assistant assuming a platform you do not have.

Then the three gaps, in order: check the facts, wire the form, make the mailbox. Then put it on a domain you own. There are three ways to get files onto a Flashcloud account: push to GitHub and let cPanel Git Version Control pull the repository, upload with File Manager or FTP, or connect the AI assistant through the Flashcloud AI Connector and let it write the files. Every change an assistant makes through the connector is a two-step confirmed action: it proposes exactly what will happen and nothing runs until you approve it.

One decision sits underneath all of this: which tool, and what you own at the end, which is the subject of AI website builder vs AI coding tool: what you own. The answer differs by row. A builder's hosted output is fine for a landing page and a liability for a client site.

Two habits save the most pain afterwards. Keep the assistant's version of the files as your source of truth and treat the copy on the server as published output, so next month's change starts from the right code. And read AI-written code for keys and credentials before it goes near a server, because an assistant will write a key into a page without being asked.

The hire route

Hiring is the right answer more often than this industry admits, and cheapest when you hire for the specific thing rather than for "a website".

Our own team prices that work per job for the same reason: extra pages on the free starter site in the same style, a custom design with the homepage approved before anything else is built, an online store with shipping, tax and your products loaded and the payment gateway you choose integrated (the merchant account and the gateway's approval are between you and the processor), or a rebuild on a modern theme. Work happens on a staging copy and you approve it before it goes live, with an anytime refund on unfinished work. Ask support for the current menu; it is not something you have to decide before the free five pages.

An assistant is good at drafting pages and copy you will edit. It is not an account manager, a payment processor or the person who answers at 7pm when checkout breaks. Pay for the parts that carry money or liability, draft the rest.

The cost comparison across all three routes, with the year-two numbers that usually decide it, is in how much does a small business website cost.

Picking your row

Three questions, in order.

Must a visitor pay you on the site? If yes, you are the store row or the course row, the build is a project, and the assistant writes catalogue copy rather than the checkout.

Must a visitor log in? If yes, accounts and content locking make it software: course, membership or app.

Must a visitor book a time? If yes, the booking engine is a third-party account in your name and the site's job is to present it properly: restaurant, salon, clinic.

If all three are no, you are a brochure site, which is most small businesses, and three routes are open: the free handcrafted starter site that comes with your plan, an assistant drafting pages you check and upload, or a few hundred dollars of per-job work. All three end on the same shared plan with the same inclusions, so nothing about the hosting changes if you start with one and move to another. The do-it-yourself sequence, platform choice included, is in how to build a website yourself.

A piece per row is coming: the brochure site, the portfolio, the landing page, the church or nonprofit site, the restaurant or salon, and an updated guide to building it yourself with AI. All of them will sit on the AI and your website hub once it is up.

The useful thing to take from the table is that hosting is not your hard decision. Nine rows in ten run on a shared plan with the domain, SSL, mailboxes and daily backups included, which means the question you are really answering is who builds it. If your row is the brochure site, that question has a free answer waiting on your account. The free handcrafted starter site is that answer, five pages built by our team and usually ready in one to two working days, so the AI route becomes the one you take for the rows that need more.