State of Enterprise WordPress 2024 Report

Brad:
Hey everybody, welcome back to another exciting episode of Scaling Enterprise, the WordPress Enterprise Podcast on Do the Woo. We are back in the new year, 2025—so excited to get back into fun conversations, fun interviews, and continue the conversation around WordPress and the enterprise. Today, I’m one half of your hosting crew, Brad Williams of WebDev Studios, and I’m also joined by Tom Willmot of Human Made. Hey Tom, how’s it going?

Tom:
Great to be back. Good to be here in the new year, getting these episodes flowing again. We had a little break there with Christmas and whatnot, and I look forward today to doing a bit of a director’s commentary on the state of enterprise WordPress, which a whole group of us in the enterprise WordPress ecosystem have collaborated on. I think, actually, it’s being released today—the results of the report are being released today. So this is well-timed. By the time you’re listening to this or watching us, you should already have seen us sharing this across socials. I think the best way to do it, Brad, is I could just share my screen, and we could go through the site and do it. Yeah, do a little bit of a director’s commentary.

Brad:
Yeah, let’s share it out. We’re on video now, so definitely check out the video. If you’re listening to the audio-only version, we’ll try to be as descriptive as we can about the data points and things we’re discussing, but certainly, if you can pop over and check out the video to see the actual report that we’re sharing, it’s really—not only is the data interesting, but it’s a really nicely prepared website with nice visuals around the stats and graphs. And it’s always fun to kind of dig in and nerd out on some data, right Tom? So yeah, let’s dig in. I think these results are fun, especially this being the second year that Big Bite has led the charge on this. Now we’re starting to see a little bit of historical data between last year and this year, which is also interesting to compare.

Tom:
And shoutout to Iain and Big Bite for spearheading this. It’s a collaboration between a whole group of us, but it’s definitely been spearheaded by Iain and Big Bite. We did try to get him for today—it would have been great to have him on here—but unfortunately, we didn’t give him enough notice to be able to make it. So I’ll see if I can grab him at a different time, and maybe we can put out an extra episode chatting with him, just to get a bit of the history and how he’s thinking about this.

I mean, maybe this is a good place to start. I think it is impressive just how many of the main players in enterprise WordPress are involved in this. There’s a whole survey that goes out, and we are all sharing this with our client bases and networks. So that’s where the audience for the report comes from, which you’ll see reflected in the results.

Brad:
I love seeing the agencies, the hosts—I mean, it’s a who’s who of WordPress in the enterprise within the community and of companies. If you’re at an event, if you’re at a campus, and someone is talking about WordPress Enterprise, they’re probably a part of one of these companies, most likely in the WordPress space. So it’s very much a group effort, and I think it also just lends a lot of validity to what we’re talking about and the data that is coming in because a lot of this data is directly from our clients in the enterprise. And these are big…

Tom:
Brands. These are big brands. I think that’s a great point, which actually—it might be nice to even have a bunch of their logos on here just to really reinforce that. Just here, we’ve got Amnesty International, The Times, Princeton University, Harvard University, and I know the University of Liverpool—that’s one of ours.

So yeah, these are the biggest users of WordPress in the world, and it’s interesting to know what they’re thinking and to be able to compare how that’s changing. Alright, shall I scroll down a bit, and we can actually get into it? Let’s see how this goes. Yeah, yeah. Let’s see how this goes.

I guess the first thing, we’ve got a broad set of questions around the profile of the companies filling this out. I found this geographic split a bit surprising. My intuition probably would’ve told me that it would be much more skewed toward North America. I wonder if this reflects the European presence—the fact that there are a bunch of European agencies who are contributing to this.

Brad:
I think so. I mean, yeah, I kind of felt the same, but I agree. I think it’s based on a lot of the agencies having clients in those areas more so. Seeing more and more of Europe responding to the report. In fact, North America was down last year—it was 36%, and this year it’s 28%. That’s interesting. It doesn’t mean fewer people are using it, just that fewer people responded to the survey in North America.

