WordPress powers 40.7% of the web. Next.js powers Nike, Netflix, TikTok, OpenAI, and Anthropic. Yet most agencies still default to WordPress.
That's not because agencies are lazy or clients are uninformed. It's because the economics of running an agency fit WordPress extremely well, and fit Next.js badly. Once you see the business model, the whole pattern makes sense. Here's how it works, and why we chose the harder side of it anyway.
WordPress Won by Lowering the Barrier
WordPress succeeded because it absorbed the technical decisions: hosting, routing, content structure, and a large share of SEO mechanics all came pre-solved, with themes and plugins covering most of what a business site needs.
That lowered the barrier to building capable websites, and that was genuinely good for the web. Businesses that could never have afforded custom development got online. A huge industry of designers, marketers, and builders grew around the platform, and plenty of them do strong work.
The trade is that a pre-solved platform makes its decisions once, for everyone. Implementation quality varies widely, and when your needs outgrow what the themes and plugins decided for you, you start working against the platform instead of with it.
Next.js Moves the Decisions Back to You
Building well on Next.js means owning the decisions WordPress absorbs: rendering strategy, caching, data fetching, content architecture, metadata generation, deployment. That's software engineering work, and it's a different staffing profile than theme customization.
The same shift shows up in SEO. On WordPress, a lot of SEO work happens in plugin settings. On Next.js there is no plugin layer; metadata, structured data, and performance are handled in the code itself. Neither approach is beneath the other, but they're different skills, and an agency built around one can't switch to the other by hiring one developer.
That staffing reality, not stubbornness, is a big part of why most agencies stay where they are.
Agency Economics Favor WordPress
Here's the honest comparison of the two business models:
WordPress model:
- $3,000–$10,000 per site
- 2–4 week delivery
- Reusable templates and starter themes
- Broad hiring pool
- Plugin-driven features
- Healthy margins on straightforward work
- Recurring revenue from maintenance plans
Next.js model:
- $15,000–$60,000+ per site
- 6–12 week delivery
- Custom architecture every time
- Senior engineers required
- Higher accountability for outcomes
- Harder to hand off
Most clients don't ask for Next.js. They ask for "a website." Selling Next.js means explaining why it's worth 3 to 5 times a WordPress quote, to someone who didn't come in asking that question. For an agency optimized for volume, the easy sale is the rational sale.
None of that is a scandal. It's just a business model, and it's worth understanding as one, because the platform recommendation you get from an agency is partly a reflection of the agency's own economics.
Risk Shapes the Choice Too
WordPress feels safe to an agency for defensible reasons. If a developer leaves, someone else can step in. If a client wants to leave, they can find another WordPress shop anywhere. The ecosystem is enormous and nobody gets stranded.
Next.js concentrates responsibility. The studio that builds your site needs to genuinely understand it, and so does whoever maintains it. That accountability is exactly what some agencies avoid, and exactly what we wanted. More on that below.
Clients Ask for What They Know
When businesses come to an agency, they say "I need a website," "I need SEO," "I need more leads." Nobody walks in asking for server-rendered metadata or sub-second mobile loads, because there's no reason they'd know those layers exist, any more than I know what's in my car's transmission.
So agencies sell what's being asked for, clients keep seeing the same kind of site, and the cycle reinforces itself. Breaking it requires someone in the conversation to explain what's possible, and that education takes time most volume-based sales processes don't have.
When WordPress Makes Sense
WordPress is the right call more often than a studio like ours might like to admit:
- Sites with a handful of pages and no serious competition
- Businesses that need to launch in two weeks
- Budgets under $5,000
- Content teams publishing daily without developer involvement
- Projects where good enough is genuinely good enough
For those situations, WordPress delivers real value at a price nothing custom can match. If that's your situation, it's not a compromise. It's the correct engineering decision.
When Next.js Becomes Necessary
The platform choice starts to matter enormously when:
- Performance directly affects your conversions or rankings
- You need custom functionality that plugins can't provide
- You're investing in organic search as a long-term asset
- Your buyers research in ChatGPT, Claude, or Perplexity, and machine readability matters
- The site needs to feel premium rather than templated, because your market notices
Most sites never reach this point. But when the website is a competitive asset instead of a brochure, the architecture underneath it stops being an implementation detail.
Why We Made the Switch
We used to build WordPress sites at Vizantir. We moved to Next.js because our clients kept hitting the platform's ceilings: performance problems we could only partially fix, plugin conflicts, security incidents, design limits that forced compromises we didn't want to make.
We got tired of apologizing for a platform. We wanted to build things we could fully stand behind, where every layer of the result was a decision we made rather than a default we inherited.
The switch cost us things. It's harder work. It requires engineers rather than a broad hiring pool. It shrinks our client pool to businesses ready to invest $15K and up, and it means owning long-term responsibility for every codebase we ship instead of handing sites off to the ecosystem.
We took that trade because the sites are better: faster, more secure, more durable, and built to fit one business instead of adapted from a template. Our clients get better results, and we do work we're proud of. We'd make the same trade again.
If your website has outgrown what its platform can do, and you want to talk through whether that's actually true before spending anything, book a strategy call.