WordPress & WooCommerce

WordPress or bespoke development with React/Next.js?

WordPress vs bespoke development is not a question of good or better, but of what you are building. WordPress is a content management system: the right foundation for websites that mainly inform, persuade and sell, and that you want to update yourself. Bespoke development with React and Next.js is intended for applications: software in the browser with users, roles, data and its own logic. The dividing line is not the size of the project, but what it needs to do.

At a glance

WordPress or bespoke development: the short answer

If it is about pages that visitors read, such as services, case studies, articles or products, WordPress is almost always the sensible choice. Its admin is designed for people who do not write code, and most features already exist.

If it is about something users do, such as logging in, booking, calculating, tracking cases or collaborating, sooner or later you will run up against the way WordPress is built. Bespoke development then makes more sense: the application is built around your process, instead of your process around a plugin.

Many projects fall somewhere in between. Then it helps to look at where the centre of gravity lies, and whether the two can coexist.

WordPress vs bespoke development – the two ways of building side by side

Comparison

WordPress vs bespoke development: the differences side by side

Seven points on which the two approaches differ.

WordPress compared with bespoke development in React and Next.js
AspectWordPressBespoke with React/Next.js
ContentBuilt-in management of pages, posts and mediaNo admin out of the box: it is built or connected
FunctionalityPlugins for common features; custom code where neededEvery feature is designed and built for this project
AdministrationBy the client, without technical knowledgeAs designed: a dedicated environment per role
ScaleStrong with lots of content; less so with lots of simultaneous interactionBuilt for the expected users, data and load
DevelopmentFaster: much already exists and only needs configuringSlower at the start: the foundation is laid first
SEOEasy to get right with the correct structure and settingsEqually possible, provided the rendering is set up for it
CostsStarting prices per website typePrice on request, after an initial scoping

The key question

Are you building content or an application?

This distinction matters more than any technical comparison. Picture what a visitor does on your website.

Content

They read and get in touch

The visitor looks for information, compares, views your work and fills in a form or places an order. The value lies in the content and in how easily you can update it. That is WordPress territory, with WooCommerce added for an online shop.

In practice

They log in and work with it

The user has an account, sees their own data, carries out actions and comes back. The value lies in the logic: who is allowed to do what, what happens after which step, which data belongs to whom. That is the territory of a bespoke web application.

A form, a search filter or a simple calculator does not yet turn a website into an application. Components like these fit perfectly well in WordPress. Where the line lies is explained in What is a web application?

Management and maintenance

What changes in day-to-day management?

The choice determines not only how it is built, but also who works with it after handover and what needs to be maintained.

01

Editing content

In WordPress, you edit text, images and pages yourself in an environment made for that purpose. With bespoke development, that environment only exists if it is designed in: for the parts you want to manage yourself, there is a dedicated admin screen or a connected CMS.

02

Maintenance

WordPress requires regular updates to the core, the theme and the plugins. Bespoke development has no third-party plugins that can drift out of step, but there too the libraries used and the server environment need to be kept up to date.

03

Dependency

With WordPress, you rely on plugins from other developers: convenient, as long as they are maintained. With bespoke development, you rely on your own project’s code, and therefore on good documentation and a developer who knows it.

04

Expand

In WordPress, an extra feature is quick to add if a good plugin exists for it, and harder if it goes against the logic of the system. With bespoke development, every extension costs development time, but it fits into a structure made for it.

Visibility

Is WordPress or Next.js better for SEO?

Search engines judge what they get to see of a page, not the system behind it. With either one you can build a website that is easy to find, and with either one you can get it wrong.

By default, WordPress sends complete HTML to the browser. The content is therefore immediately readable for search engines and AI crawlers. The work lies in a sensible structure, a lightweight theme, few unnecessary plugins and correct metadata.

With React, it depends on the rendering. An application that is built entirely in the browser shows little content to a crawler that does not execute JavaScript. Next.js solves this by building pages on the server or in advance, so that complete HTML is sent there too. For the public pages of a bespoke platform, that is not a detail but a requirement.

The part behind the login does not need to be found. What counts there is speed and usability, not indexing. How to measure and improve speed is covered in Improving Core Web Vitals.

Cost logic

Is WordPress cheaper than bespoke development?

Usually at the start, yes, but not always over the entire lifespan. The difference comes from the way the costs arise.

