Why I still reach for Webflow
Webflow, Next.js + Sanity, or AI-generated full-stack? The decision isn't about technical purity — it's about who owns the site six months after launch.
I've shipped production React for ten years. I still recommend Webflow to half my clients. The reason isn't nostalgia — it's operational speed, and a hard question most teams skip: who owns this site six months after launch?
The question that actually decides the stack
Not "which is more powerful" or "which is more modern." The question is who edits the site once I'm gone. A marketing team that can publish pages, edit copy, and A/B test without a deploy pipeline will out-learn a team waiting on engineering tickets every single time. The best stack is the one your team can actually operate.
Webflow: when the marketing team owns it
If a non-technical team needs to ship and iterate fast, Webflow wins. Visual editing, no deploy pipeline, and real performance and accessibility if you build it right. The trap is treating it as a toy — a sloppy Webflow build rots as fast as any other. A disciplined component system is what makes it last.
Next.js + Sanity: when engineering owns it
When the site is deeply custom, integrates with a product, or needs logic Webflow can't express, I reach for Next.js and a headless CMS. More power and control, and more responsibility — someone has to maintain a codebase and a deploy pipeline. Worth it when the site is a product surface, not just marketing.
AI-generated full-stack: when speed beats everything
For throwaway experiments, internal tools, and rapid prototypes, AI-generated full-stack code is now genuinely fast. I use it where being 80% right today beats perfect next week, and I do not use it where it becomes load-bearing without review — the same caution I apply to shipping AI code generally.
The decision matrix
- Non-technical team, marketing site, frequent edits → Webflow
- Custom logic, product integration, engineering team → Next.js + Sanity
- Prototype, internal tool, speed over longevity → AI-generated
The mistake I see most
Teams pick a stack for status, not fit. A five-person startup adopts a complex headless setup because it sounds serious, then ships nothing for two months because every copy change needs a developer. The unglamorous truth: the right stack is whichever one gets your team shipping and learning fastest.
Why this matters for AI work
People expect an "AI architect" to push the newest stack on everything. The opposite is true. Knowing when not to reach for the powerful option is the entire skill, in stacks and in AI itself. The tool should fit the team, not the other way around.
Want help picking the right stack for your situation? Book a call or see recent work.
I ship production AI for startups and teams — agents, RAG, automations — on a decade of design & Webflow craft.
About me →Keep going.
Websites that grow with the brand
The modular system that lets non-technical teams ship pages without breaking the design — and why that discipline is what makes the AI I build ship clean.
AI agency vs. in-house vs. fractional: how to staff your AI work
The real trade-offs between hiring an AI agency, building an in-house team, and bringing in a fractional AI lead — and which fits your stage.
How to add AI to your SaaS (without a rebuild)
A practical sequence for shipping your first real AI feature into an existing product — what to build first, what to skip, and how not to break what already works.