ℹ️ Ha ha ha hahahahahaha... I have to post this. Tbh I think my writing style is rather dull. My content is strong, but my presentation is lacking. Lately I've been experimenting with using Claude to "tweak" my styling, by asking it to rewrite my article in the style of a different writer who I like- in this case, Mark Manson, author of "How not to give a fuck." When you read this, know it's not in my voice, and that it pulls no punches. Heck it kicks below the belt multiple times. This is not my style of communicating my thoughts. And yet it's uniquely great in its own right, and deserves to be published. I think Claude is developing a sense of humor. Nice one buddy.
Every few weeks someone on r/webflow posts the same breathless manifesto: "Webflow is too expensive in the age of AI. I'm moving everything to Astro + Sanity + Claude." The replies roll in like a cult meeting. Yes brother. Headless CMS. Claude Code. So much faster. So much cheaper. We are free.
Then you scroll a bit further and realise most of these people have never handed a site to a marketing team and watched them try to launch a campaign page on a Thursday afternoon.
This is the problem with technical debates on the internet. They're almost always had by people who only think about the first five minutes of a project -- the part where they are happily building. They never think about month eleven, when they're on holiday and the client's head of marketing needs to update the pricing page before a board meeting.
That's the part that matters. That's the only part that matters. And that's the part vibe coding absolutely eats.
The fantasy
Here's the pitch, if you haven't heard it: drop Webflow, spin up an Astro site, plug in Sanity, let Claude do the heavy lifting. You save the Webflow subscription. You get "real" code. You get infinite flexibility. You get to tell people at parties you're a developer again.
I'll be honest -- it's a seductive pitch. I use Claude every day. It's extraordinary. The stack works. For a solo operator building their own site, it's genuinely a good option.
But "it works" and "it works for client projects at scale" are two completely different sentences. People keep conflating them. And that confusion is going to cost a lot of agencies a lot of money over the next two years.
The question nobody asks
Before you migrate anything, answer this: who is going to change the word 'Solutions' to 'Services' in the main nav at 4pm on a Friday?
If the answer is "me" -- congrats, you've built yourself a job, not a business.
If the answer is "the client's marketing coordinator" -- then you'd better hope they were told, before signing off on the migration, that every edit now requires opening a pull request, running a build, previewing in staging, and merging to production. Which they won't do. Which means they'll text you instead. Forever.
If the answer is "the client will just ask Claude to do it" -- please, for the love of god, tell me you're joking.
Because here's what happens the first time an enthusiastic marketing manager tells Claude to "tweak the hero section a bit." Claude, being helpful, tweaks the hero section. It also subtly restructures the heading hierarchy because it thought that'd look cleaner. Your h1 is now an h2. Your primary keyword just got demoted. You won't notice for six weeks. When you do, you won't know why your organic traffic cratered, because there's no audit trail -- just a git log full of "update homepage" commits and a CMS with no changelog for the parts that weren't in the CMS.
This is the thing people miss. Vibe coding doesn't lack power. It lacks surgical precision. One poorly worded prompt and your SEO is trashed, your tracking pixels are gone, or your branding is quietly broken on three pages nobody checks regularly. You've traded a rigid tool that constrains bad decisions for a flexible one that enthusiastically executes them.
The staging problem
"Just set up staging environments," I hear you say. Sure. Whose job is that? Whose job is keeping them in sync with production? Whose job is making sure the CMS content on staging doesn't leak to production when you merge? Whose job is writing the runbook for the client's intern when you're on leave?
Webflow ships with staging baked in. You publish to a subdomain, the client reviews, you publish to live. That's it. That's the whole workflow. A marketing coordinator can do it. A junior can do it. You can do it from your phone.
To replicate that experience on a custom Astro + Sanity setup, you are now running a small DevOps operation. You're maintaining preview deployments, branch protections, environment variables, and a deploy pipeline. For a ten-page marketing site. For a client who just wants to update their pricing.
You haven't saved money. You've just moved the cost from a line item on an invoice to a shadow cost buried in your own time -- which, because you're not billing it, feels free. It isn't.
The "Webflow is building for Enterprise" thing
This one comes up in every thread and it's backwards.
Yes, Webflow ships big features to Enterprise first. That's how every SaaS works. It's called product development. Eventually those features roll down the plans once the docs, support flows, and edge cases are ironed out. NextGen CMS did exactly this.
But notice what people are actually saying when they make this complaint: "A bunch of huge companies with real IT departments and real budgets are choosing Webflow." That's meant to be the gotcha. Companies with full engineering teams -- people who could build anything they want -- are deliberately choosing Webflow.
Think about that for thirty seconds. Why would they?
Because the Webflow value proposition isn't "we're the only way to build a website." It's "we're the best way to let your marketing org move fast without breaking things." Engineering teams know this. They've lived through five years of "let's just build the marketing site in Next.js." They've watched it rot. They've been the person paged at 11pm because someone's deploy broke the homepage before a product launch.
The Enterprise adoption isn't a red flag. It's a market verdict from the people who've tried both.
The free lunch that isn't
One commenter on that Reddit thread buried a single sentence near the bottom that nobody upvoted:
"You all realize Claude etc is heavily subsidized right?"
They're right, and it's the part of this conversation nobody wants to have. The current economics of "just vibe code it" are running on venture capital. AI inference pricing today is not AI inference pricing in two years. If you're building a business model around "my stack costs $0.0001 per Claude call forever," you're building on sand.
Webflow charges you $39 a month. Predictable, boring, sustainable. Your AI-coded stack might be cheaper today. Ask me again when pricing normalises and your build times triple because now you're rate-limited on the token budget.
Where vibe coding actually wins
I'm not here to tell you Webflow is always the answer. It isn't. There's a category of project where I leave it on the shelf, every time.
Anything with a non-traditional UI. A site whose entire experience is a 3D scene, or an interactive map, or a full-screen video piece. Anything where the Webflow canvas stops helping and starts fighting you, and where the CMS doesn't meaningfully benefit the client because the content is the code. For those projects, go custom. Use Astro. Use Next. Use Claude. Go nuts.
But if your project is "a company's marketing website with a blog, some CMS collections, a pricing page, and a contact form" -- and if that company has employees who are going to edit it -- you are not the exception. You are the rule. And the rule is: Webflow still wins.
The actual question
The whole vibe-coding-vs-Webflow debate is a proxy for a deeper question that nobody on Reddit wants to ask out loud: who is this website actually for?
Is it for you to feel clever about your tech stack? Cool, do whatever.
Is it for your client's business to run smoothly, for their team to ship campaigns without pinging you, for their content to stay stable while their marketing lead sleeps at night? Then stop pretending the tooling is the bottleneck. The bottleneck has never been the tooling. It's been the handoff. Webflow handles the handoff. A custom stack, no matter how elegant, usually doesn't.
So the next time you see someone on Reddit proudly announcing their migration, ask yourself one question before you nod along:
Did they tell you what happens when the client needs to change something and they're not around?
If they didn't -- they haven't finished thinking.
