WordPress vs Custom Website: What Should You Build in 2026?

Every few months, someone declares WordPress dead. Every few months, it's still powering 40% of the web and probably the majority of small business sites in the UK. Meanwhile, custom-built sites have become more accessible than ever thanks to frameworks like Next.js and AI-assisted development.

So which should you build in 2026? The honest answer: it depends on the specific project. Here's how I think about the decision.

Start With the Client's Actual Needs

Before we get into technical comparisons, the right question is always: what does this site actually need to do?

Most small business websites need:

That's it. No custom API integrations. No complex authentication. No real-time features. Just a professional presence that converts visitors into enquiries.

For this use case, WordPress is almost always the right answer. Not because WordPress is the best technology — it's not — but because it's the right tool for the job.

When WordPress Wins

The client wants to manage their own content. WordPress has the most mature, most understood CMS interface in the world. A business owner who's never touched website admin can learn to add a blog post or update a phone number in half an hour. Try teaching them to edit Markdown files in a Git repository and see how that goes.

You need plugins that already exist. E-commerce (WooCommerce), membership sites (MemberPress), booking systems, multilingual support, SEO (Yoast, Rank Math) — WordPress has solved these problems already, often for free. Building equivalent functionality from scratch in a custom stack takes weeks.

Speed of delivery matters. For a standard business website, a developer comfortable with WordPress can deliver a professional result faster than building anything custom. Faster delivery means lower cost to the client and higher margin for you.

The client has a maintenance budget. WordPress sites need ongoing attention — updates, security monitoring, backups. If the client understands this and has budgeted for it, that's a sustainable arrangement. If they expect to set it and forget it forever, adjust expectations or choose a more stable stack.

UK context: Most small business clients in the UK have heard of WordPress, often have opinions about it (usually positive), and have staff who've used it. That familiarity has real value for long-term site management.

When Custom Wins

The performance requirements are exceptional. WordPress sites can be fast, but they're never as fast as a statically generated Next.js or Astro site with no CMS overhead. If Core Web Vitals are critical — because the client is in a hyper-competitive SEO niche, or because the site is under heavy load — a custom build wins on performance.

The site has complex interactive features. A web app with real-time data, complex user authentication, API integrations, or significant client-side logic is better built as a React/Next.js application. Bending WordPress to do this is painful and produces fragile results.

Long-term maintenance by developers only. If the site will always be maintained by technical staff and non-technical editing is not a requirement, the constraints of WordPress aren't worth it. Build what makes sense architecturally.

You want a headless CMS approach. Some teams want a proper CMS for content editors but not WordPress as the delivery layer. Headless CMS options like Contentful, Sanity, or even WordPress in headless mode, combined with a Next.js frontend, give you the best of both worlds. More complexity upfront, but more flexibility.

Security is a top priority. Custom static sites have a much smaller attack surface than WordPress. For clients in financial services, healthcare, or government, this matters. A static site with no database and no PHP execution is dramatically harder to compromise than a WordPress installation.

The Costs Nobody Talks About

WordPress hidden costs: A WordPress site isn't free to maintain. Premium themes and plugins cost money. Proper hosting (not the cheapest shared plan) costs money. A developer to handle updates and security costs money. Clients who choose WordPress because it's "free" and then don't invest in maintenance end up with hacked or broken sites. Budget at minimum £50-150/month for decent hosting and maintenance.

Custom site hidden costs: A custom build costs more upfront — typically 2-3x a comparable WordPress site. Content updates require developer involvement unless you've built a proper CMS. That's ongoing cost the client may not anticipate.

My Decision Framework

I ask three questions:

If the answer to 1 and 2 is yes and 3 is no, WordPress. Every time.

In Practice, 2026

With AI tools available, the "custom build takes too long" argument is weaker than it used to be. I can scaffold a Next.js + Supabase project in an afternoon and have something live by the end of the week. The gap in delivery time between WordPress and custom has closed.

But the content management gap hasn't closed. Clients still need to update their own sites, and WordPress still wins there by a wide margin.

My current approach for most client sites: WordPress with a lightweight theme and Gutenberg blocks for standard business sites. Next.js with a headless CMS for anything requiring significant interactivity or performance. And custom React/Next.js with Supabase for actual web applications.

Need help deciding which approach fits your project? I work with UK businesses on both WordPress sites and custom web applications. Reach out at kylanjari@gmail.com.

And if you want to watch me build both types of sites from scratch using AI tools, the @PromptToCode YouTube channel has real-time builds of exactly this — no polished tutorials, just actual development workflow.