WordPress is the right answer for most business websites, because it is cheaper, your team can edit it, and a plugin exists for almost everything. A custom build in something like Next.js earns its cost when performance genuinely matters commercially, when the interface is doing something unusual, or when the site must behave more like an application than a brochure.
What people mean by headless
Normally a CMS does two jobs: it stores your content and it draws the pages. Headless means splitting those apart. Something still stores the content, and a separate front end — often Next.js — fetches it and renders the site.
The appeal is that the front end is no longer constrained by what a theme allows. You can build anything, because you are building it. The cost is that you are building it, which is precisely the expensive part.
When WordPress is simply the right answer
Most of the time, and we will say so rather than upsell you into something with a more impressive name.
If your site is pages, a blog, a contact form and maybe a shop, WordPress does all of it, cheaply, with a plugin for nearly anything you will want later. Your team can edit it without calling anyone. Any developer in the country can pick it up if we are hit by a bus. Those are serious advantages and they are easy to undervalue while reading about newer things.
When custom genuinely earns its cost
There are real cases, and they tend to be obvious once you see them.
- Performance is commercially material. Not vanity scores — situations where a slow page measurably costs money, usually at volume.
- The interface is the product. Configurators, calculators, anything where the visitor is doing something rather than reading something.
- The content is unusual. We built Spoormaker & Partners around a scroll-driven wireframe sequence and an archive of patents going back to 1964. That is not a theme with the colours changed.
- It needs to be 3D or interactive. ScanRF is an entire self-healing radio mesh network, explorable in a browser tab. No CMS was going to do that.
- The website is part of the credibility. For a technical business, a templated site quietly argues against the pitch. Gridloop.AI is hand-coded for that reason.
What you give up going custom
This is the part that gets skipped in conversations about modern stacks, and it is worth saying plainly because it is the reason most businesses should not do it.
| WordPress | Custom build |
|---|---|
| Cheaper to build | More expensive, scaling with the amount of code |
| A plugin exists for most things | Someone writes it |
| Your team edits pages directly | Depends entirely on how editing was built |
| Any developer can maintain it | A smaller pool, and often us |
| Slower, needs performance work | Fast by default, because nothing extra ships |
That fourth row deserves more attention than it usually gets. A custom build narrows the number of people who can pick your project up later. We think that is a fair trade when the result justifies it. We do not think it is a fair trade so your brochure site can score better on a test nobody but you will run.
The honest middle ground
Most of what people want from a custom build is actually available by running WordPress properly: good hosting, disciplined plugin choices, optimised images and a theme that is not carrying five hundred features you will never use.
A well-built WordPress site is quick. A badly built one is slow, and it is almost always slow for reasons that have nothing to do with WordPress and everything to do with what was installed on top of it.
Before paying for custom to solve a speed problem, it is worth establishing whether you have a speed problem or a plugin problem. They look identical from the outside and cost very different amounts to fix.
What should you do?
If you are asking the question because custom sounds better, the answer is WordPress. If you are asking because you have a specific requirement that WordPress keeps getting in the way of, you probably already know, and the conversation is about scope rather than platform.
Our custom builds are quoted on scope, because the only honest way to price writing code is to understand what is being written. The rest of our prices are published.
Common questions
Is Next.js better than WordPress?
Not better, different. Next.js gives you complete control over the front end and is fast by default because nothing ships that you did not write. WordPress is cheaper, editable by your team and maintainable by almost any developer. For most business websites those advantages beat raw performance.
Is a custom site faster than WordPress?
Usually yes, because nothing extra loads. But a well-built WordPress site on good hosting with disciplined plugin choices is genuinely quick. Most slow WordPress sites are slow because of what was installed on them, not because of WordPress.
Can my team still edit a custom site?
It depends entirely on whether editing was built in, which is a scoping decision rather than a technical limit. Ask the question before the build rather than after, because retrofitting an editing interface is considerably more expensive than including one.
What does a custom build cost in South Africa?
Quoted on scope. The more code a project needs, the more it costs, and there is no useful way to price it without understanding the requirement. Our platform builds are published: brochure sites from R12,000, WooCommerce from R35,000, Shopify from R45,000.
When is headless definitely the wrong choice?
When the site is pages, a blog and a contact form. You would be paying for flexibility you will never use, narrowing the pool of people who can maintain it, and making routine content changes harder than they need to be.
Not sure whether you need custom?
Describe the thing WordPress keeps getting in the way of. If it turns out WordPress does handle it, we will tell you, and that will have been the cheapest consulting you bought this year.