Tom:
And I mean, from my own anecdotal experience running Human Made, it’s definitely not that North America is the largest, with EMEA second. There is some growth shown here in APAC and Latin America, which I would say—our experience at Human Made probably reflects that, which is good to see. How about for WebDev? Is your client base primarily North America?

Brad:
Primarily? Yeah, primarily in the U.S., but yeah, North America for sure. A few here and there in other parts of the world, but yeah, primarily North America.

Tom:
Yeah, the industry sectors—I think this is quite an interesting one. I’ll just click between these so people who are viewing can see. For people who are listening, we’ve got publishing and media as the largest sector, which it was last year too.

And I think these results do reflect the difference between 2023 and 2024. They reflect a trend that we probably all agree we’ve been seeing, which is that publishing and media have long been the largest sector, but that over time these other sectors—tech, enterprise, marketing, nonprofit, financial services—are growing as sectors for WordPress Enterprise.

Brad:
Yeah, marketing has grown from 12% to 16%. I’m honestly surprised marketing isn’t a little bit higher, but maybe it’s just because it’s the enterprise large-scale version versus—I expect media to be at the top for sure. I honestly thought marketing might be in the second spot, but it’s actually technology. But yeah, maybe it’s just the sheer size of these companies, and where marketing, while it’s a part of it, might be a smaller part of it. Clearly, based on the results, it seems to be.

Tom:
Yeah, I mean, another bias that I can imagine will impact this report is that companies who are kind of closer to the WordPress community are probably more likely to be filling this in. Anecdotally, I noticed that amongst our client base—our publishing clients, who’ve been using WordPress probably for the longest—a lot of them are attending WordPress events and engaging with the open-source community.

So they’re interested in open-source and the WordPress community and are excited to fill these out, whereas some of our more traditional enterprise clients are perhaps less motivated to fill out these kinds of reports. So maybe we would see a bit of that. I don’t know, I’m just looking to see if there are any other changes here.

Interesting to see—actually, it’s a bit of a different list. No government in 2024, but we had government in 2023.

Brad:
It just barely crept onto the list last year with 2%, and manufacturing was down at 1%. So yeah, I mean, the government sector, from my perspective, has grown a bit in recent years with WordPress, but it’s still a very small percentage of the overall slice of the pie.

So it has seen some good growth. Whitehouse.gov continues to run WordPress.

Tom:
I saw that the new administration site went live, and that’s still WordPress.

Brad:
It’s still WordPress. Every administration generally launches their new site, so whatever was up there goes away basically overnight, and the new site comes online. Nobody really knows what it’s going to be or how it’s going to be built—other than, obviously, the people working on it. So it’s nice to see them stick with WordPress because, prior to the last administration, it was Drupal.

Tom:
And I don’t think we know who built it, right?

Brad:
No, I don’t know who built it—not yet. I’m sure we’ll find out eventually.

Tom:
And I think 10up built the last one, which was great to see them involved in the last one.

Okay, I’ll keep scrolling. Next, we’ve got respondents by departments. I guess, yeah, this is about where in the enterprise the people filling this survey out sit, which is interesting.

I think the interesting thing you’re reading here is: are these leadership positions making decisions around the CMS—choosing whether or not to use WordPress? Or are these the actual users of the CMS in editorial or marketing, and how’s that changing over time?

Brad:
And it’s flipped. I mean, if you look at last year, leadership was at the top at 40%, with engineering/product dev at 35%. And now, in 2024, engineering is at 44% and leadership is at 31%.

So that’s an interesting swap in the data points there. Does that essentially mean leadership is putting more of their trust in the engineering department—saying, you make your own decisions, you tell us what we should be using—versus kind of forcing a platform on their team? That’s a very interesting change from last year.

Tom:
Yeah, I’m just thinking anecdotally—that probably does reflect a little bit of what we’ve seen in the sales cycles at Human Made. It seems like leadership is delegating more of the decisions, which actually hasn’t been great.

