Run Your Website From the Same Chat That Built It

Everyone can generate a website now. Type a prompt, get a decent page — that part is a commodity. The question nobody's answering is what happens on day 2: the leads start arriving, a line of copy needs a tweak, someone asks for a section you forgot. That's when a website stops being a design project and becomes a thing you have to run — and where most tools hand you yet another dashboard to log into and dread.

Sitelas makes a different bet. Because a Sitelas site lives inside Claude through an MCP connector, the same chat that built the site also runs it. You don't open an admin panel to see who filled out your form, write back, or change the page. You just ask.

Here's what "running your site from a chat" actually looks like.

First, the 30-second why

Claude connects to outside tools through MCP connectors — you already use the ones for Gmail, Calendar, and Drive. Sitelas has one too. Add it once (in claude.ai: Customize → Connectors → Add custom connector, and paste https://sitelas.com/api/mcp), and Claude can do things with your site, not just talk about it: publish it, read its submissions, connect its integrations, restyle it. Your site becomes an automation endpoint sitting next to your other connectors — the thing a Webflow or Squarespace site can't be. (New here? Start with How to Build a Website From a Claude Chat.)

"Did anyone fill out my form today?"

That single question is the whole idea. The conversation at the top of this post is exactly it: you ask, Claude reads your site's submissions, surfaces the new lead — Maya, a bakery owner — drafts a warm reply in your voice, and logs her to your leads sheet. One message, no tabs.

It works because every form on a Sitelas site captures submissions to your Submissions inbox automatically — no integration required. You can open that inbox in the dashboard anytime:

…but running your site from a chat means you rarely need to. Claude reads those same submissions straight from your site, so "who wrote in today, and what do they want?" is answered in the thread you're already in — not in a panel you have to remember to check.

Logging the lead to a spreadsheet

Say you want every lead in a Google Sheet you can sort and share. You don't leave the chat to set it up — you ask, and Claude hands you a one-time link to finish the connection on Sitelas:

You click the link, hit Connect, do a quick Google sign-in, and you're done — about fifteen seconds, once. From then on every submission also auto-appends to a Sheet in your own Drive (file uploads land in your Drive too, linked from the row), and your visitors never see a login screen. Submissions still land in your Sitelas inbox as well — connecting Sheets just adds a second destination. (Prefer to wire it up by hand? How to Build a Form and Connect It to Google Sheets covers the dashboard path.)

Changing the site itself — still just a chat

Running a site isn't only inbox work; it's the site too. "Add an FAQ section." "Make the hero warmer." You say it, and Claude edits — but it previews first, so your live page never changes until you approve it:

This is the part worth underlining: Claude shows you a preview URL and the live site keeps serving the old version until you say "publish." Edits accumulate in the preview; nothing goes public by surprise. When it looks right, one word — "publish" — pushes it live (and a one-step revert is always there if you change your mind).

The whole loop, in one window

You: "Anyone fill out my contact form today?" → Claude reads your submissions, surfaces the lead. You: "Draft a warm reply and log her to my leads sheet." → Claude drafts the reply and appends her to your Sheet. You: "Add an FAQ section and warm up the palette." → Claude edits, shows a preview. You: "Publish." → it goes live.

No dashboard-hopping, no export-sort-reimport, no glue code. The context never resets, so the chat that knows who wrote in is the same one that drafts her reply and the same one that ships the new section.

The honest caveat

This is a conversational way to run a site, not an enterprise ops suite. There's no built-in CRM, no native bulk-email sender (Claude drafts individual replies through your own Gmail — perfect for a focused early stream of leads, not a 50k blast), and no native bookings. Commerce is single-item checkout — one Buy button per product or tier via a Stripe Payment Link you supply — not a full cart or inventory system. When your funnel outgrows a chat, bring dedicated tools. For the day-to-day of a small site — reading leads, replying, keeping the page fresh — this is the loop, and it lives where you already work.

Why this is different

	The usual patchwork (builder + form tool + sheet + dashboard)	Claude + the Sitelas connector
Where you read submissions	A separate dashboard you log into	In the chat
Replying to a lead	Copy to email, switch tabs	Drafted in the chat
Sending leads to a spreadsheet	Zapier / manual export	Ask once → your Drive
Editing the live page	Another tool, another login	Ask; preview; publish
Context across all of it	In your head, across four tabs	One thread, never resets

That's the wedge: your site isn't a destination you visit, it's an endpoint you operate — next to every other tool you already run in Claude.

Prefer not to leave for claude.ai? There's an editor too

Everything above runs from a chat — but you don't have to. Every Sitelas site also opens in a visual editor with the same AI built in: describe an edit in plain language and it happens on the canvas, or click any element and adjust it by hand. And if you want to see the read-submissions-then-act loop pushed further — scoring signups and drafting invites — I Launched a Waitlist and Ran It From One Claude Chat walks through it end to end.

Try it

Add the Sitelas connector in Claude (https://sitelas.com/api/mcp), publish a site, then just start asking: who filled out the form, draft them a reply, send the leads to a Sheet, add a section. Sitelas is free while we're in early access — set up an account at sitelas.com, connect it to Claude, and run your site from the chat you're already in.