Website builder or agency? An honest decision guide for small companies

There is a question almost every small company asks itself at some point — and to which it astonishingly rarely gets an honest answer: wouldn't a website builder simply do? The uncomfortable truth for the web services industry is: yes, often it would. And the equally true addition: in certain cases the website builder becomes the most expensive cheap decision a company can take. An attempt at a fair weighing-up.

The starting position of this text belongs disclosed: it appears as an advertisement of the Osnabrück web agency BitBau (in German) — that is, of all things, of a provider of bespoke development. One may read that as a conflict of interest. But one can also see it the other way round: an agency that does not send away enquirers with website-builder needs, but sells them expensive projects, has won in the short term and lost in the long. Honest advice begins by recommending the simple route wherever it holds.

First the terms. Website builders are rental solutions: one chooses a design template, fills it with one's own texts and pictures in the browser and pays a monthly fee in which hosting, maintenance and updates are included. No code, no servers, no technical appointments. Precisely therein lies their real strength — less in the price than in the disappearance of whole categories of worry.

Whom is that enough for? The criteria are pleasingly clear. The website is supposed to make the company findable and present it credibly: services, team, opening hours, reference photographs, contact details, directions. There are no special functions, no connection to other systems, no multilingual presence, and the content rarely changes. Anyone who recognises themselves in this description — many trades businesses, restaurateurs, freelancers, associations — gets a decent result with a website builder for little money. That is not a makeshift but the fitting solution.

This too belongs to fairness: the templates of modern website builders are long since no longer the rigid stencils of former times. Mobile display, decent basic speed, simple search engine fundamentals — good providers handle that as standard today, in part better than some agency website that has come of age. Anyone who last tried out a website builder ten years ago probably underestimates the category.

Even so, before signing up it is worth looking at points that rarely appear in the brochure. How far can the template be adapted to one's own colours and typefaces without the result looking contorted? Does the tariff allow one's own domain and a presence without the provider's advertising? How easily can the Impressum — the publisher's imprint German law requires — and the privacy policy be entered and kept up to date? What export options are there, should one one day want to leave? And how quickly does one reach support if the site is ever unreachable? Half an hour with the free trial version answers many of these questions more reliably than any comparison table.

So where do the limits lie? The first is a matter of design. Templates look good, but they look like a template — and do so for all the customers of the same provider. Anyone appearing visually interchangeable in their sector usually loses no business by it. But anyone wanting to differentiate themselves precisely through brand and appearance runs into a ceiling that no tariff upgrade can break through.

The second limit is functions and connections. Website builders can do what their range provides for. An appointment calendar from that range works; the connection to the special industry software, the inventory management or the booking system the company has worked with for years usually does not. Individual processes — configurators, customer portals, evaluations of one's own — lie in principle outside the category.

The third limit is readily overlooked: moving out. Website builders are rented flats — whoever leaves takes the furniture with them, but not the walls. Texts and pictures can usually be exported; structure, design and functions are tied to the platform and have to be rebuilt when moving. The domain and the visibility built up in search engines also want moving carefully. That is no argument against getting started — but a reason not to confuse the rental solution with a home of one's own.

Anyone deciding on the website builder can, however, protect their later freedom of movement from the outset. The domain belongs registered to one's own company, not to the website builder provider — it is the address under which customers know the company, and it must survive every move. Email addresses should run independently of the website builder, so that a change of platform does not cut off communication. Texts belong additionally backed up locally, photographs kept at original resolution rather than only in the platform. Anyone taking these precautions on the first day negotiates from a position of strength when moving out — anyone who neglects them pays the price years later in the form of dependency.

And finally multilingualism. For a presence in two or three languages some website builders offer add-on modules; it rarely becomes really convenient, consistent and search-engine-friendly that way. Anyone wanting to run their offering seriously in several languages — with clean addresses per language and translations maintainable centrally — is working, from a certain point on, against the tool instead of with it.

