8 July 2026 · 6 min read
Website builder or agency: the honest decision
For some companies, a website builder is the right choice - and that's an agency saying so. Where the limits really are, which questions settle the decision, and what to do if you already have one
Here's something an agency rarely tells you to your face: for some companies, a website builder is the right choice. Wix, Squarespace and their relatives aren't toys, and anyone claiming otherwise is trying to sell you something. The question isn't whether a builder is good enough - it's whether your website is meant to be a shop window or a tool.
What a builder actually does well
Credit first, because it's earned. A modern builder takes everything off your hands that counts as running the site: hosting is included, the security certificate sets itself up, updates happen in the background. The templates are respectable design work, often better than what small companies got from the local agency fifteen years ago. And the basics of getting found - clean page titles, a directory for search engines, even multilingual linking if you want it - are handled automatically by the system.
No wonder they're everywhere: Wix alone runs a good four percent of all websites worldwide. That's not a niche tool, that's infrastructure.
If your website mainly needs to exist - who we are, what we do, how to reach us, a few good photos - a builder gives you that quickly and without depending on a service provider. For a whole class of companies, that's the right answer, and they deserve to hear it.
The question isn't quality, it's work
The difference shows up where the website stops standing around and starts working.
Working means: it should be found when someone in your region searches for what you do - against competitors who want the same thing. It should turn visitors into enquiries, not just inform them. It should talk to your processes: an enquiry should arrive where it gets handled, a booking should know the calendar, a customer area should know who's logged in. And it should be able to grow without being rebuilt for it.
For the shop window, the builder was made. For the work, it starts to pinch - it has to serve millions of websites at once, and can therefore only offer what can be standardised for millions.
Where the limits really are
Three limits are documented, and they remain in place even on the most expensive plan.
The flat isn't yours. A builder website runs on the provider's servers and only there - you can't move it. If you ever switch, you take your texts and images with you, but the website itself - design, structure, everything you've set up over the years - stays behind and gets rebuilt. With blogs, even taking the content along is restricted. That's not a scandal; it's in the providers' own help articles. But it belongs in the decision: you're renting with no way to take the building with you when you leave.
Multilingual has a catch. Builders have been able to translate for years, and much of it is well done. The finer points aren't: the addresses of your subpages stay in one language - your French services page is still called /angebot, which is ideal neither for visitors nor for search in French-speaking Switzerland. Here especially, where a second language is often half the market, this point deserves a close look.
Customisation ends where the app market ends. What the provider's catalogue offers, you can have - what it doesn't, you can't, because access to the code and the server doesn't exist by design. Whether the builder is enough today is the wrong question. The right one: is it enough for what you're planning in three years?
And because you'd ask anyway: yes, there's a middle way, and it's usually called WordPress. Open systems of this kind, unlike builders, can move with you - the website is yours and runs with any host. In return, a duty comes back to you that the builder handled invisibly: updates, security, maintenance. Outdated plugins are among the most common reasons company websites get hacked - so the middle way is no middle way at all if nobody takes on the upkeep. As a rule of thumb: open systems with a partner who's contractually responsible for maintenance, or not at all.
In fairness: the other side has catches too
An honest comparison looks both ways. A custom-built website has risks of its own, and their names are dependence and quality.
Dependence: if only your service provider understands the website, you've traded builder lock-in for agency lock-in - and that's no improvement. So demand that what you pay for belongs to you: the code, the domain, the accounts, the content. And that everyday things - a text, a photo, a new job listing - live in the content management system, where you change them yourself, without a ticket and without an invoice. A well-built website makes you more independent than a builder, not less. A badly built one does the opposite.
Quality: "custom-built" is no guarantee of quality, just as "builder" is no defect. Poor craftsmanship exists in bespoke work too, and as a layperson you won't spot it by looks. What you can spot: whether someone takes your questions seriously, whether they show you references you can visit yourself, and whether they'll occasionally talk you out of a commission. Anyone who sells you the big solution in every case had the answer ready before they heard your question.
The four-question self-test
A quiet quarter of an hour is all this decision needs. Four questions:
Should the website actively bring in new customers - beyond reassuring those who already know you? Do you need it in more than one language - properly, not as an afterthought? Should it work with other systems, now or foreseeably - bookings, customer login, connections to your software? And: do you want to be able to take what you build with you one day?
Four times no: take the builder, with our blessing, and invest the difference in good photography - it'll do more for you there than any technology. One or two yeses: now it's a trade-off, and this is exactly where a conversation beats any comparison table. Three or four yeses: then the website is a tool of your business, and tools are things you have built.
If you already have a builder site
Maybe you're reading this with a Wix site long since live. First things first: no cause for alarm. If it does its job, it does its job - nobody should switch because an article suggested it.
But if your company is outgrowing it, plan the switch as what it is: a new build plus a move. The content comes along, the building doesn't - and so that no visibility gets lost on the way, the move wants proper preparation. We've written that up separately.
Deep DiveRelaunching your website without vanishing from Google - the moving plan in detail
The best time for that planning, by the way, is before it gets urgent. A move under time pressure is the most expensive kind - with flats and with websites alike.