I Build on Webflow Every Day. Here's What This Week Actually Means.

I manage a Webflow site full-time and build on the platform for clients, so when Webflow restructured this week, and the way it happened became its own story, I had more than a passing interest. This is me thinking out loud about a tool my work depends on.

The CEO published a post laying out a pivot to what she called an "agentic web marketing platform": smaller, faster teams, AI agents working alongside marketers. And then the story became less about the strategy and more about the way it happened.

Let me separate two things, because they keep getting blended together.

The execution and the strategy are different questions

The handling drew real criticism, and from what's been reported, fairly. People described being locked out of their laptops before they'd been told they'd lost their jobs. One engineer ended up asking publicly online whether he still had a role. The company didn't disclose how many people were affected; the announcement just said "many." For a second restructuring in under two years, that's not the way you want people who built the thing to find out.

I can hold that and still think the direction is sound. Both are true at once. Saying the strategy makes sense isn't a defence of how the news landed on the people it landed on, and I'm not interested in glossing over that part just because I like the product. That said, I'm wary of joining a pile-on. People had a bad Wednesday; I'm not here to mine it for a take. So I'll say it once, plainly, and move to what I actually came to talk about.

The AI panic is aimed at the wrong end of the market

Here's my real read, and it's calmer than most you'll see this week.

If your whole offer was "I'll build you a simple five-page site," this is a genuinely harder moment, and I won't pretend otherwise. A small business can now describe a brochure site to an AI tool and have something live by lunch. That floor is eroding and it isn't coming back. If that's where you've been working, the honest move is to think hard about where you go next.

But that's the bottom of the market. At the top: the enterprise client, the large organisation with a real web footprint, the team treating their site as a growth engine, none of that AI-builder story applies. A massive organisation doesn't benefit from "describe it and ship by lunch." They benefit from structured content, governance, integrations, experimentation, a brand that doesn't look generated. They benefit from control. That's exactly what an AI builder can't hand you yet, and exactly what Webflow's pivot leans into. For the kind of work I do, and the site I manage day to day, this news is closer to reassuring than threatening.

Webflow is affordable, for who it's affordable for

People always ask about cost, so I'll be straight. Webflow was never the cheapest option, and a company that just narrowed its market isn't about to get cheaper. But "affordable" is the wrong frame. It's affordable for the teams it's built for: the ones where it pays for itself in shipping speed, in not babysitting servers, in not playing the WordPress plugin lottery at 2am. The pivot just makes that explicit. That's positioning, not a flaw to apologise for.

What I think happens next

A few predictions, held loosely.

Agents will land inside the Designer, not replace it. I'd expect the visual canvas to stay and AI to sit on top of it, handling things like funnel optimisation or testing variants. That's my guess at the shape, not something Webflow has spelled out.

The partner ecosystem splits. Developers who think in systems: data layers, integrations, automation, CRO, get more valuable. Template-flippers and brochure-site builders get squeezed by the same tools eating the floor. The easy stuff got easy; the hard stuff stayed hard and got more valuable.

And my own default doesn't change. On every project I start with the same question: what gives me the most control here? Sometimes that's Webflow. Sometimes it's a custom build with Airtable or Xano underneath and automation on top. Webflow is one strong tool in the stack, not a religion, which is exactly why this week doesn't rattle my confidence in it, even as it gave me reason to think about how I'd want to be treated if I were on the other side of a decision like that.

Where I'd focus right now

If you're already on Webflow: invest in your CMS architecture and data layer now. Agents need structured data to do anything useful. A messy content model holds you back more than the platform's direction does.

If you're hiring a Webflow developer: hire for systems thinking, not just a nice visual eye. The visual part is becoming the easy part.

If you're a freelancer or agency: the moat is depth. Learn the integrations, the APIs, the automation layer. That's the work AI can't take, and increasingly the only work worth charging for.

Webflow's bet is that the future of marketing isn't AI replacing marketers. It's AI joining the team. I think that bet is roughly right. I'm lucky to be sitting at the end of the market where that's true, and not everyone is. I just hope the company remembers, as it builds toward it, that the teams it's betting on are made of people too.