I asked Claude to build me a landing page. It took 40 seconds.
Getting it live took 3 hours.
Not because I'm bad at tech. Because the entire handoff between "AI gave me HTML" and "page is on the web" was designed for someone who isn't me.
Here is exactly what happened.
Claude generated a clean, complete HTML file. Looked right in the chat. I copied it.
Then I opened Netlify. Created an account. Got asked for a team name.Typed something. Got asked for a project name. Typed something else. Looked for the drag-and-drop deploy option I'd seen in a tutorial. Couldn't find it. The UI had changed.
Opened YouTube. Found a tutorial. It was from 2022. The sidebar it referenced didn't exist anymore.
Went back to Claude. Asked how to deploy to Netlify. It gave me CLI commands.
I don't have Node installed on this machine.
Opened a new tab. Searched "deploy HTML without terminal." Found a Reddit thread from 2021. Someone suggested GitHub Pages. Opened GitHub. Created a repo. Got confused about whether it should be public or private. Picked public. Tried to upload the file. GitHub asked me to commit with a message. I typed "first commit." The page deployed but showed a 404. Turned out I needed the file named index.html not page.html.
Renamed it. Redeployed. Waited.
3 hours after Claude handed me a finished HTML file, I had a live URL.
The hell loop nobody talks about
There's a term from AI coding discussions called the "hell loop" — when an agent goes in circles trying to fix a bug it created itself. You lose the thread, forget where you started, spend more time recovering context than actually solving the problem.
The deploy version of this is the same thing.
Tab 1: the HTML sitting in the chat.
Tab 2: Netlify, half-configured.
Tab 3: a tutorial that's out of date.
Tab 4: Stack Overflow.
Tab 5: back to Claude, asking for help deploying.
Claude suggests the terminal again.
You are now debugging the deploy process instead of shipping the thing you built.
Why this keeps happening
Every deployment tool was built by developers for developers. The mental model is: you have a local environment, you have Git, you have a terminal, you know what a CLI flag means.
That mental model does not describe the person who just used Claude to build a landing page for their campaign. It doesn't describe the solo founder testing an offer. The freelancer sending a quick demo to a client. The marketer who got a beautiful HTML file and just needs a URL.
AI lowered the floor for creation dramatically.
The deploy floor didn't move.
What actually fixed it for me
I got frustrated enough to build a Chrome extension called HTML Deployer that sits inside the Claude or ChatGPT tab where the conversation already happened.
It detects the HTML automatically. No copy-paste. You preview it on desktop, tablet, and mobile before anything goes live. Then you pick where it goes: Netlify, GitHub Pages, FTP, or your own server.
Click deploy. Get a URL.
The whole thing takes under 60 seconds and you never leave the tab.
I built it because I was tired of paying the deploy tax on every single project. Turns out a lot of other people were paying it too.
If you've hit this wall before, what was your workaround? And if you're a developer reading this thinking "just use Netlify drop" — try explaining that to someone who has never seen a deploy pipeline in their life. That's the gap.
Top comments (12)
The "deploy hell loop" framing is spot on. The gap between "AI handed me the code" and "it's actually live" is where the real friction lives — and it's not a code quality problem, it's a deployment UX problem. The Chrome extension approach is clever: embedding the deploy flow where the conversation already happened removes the context switch entirely. Have you thought about a /deploy endpoint or a Vercel integration that Claude could call directly from the chat?
Exactly. That context switch is the killer.
A direct deploy endpoint is definitely something I’ve been thinking about. The tricky part is making it feel safe and predictable, because people need to preview what is about to go live before an AI agent pushes it somewhere.
A Vercel integration could make a lot of sense too, especially for users already in that ecosystem. For now, I started with the Chrome extension because it keeps the flow inside the chat and gives the user one last review step before deploy.
i totally get your frustration with the deployment process-it's often way more complicated than it should be. moonshift simplifies that by letting you get a full next.js + postgres + auth build deployed in about 7 minutes. you own the code on your github, and it's a flat per-build cost. how about a free run to try it out, no strings attached?
Totally agree that the deployment layer needs to get simpler. Moonshift sounds like it’s tackling a bigger full-stack use case, which is really interesting.
My pain point here was even more basic: someone has a single HTML page from Claude or ChatGPT and just needs a live URL without setting up a repo, terminal, framework, or environment.
Happy to check out Moonshift though. The more tools that reduce deployment friction, the better.
Yep, this is painfully relatable. Making the page is the easy part now, but getting it live can still turn into a weird maze of tabs, docs, and outdated tutorials. Pretty cool that you just built the thing you wished existed. Do you reckon this becomes built into AI tools eventually?
Yep, I think some version of this definitely becomes built in eventually.
But my guess is AI tools will solve the basic version first, like publish this as a temporary page or export to a simple host. The messy part is still everything around real deployment: previewing mobile before it goes live, choosing Netlify vs GitHub vs FTP, reusing your own hosting, keeping history, not losing the final URL, that kind of thing.
That is the gap I kept running into. AI had already solved creating the page. I just wanted the last mile to feel as simple as the prompt that created it.
Whenever I start a new project, one of the first tasks is deploying!
Same ❤️
Been there. Spent way more time fighting deployment tools than actually building. Worst is when the tutorial shows a button that doesn't exist anymore.
That outdated tutorial problem is so real.
You start with a simple goal: get this page online. Then suddenly you’re decoding UI changes, old docs, random menu names, and missing buttons.
That was exactly the moment I realized the issue wasn’t building the page anymore. It was all the tiny assumptions hidden in the deploy process.
Super relatable. AI speeds up page writing, but deployment setup always costs most of the actual working time.
Exactly. The code generation part feels almost instant now, but the setup around deployment still has all the old friction.
That was the weird realization for me. I was not spending 3 hours building the page. I was spending 3 hours turning a finished page into a URL I could actually share.
That gap feels small until you hit it over and over. Then it becomes the most annoying part of the workflow.