It has lengthened sales cycles because then you’re talking to people who can’t necessarily make the final decision. They’re putting together a case that they’re submitting to leadership for approval.

And, of course, you ideally want to be talking to the decision-makers. Whether that’s related or not, I don’t know. I mean, I remember last year when this report came out—40% of the respondents being in leadership was great.

That was a great result, and I think that’s really great to see. Especially considering the history of WordPress—WordPress has often come into these organizations kind of bottom-up. People on the ground—users—advocate for it to be chosen as the platform.

And over time, we’ve seen a shift towards leadership making these re-platform decisions. So, great to see that still reflected, I suppose.

Brad:
Let’s get into traffic—everyone’s favorite data.

Tom:
Everyone’s favorite data point! So yeah, what do we have here? Over 10 million, 5 to 10 million, 1 to 5 million, under 1 million, and fewer than 500,000.

Brad:
I mean, obviously, the fewer than 500,000 category is sitting at 29% at the top. But overall, there’s not a huge swing between these different traffic segments.

Yeah, it’s pretty broad.

Tom:
Yeah, exactly—it’s pretty broad, which is good. I think, for the overall survey, it’s not skewed one way or the other toward either massive traffic sites or smaller sites. Otherwise, their answers would probably be very different.

So yeah, it’s nice to see kind of a decent spread across these different traffic sizes.

Brad:
Yeah, and I think it really speaks to one of WordPress’s strengths as a platform for these kinds of enterprise customers—it can really scale across a full range of traffic and complexity.

Especially from a budget point of view. Some of the competitive platforms—like AEM—could be a good fit for the really large sites where it makes sense to make a big investment, but they really struggle to justify using AEM licenses for smaller sites.

Tom:
Yeah, absolutely. It speaks to the power of WordPress—the fact that people can run it at a small scale or a massive scale, and it works either way.

I mean, it might be nice in future years to have some higher options here because over 10 million—I mean, actually, that’s still relatively small.

When you really get to the top end of WordPress, you can certainly be talking tens, hundreds of millions—even billions of visitors a month.

Brad:
And these are monthly visits. So when you say small, that’s true—many WordPress developers and companies out there consider 10 million visits in a month to be pretty significant.

But I get your point—there are absolutely WordPress sites that are handling way more traffic than this in a monthly span.

Tom:
Yeah. Although this is visitors, not page views—so that’s a good point.

Okay, I think that’s a nice result, which speaks to WordPress’s broad penetration.

Tom:
Yeah, so next up, we have the DXP/CMS stack question. Are you relying only on WordPress, or are you using it with other platforms?

Brad:
Yeah, I like this data. 55% are only using WordPress—over half of the respondents are only using WordPress, which last year was 38%. So that’s interesting.

Which is surprising, honestly, because in the enterprise, I am fairly confident that every one of our enterprise clients uses multiple platforms. WordPress is one piece of their strategy, and usually, it’s a big piece, but it’s not the only piece.

So to see that over half of the respondents are all in on WordPress for everything is very interesting to me.

Tom:
Yeah, that is interesting. That’s probably great for WordPress.

And I wonder—if we just surveyed Human Made’s client base or WebDev’s client base, would the number be that high? I think we probably do see more multi-CMS environments.

Brad:
I think this, again, and honestly, that’s the way I pitch it—we don’t have to replace everything. WordPress is really good at doing what it does in certain areas within your online solution.

So for marketing, media, publishing—it doesn’t have to replace everything. It’s a very good secondary CMS in many cases.

Tom:
And I mean, I think probably the narrative we would like to draw from this—and leave it to the listener to decide whether this is enough evidence or not—is that WordPress often comes in as a secondary CMS, and then over time, it becomes the primary CMS, and then eventually the only CMS.

That’s certainly our goal—when we’re bringing in WordPress as a secondary CMS, we want to make sure it has a path to growing into the primary one.

