This site was built in an AI chat. Here's how.
The SiteShip website was built through SiteShip's own connector, in a conversation. These are the steps we took, and the parts of the engine that did the work.
The SiteShip team · 5 min read
The line at the top of every page here says "This site was built in an AI chat. Yours can be too." It's true. The site you are reading was built through SiteShip's own connector, the same one you would add to ChatGPT or Claude. Its pages, templates and data were written in a conversation, not in a design tool.
Here is how it went, step by step. We've left out timings and numbers on purpose: this is one site, built by the people who make the tool, and we don't want to pass that off as a measurement.
1. It started with a brief
We began the way a customer does: by telling the AI what we wanted. What SiteShip is, who it's for, and the feeling we were after, which was a voyage. A night sky at the top, a ship on the water, and a sea that gets deeper as you scroll down to the price and the questions.
We didn't get there in one go. We first asked for a few different directions as rough mock-ups, turned most of them down, and picked the voyage. Then we had that direction built for real in SiteShip, which is where the rest of this story happens.
A brief doesn't have to be long. It has to say what the business is and what the page should make someone do.
2. The first preview came back in the chat
The AI built a home page and returned a private preview link. Nobody else could see it. That first version was not the site you see now. It was a starting point to react to, which is much easier than describing everything up front.
3. We changed it one section at a time
After that, the work was a long conversation, with requests of the kind you would make yourself: make this bigger, say this more plainly, shorten that answer. Each request changed one part and left the rest alone.
Two things the engine does mattered more than we expected:
- Every change is checked. When the AI wrote something that would have broken a page, the engine refused that file and said why, and the AI fixed it in the same turn. We saw the fixed version, not the broken one.
- Every change can be undone. Earlier versions are kept, so trying an idea costs nothing.
The look itself is held in one small file of colours and fonts. The night blue, the cream panels and the amber buttons are named once there and used everywhere, which is why the pages match.
4. The galley is one list, not a pile of pages
The galley is our library of recipes: prompts you can copy into your own chat. Each recipe has its own page, and nobody wrote those pages one by one.
All the recipes live in a single data file: a title, a summary, what you need, the prompt, and what you get. One template turns each entry into a page. Add an entry to the list and a new page exists, with its link on the galley and in its category.
The same is true of the prices, the questions on the home page and the comparison pages. Each is a list in one file. When a price changes, it changes in one place.
This is the part that plain AI-written HTML tends to get wrong. Ask for a dozen similar pages and you get a dozen copies that slowly drift apart. Ask SiteShip, and you get one list and one template.
5. The search box made the engine better
The galley has a search box that narrows the recipes as you type. When we first asked for one, the engine couldn't do it. It could filter a list with buttons, but not by typing. So we added that to the engine, and now any SiteShip site can have a search box.
Once the engine knew how, adding it here took one sentence: the AI only had to mark which box does the searching and which cards are searched. No script was written for this site.
The same goes for the menus, the pop-up that explains how to add SiteShip, and the questions that open and close. They are built into the engine, and the AI switches them on.
6. Nothing went live until someone clicked
Through all of this, the changes sat in a draft. The live site changes only when a person clicks Publish. An AI can prepare a change; it can't ship one by itself unless the owner allows it.
What this means for your site
Most small-business websites are simpler than this one. You probably don't need a sea that gets deeper as you scroll. But the steps are the same ones you would take:
- Tell your AI about your business.
- Look at the preview.
- Say what to change, one thing at a time.
- Click Publish when you're happy.
If you'd like a head start, the galley has recipes for whole sites, such as a coffee shop or a plumber. If you're wondering how this differs from asking your AI for some HTML, the engine page explains it.
The takeaway: we didn't build SiteShip's website and then claim an AI could have. We built it the way you would, in a chat, and the site you are looking at is the result.
Free to build. Pay only to go live.