WordPress vs custom vs headless is the real question, and most SMB owners frame it as two options when there are three. Short version: pick WordPress to start fast and cheap with lots of content, custom when your site has to carry its own logic or a genuinely unique design, and headless when top speed and flexibility outweigh a familiar editing environment. We build all three and hold no preference detached from your situation. The complete guide to having a custom website built covers the wider frame; this article puts the three side by side in one matrix, with real prices, speed numbers and an honest “choose this if” per case. You can also start at our website service for what we deliver.
What is the difference between WordPress, custom and headless?
- WordPress: an off-the-shelf CMS that runs roughly 40 percent of the web. You pick a theme, add plugins and manage everything in one dashboard. Fast to set up, with a huge market of templates and developers.
- Custom: a website built fully to your requirements, in code you own. Not a theme you bend into shape, but exactly what the design and your processes need. Think a configurator, a calculation module, or a unique design a template will never reach.
- Headless: you split the content (the CMS) from the presentation (the frontend). Editors work in a pleasant CMS like Strapi, Payload or Sanity, and developers build the frontend in a fast modern stack like Astro or Next.js. For the deep comparison of that CMS choice, see our article on comparing headless CMS options: Strapi, Payload and Sanity.
Which approach is cheapest to start with?
Honest answer: WordPress, almost always, in year one. But the starting price is not the same as the price over three years. The table below shows the ranges we consider realistic in the Dutch SMB market, including what keeps landing after the build.
| Approach | One-time build cost | Per month | 3-year TCO |
|---|---|---|---|
| WordPress (theme + plugins) | €4,500 to €8,000 | €30 to €150 | €6,000 to €14,000 |
| Custom (own frontend, own logic) | €12,000 to €25,000 | €20 to €120 | €13,000 to €30,000 |
| Headless (separate CMS + modern frontend) | €12,000 to €25,000 | €40 to €200 | €14,000 to €32,000 |
The monthly cost differs for different reasons. With WordPress you pay for premium plugins, a page-builder licence and often a maintenance retainer. With custom the hosting is cheap (a static site can run under €20 per month), but the money sits upfront in the build. With headless you pay for the CMS plus hosting for the frontend; Sanity and similar services have a free tier but climb with volume. For the full cost reasoning behind an owned build, see the pillar on having a custom website built.
What is faster: WordPress, custom or headless?
Speed is no longer a luxury but a ranking factor and a conversion factor. Google measures the loading experience through Core Web Vitals, and those scores feed into search results. This is where the three approaches separate most clearly.
A standard WordPress site with a heavy theme and a page builder like Elementor runs server-side PHP and database queries on every page view. With good caching and a light theme it scores fine, but in practice many WordPress sites buckle under their plugin weight. Custom and headless often build pages statically, so the visitor gets lean HTML with no database query in the moment. According to the HTTP Archive Web Almanac, page weight is one of the biggest causes of slow sites, and a lean custom frontend wins there.
| Speed factor | WordPress | Custom | Headless |
|---|---|---|---|
| Rendering | Server-side PHP per request (cacheable) | Often statically pre-generated | Statically pre-generated |
| Typical LCP | Moderate to good (theme dependent) | Good to excellent | Good to excellent |
| Risk of heavy pages | High with many plugins | Low, only what is needed | Low, only what is needed |
| Caching out of the box | Plugin required | Built into the build | Built into the build |
What about security and maintenance?
WordPress is the most popular CMS in the world, and that also makes it the biggest target. WordPress itself is rarely the hole; outdated plugins and themes are. According to WordPress.org, updating on time is the single most important security measure, and that is exactly where SMBs let things slide. A site with fifteen plugins has fifteen-plus update sources, each able to open a gap.
Custom and headless have a much smaller attack surface. A static frontend has no live database that the visitor touches and no plugin ecosystem to keep up with. That does not mean zero maintenance, since dependencies still need updating, but the frequency and risk sit lower.
| Maintenance factor | WordPress | Custom | Headless |
|---|---|---|---|
| Attack surface | Large (core + plugins + theme) | Small | Small to medium (CMS separate) |
| Update frequency | Weekly to monthly | Quarterly | Quarterly (CMS tracked separately) |
| Who can maintain it | Many parties, low barrier | Developer needed | Developer needed |
| Risk if not updated | High (known exploits) | Low | Low to medium |
Who can manage the content after launch?
This is the point where WordPress often wins after all, and where headless and custom show their weakness. WordPress has an editing environment that hundreds of thousands of people already know. A new hire logs in and can write a blog post or edit a page within an hour.
With pure custom that is far from guaranteed: if there is no CMS layer, a developer has to make every text change. That is exactly the problem headless solves. Your editors get a modern CMS (Sanity, Payload, Strapi) that works as pleasantly as WordPress, while developers keep the frontend free. For which headless CMS fits your editorial team, read comparing headless CMS options.
- WordPress: familiar editor, enormous talent pool, editors can do almost everything themselves. WordPress’s strongest card.
- Custom without a CMS: developer needed for every text change. Fine for sites that rarely change, frustrating for content-heavy brands.
- Headless: modern CMS for the editors, free frontend for developers. The middle road, provided you set the CMS up well.
Who actually owns the website?
Code ownership sounds abstract until the day you want to switch. With WordPress the core is open source and belongs to nobody in particular, but your build partner can still make you dependent through a proprietary page builder, a custom plugin set, or hosting only they control. With custom and headless, code ownership should be a delivered item: all source code in a Git repository under your own account.
| Ownership factor | WordPress | Custom | Headless |
|---|---|---|---|
| Underlying platform | Open source, not exclusively yours | Fully your code | Frontend your code, CMS of your choice |
| Lock-in risk | Via builder/plugins/hosting | Low with Git ownership | Low with Git ownership |
| Switching to another party | Possible, often messy | Clean, if documented | Clean, if documented |
Ask any party, whatever the approach, about the exit. Do you get the repository under your own account? Are the credentials in your name? The broader explanation sits in our article on website ownership and avoiding lock-in, and the deeper take on the principle in code ownership and vendor lock-in.
How does headless compare to a plain custom build?
Good question, because the two bleed into each other. A headless setup is really a custom frontend paired with an off-the-shelf CMS. The difference sits in where your content lives and how your editors reach it.
| Trait | Custom (no separate CMS) | Headless (custom + separate CMS) |
|---|---|---|
| Content management | Often in code or simple fields | Full CMS for editors |
| Best for | Sites that rarely change, own logic | Content-heavy brands wanting speed |
| Editor experience | Limited unless built in | Modern, pleasant, self-sufficient |
| Multi-channel (web + app) | Not automatic | Yes, one source for all channels |
Short version: pick pure custom when the site has little editing but does have unique functionality or an outspoken design. Pick headless when your editors publish a lot and you still want the speed and freedom of an own frontend. For the visual side of that frontend, the design a template will never reach, see our web design service.
Choose WordPress if…
- You need to go live fast and the budget is tight (€4,500 to €8,000).
- You publish a lot of content and editors should work independently without a developer.
- You do not need a unique design or own logic that a good theme cannot handle.
- You want a large pool of parties able to maintain the site later.
- The site is a brochure or blog, not an application dressed up as a website.
Choose custom if…
- Your site carries its own logic: a configurator, a calculation module, a booking flow.
- The design has to be unique and a template will not reach it. See the De Bungelaer case study and the Quantum Life case study.
- Speed and security sit at the top and you want to keep the attack surface small.
- You want code ownership and migration freedom without plugin dependence.
- The site has little daily editing, so a heavy CMS is not needed.
Choose headless if…
- Top speed is a hard requirement (a fast shop, a brand steering on Core Web Vitals).
- Your editors publish a lot but you still want a free, fast frontend.
- You reuse content across channels: website, app, screens, email.
- You want the best of both worlds: a pleasant CMS plus a custom frontend.
- You have budget and time for a setup that needs more initial configuration than WordPress.
Which mistake do SMB owners make most often in this choice?
The most common mistake is paying a custom or headless price for a site WordPress would have handled fine. A seven-page brochure site with a blog rarely needs an own frontend. The reverse happens too: a brand that leans hard on content and conversion, then gets stuck on a slow WordPress theme that never hits the green on Core Web Vitals.
The second mistake is not accounting for who maintains the site in two years. A beautiful headless setup that nobody on your team dares to touch costs you a developer for every comma. And the third mistake is underestimating the licence cost of WordPress plugins, which makes the “cheap” option more expensive over three years than expected. For the broader weighing between platforms, including Webflow and Wix, see our comparison of WordPress, Webflow, Wix and Shopify and the technical depth in Astro and Next.js vs WordPress.
How do you choose in 5 minutes?
- Do you need a unique design or own logic? Yes, and little editing = custom.
- Do you publish a lot of content and demand top speed? Yes = headless.
- Do you want to go live fast and cheap with lots of editing and a standard design? Yes = WordPress.
- Torn between custom and headless? Do you need a pleasant editing environment? Yes = headless. No = custom.
- Does an off-the-shelf theme simply fit? Then WordPress is the pragmatic choice; build nothing more complicated.
What is the first step?
Write on one page what your site has to do: how many pages, how often you publish, whether there is a calculation module or booking flow in it, and how important speed is to you. Then walk through the five-minute check above. Nine times out of ten the choice becomes clear from that alone.
Book a free intake call. In thirty minutes we look at your content and your goals and give honest advice on WordPress, custom or headless. For the full frame also read the complete guide to having a custom website built and explore our website service.
