Sooner or later the question lands on the table: do we build this in WordPress, or do we go custom? It's a decision that's usually made far too early — before it's clear what the site actually needs to do. And that's exactly the wrong order. Here's what it really depends on, and how five questions get you to a solid answer.
Purpose first, technology second
WordPress and custom builds aren't camps you belong to. They're tools. You don't pick a hammer because you're a fan of hammers, but because there's a nail in front of you.
So the question isn't 'which is better?' but 'what does this site need to do three years from now?'. Once that's clear, the technology usually points itself out. That's why we always choose in that order: goal, structure, and only then the build.
Where WordPress is strong
WordPress is the most-used CMS in the world for good reason. For a large share of small and medium businesses it does exactly what's needed:
- You manage content yourself — pages, news, copy and images
- A vast ecosystem of plugins for forms, SEO and integrations
- Familiar to colleagues who have worked with it before
- Quick to extend without immediately needing code
- Easy to hand over — you're not locked to a single agency
Where a custom build makes the difference
Custom means: built around what you actually need, with no dead weight. That pays off the moment your site is more than a set of pages — when there's logic in it, a link to another system, or an experience you can't buy off the shelf.
It also delivers something hard to copy: speed and security. No dozens of plugins tripping over each other, no updates breaking something overnight. And visually you're tied to nothing — your site won't look like the sixth competitor using the same theme.
- Complex or unique functionality no plugin solves well
- Integrations with stock, planning, membership records or a CRM
- High demands on speed, security or scalability
- A brand experience that genuinely has to stand apart
The five questions that settle it
Run through these before you call an agency. They'll save you a lot of discussion — and often money too:
- Who will maintain the site? You, weekly? Then a familiar CMS weighs heavily.
- How unique is the functionality? Is there already a decent standard solution?
- Does data need to move to and from another system? The more integrations, the sooner custom pays off.
- How much do speed and findability drive your revenue? For a webshop, every second counts.
- What's the growth plan? Are you building for today, or for where you want to be in three years?
The answer is often: a bit of both
In practice it's rarely black and white. A WordPress site with a custom theme — so no ready-made template — gives you the ease of a CMS with a design and a speed that are genuinely yours. For many businesses that's the sweet spot.
The reverse works too: a custom-built site with a simple CMS behind the parts you want to update yourself. The question isn't whether you can edit your own copy — you always can — but how much freedom sits underneath it.
What it costs — and what it saves you
With us a website starts from € 1,950 and a webshop from € 3,500. That range mostly tracks the questions above: the more custom logic and integrations, the higher the investment up front.
Don't look at build cost alone. A site you can easily maintain yourself saves hours every month. A site that's fast and findable earns itself back in enquiries. And a site that needs replacing in two years was never the cheapest one.