Brad:
Interesting, too—a few new responses over last year. Things like Salesforce, Payload CMS, and Strapi are now on the list, while some other platforms are falling off.

Drupal is still on here, but it has gone from 9% to 5%. Acquia—which is essentially Drupal—is falling off the list.

There’s definitely some shift towards the bottom in terms of which platforms enterprises are using. Some are starting to grow, and some are starting to fall off, but WordPress still sits at the top.

Tom:
Yeah, I mean, another real strength of WordPress is, as you said, that secondary CMS penetration is so high. The market share of WordPress in enterprise is really high compared to these other platforms.

Even though, actually, those competitors probably have a smaller number of total clients, on average, those clients are using their platforms as a primary CMS more often than WordPress users do.

Brad:
That makes sense. And I think you’re right about WordPress coming in for one particular use case—one project—and then spreading.

Most people, especially in the professional world and the enterprise world, are familiar with WordPress in some capacity at this point.

So I feel like teams are probably excited when they get the opportunity to work with WordPress, and then they push it internally—
“We should use it here,”
“We should use it there for this other thing,”
because whatever they were using has been such a headache, costs so much, and takes so much time.

And over time, those tentacles start to spread through departments within the enterprise. And next thing you know—it’s really taken over.

Tom:
That’s exactly it.

Okay, now we get onto the second set of questions. That first set was all about the profile of the kinds of companies filling out the survey.

Now, let’s turn our attention to how they’re using WordPress.

So, first question: How does the organization use WordPress?

We’ve got a range of answers here:

• Publishing news (which isn’t surprising, given that the largest industry in the report was publishing).
• On-site content/self-building sites.
• Publishing blogs.
• Periodically maintaining or updating online content.
• Directly selling a product or service online.

I mean, that last one is interesting—directly selling a product or service online. That is a bit of a growing use case.

Brad:
Yeah, it’s nice to see more sites using WordPress to sell products and services—especially as things like WooCommerce become more mature and have been around longer.

I think the enterprise is starting to be more open to WooCommerce as a solution, among other payment systems within WordPress.

And yeah, if enterprises are starting to sell products and services, that speaks really highly to the platform. That means it’s directly generating revenue for them.

So that is not a light decision they’re going to make—what systems to use to sell products and services.

Tom:
And it’s great for the ecosystem as well.

Companies that are making money off of their WordPress-powered website are going to be more willing to invest in it—more willing to put money back into it.

So that’s great for the ecosystem, too.

Brad:
And it has grown—12% year to year—but honestly, that’s still a pretty decent number.

I wouldn’t expect it to take over. Publishing content, publishing news—those are always going to sit towards the top, because WordPress is a content publishing system, and that’s what it’s always done really well.

So I think where it’s sitting now—even at 12% for eCommerce—is a pretty healthy spot, considering.

Tom:
Yeah, I think so.

Next up—headless. Headless has been a major trend within the enterprise CMS space.

So this is a really interesting question: Is your organization using WordPress as a headless CMS?

In 2023, 56% of people said no—they were not using it as a headless CMS.

In 2024, that number has gone all the way up to 75%—meaning even more respondents are saying no to headless.

Which, I guess—I would read that as a reflection that we’re past peak headless CMS as an industry.

Brad:
Yeah, that’s not surprising.

I agree. I think when headless first became a buzzword—3, 4, 5 years ago—so many projects would come in, and they’d say:

“Hey, we want headless.”

And then we’d dig into it, and it’s a five-page marketing site.

“You don’t need headless. Why do we need headless?”

And when you really start breaking it down—headless is great when it’s great. When it’s a good solution for a specific challenge, it makes sense.

But it’s not for everything. And I think the buzzword took over for a while—people were saying headless everything.

Now, I think you’re right—it’s kind of settled back.

There is a place for headless, 100%. But it will never be the dominant way that WordPress is structured and used, in my opinion.

