WordPress or Next.js? For a Mid-Size Site, the Bill Is the Wrong Question
One developer, 300,000 visitors a month and Claude on every desk. The two options cost nearly the same to run.
For two decades, the safe answer to "What should we build the website on?" has been WordPress. It runs 39 percent of all websites.
The challenger is a custom site built with Next.js, a framework for building websites with React, the most widely used toolkit for web interfaces. Assistants such as Claude, which now write code, mock up pages and publish content, have reopened the question.
Consider a marketing site with 300,000 visitors a month, a marketing team and one full-time developer with about 160 working hours a month. Everyone uses Claude.
The two setups
The first is WordPress on a managed host such as Kinsta or WP Engine, which runs the servers, backups and core software updates.
The second is Next.js on Microsoft Azure behind Cloudflare, a content delivery network that serves saved copies of pages from locations near each reader and filters hostile traffic. Content is managed in Payload, an open-source content management system, or CMS, the editing tool behind a site. Here Claude also works on the code and can see into Azure and Cloudflare.
Why Payload
A custom site still needs a CMS. One can be rented: Contentful, a hosted CMS, lists its Lite plan at $300 a month, and the median buyer pays about $51,000 a year, according to Vendr, a software purchasing firm. One can be built: Claude can produce the basics in days, but user roles, drafts, version history and previews take months to make dependable.
Payload is the third route. It ships those features, costs nothing to license and is written in the same language as the site, so Claude can extend it like any other code. Single sign-on and formal publishing workflows, however, are enterprise features, priced on request.
Contentful's list price, and Vendr's median across 122 purchases.
Show the numbers
| USD | |
|---|---|
| Payload, self-hosted | $0 |
| Contentful Lite | $3,600 |
| Contentful, median contract | $51,408 |
Cost
The developer's salary and the Claude subscriptions are the same in both setups, so they drop out.
A managed WordPress plan with room for 300,000 monthly visits runs from about $1,300 to $3,300 a year, depending on the host and the headroom. This note uses $2,200. Paid plugins, the add-ons that supply features such as forms and search optimization, add roughly $1,000.
On Azure, two small application servers and a managed database come to an estimated $250 to $350 a month. Cloudflare's Pro plan is $20.
- Hosting
- Paid plugins
- Cloudflare Pro
List prices in U.S. dollars, checked November 2026. Azure and plugin figures are estimates.
Show the numbers
| Hosting | Paid plugins | Cloudflare Pro | Total | |
|---|---|---|---|---|
| Managed WordPress | $2,200 | $1,000 | $0 | $3,200 |
| Next.js + Payload | $3,600 | $0 | $240 | $3,840 |
The custom stack costs about $640 a year more, and a pricier WordPress host would reverse the order. Managed WordPress hosts also bill by the visit, and WP Engine charges $2 for every 1,000 visits over the plan, so a campaign that brings 100,000 extra visitors adds $200. Cloudflare's fee is flat.
Initial development
WordPress wins the build. One European agency prices a small-business WordPress site at about 5,000 euros and a custom Next.js site at 16,000. In-house, the gap shows up as time: perhaps four to six weeks for WordPress against eight to twelve for the custom stack, because the component library, the deployment pipeline and Claude's access controls must be built first.
Maintenance
Vendr's buyer data suggests a production WordPress site needs 10 to 20 hours of technical upkeep a month, much of it testing plugin updates.
On the Next.js stack, Claude prepares updates as pull requests, proposed changes that a person reviews before they go live. Reviewing them takes perhaps three to six hours a month.
WordPress range from Vendr buyer data. The Next.js range is an estimate. Claude can shorten both.
Show the numbers
| Low | High | |
|---|---|---|
| Managed WordPress | 10 | 20 |
| Next.js + Payload | 3 | 6 |
With a salaried developer, this is not a cash saving. It returns roughly 10 hours a month, about 6 percent of the developer's time, to building.
Creative flexibility
The setups differ most in where each keeps the site. On the Next.js stack, design, layouts and components, the reusable building blocks of a page, are code in one repository, the form Claude reads and writes best. In WordPress, much of the site sits in a database behind admin screens, as page-builder layouts and plugin settings.
So a design prototype made with Claude on the Next.js stack is built from the live components and can be published as it stands. A WordPress mock-up usually has to be rebuilt in the block editor or the theme.
Editorial flexibility
For routine posts there is little to choose. Both systems offer connectors built on the Model Context Protocol, an open standard that lets AI assistants operate outside tools, so a marketer can ask Claude to draft a post and save it for an editor's approval.
Pages are different. On the Next.js stack, a marketer describes a campaign page, Claude assembles it from existing components and returns a preview link, and a named publisher releases it. In WordPress, marketers build pages by hand in the block editor, which is dependable but slower.
| Task | WordPress with Claude | Next.js stack with Claude |
|---|---|---|
| Blog post | Claude drafts, editor approves | Claude drafts, editor approves |
| Campaign page from existing sections | Marketer builds it in the block editor | Claude assembles it; publisher approves the preview |
| Design prototype | A mock-up, rebuilt later | Built from live components, ready to publish |
| New interactive section | Custom block or another plugin | Developer and Claude write one component |
Site speed
Google's Core Web Vitals tests ask, among other things, that a page's main content appear within 2.5 seconds. In field data from June 2026, 38 percent of WordPress sites passed them on phones.
Next.js does not guarantee better. In a November 2026 sample of Next.js sites, four in ten failed Google's responsiveness test. The custom stack offers control instead: pages built in advance and served from Cloudflare's cache, with no plugin scripts. Slow pages lose visitors, and Google recommends meeting its thresholds for success in search, so speed should be a requirement from the first day.
Risk and governance
With managed WordPress, the host is accountable for uptime. On the custom stack the team is: if the database fails at 2 a.m., the problem belongs to the developer. The question becomes how much authority to give Claude.
Four rules make that workable. Claude gets read-only access to Azure and Cloudflare, enough to study logs and costs. Every change, whether to code, servers or Cloudflare rules, goes through an automated pipeline that deploys only after a person approves. Emergency access is narrow, time-limited and logged. And Claude uses its own accounts, so the audit trail shows what the AI did and what a person did.
One developer is a risk in both setups. A WordPress developer can be replaced in weeks. A custom codebase takes longer to hand over.
Security
WordPress's exposure is its plugins. Patchstack, a security firm, counted 11,334 new vulnerabilities in the WordPress ecosystem in 2025, 91 percent of them in plugins. The managed host patches the servers and WordPress itself.
The custom stack has no plugins and serves most pages from a cache, but the developer must patch Next.js, Payload and the software they depend on. Claude adds a risk of its own: it can be misled by instructions hidden in the text it reads, which is the reason for the read-only access.
Other considerations
WordPress has a ready-made connector for almost every marketing tool. On Next.js, integrations are built with Claude and then maintained in-house. Payload is owned by Figma, so its direction depends on one company.
| Area | Managed WordPress | Next.js + Payload |
|---|---|---|
| Running cost | About $3,200 a year | About $3,800 a year |
| Initial build | 4 to 6 weeks (estimate) | 8 to 12 weeks (estimate) |
| Upkeep | 10 to 20 developer hours a month | 3 to 6 hours of review (estimate) |
| Creative flexibility | Limited by themes and page builders | Open-ended |
| Editorial flexibility | Strong for posts; pages built by hand | Posts and pages through Claude, with approval |
| Site speed | Often slow in field data | Fast if designed for it |
| Governance | Host accountable; thin change history | Team accountable; full change history |
| Security | Plugin exposure; host patches the core | No plugins; team patches the stack |
| Handover | Easy | Harder |
The CMO view
A chief marketing officer is choosing how the team will work. WordPress offers a familiar editor, a host to call and a site any agency can take over. The Next.js stack offers a team that can take a page from idea to live in an afternoon, and a record of every change. Its price is dependence on one developer and firm rules about what Claude may do.
The recommendation
For a team that already works in Claude, the Next.js stack is the better choice, on four conditions: a component library built before launch; Claude's access set up as described above; a speed target written into the brief; and a second person who knows the codebase.
WordPress remains the right choice if the team mostly publishes articles, depends on particular plugins, wants a host accountable for uptime or needs the freedom to change agencies quickly.
At this size the two bills are nearly identical. The choice turns on how much of the team's work with Claude can go live without being rebuilt.
Sources and assumptions
- WordPress share of websites, 39.3 percent: W3Techs, November 2026
- Managed WordPress plans: Kinsta pricing (Single 315k at $1,275 a year; Single 500k at $2,175 a year, used in the chart); WP Engine plans, with the 400,000-visit tier at about $276 a month per HostArbiter; WP Engine overage pricing
- Plugin prices ($50 to $500 a year each) and 10 to 20 maintenance hours a month: Vendr, WordPress. The $1,000 plugin figure assumes five to eight paid plugins.
- Azure: App Service P0v3 at about $57 a month each (Usage.ai); PostgreSQL D2ds_v5 at about $130 a month (Bytebase). The $250 to $350 monthly total, including storage, backups and monitoring, is an estimate; confirm it in the Azure pricing calculator. The chart uses $300 a month.
- Cloudflare Pro, $20 a month billed annually: Cloudflare plans
- Contentful: list prices; Vendr median of $51,408
- Payload: open-source licence; enterprise features; Figma acquisition
- MCP connectors: WordPress MCP Adapter; Payload MCP plugin
- Build prices: Kolonell (Dutch market)
- Site speed: Google on Core Web Vitals; PageSpeed Matters (HTTP Archive and Chrome field data, June 2026); CoreWebVitals.io (November 2026, 1,959 Next.js sites)
- Security: Patchstack, State of WordPress Security in 2026
- The build-time and review-hour estimates, and the comparison of how Claude's page prototypes carry over in each system, are the author's judgment.