Webflow or WordPress? Three Studio Stories That'll Help You Decide

You've probably already read five articles trying to figure this out. I have too. Most of them follow the same formula: a giant table comparing features, some bullet points about pricing, a vague "it depends on your needs" conclusion. They're not wrong. They're just not very useful.

So I'm going to try something different here.

Instead of comparing the platforms directly, I'm going to walk you through three agencies that made three different choices. They're composites, built from patterns I keep seeing across the dozens of agency owners I've spoken to in the last couple of years, but the details are real. Real costs. Real frustrations. Real numbers. Real outcomes.

By the end, you'll see your own agency in at least one of these stories. And once you see yourself, the answer to "Webflow or WordPress?" stops being abstract. It becomes obvious.

Let's meet them.

Studio One: Lina's all-Webflow design shop

Lina runs a four-person studio in Brooklyn. She started it in 2022 after seven years at a brand agency, where she'd been the senior designer who quietly knew Webflow on the side. When she opened her own doors, she made one decision early and stuck with it: everything would be built in Webflow. No exceptions.

Three years in, here's what her studio looks like.

What she builds

Her typical client is a Series A or B startup that needs a beautiful marketing site. Sometimes it's a DTC skincare brand, sometimes a B2B SaaS company, sometimes a media-adjacent project. Project size is usually $25,000 to $45,000. Twelve to twenty pages, a blog, a careers section, a few landing pages. Nothing wildly custom.

She runs about 18 to 22 of these projects a year.

What Lina would tell you

"Webflow lets me run a profitable design studio without ever needing a developer. That's the whole game for me. But the moment a project has anything genuinely custom, memberships, complex e-commerce, real integrations, I either have to say no, or I have to bring in someone outside my team. That happens about three times a year. I've made peace with it."

Studio Two: Marcus's 14-person WordPress agency

Marcus runs a fourteen-person agency in Austin. He started it in 2014 with one partner, both web developers. They've been on WordPress since day one. They considered moving, really considered, around 2022, and decided not to. He's glad they didn't.

Here's what his agency looks like in 2026.

What they build

Marcus's typical client is a mid-market B2B company doing $20M to $200M in revenue. Manufacturers, professional services, a couple of healthcare clients, two universities, three SaaS companies. Project size is usually $60,000 to $180,000 for a new build, with annual retainers between $30,000 and $90,000 per client.

They run about 12 to 15 new builds a year, plus a portfolio of around 40 active retainer clients.

Their stack

Marcus's team has standardized hard. Every new project starts with the same recipe: WordPress core, Bricks Builder, Advanced Custom Fields Pro, Yoast SEO, a custom internal starter theme they've been refining for years, and a few specific plugins depending on the project type. They host almost everything on Kinsta or WP Engine, with a handful of clients on dedicated infrastructure.

They have three developers, four designers, three project managers, two account leads, a content lead, and Marcus.

What Marcus would tell you

“WordPress is the right choice for the kind of agency I want to run. I want recurring revenue, I want technical depth, I want to be the partner clients call for years. WordPress lets me be that. But I'll be honest, if I started my agency today as a one-person design shop, I'd probably pick Webflow. I'm running a development agency, not a design studio. Different choice, different platform.”

Studio Three: Henna Studio, the ones who run both

Henna is a seven-person studio in Manchester, UK. They started in 2020 as a WordPress-only shop, added Webflow capability in early 2024, and now describe themselves as "platform-agnostic." Their two co-founders, one a designer, one a developer, split the team along those lines.

Here's their picture.

What they build

Their client mix is wider than Marcus or Lina's. They serve UK SaaS startups, two small media publications, a few nonprofits, a handful of B2B service businesses, and the occasional e-commerce brand. Project size ranges from £15,000 to £80,000, a wider spread, by design.

They run roughly 20 new builds a year, plus 15 ongoing retainer clients.

How they decide

Their internal rule is pretty simple: default to Webflow unless one of three conditions is true.

The client has more than a few hundred content items, complex content modelling needs, or wants in-house editorial control. → WordPress.

The project has memberships, marketplaces, learning systems, or anything with complex user roles. → WordPress.

