The bait, then the rug-pull.
The opening promise is blunt: Claude can now build the thing clients pay thousands for, but almost everyone using it is missing the one piece that makes it sellable. That gap and how to close it in a single session is what the next 26 minutes are about.
Where the time goes.
01 · The CMS Problem Solved
Core tension: clients need to edit, developers do not want to be on call forever. Frames the CMS as the fix.
02 · What The CMS Does
Walkthrough of the Claude CMS landing page and one-dashboard-per-client architecture.
03 · Live CMS Demo
Real-time demo of editing copy, changing prices, toggling mobile view, and the SEO panel inside an existing CMS build.
04 · Grab Claude And Start
Step 1: Claude desktop on the 20-per-month plan, or online alternatives like Base 44.
05 · Pick A Design Reference
Screenshot inspiration from real sites and Dribbble prevents the default Claude aesthetic.
06 · Use The Blueprint Extractor
Firecrawl-powered skill extracts structured style context from live websites and feeds it to Claude as design intent.
07 · One Shot Website Build
One-shot output demo: Leverage brand, AI-generated graphics via Kie.ai, multi-section landing page.
08 · Add Logos And Polish
Iterative screenshot-feedback loop with Claude to reach production quality.
09 · Host It For Free
Single Claude prompt creates a private GitHub repo and deploys to Vercel at no cost.
10 · GitHub And Vercel Explained
GitHub is code storage, Vercel is the live mirror. CLI authentication means Claude handles both without manual dashboard work.
11 · Deploy The Website Live
Claude creates the repo and publishes live; domain purchase shown inside Vercel dashboard.
12 · Build The CMS In Claude
Three-layer architecture: master dashboard, client sites, ingestion machine. Claude receives a pre-built CMS prompt file. Vercel and OpenRouter tokens wired in.
13 · Add The Safety Layer
Guardian validation: client edits are AI-checked before publish. Copy, image, and page edits allowed; structural changes blocked by default.
14 · Connect MongoDB
Document model matches page/version data shapes. Free 512MB tier on Atlas, always-on cloud.
15 · Set Up Your Cluster
Creating an Atlas account, cluster, database user, and choosing the Drivers connection method.
16 · Publish The CMS Live
CMS deployed to Vercel; MongoDB hydration from scratch demonstrated by wiping local copy and watching Atlas restore it.
17 · Two Links One System
Owner link (private master dashboard) vs. client link (password-protected Vercel editor). Credentials never touch the client.
18 · Client Editor Walkthrough
Client experience: enter password, open editor, change copy, publish, verify change is live on Vercel.
19 · Scale To Many Sites
Claude creates one master command site plus individual client sites; all feed into one dashboard.
Named ideas worth stealing.
Build Ingest Hand Off
- Build the site in Claude Code
- Run the ingestion machine to make it CMS-editable
- Hand client a password-protected editor link
Three-step deployment model that separates build-time from edit-time and removes the developer from the client-edit loop entirely.
Guardian Validation Layer
AI middleware that validates every client edit before it publishes. Allows copy, image, and page changes; blocks structural edits by default. Implemented as an optional safe-gate.
Two-Link Architecture
- Owner dashboard (local/private, holds all API keys)
- Client editor link (Vercel-hosted, password-gated)
Separates infrastructure credentials from client access. Owner controls model selection, Vercel token, and MongoDB connection. Client only sees the editor.
Lines you could clip.
"99% of Claude websites are unusable because of one limitation."
"A beautiful site that they cannot touch."
"AI is not writing code. We are basically just changing copy on it."
"Nothing is live until publish, and every publish is a snapshot."
Things they pointed at.
Word for word.
The gap between a Claude site and a sellable one.
Building the website is the easy part; the thing that makes it a business is the layer between your code and your client cursor.
- A client who cannot edit their own site will always need you, and that dependency caps how many clients you can take on at once.
- Design reference screenshots fed directly to Claude at the start of a build prevent the generic AI aesthetic without requiring manual CSS overrides later.
- Firecrawl lets Claude analyze any live website mathematically for color, typography, and spacing, giving it design intent rather than just a description.
- Deploying via CLI-authenticated GitHub and Vercel means Claude handles the entire push without you touching a terminal.
- A document-oriented database maps naturally to versioned page snapshots -- each publish is a recoverable state, not an overwrite.
- Separating the owner dashboard from the client editor link means API keys and infrastructure controls never enter the client relationship.
- A validation layer that blocks structural edits by default is the difference between a client editor and a client liability.
- Charging for recurring CMS access converts a one-time build fee into an ongoing service relationship.
- Version history baked into the CMS removes the most common objection to handing clients editor access: the fear that they will break something irreversible.




























































