WordPress vs Next.js + Payload CMS: What a Small-Business Website Really Costs in 2026

Before you read: this is not a niche experiment. The two largest US aggregates producers, Vulcan Materials and Martin Marietta, already run their websites on Next.js. Most regional suppliers, such as Houston Sand & Gravel and Liberty Sand & Gravel, are on WordPress, and Luck Stone still reports Drupal 7, which lost official support in January 2025. Fifteen checked examples across WordPress, Drupal, Webflow and Next.js are listed at the end of this article.

How to read the numbers: all prices are typical US industry ranges for 2026, not a quote. Licence and hosting prices come from the vendors' published pricing pages, and the security figures come from Patchstack's 2025 WordPress security report. Every source is named at the bottom of the page.

For a 10–15 page informational business site, a Next.js + Payload CMS build costs about the same to launch as a quality WordPress build, and noticeably less to own over three years. It is faster, has far less to patch, and is much easier to extend and automate with AI.

• Launch cost: roughly equal. AI-assisted development has removed the old "custom code is expensive" penalty for sites of this size.
• 3-year cost: lower, because there are no paid plugin licences to renew and far less maintenance work.
• Security: most WordPress breaches come through third-party plugins. A Payload site has no plugin marketplace to exploit.
• Editing: your team edits text, photos, FAQs, locations and Spanish translations in a clean admin panel, side by side, without touching layout.
• Change and automation: new features (a quote calculator, delivery-zone lookup, CRM hand-off) are normal code changes, not plugin hunts.

Why ask this question now

Most website briefs still name WordPress, Webflow or Drupal because those were the safe answer ten years ago. Three things have changed since then.

• AI-assisted development. Writing a custom, hand-built site used to cost more than assembling one from a theme and plugins. With AI coding tools, a senior developer now builds a custom Next.js site in about the time it takes to configure and debug a WordPress theme stack.
• Modern CMS options matured. Payload CMS is free, open-source (MIT licence) and runs inside the website's own code. Figma acquired the Payload team in June 2025, and the project remains MIT-licensed.
• The old platforms aged. Drupal 7, still behind many business sites, reached end of life on January 5, 2025, according to Drupal.org. WordPress security problems keep growing through its plugin ecosystem (see the security section below).

The question is no longer "can we afford custom?" It is "why pay ongoing plugin and maintenance costs for a site that is slower and harder to change?"

The four options in plain English

The key difference is how many separate vendors' code your site depends on. A typical WordPress site runs 20–40 plugins from different authors. A Next.js + Payload site is one codebase your agency wrote and controls.

• WordPress is a PHP blogging engine from 2003, extended with a theme and plugins. Features are added by installing a plugin, often paid, often from a small vendor, so dozens of third-party authors control parts of your site.
• Drupal is a PHP CMS built for large, complex sites. Features come from contributed modules plus custom PHP, maintained by the Drupal community and specialist developers.
• Webflow is a hosted visual site builder. Features are either built in or embedded as third-party scripts, and you rent the platform rather than own it.
• Next.js + Payload is a modern React website with an open-source CMS inside the same codebase. Features are written directly into the site, usually in hours with AI-assisted development, and you own all of it.

Next.js is the framework behind sites from companies like Nike, Notion and TikTok. Payload is the admin panel where your team edits content. Both are free and open source; you pay only for building and hosting.

Cost: launch and three years of ownership

Over three years, a Next.js + Payload site typically costs $15,000–$25,000 all-in, against $18,000–$33,000 for an equivalent WordPress site. The build price is similar; the gap comes from licences and maintenance.

The figures below are for a 12-page site in English and Spanish, in US dollars.