Because it requires more technical expertise, and not every team has that capacity.

But when headless is done right, for the right use case—it’s amazing.

But it’s not for everybody—and I think that’s what this data is starting to show.

Tom:
And this split starts to feel quite healthy, actually, in terms of how often headless makes sense.

Somewhere under a quarter of the time feels like a reasonable answer for that question.

For me, this also reflects one of the reasons we co-founded the Scale Consortium in the first place.

These headless CMS startups did an amazing job in the early days—going to market, convincing everybody that what they needed was headless, and that headless was going to solve all their problems.

And because the WordPress ecosystem didn’t tell a clear story—

1. How WordPress can be a great headless CMS.
2. When headless actually makes sense, and when it doesn’t.

For a while, those headless CMS startups did really well.

And so, yeah—part of what we hope to do through Scale is to better tell the world what WordPress’s approach to industry trends is.

---

How long has your organization used WordPress?

Brad:
I love to see this: 75% over five years.

Three-quarters of respondents have been using WordPress for over five years. That’s awesome.

Tom:
Yeah, and that tells us something important—people are sticking with the platform.

I think this number does reflect the fact that we are surveying established clients.

We probably have less access to organizations that are newly moving to WordPress.

I mean, only 1% of respondents were new to the platform.

I think we’d like to see that number higher, right?

We want to see more people coming onto the platform.

If you look at net new sites moving to WordPress in the top 100,000 or top 10,000 sites, the data looks much healthier than this survey suggests.

So, there’s probably some bias here—agencies like ours tend to specialize in building long-term relationships.

So naturally, our client base is made up mostly of organizations we’ve been working with for years.

---

How frequently does your organization use WordPress?

Tom:
Okay, so here we go.

• Daily: 65%
• Weekly
• Monthly
• Less often

Clearly, most organizations are using WordPress every day.

That’s a great sign.

Brad:
Yeah, that makes sense.

This data point is really directly related to the business type and how their website operates.

A media company is going to be publishing daily, hourly—by the minute, even.

A marketing site might be more static, focused on campaign-based content updates.

But overall, it’s nice to see that organizations are in WordPress, working with it on a daily basis.

---

Which WordPress editor do you use?

Tom:
This is an interesting one.

• Block Editor (Gutenberg): 59% (up from 54% last year)
• Classic Editor: 22%
• Both: The rest

Brad:
It’s interesting that Classic Editor actually went up slightly.

That surprises me a little bit.

I get that it’s all based on who responded, but the fact that Classic Editor usage actually increased in a year—I don’t know what to make of that.

I think what it tells us is that, especially for large organizations, making the shift is not a small thing.

Moving from Classic Editor to Block Editor is a big lift.

So many organizations want to get there, but the process to get there is the challenge.

Not every enterprise can just rebuild their website from the ground up—
whether due to time constraints, budgets, or internal processes.

So a lot of them are just chipping away at it over time.

I totally understand why it’s taking enterprise clients longer to adopt the Block Editor.

They have more complex workflows, and more considerations go into these decisions.

But it’s still nice to see Block Editor adoption going up.

---

Does the Block Editor make it easier than the Classic Editor to create and publish content?

Tom:
Now, this one is fascinating:

• Yes, much easier: 55%
• Yes, a little easier: 20%
• No difference: 20%
• No, it makes it harder: 0%!

So not a single person said the Block Editor makes publishing harder.

Brad:
That no difference group—I’d really love to know what kind of content they’re publishing.

My guess is text-only content.

If you’re just writing text, then yeah—there’s no difference between Classic Editor and Block Editor.

But the moment you start dealing with any kind of complex content structure, the Block Editor makes things so much easier.

Tom:
Yeah, and looking ahead, I think it will be interesting to track Full Site Editing adoption in future surveys.

Enterprise adoption of Full Site Editing is still early, so in the next few years, we should add questions about that to this survey.

---