The client has internal IT, strong data ownership preferences, or existing WordPress infrastructure. → WordPress.

Otherwise: Webflow.

In practice, about 60% of their projects end up on Webflow and 40% on WordPress.

What the founders would tell you

“Picking one platform was a luxury we couldn't afford. Our market in Manchester is too varied. When a major regional publisher came to us in 2023, they needed WordPress, full stop, non-negotiable. We almost lost the deal because we were Webflow-only at the time. We pivoted, hired a WP lead, and we're not going back to single-stack. But I won't pretend it's free. Running both costs us maybe 10% of our potential margin. We just decided we'd rather have the broader market.”

The patterns across all three stories

Step back from the individual studios and a few things become really clear.

Pattern one: Lina's profile (design-led, small team, marketing-site work) is the cleanest fit for Webflow. She's not compromising anything. The platform's strengths line up exactly with what her studio sells. The friction points she hits, memberships, custom integrations, the seat pricing change — are real but rare. She's running a more profitable business than she would have on WordPress.

Pattern two: Marcus's profile (developer-led, mid-sized team, complex B2B work) is the cleanest fit for WordPress. He could not run his business on Webflow. Half his projects wouldn't even be possible. The frustrations he lives with, plugin maintenance, hosting ops, hiring senior devs — are the cost of operating at his level of complexity. Those costs are baked into his pricing.

Pattern three: Henna's profile (mixed clients, mid-sized team, geographic constraints) is when hybrid makes sense. They're not picking both because they can't decide. They're picking both because their market demands it. If Lina tried to run a hybrid model with her current client base, she'd just be adding overhead. If Marcus did it, the same thing. Henna's market is wide enough to justify the cost.

The platforms aren't competing on the same field. They're solving for different agencies.

So which studio are you most like?

This is the question that actually matters. Let me give you a quick way to tell.

You're most like Lina if:

• Your studio is small (1–6 people)
• Your team skews designer over developer
• Most of your clients want marketing sites in the $15k–$60k range
• You don't want to manage hosting or be on call
• You'd rather do more projects than do bigger projects

You're most like Marcus if:

• Your agency is bigger (10+ people) or you want it to be
• You have or want to hire real developers
• Your clients have technical depth or complex needs
• You want recurring revenue as your primary growth engine
• You can imagine your agency as a long-term partner to ten or twenty clients, not just a project shop

You're most like Henna if:

• Your client base is genuinely varied
• You serve a regional market where you can't be too specialized
• You're past three or four years in business and you've already done both
• You have co-founders or senior leads who naturally split along design vs development
• You'd rather have wider market access than tighter operational margins

If you read those three descriptions and one of them made you nod harder than the others, that's your answer.

If two of them made you nod equally, you're at a transition point, probably either growing into Henna's model from Lina's, or shrinking into Lina's model from a former Marcus-style ambition. Both are valid moves.

If none of them fit, you might be running a different kind of agency entirely (e-commerce specialist, niche industry vertical, productized service shop), in which case the Webflow-vs-WordPress question might be the wrong one for you, and you should look at platform fit through your specific lens.

What I'd say if you were sitting across from me

If you and I were having coffee right now and you asked me this question, here's what I'd actually say.

I'd ask you three questions first:

"What's your team's natural instinct, design or development?" Not what you wish it were. What it actually is. The platform that fits your team's instinct will make you faster, happier, and more profitable.

"What kind of clients do you want in three years?" Not the clients you have now. The clients you want. Marketing teams at growing companies lean Webflow. Technical teams at mid-market businesses lean WordPress. Your future client base is the better predictor than your current one.

"How much do you want to own your stack?" Some agency owners love owning the infrastructure, the hosting decisions, the deep technical control. Others would happily pay someone else to handle all of it. There's no right answer, just two different temperaments.

Your answers to those three questions usually make the platform decision obvious. If they don't, run with Webflow. The cost of being wrong is lower, and you can migrate later if you need to.

What you should not do is keep agonising over this. The agencies that win on either platform are the ones who picked, committed, built a real system, and got disciplined about their craft. The agencies that struggle are the ones who second-guess the choice every six months and never get deep on either tool.

Pick a story. Pick a platform. Build the studio you actually want to run.