• WordPress: build $12k–$18k · hosting $30–$60 a month (managed) · licences $400–$700 a year (page builder, multilingual, forms, SEO, backups, security) · maintenance $100–$300 a month (updates, conflicts, malware checks) · 3-year total $18k–$33k
• Drupal: build $20k–$40k · hosting $50–$150 a month · licences $0–$300 a year · maintenance $150–$400 a month · 3-year total $27k–$61k
• Webflow: build $8k–$15k · hosting $23–$39 a month (site plan) · licences $108–$350 a year (Spanish localization add-on) · maintenance $0–$100 a month · 3-year total $9k–$21k
• Next.js + Payload: build $12k–$18k · hosting $20–$50 a month · licences $0 · maintenance $50–$150 a month · 3-year total $15k–$25k

Webflow looks cheapest, but it cannot meet several items in a typical brief (user accounts, custom email notifications, real configuration control) without extra paid tools. See the admin requirements section below.

Where the numbers come from

• Build: US web agencies typically bill $100–$175 an hour. A custom-designed, 12-page bilingual site with a full admin panel takes roughly 100–130 hours, including wireframes, design, build, content loading, testing and launch. Drupal costs more because its developer pool is smaller and more specialised. Webflow costs less up front because hosting and the CMS come ready-made, within the platform's limits.
• Hosting: published plan prices. Managed WordPress hosts (such as WP Engine or Kinsta) start around $30–$35 a month; Webflow site plans are $23–$39 a month; a Next.js site runs on Vercel Pro (about $20 a month) or a small cloud server plus database.
• Licences: list prices of the plugins a site like this usually needs. On WordPress: a page builder, a multilingual plugin (WPML's CMS plan is €99 a year), a forms plugin, a custom-fields plugin and a backup or security service, each roughly $50–$200 a year. On Webflow: the localization add-on for Spanish, $9–$29 a month. Next.js and Payload are free and open source.
• Maintenance: typical agency care plans. WordPress plans run $100–$300 a month because plugins, themes and core need frequent updates and conflict checks. A Next.js + Payload site has far fewer moving parts, so monthly upkeep is mostly dependency updates and monitoring.
• 3-year total: build + 36 months of hosting + 3 years of licences + 36 months of maintenance, low end to high end.

Complexity: who can build and maintain it

WordPress is easy to start and hard to keep healthy; Next.js + Payload is the reverse. The complexity in WordPress hides in the interaction between plugins, which nobody fully controls.

• WordPress: core + theme + 20–40 plugins + a page builder. The typical failure is a plugin update that breaks the layout or a form. Any WordPress freelancer can work on it, but quality varies widely, and edits usually happen on the live site. You can move it elsewhere, but the plugins and licences come along.
• Drupal: core + modules + a custom theme. Major version upgrades need serious developer time from a small, expensive specialist pool. Changes are sometimes tested before going live.
• Webflow: one hosted platform with a webflow.io staging address. The typical failure is a limit you cannot code around. Leaving means exporting static pages and rebuilding.
• Next.js + Payload: one codebase + one database. Every change is previewed and tested on staging before it goes live. Any React / Next.js developer, the largest web talent pool today, can work on it, and you can host it anywhere.

For a business owner, the practical point is simple: on WordPress, "small changes" often turn into billable debugging. On Next.js + Payload, the site behaves the same until someone deliberately changes it.

Day-to-day editing, posting and Spanish content

Your team never needs a developer to change text, photos, prices, FAQs, gallery images or locations. The admin panel is built around your business, not around a generic blog.

• Structured content, not page-builder drag-and-drop. A "Product" has fields for name, photo, description, uses, unit (ton or cubic yard) and availability by yard. Add a new product once and it appears on the Products page, in the quote form and in search results, already styled.
• English and Spanish side by side. Payload has built-in field-level localization: each field has an English and a Spanish version, switched with one toggle. No separate multilingual plugin, no duplicated pages drifting out of sync. Missing Spanish text can fall back to English until it is translated.
• Live preview and drafts. Editors see the real page before publishing, can save drafts and schedule posts, and can roll back to earlier versions.
• Posting news or projects. A blog or "recent projects" collection works like any CMS: title, photos, text, publish.
• Gallery. Upload photos once; the site automatically resizes and compresses them for phones, which matters for an image-heavy gallery.

On WordPress the same tasks are possible, but through a page builder where an editor can accidentally break the layout, and a multilingual plugin that duplicates every page.

Admin requirements: how each is met

Every admin capability a typical brief lists for WordPress, Webflow or Drupal exists in Payload, usually built in rather than bought as a plugin. "Plugins" is the one item that changes meaning: in Payload, integrations are configured settings, not third-party code you install.

• Content management. WordPress has it built in, with layout via a page-builder plugin. Webflow has it built in, with CMS item limits per plan. Payload has collections for pages, products, locations, FAQs, gallery and posts.
• Email notifications. WordPress needs plugins (forms + SMTP). Webflow sends form emails only; more needs Zapier or similar. On Payload they are set up in the build: emails on quote requests, contact forms and new content, routed by service or location.
• User accounts and roles. WordPress has basic roles; fine-grained roles need a plugin. Webflow offers limited editor seats per paid workspace. Payload has admin, editor, sales and translator roles with field-level permissions built in.
• Theme and appearance settings. WordPress uses the theme customizer, where changes can break layouts. Webflow gives full designer-level visual control. Payload has a site settings panel: logo, colours, header and footer menus, banners, hours, phone and social links.
• Plugins and integrations. WordPress installs third-party plugins; Webflow uses apps and embedded scripts. Payload configures integrations in settings: Google Maps, analytics, reCAPTCHA, CRM, email provider.
• Site configuration. WordPress spreads settings across plugins; Webflow has its site settings. Payload has one settings area for SEO defaults, redirects, languages, contact routing and a maintenance banner.

Bottom line for the buyer: you get every admin control on the list, in one consistent panel, with no annual plugin fees.

Security and maintenance

WordPress's main risk is its plugins. Patchstack counted 7,966 new vulnerabilities in the WordPress ecosystem in 2024, 96% of them in plugins, and 33% were not fixed by the time they were made public. WordPress core itself had only seven.

• WordPress: every plugin is a door. Updates must be applied every week or two, and each update can break something else. Hacked WordPress sites are commonly used for spam and phishing, which can get a business domain blacklisted by Google.
• Drupal: more secure by design, but moving off an old major version (Drupal 7 to 10 or 11) is effectively a rebuild, and it needs scarce specialist developers. Sites still on Drupal 7 have had no official security support since January 2025.
• Webflow: Webflow handles security for you; the risk is lock-in, not hacking.
• Next.js + Payload: the public website is mostly pre-built pages served from a global network, with no plugin marketplace. The admin login has built-in lockout after failed attempts and can be moved to its own address or locked to office IPs. Dependencies are updated through automated, tested pull requests, and nothing reaches the live site without passing the build.

Maintenance on Next.js + Payload is mostly a monthly dependency update and uptime monitoring. There is no plugin-conflict category of work.

Speed, SEO and AI search visibility

A Next.js site loads pages pre-built from servers close to the visitor, so pages typically appear in under a second on a phone. A page-builder WordPress site loads the builder's code, plus every plugin's scripts, on every page.

• Google rankings: Google's Core Web Vitals measure load speed and layout stability. Next.js passes them by default; WordPress page-builder sites often need paid caching and image-optimization plugins to pass.
• Local SEO: each location (yard, delivery area, city) becomes its own page with its own address data, map and structured data, generated from one entry in the admin.
• Bilingual SEO: English and Spanish pages get proper language tags (hreflang) automatically, so Google shows Spanish pages to Spanish searchers.
• AI search (ChatGPT, Google AI Overviews, Perplexity): these tools read clean, structured pages best. Products, FAQs and locations stored as structured content can be published as schema markup that AI answers quote directly.
• Mobile: contractors and homeowners search from job sites on phones. Fast pages on a weak signal mean more calls and quote requests.

Scalability and ability to change

An informational site is phase one. The features that grow a materials business come next, and they are where the platforms differ most.

• Instant quote calculator (material × tons × delivery distance). WordPress needs a paid form or calculator plugin with limited logic; Webflow needs a third-party embed. On Next.js + Payload it is custom logic in the site, priced from your own rate table in the admin.
• Delivery-zone lookup by address or ZIP. WordPress needs a map plugin plus custom code; Webflow an embed. On Next.js + Payload it is built in with Google Maps, with zones edited in the admin.
• Online ordering and deposits. WordPress adds WooCommerce, a second large plugin stack. Webflow's Ecommerce plan is limited for bulk goods. On Next.js + Payload, Stripe checkout is added to the existing product data.
• Contractor accounts (saved addresses, reorders, invoices). WordPress needs membership plugins; on Webflow it is not practical. On Next.js + Payload it uses the same user system already in place.
• CRM, accounting and dispatch integrations. WordPress needs a plugin per tool, if one exists; Webflow relies on Zapier. Next.js + Payload connects directly through each tool's API.
• More locations or states. WordPress duplicates pages per location; Webflow needs more CMS items and a higher plan. On Next.js + Payload you add a location entry and the pages generate themselves.

Traffic is not a scaling concern for any of these at this size. The scaling that matters is adding features without rebuilding, and that is where owning clean code pays off.

Automation and AI: what becomes possible

Because the content lives in a clean database with an API, AI and automation plug straight into it. On WordPress, each of these is a separate plugin or a fragile workaround.

• Translation: write in English, get a draft Spanish version generated automatically for review, then publish both.
• Quote handling: a quote request is checked, priced from your rate table, emailed to the right yard, logged in your CRM, and answered with a confirmation in the customer's language, within seconds.
• Lead routing: contractor enquiries go to sales, homeowner enquiries to the office, haulage requests to dispatch.
• Content upkeep: AI drafts project write-ups from a few photos and notes; FAQs are expanded from real questions customers ask by email or chat.
• Faster changes from your agency: with AI-assisted development, typical change requests (a new section, a new form, a layout tweak) are done in hours, not days, and every change is reviewed and tested before it goes live.

This is the real long-term difference. A WordPress site stays roughly what it was on launch day. A Next.js + Payload site keeps getting cheaper to improve.

Honest trade-offs

Next.js + Payload is not the right answer for everyone. These are the cases where we would recommend something else.

• You want to change the layout yourself, visually, every week. Webflow gives designers pixel-level control. Payload lets editors rearrange pre-designed blocks, which keeps the site consistent but is less free-form. (We have written separately about when to move from Bubble and Webflow to custom code, and when to stay.)
• You plan to hire a cheap freelancer for every small change. WordPress has the largest pool of low-cost freelancers. Next.js developers are plentiful too, but rarely at the bottom of the price range.
• You need a specific off-the-shelf plugin (a niche booking or membership product with no API). On WordPress it may already exist.
• Your budget is under about $5,000. A WordPress theme or a Webflow template is the realistic option at that level.

For a business that wants a professional, fast, bilingual site it can grow into quoting, ordering and automation, none of these apply.

Worked example: a bilingual sand and gravel supplier

A regional supplier of sand, gravel and topsoil wants a 12-page English and Spanish site with a full admin panel. On Next.js + Payload this is a 4–5 week project, typically $14,000–$18,000, with hosting around $20–$50 a month and no licence fees.

Site map: Home · About Us · Services (Products, Quote, General Contractor, Locations, Haulage) · Remodelling · Gallery · FAQ · Contact.

How the content is modelled in the admin

• Products (material, photo, uses, unit, availability) feed the Products page, the quote form and the Home highlights. Edited by office staff.
• Locations (yard address, hours, map, delivery area) feed Locations, Contact, the footer and local SEO pages. Edited by the owner.
• Services (haulage, contractor supply, remodelling) feed the Services pages and Home. Edited by the owner.
• Gallery projects (photos, material used, location) feed Gallery and Remodelling. Edited by office staff.
• FAQs feed the FAQ page, plus FAQ blocks on any page. Edited by office staff.
• Quote and contact requests land in an admin inbox with email notifications. Handled by sales.
• Site settings (logo, colours, menus, phone, social, SEO, languages) apply to every page. Edited by the owner.

Timeline

1. Week 1: discovery, site map, wireframes for all page types.
2. Week 2: visual design (desktop and mobile), approved before build.
3. Weeks 2–4: build the site and admin, quote form and notifications, English and Spanish.
4. Week 4: content loading from the client's text and photos; Spanish review.
5. Week 5: testing on phones and browsers, SEO setup, admin training, launch.

Wireframes, design, development, content integration, project management, testing and deployment are all included in that range.

Real sites in the industry, by platform

The two largest US aggregates producers, Vulcan Materials and Martin Marietta, both run their websites on Next.js. Most regional suppliers are on WordPress, and several big European groups use Drupal. We checked each site's platform from its page source on 8 October 2026.

Next.js

• Vulcan Materials, the largest US producer of construction aggregates: Next.js front end with a headless CMS (Contentstack).
• Martin Marietta, aggregates, cement and ready-mix in the US: Next.js, hosted on Vercel.
• NerdHeadz, our own site (not aggregates): Next.js + Payload CMS, the stack described in this article.

WordPress

• Houston Sand & Gravel, sand, gravel and soil supplier in Houston, TX: WordPress 6.9 with the Elementor page builder.
• Liberty Sand & Gravel, rock, sand and gravel in Dallas–Fort Worth: WordPress with Elementor.
• Rogers Group, crushed stone, asphalt and construction in the Southeast US: WordPress with the WPBakery page builder.
• Arcosa Aggregates, natural and recycled aggregates in the US: WordPress.
• Ozinga, ready-mix concrete and materials in the Midwest: WordPress.
• Kafka Granite, decorative granite and aggregates in Wisconsin: WordPress.

Drupal

• Luck Stone, crushed stone, sand and gravel in Virginia: the page header still reports Drupal 7, which lost official support in January 2025.
• Heidelberg Materials UK, aggregates, cement and concrete in the UK: Drupal 11.
• Holcim UK, aggregates and building materials in the UK: Drupal.

Webflow

• JFK Quarry, crushed stone, concrete and asphalt in Canada: Webflow.
• Western Paving, concrete and paving contractor in Utah: Webflow.
• Béton Hébert, concrete construction in Montreal: Webflow.

Sand and gravel sites in particular range from page-builder WordPress sites like Houston Sand & Gravel to hand-coded HTML with no CMS at all, like Mike Schaeper Sand & Gravel, which its owners cannot edit without a developer. We found no aggregates supplier publicly running Payload yet; the closest industry examples are the Next.js sites above.

Sources

• Patchstack, "State of WordPress Security in 2025" whitepaper (vulnerability counts for 2024).
• Drupal.org public service announcement of June 7, 2023 (Drupal 7 end of life on January 5, 2025).
• WPML, Webflow and Vercel published pricing pages, checked October 2026; Flow Ninja's 2026 Webflow pricing breakdown for localization add-on prices.
• CMSWire, "When CMS Meets UX Design: What Figma's Payload Deal Really Means" (Figma's June 2025 acquisition of the Payload team).
• Next.js showcase (companies using Next.js).
• Website platforms: each site's page source, checked on 8 October 2026.

Build and maintenance costs are typical US industry ranges (see "Where the numbers come from"), not a quote.

WordPress, Drupal and Webflow were the safe default when custom code was expensive. AI-assisted development changed that maths. For a 10–15 page business site, Next.js with Payload CMS launches for about the same price as a quality WordPress build, costs less to run, has far less to patch, and keeps getting cheaper to improve.

If your brief names WordPress, Webflow or Drupal, ask the question behind it: who edits the site, what will it need to do in two years, and what will it cost to keep healthy until then. The answer usually points to owning clean code.

Planning a new business website? Talk to our team — we will map your pages, admin needs and languages to a fixed scope and timeline.