How many people in your organization are using WordPress?

Brad:
As expected, the largest group (41%) is organizations with 50 or more users in WordPress.

These are big teams—editorial teams, marketing teams, publishing teams.

It just reinforces what we already know—WordPress scales well.

And with new collaboration features coming to WordPress—kind of like Google Docs-style collaboration—that will be a huge boost for these larger teams.

Tom:
Yeah, and we’re seeing a shift toward larger organizations responding.

That’s a good sign.

---

What types of integrations does your WordPress setup include?

Tom:
This one is always interesting because enterprise WordPress sites tend to have a lot of integrations.

And this year, we’re seeing some movement in the rankings.

• Payment gateways are moving up—which aligns with the growth in eCommerce usage.
• MarTech (Marketing Technology) is still at the top.
• CRM integrations have fallen slightly but are still common.
• SSO (Single Sign-On)—pretty much every enterprise site we work on requires it.

Brad:
Yeah, I agree. I think most enterprise sites require SSO and CRM integration.

I’d be curious to know whether respondents could select multiple answers here, because most of the enterprise clients we work with would have all of these integrations.

---

Does your organization contribute to open-source WordPress?

Tom:
This one is surprising—more than 50% of respondents said yes (either frequently or infrequently).

That’s up quite a bit from last year.

Brad:
Yeah, that’s great to see.

Contributing to WordPress and open source in general is so important.

If nobody contributes, there is no project.

So it’s awesome to see more enterprise companies getting involved.

I always tell our clients:

If your engineers are contributing to WordPress, they’re bringing all that knowledge back to your organization.

That means they’ll drive your initiatives faster, build better, and work more efficiently.

There’s a huge benefit to allowing internal teams to contribute to WordPress.

And it’s really nice to see this trending in the right direction.

Which department was the key decision-maker in choosing WordPress?

Brad:
You can see a shift in leadership’s role in making this decision.

Last year, leadership/C-suite was at 20%—this year, it dropped to 12%.

That aligns with what we discussed earlier—leadership is handing more decision-making control to engineering teams.

Instead of leadership saying, “Here’s the CMS we’re using,” they’re now saying, “Engineering, you tell us what we should be using.”

That’s a really interesting change.

Tom:
Yeah, and I’m torn on whether that’s a good thing or not.

On the one hand, it’s great that people with deep technical knowledge are making these decisions.

On the other hand, it could reflect a shift toward smaller, more localized CMS decisions, rather than big, organization-wide replatforming decisions.

A large-scale replatforming project is usually a C-suite decision.

So the fact that leadership is less involved might suggest that there are fewer big replatforming projects happening.

Hard to say.

Brad:
Also, Finance was at 2%—which, I think, is funny.

“Whichever CMS is cheapest—that’s what we’re going with!”

That’s one way to make a decision.

---

Was cost a contributing factor in choosing WordPress?

Tom:
Only 40% said cost was a factor.

I think that’s interesting—WordPress is often praised for being more cost-effective than proprietary CMSs, but here, the decision is really being driven by functionality.

Brad:
Yeah, 75% of respondents said functionality was the most important factor—that makes a lot of sense.

We talk about WordPress’s extensibility a lot.

That’s always been one of its biggest strengths.

You can quickly add advanced functionality with plugins.

You can go from a simple blog to a massive eCommerce store doing millions of dollars a day.

That level of flexibility is why WordPress remains the top choice.

---

Multilingual Support in Enterprise WordPress

Tom:
This is an interesting one—because multilingual support is coming in Phase 4 of Gutenberg.

But here, only 18% of respondents said multilingual was very important, and another 22% said it was quite important.

That means less than half of respondents consider multilingual a major priority.

Brad:
Yeah, I thought this number would be higher.

Many of our enterprise clients require multilingual support—especially global companies.

It will be interesting to see if this number grows once multilingual support is a core feature of WordPress.

Because right now, it requires third-party solutions like WPML, which can be clunky.