WordPress. Much of what you need already exists: the admin, the forms, the online shop, the translations. You mainly pay for structure, design, configuration and the technical finishing. That is why I can work with starting prices: at MadeByDries, a business website starts from € 2,495 excl. VAT. The final quote is based on the agreed scope.

Bespoke development. Here, little exists in advance. User roles, data model, screens and logic are designed and built for this one project. The scale depends so heavily on what the application needs to do that a starting price would mean nothing. For bespoke development, therefore: price on request, after an initial scoping.

The tipping point is where WordPress is used against its nature. An application assembled from ten plugins and lots of custom code is cheaper than bespoke development at the start, but becomes more expensive and more fragile with every extension. Conversely, bespoke development for an ordinary business website means spending money on something that already exists.

When to choose which

When should you choose WordPress, and when bespoke development?

Two lists of recognisable signs. If you recognise yourself in both, read the next section.

WordPress suits you when

  • the website mainly consists of pages, articles, case studies or products
  • you want to add and edit content yourself
  • the features you need are common ones: forms, a blog, an online shop, multiple languages
  • you want to go live quickly on a limited budget
  • you want to be able to switch developers later

Bespoke development suits you when

  • users log in and each see their own data
  • there are roles with different permissions
  • the process consists of steps that follow on from and depend on each other
  • the application exchanges data with other systems
  • you want to offer the platform itself as a product, for example as SaaS

You will find the service behind the first list on the WordPress website development page, and the one behind the second on the bespoke web applications page.

Combining both

Can you have both?

Yes. The two are not mutually exclusive, and for projects with both a lot of content and their own logic, a combination is often the most honest solution.

There are three common approaches.

01

Side by side

The public website runs on WordPress, and the application runs separately, for example on a subdomain. Marketing manages the content, users work in the platform. Each part does what it is good at.

02

Headless WordPress

WordPress serves only as the content management system, and the front end is built in React and Next.js. You keep the familiar admin and get complete freedom on the front end. It does mean two systems to maintain, so it has to be worth it.

03

One first, then the other

You start with a WordPress website and have the application built later, once it is clear exactly what it needs to do. That way, you do not pay for logic you do not yet need.

FAQ

Frequently asked questions about WordPress and bespoke development

A WordPress website is built on an existing content management system, with a theme and plugins, and can have an entirely custom design. With bespoke development, the application itself is programmed, in this case in React and Next.js. In both cases the design can be made to measure: the difference lies in what runs underneath that design.

In everyday language, yes: the design is made for you and is not a filled-in template. In this article, by bespoke development I mean something else: software programmed for a single project, such as a customer portal or a booking system.

Not automatically. Next.js offers techniques for building pages in advance or on the server, which makes fast pages possible. A well-built WordPress website with solid hosting and caching can be fast too. How it is built matters more than the system.

No. React is the library you use to build the components of an interface. Next.js is a framework on top of React that adds routing and server-side rendering, among other things. So anyone working with Next.js is also working with React.

A set-up in which WordPress only manages the content and delivers it via an API, while the pages visitors see are built with a different technology, such as Next.js. It combines a familiar admin with a free-form front end, but is more complex to build and maintain.

Yes. You take the content and URL structure with you, and the application is built from scratch. Often a complete switch is not necessary, and it is enough to place the application alongside the existing website.

A website with a custom design falls within the standard starting prices. For a bespoke application, such as a portal or a platform, there is no starting price: the price follows from an initial scoping of roles, data, screens and integrations.

More on this topic

Further reading

The related service

Bespoke web applications

Portals, booking systems, dashboards and platforms for processes that do not fit an off-the-shelf package, built in React and Next.js.

Dries Nijs, Organic Web Specialist and author of this article

About the author

Dries Nijs, Organic Web Specialist

I am Dries Nijs and I work from Maasmechelen. I have been building for the web since the 1990s and today I work on both sides of this comparison: websites and online shops in WordPress, and web applications in React, Next.js and Node.js. MadeByDries is the personal brand under which I work.

Not sure which side your project falls on?

Describe what you want to build and who will need to work with it. I will then tell you which foundation I think fits, and why.

Discuss your project

Tell me what you want to build or improve

You do not need a technical brief yet. Tell me where you are now and what you want to achieve, and I will help you find the right approach.

Choose at least one topic. You can select more than one.

I only use your details to respond to your enquiry.

Prefer to email me directly?

Location
Maasmechelen, Belgium