Ask an AI design tool for a website and you get something close to finished in minutes: a layout, a colour system, working markup. For teams that used to spend the first month of a project on wireframes, that is a real change.
It also moves the hard part. A site that goes live is a site someone has to run, and for most organisations that is where the time and budget go.
What launch day leaves open
A generated site settles what the pages look like. The operating questions are still waiting:
- Who approves a page before it goes out, and where is that approval recorded?
- Who patches the servers, renews the certificates, and upgrades the CMS?
- What happens when a news story sends a surge of visitors to one page?
- Who tests the site for vulnerabilities, and how often?
- How does the second site, and the twentieth, reuse what the first one built?
None of these gets easier because the first draft was quick. Some get harder, because a team that can produce sites quickly tends to produce more of them.
Speed needs a foundation under it
Public services have had to answer these questions for years. Their websites have to stay up when an announcement sends a large share of the public to the same page, and every change has to be approved and traceable. Visor's foundations come from that setting, in technology used to run Singapore Government websites.
In Visor, approval is a workflow state on every page and entry, drawn on a canvas and assigned per collection. Publishing triggers a static build, so a spike meets cached files on 200+ edge locations. Patching and CMS upgrades are the platform's job, and security scans run on a schedule. A template built once can be cloned for the next site, with its own theme.
Where AI fits
Visor uses AI in the build. The template ships with skills that set up a project and turn a design exported from any AI tool, such as Claude, into a theme, layouts, and widgets. Developers review the output before editors use it.
On the published site, AI agents can read a site's content through a read-only token and answer visitors in a chat widget. The operating model underneath stays the same: approved content, static delivery, and a platform that is patched, tested, and supported.
The question to ask
When you evaluate a website platform now, the speed of the first build tells you less than it used to. Ask what happens in year two, on site twenty, and on the day traffic spikes. That is where platforms differ.
