The website you run by chat.
Ask for a change in plain language. An AI agent makes it in your Git repository, you review a preview, and nothing publishes without your approval. Try it below on a sample site.
This is how insidea.com itself is run.
Pick a request below or type your own. You will see the steps a real change goes through: a branch, the edit, the checks, a preview, and your approval.
- Request
- Branch
- Checks
- Preview
- Live
- 538453dInitial sitelive
A scripted demo on a sample site. On a real project the agent works in your repository.
From a message to a live change.
What is an AI-managed website?
It is a website you run by chat. You ask for a change in plain language, an AI agent makes it in your Git repository on a separate branch, and you see a preview link before anything goes live. Nothing ships without your approval. This is how insidea.com itself is run.
- 01 · You ask in chat
- “Add a pricing FAQ”: A plain-language request
- “Publish this case study”: New content
- “Fix the mobile menu”: A bug or a design change
- “Update our review count”: One fact, on every page
- 02 · AI agentAI agent: Works in your Git repository
- Reads the code and the content
- Makes the change on a branch
- Runs the build and the checks
- Opens a pull request
- 03 · Review
- Preview link: See it before it is live
- Before and after report: What changed, and why
- Your approval: Nothing ships without a yes
- 04 · Deploy
- Merge: Reviewed change joins the site
- Automatic deploy: Live about a minute later
- CMS publish: Content synced to the CMS
- 05 · Record
- Git history: Every change, reversible
- Automated checks: SEO audit and claims lint
- Open-work list: What is done, what is next
Every change is a reviewed pull request, so the full history is in Git and anything can be rolled back.
What changes when a website is run this way?
The site looks the same to a visitor. What changes is how a request becomes a live change, and what record it leaves behind.
Asking for a change
The usual wayA ticket or an email to a developer or an agency
AI-managedA message in chat, in plain language
Who makes it
The usual wayA developer, when they are next free
AI-managedAn AI agent, working in your Git repository
Seeing it first
The usual wayOften on the live site, after it has shipped
AI-managedOn a preview link, before anything is live
Approving it
The usual wayAssumed once the ticket is closed
AI-managedAn explicit yes from you, every time
The record
The usual waySpread across emails, tickets and CMS revisions
AI-managedEvery change in one Git history
Undoing it
The usual wayRestoring a backup of the whole site
AI-managedReverting the one change
What keeps an AI-managed website safe?
Nothing publishes without a yes
The agent works on a separate branch and stops at a preview. The live site only changes when you approve.
Every change is checked
The build has to pass, and automated checks for search basics and content rules run before you are asked to review.
Everything is reversible
Each change is one entry in Git. Rolling it back is another reviewed change, not a rebuild.
People stay in charge
INSIDEA sets up the site, the checks and the rules the agent follows, and stays on hand for design direction and larger work.
What does an AI-managed website need?
Three things, all of which we set up as part of a new build or a migration. insidea.com runs on exactly this: Next.js, Sanity and Vercel, with every change reviewed in Git.
Website design, redesign and migration →A Git repository
Where the site's code lives and where every change is recorded. We use GitHub.
Hosting with previews
Each proposed change gets its own preview link. We use Vercel.
A headless CMS
For blog posts, case studies and other content your team edits. We use Sanity.
AI-managed websites, answered.
What is an AI-managed website?
A website you run by chat. You ask for a change in plain language, an AI agent makes it in your Git repository on a separate branch, and you review a preview link before anything goes live. Nothing ships without your approval, and every change stays in the Git history.
Can the AI publish to my live site on its own?
No. The agent stops at a preview and waits. The live site changes only after you approve, and that approval is recorded with the change.
What can I ask it to change?
Copy, pages, sections, components, layout and design details, bug fixes and search fixes. Larger pieces of work, such as a new brand direction or a full redesign, are scoped with our team first.
Do I need developers on my team?
Not for day-to-day changes. INSIDEA builds the site, sets up the repository, hosting and checks, and supports the work that needs a designer or an engineer.
Which websites can be run this way?
The site's code has to live in a Git repository, so this suits custom-code sites, such as Next.js with a headless CMS. Sites on HubSpot Content Hub, WordPress, Webflow or Shopify are managed in their own editors, and we can migrate them if you want to move.
Is insidea.com really run this way?
Yes. insidea.com is built on Next.js, Sanity and Vercel, and changes to it are requested in chat, made by an AI agent as pull requests, previewed, and approved by a person before they go live.
How is an AI-managed website priced?
A monthly retainer, scoped at proposal, from $2,000 a month. Specifics on the strategy call.
Run your website by chat.
Book a 30-minute strategy call. We look at your current site and tell you what it would take to run it this way.
How INSIDEA works
