I Launched a Waitlist and Ran It From One Claude Chat
One conversation: Claude builds the launch page, collects every signup in your Sitelas inbox, scores them by fit, and drafts the early-access invites from your Gmail — no site builder, form tool, or spreadsheet triage.
Usman Haider

A waitlist is the cheapest demand test you can run before you build the thing. The problem is all the tools in between. You need a landing-page tool, a form tool and a spreadsheet to watch signups. Then, once you have a list, a mail merge to invite the right people. Four tools and a long evening, for what should be a two-day experiment.
I ran the whole thing for a fictional indie SaaS, Juno (an analytics co-pilot), from a single Claude chat. Page to published list to drafted invites. Here's exactly how — and why it's a category no static-site builder can touch.
What an MCP connector actually is (30-second version)
Claude can connect to outside tools through connectors. Add one, and Claude can do things in that tool for you, not just talk about it. You already use the Gmail, Calendar, and Google Drive connectors. Sitelas has one too. Add it and Claude can design sites, publish them, read your form submissions and forward them to your other tools, all from chat. That's the difference between "Claude gives me launch advice" and "Claude runs the launch." (Want the plain step-by-step first? See How to Build a Website From a Claude Chat.)
Step 1: Connect Sitelas to Claude
One-time setup: Sitelas is in Claude's connector directory, so adding it takes one click — open the listing and choose Add.
Using Claude Code or Claude Desktop instead? Those read a config file rather than the directory, so point them at https://sitelas.com/api/mcp.
Sign in to Sitelas when prompted, and switch on the Gmail connector while you're there (we'll use it for the invites). Setup's done; everything else is just asking.
Step 2: Ask Claude to build and publish the launch page
You describe it once — Claude picks a layout, writes the form, previews it, and publishes:

That's the real, branded launch page at the top of this post — live on the web, with a working waitlist form. Because you told it to publish, Claude previews the page and puts it live in one go. For any change after launch it shows you a preview first, so your live page never changes until you say so. Every submission already lands in your Sitelas inbox. Want changes? "Add a launch countdown." "Make the hero darker." You say it; Claude edits, previews, and republishes. No drag-and-drop, no template wrestling. Want a head start? The SaaS and waitlist templates have waitlist and sign-up sections laid out.
Step 3: Every signup lands in your inbox — no setup
There's nothing to connect. The moment your page is live, every signup waits in your Sitelas inbox: name, email and anything else you asked for. No spreadsheet to wire up, no export, no "which tab was that in."

And because your site is connected to Claude, you don't even open the inbox. Claude reads it for you in the chat. That's the next step. Want a spreadsheet mirror too? Add a Zapier webhook address to the form's settings and every signup also goes to a Google Sheet. As you'll see, you may not need one.
Step 4: Let the signups roll in — then ask Claude to score them by fit
Post the link on X, in your communities, on launch day. As signups arrive, Claude reads them straight from your site's submissions — no exporting, no sorting a spreadsheet by hand. You ask:

A 400-row spreadsheet becomes a ranked, reasoned shortlist — the people most likely to convert and give you real feedback, first. Then you push on it like a growth partner: "Who mentioned churn?" "Group the enterprise ones for a separate track."
Step 5: Ask Claude to draft the invites
Gmail is already connected, so you close the loop in the same chat:

Claude drafts a personal invite for each of your top signups, mentioning what they said they'd use Juno for. Everyone else gets a warm "you're on the list" note. You review, approve, send. From "waitlist is live" to "best 20 invited" without leaving the window.
The whole loop, in one window
You: "Build & publish a waitlist page." → Claude (Sitelas) ships it. …signups arrive, captured in your inbox, no setup… You: "Score the signups by fit, give me the top 20." → Claude (Sitelas) returns a ranked shortlist. You: "Draft the early-access invites." → Claude (Gmail) writes them, personalized.
A handful of messages and one quick click. One window. A live landing page, a self-updating list, AI segmentation, and drafted invites.
What makes this different
It's not that any single piece is new — it's that there are no handoffs. Normally the page lives in one tool, the signups in another, the segmentation in your head, the invites in a fourth tab. Every gap is glue work. With Claude's connectors it all happens in one conversation. Claude already knows who scored highest when it drafts their invite, because the same chat ranked them.
That's the part a Webflow or Squarespace site can't do. Your site isn't just a place people visit. It's a tool Claude can use, next to every other tool you run in Claude. That's what running your website from a Claude chat means. Form submission → fit score → personalized invite, composed in one thread — no Zapier seat, no dashboard-hopping, no glue code.
| The usual patchwork (page + form + sheet + mail-merge) | Claude + Sitelas connector | |
|---|---|---|
| Tools to juggle | 4 | 1 (Claude) |
| Build + publish the launch page | Separate tool | In chat |
| Auto-collected signups | Maybe | Yes → your Sitelas inbox |
| AI scoring / segmentation | No | Yes |
| Personalized invites from one place | No | Yes (Gmail) |
Prefer not to leave for claude.ai? There's an editor too
Everything above runs from claude.ai — but you don't have to. Every Sitelas site also opens in a visual editor with AI built in. Describe an edit in plain words and it happens on the page, or click anything and change it by hand.

The honest caveat
This is a lightweight, conversational pipeline — not a full growth stack. There's no built-in bulk email sender and no built-in CRM. Claude drafts individual messages through your own Gmail, which suits a small early-access list, not a mass mailing. When your list is huge and your funnel is mature, bring dedicated tools. But for the launch itself, the real work is getting a page up and inviting the right people fast. This is the whole loop in one chat window.
Questions people ask
How do you create a waitlist landing page? Connect Sitelas to Claude and describe your product. Ask for a waitlist page with an email form. Claude shows you a preview, and it goes live when you say publish.
How do you automate waitlist management? Every signup saves to your Sitelas inbox with no setup. Ask Claude to read the signups, rank them and draft invites. In Claude Cowork, it can check them every morning.
Can I email everyone on my waitlist? Not as a bulk send. Sitelas doesn't send newsletters or mass email. Claude can draft individual invites through your own Gmail, which suits a small early-access list.
Do I need a spreadsheet for my signups? No. They stay in your Sitelas inbox, and you can export them as a CSV file. A webhook can also add each one to a Google Sheet through Zapier.
Try it
Add the Sitelas connector in Claude (plus Gmail). Ask it to build and publish your waitlist page, then score the signups that land in your inbox and draft the invites. Set up an account at sitelas.com, connect it to Claude, and launch from the chat you're already in. Want it to report back on its own? See the same waitlist run from Claude Cowork, with a digest every morning.
Templates to start from
Build this with a ready-made design, then change anything.

Gnomon
A download page for a phone app: bold full-colour sections, app screens you edit, a spot for your video and an FAQ.

Splice
A warm one-page site for a team or HR app: features that pile up as you scroll, customer stories and a sign-up form.

Orrery
A bright one-page site for a CRM or follow-up tool: a product tour, customer quotes, three plans and a sign-up form.

Usman Haider
Founder of Sitelas — the website builder for AI agents.