Quick answer: a builder is the right call when the task is minimal — establishing a presence, testing an idea, collecting enquiries from ads. Custom development is what you need when the site has to bring in clients from search, work in several languages, hold a filterable catalogue, or integrate with your systems. The thing to compare isn't price but the ceiling: a builder is cheaper at the start, but hitting its limits a year in costs more than building for the job from the outset.
The builder-versus-custom debate is usually framed around price: one is cheap, the other isn't. That's the wrong frame. Price is a consequence. What you should be comparing is the ceiling — how far a solution carries your task, and what happens when you reach its limit.
Below is an honest breakdown of both, without campaigning for either. I build custom sites, so I have an obvious interest — which is why I'll start with where builders genuinely win.
When a website builder is the right choice
There are situations where hiring a developer makes no sense, and it's worth saying so plainly.
You're testing an idea. There's no certainty yet that the service sells, that the niche is yours, that the model works. Putting a page together on Squarespace or Wix over a weekend and running ads is more sensible than investing in building something that may not be needed.
The site just needs to exist. Clients come from referrals, social media or offline, and the site is confirmation that you're real: address, services, contact. Search isn't a channel you're counting on.
The budget is genuinely tight. If the choice is between a builder and no website at all, the builder wins. It isn't ideal, but it works.
You want to change everything yourself, often. Some business owners edit their site weekly and enjoy it. A builder gives that freedom with no intermediary.
In all of these cases, custom development means paying for capabilities you won't use.
Website builder limitations: where the ceiling starts
Problems begin when the site stops being a formality and has to bring in clients. That's when limits appear that weren't visible at the start.
Technical SEO. Builders give you the basics: title, description, sometimes a sitemap. But Schema.org structured data, precise control over canonical URLs, control of heading structure, steering indexation of individual sections — that's where the freedom ends. In a competitive market that ceiling is enough to keep you below a certain position regardless of how good your content is.
Speed. A builder is universal, so it loads code for every eventuality, including features your page doesn't have. Hence unnecessary scripts, unoptimised images and weak Core Web Vitals, which affect both rankings and visitor behaviour. With custom development this is solved at the architecture level: when I moved an auto service business from a legacy platform to a custom-built theme, its mobile performance score went from around 50 to 92 — not through magic, but because only what's needed gets loaded.
Multilingual setup. Formally, language versions exist almost everywhere. In practice, the correct technical connection between versions — separate addresses and markup telling search engines which version serves which audience — is either poorly implemented or locked behind paid extensions. The typical result is language versions competing with each other instead of each serving its own market. For any business selling across borders, that's a direct loss.
Catalogues, filters, integrations. The moment you need a catalogue filtered by several parameters, synchronisation with your CRM, a client portal, or a non-standard pricing calculator, a builder either can't do it or does it through workarounds that break on updates.
Readiness for AI search. More and more people look for suppliers and services through ChatGPT, Perplexity and Google's AI answers. Appearing in those answers depends on how unambiguously your site states its facts to a machine: structured data, clean semantics, content accessible without executing scripts. Builders give you exactly the markup their platform's developers anticipated, and adding your own usually isn't possible.
AI-generated websites: the third option and its risks
The choice used to be binary. Now there's a third path: generate the site with AI. It deserves a separate warning, because it looks like the best of both worlds — the speed of a builder with the flexibility of code.
The tool is genuinely powerful; I use AI in my own work every day. The problem isn't the tool, it's the absence of oversight. AI does exactly what it's told, but it doesn't know that you can't change a URL structure without redirects, that you can't lose structured data, that you can't swap language versions around. One of my clients learned this in practice: after an AI-generated redesign was pushed straight to the live site, traffic started falling within two days and didn't recover for over a month. I've written that case up separately.
The conclusion is straightforward: AI is excellent as an accelerator under expert oversight and dangerous as a replacement for one.
What a website builder actually costs
A builder is cheaper at the start, but its cost isn't one-off. The platform subscription, paid extensions for whatever isn't in the base plan, separate charges for language versions or for lifting limits — over two or three years that adds up to a figure comparable with custom development.
The second expense arrives when you move. Sites built on a builder can rarely be transferred whole: the markup is proprietary, the export partial, the URL structure often changes. So you're paying not for a migration but for a new website plus the work of moving without losing rankings — which is more expensive than building for the job in the first place.
Hence a practical conclusion: if you already know that in a year or two you'll need a catalogue, language versions or serious SEO, a builder at this stage isn't a saving. It's a deferred cost.
Signs your business has outgrown its builder
Indicators that a builder has stopped coping:
Rankings aren't improving even though you've improved the content and it's objectively better than that of competitors ranking above you.
Speed scores won't rise no matter what you do with images.
A feature you need can't be built — only something "similar", or via a third-party extension with a monthly fee.
Language versions bring no traffic despite good translations.
Every small change requires working around the platform's limits.
If two or three of those apply, the question is no longer whether to change your setup, but when and at what cost.
The price of a builder versus custom development
Builder: platform subscription plus extensions, typically a few hundred euros a year, plus your own time assembling it.
Custom development: a simple landing page — €700-1,400; a conversion landing page with full search and AI optimisation — from €2,000; a multi-page website — from €2,000; a redesign of an existing site — from €1,000.
Comparing those figures directly is misleading: they're different products for different jobs. The right question isn't "which is cheaper" but "what horizon am I planning this site for".
How to choose between a builder and custom development: three questions
Will search be a channel for winning clients? If yes, a builder will limit you at a technical level and no amount of content will get around it. If not, and your clients come from elsewhere, the limitation won't touch you.
Do you need a catalogue, integrations or language versions? A filterable catalogue, CRM synchronisation, proper multilingual setup — that's the line where builders end.
What's your planning horizon? A site for six months to test a hypothesis and a site meant to be your main sales channel for five years are different jobs, and they don't need to be solved with the same tool.
How I build websites for a specific job
I combine development and SEO, so the technical base — markup, speed, structure, AI-search readiness — is designed in from the start rather than bolted on later. That same combination lets me say honestly in a first conversation that a builder will cover your task, if it genuinely will. Taking on a project a client doesn't need serves neither side.
Website builder or custom development: what to choose
A builder — when the task is minimal, the horizon short, and search isn't part of the plan. Custom development — when the site has to bring in clients, work in several languages, hold a catalogue or integrate with your systems.
The mistake isn't starting with a builder. The mistake is staying on one after your business has outgrown it, and spending year after year blaming flat growth on your copy when the real limit is the platform.
If you're unsure which situation you're in, write to me and we'll look at your site and your goals together. If it turns out a builder is all you need, I'll tell you that.