When does the calculation tip towards the agency? A look at the project examples from BitBau shows the typical cases. QR2GO, a platform for creating and evaluating QR codes with analytics features, came into being in twenty-four weeks; ScanYou, a tool for automated visual comparison tests of websites, in sixteen. Neither is a website in the classic sense, but a software product with a logic of its own — for website builders simply no terrain. Anyone with a business idea that consists of more than pages does not even face the choice.

More revealing is the borderline case in between: the Praxis am Salzmarkt, a medical practice website. To all appearances a website-builder candidate — a manageable number of pages, a clear purpose. What tipped the balance towards bespoke development was the requirement to run the presence entirely in three languages, maintained from a single source; it was implemented in twelve weeks. The lesson from it: it is not the size of the company that decides the route, but the concrete requirement. Sometimes a single one is enough to change the category.

The agency side of the weighing-up also involves a requirement that is rarely spoken openly: the client's time and collaboration. The projects mentioned took twelve, sixteen and twenty-four weeks — and over such periods a project is not an order but a collaboration. Content has to be delivered, interim states looked at, decisions taken, and continuously at that, not only shortly before the launch. Anyone who has no room for this alongside the day-to-day business will get no good result even from the best agency — and is under some circumstances more honestly served by the solution that demands less involvement. That is not a flaw but a sober question of resources, which one should answer before the commission, not during it.

Honesty also involves cost truth in both directions. The website builder costs little per month, but it costs permanently — plus one's own working hours, which owners put into templates, texts and technical questions in the evenings and rarely count in. An agency project costs noticeable money up front and ongoing maintenance afterwards — but specialists are at work, and the result belongs to the company. Which calculation comes out cheaper depends on the time horizon and on what one's own time is worth. Blanket answers to this question are almost always sales arguments.

There are middle ways too. The most pragmatic: start with the website builder and change when the requirements grow. The move then does cost something, but one pays for it out of a running business — and by then knows very precisely what one really needs. The opposite exists as well: one can commission an agency and still deliberately build small. A cleanly designed presence without special functions is no contradiction but often the most sensible stage one.

If the change from website builder to agency does eventually become due, an orderly approach has proved its worth. First collect the requirements at which the website builder concretely fails — this list is the best brief an agency can get, because it comes from lived operation instead of from conjecture. Then clarify what comes along: the domain, the texts, the pictures, the visibility built up, via clean redirects from old addresses to new. The moving date belongs in a quiet business phase, not in the middle of the peak season. Seen that way, the change loses its terror: it is not a fresh start from zero but a move with an inventory.

For the decision itself, five questions suffice. Does the website need functions that are not available off the peg? Does it have to talk to the company's other systems? Is it supposed to appear in several languages? Is the presence an essential part of the positioning — or a compulsory exercise that simply has to exist? And: is there somebody in the house who can and will take on the upkeep permanently? The more often the answer is “yes, but not off the peg”, the more the conversation with specialists is worth having.

One special case deserves a note of its own: the small online shop. Website builder providers carry shop functions in their range, and for a manageable offering with standard shipping these can well suffice. But as soon as an existing inventory management system is to be connected, prices calculated per customer group or particular ordering processes mapped, the category tips quickly. Added to that: selling to consumers brings additional legal requirements whose classification belongs in expert hands. Precisely with a shop, therefore, a sober list of requirements before the choice of system is worth more than anywhere else — subsequent system changes are especially laborious here, because ongoing orders and customer data have to move along.

This conversation is, incidentally, at the same time the best test of the other side. A reputable agency will ask precisely these questions in the first conversation — and, with a clear website-builder profile, will say precisely that. Anyone who instead hears only sales rhetoric in answer to the question “wouldn't a website builder do?” has already received their answer about the provider, if a different one than expected.

That leaves the conclusion. The question “website builder or agency?” has no general answer, but an individual one — and that one is usually found quickly if one lets requirements rather than taste decide. The website builder is the right choice for everyone whose website is above all supposed to present. The agency becomes it where the website has to work: map processes, connect systems, run languages, carry a brand. Anyone who understands their website as a tool usually already knows which of the two worlds it belongs to.