The CMS World Is Shifting, and Agencies Need a New Foundation

I saw three headlines last week and felt something click into place. 

Wix cut roughly 20% of its workforce, around 1,000 people, citing AI competition and currency pressure. Webflow restructured its team with no warning, employees finding out when their laptops locked at 7am, brutal, accompanied by a CEO memo about pivoting to “the agentic web.” And Contentful, one of the headless CMS success stories of the last decade, signed a definitive agreement to be acquired by Salesforce. 

I want to be upfront: I work at Blutui, a platform built specifically for agencies, so I have a stake in how this conversation goes. But I’d be making this argument regardless, because what happened last week wasn’t just industry noise. It was the clearest signal yet that the CMS model, the one most agencies have quietly built their entire web practice around, was never really built for them in the first place.

The CMS Was Never Yours 

Before I joined Blutui, I spent time working inside agencies. And one thing that struck me consistently was how much of an agency’s energy went into working around their tools rather than working with them. 

The CMS was designed to solve a specific problem: give marketing teams control over content without needing a developer for every update. For a single organisation managing its own website, that makes sense. But agencies aren’t single organisations managing one website. They’re running web practices across dozens, often hundreds of clients simultaneously, each with different needs, different timelines, and different levels of technical sophistication. 

The brief was always narrow. Onboarding a new client or project meant starting from scratch. Maintaining consistency across a client portfolio meant manual effort at every level. White-labelling was an afterthought, if it existed at all. And the platform’s priorities, its roadmap, its pricing, its future, were never set with the agency in mind, they were set for anyone with a credit card that worked. 

Agencies adopted mainstream CMS tools en masse because they were the best available option at the time. But “best available” and “fit for purpose” are not the same thing, and that gap has been widening for years. 

The Disruption Was Predictable 

What’s happened to Wix and Webflow isn’t surprising if you’ve been watching the trajectory. Both platforms built their businesses on democratising web creation, which worked brilliantly, right up until AI-powered builders arrived and democratised it further, faster, and cheaper. 

Wix’s share price has fallen over 50% in 2026. Webflow is repositioning itself as an enterprise marketing platform, which is a polite way of saying it’s moving away from the mid-market where most agencies actually operate. Their new customer sits in a corporate marketing department. The agency that championed Webflow to its clients for the last five years is an afterthought. 

For agencies who built their production workflows around these tools, that’s a real strategic problem. Pricing structures are changing. Roadmaps are shifting toward features that serve the platform’s new target customer. And with Contentful now under Salesforce’s purview, the risk of that same drift is imminent for anyone whose headless CMS sits at the centre of a complex client stack.

I’ve seen this pattern play out before. A specialist tool gets acquired or repositioned, the platform’s priorities migrate toward the acquirer’s customer base, and the agencies who built their workflows around it are left renegotiating their practice from the ground up. Usually at the worst possible time. 

What Agencies Actually Need 

The agencies I’ve watched navigate disruption best aren’t necessarily the ones using the most sophisticated CMS. They’re the ones who stopped treating a CMS as the foundation of their web practice and started building around an ecosystem designed specifically for how agencies operate. 

The difference matters. An agency web ecosystem is architected around the agency, not the end client. White-labelling is native, not bolted on. Onboarding a new client doesn’t mean rebuilding from scratch. Design consistency across a portfolio is managed centrally. The agency is the product of record in the client relationship, not just the implementation layer sitting on top of someone else’s software. 

The commercial model shifts too. Agencies operating within a proper web ecosystem aren’t just delivering projects, they’re building a recurring revenue base from managed sites. That’s a fundamentally different business from one that depends on hunting for the next build. You’re compounding value on the portfolio you already have, and that portfolio becomes a genuine asset rather than a list of completed jobs. 

None of this is a new idea. But the urgency around it is new. Last week made that urgency visible in a way that’s hard to ignore. 

The Question I’d Be Asking Right Now 

If Webflow is repositioning for enterprise, if Contentful is being absorbed into a CRM giant, if Wix is cutting a fifth of its team under pressure from AI, what does that say about the durability of any platform that wasn’t designed with agencies at the centre of its thinking? 

The right time to ask that question isn’t when your platform sends a pricing update or announces it’s been acquired. It’s now, while you still have the space to make a deliberate decision rather than a reactive one. 

The agencies who will feel this disruption least aren’t the ones who found a better CMS. They’re the ones who stopped depending on platforms that were never really theirs to begin with.