Once it’s built into WordPress natively, maybe adoption will increase.

Tom:
Yeah, and another thing I’m watching is AI translation tools.

Browsers are getting better at real-time translation, which might reduce the need for dedicated multilingual site structures.

But if companies need different content for different regions—not just translation—then multilingual support will always be a key feature.

---

What were the setup, design, and build costs for your WordPress site?

Tom:
This is an area that surprises people who aren’t in the enterprise space—the amount of money organizations spend on WordPress.

• Most common answer: Less than $50,000
• Some spending $100,000–$500,000
• A small group spending over $1 million

The fact that less than $50K was the largest group is surprising.

Brad:
Yeah, I agree.

I would have expected $50K–$100K to be the top category.

But I think this speaks to quick engagements—short-term projects, smaller marketing sites, rather than large enterprise builds.

That’s a key data point for agencies.

There’s a lot of enterprise work happening below six figures—which is something to keep in mind.

Tom:
Yeah, most agencies are probably focused on $100K+ projects.

But WordPress offers a unique strength here—you can start small, and then scale up.

A company might launch a small $50K project, and then continue to invest in it over time.

Brad:
Yeah, and you can see that in the trend—the “under $50K” category increased from 35% to 40% this year.

That might reflect budget tightening—we’ve seen tech industry downsizing and cost-cutting across enterprises.

So companies are trying to do more with less.

---

Do you have an in-house engineering team managing WordPress?

Tom:
This is a major shift.

• 90% of respondents now have an in-house engineering team managing WordPress.
• Last year, 25% of respondents relied solely on an external agency—this year, it’s less than 15%.

That’s a huge swing toward in-house teams.

Brad:
Yeah, I think many enterprises are bringing development in-house.

This is something we’ve seen anecdotally at WebDev Studios.

Where in the past, we might have built the entire project, now we’re collaborating with in-house teams—providing specialized consulting and support, rather than full development.

Tom:
Yeah, and for WordPress as a whole, this is great—it means enterprises are investing long-term in WordPress.

But for agencies, it does present some challenges.

If enterprises are doing more in-house, they’re spending less externally.

That might explain why average project budgets are going down.

---

Where are enterprises hosting their WordPress sites?

Brad:
I was surprised to see that the most common answer is still “own servers.”

I would have expected more adoption of managed WordPress hosting.

Tom:
Yeah, but a lot of these big enterprises have cloud contracts—they already have AWS, Azure, or Google Cloud deals.

So, internally, there’s often a mandate to use those services instead of third-party managed WordPress hosting.

Brad:
Yeah, but that also means they miss out on the benefits of specialized WordPress hosting.

We run into a lot of challenges with clients who insist on running WordPress on their own infrastructure—it often causes issues that wouldn’t exist on a dedicated WordPress hosting provider.

---

How much are enterprises spending on WordPress hosting?

Tom:

• Most common spend: Less than $2,000 per month
• Next largest: $2,000–$5,000 per month
• A third of respondents spend over $5,000 per month

Not much change from last year, but high-end hosting spend can be significant.

Brad:
Yeah, if you’re getting 10 million+ visits a month, you’re investing in serious hosting infrastructure.

---

Looking Ahead: Will your organization continue using WordPress?

Tom:

• 2023: 90% said yes.
• 2024: That dropped to 75%.

So while the vast majority still plan to use WordPress, there’s a notable increase in organizations considering alternatives.

Brad:
Yeah, I wish we had a follow-up question on why.

Are they actively planning a move, or just exploring other options?

That’s something we’ll want to track next year.

---

Final Thoughts

Tom:
That wraps up our deep dive into the data!

Big thanks to Big Bite and Iain for leading this effort.

Brad:
Yeah, and now that the report is public, I’m looking forward to seeing the public conversation around this data.

Tom:
Yeah, thanks to everyone who participated! Let’s keep the conversation going.

Brad:
Yeah, thanks, everyone!