← Back to all posts

Vibe coding did not kill Webflow

AI can write your site in a minute. Living with that site is another story.

Abstract artwork: scattered deep blue blocks resolving into an ordered glowing cyan grid

The moment AI started writing decent code, people lined up to declare no-code dead. Why click around a visual editor when you can type "make me a landing page" and get one? I build with both, AI-assisted code every week and Webflow for years of client work, and I think the obituary is early.

What actually happens with a vibe-coded site

Sixty seconds in, you have something impressive. The demo moment is real and genuinely fun. Then real life arrives: the client wants to edit a headline themselves, marketing wants a new case study page every week, someone needs the font changed everywhere except in that one section. And you discover the catch. Generated code is cheap to create and unpredictable to change. Every edit is another prompt, another diff to review, another chance for the layout to quietly drift. The site was free. Owning it is not.

Webflow's boring superpowers

Against that, Webflow's advantages look boring on a demo stage and priceless in month six. A design system the tool itself enforces: classes, components, a style guide that every page inherits from. A CMS a marketer edits on a Tuesday without breaking anything. Changes that stay changed, made visually and verified by looking. Hosting that never surprises you. None of this demos well, and all of it is what keeps a site alive for years.

The real division of labor

I use AI all over my Webflow work: drafting copy, generating custom code embeds, thinking through page structure, debugging an interaction. And Webflow keeps pulling AI deeper into the Designer itself. That points at the likely future: not AI replacing the tools, but AI operating inside them, where structure keeps it honest. A model producing arbitrary code can break anything. A model working inside a design system can only fill in the blanks. Constraints are what make AI output usable. Could a future model own the whole pipeline, structure, maintenance and editing interface included? Maybe. Nobody serious is certain either way.

The part people miss

The bottleneck was never typing the code. It is knowing what good looks like, and keeping it good for years. I said it on stage at LOGIN and it holds here too: vibe coding is easy. Being good isn't.

Webflow links in this post are partner links.