Website builder or a site built for you — which is right for a small business?

What actually differs between a website builder and a built site?

The difference that matters is not design quality or price — it is where the site runs and how much of it you can take away. On a builder, the site is a document inside someone else's software, and what happens when you stop paying is the vendor's decision rather than yours. A built site is a set of files you hold, that any competent developer can host anywhere. Everything else follows from that one fact.

It is worth being precise about the word "custom", because the industry uses it loosely. A site built for you can still use an off-the-shelf framework, an open-source content system and a template as a starting point. What makes it portable is not that every line was written from scratch — it is that the result is standard files in standard formats, under licences that let you move them.

What can you actually take with you if you leave?

This is the one question with a documented answer, so it is worth checking rather than guessing. Each platform publishes what its export includes. Below is what four of them said on 25 August 2026, taken from their own pages. Before you commit to any platform, read its export page — not a review of it, and not what a salesperson tells you.

Notice the pattern: the thing that survives a move is almost always the writing, and the thing that does not is the structure — the shop, the booking, the layout, the styling. That is worth knowing before you spend two months getting a site exactly right on a platform you might outgrow, because the two months are the part you cannot export.

Checked against the source: 25 August 2026

When is a website builder genuinely the better choice?

A builder is the better choice when the site is a small, stable part of how customers find you, when the budget genuinely cannot stretch, or when you are still testing whether the business works at all. In those cases paying a studio is not just expensive, it is the wrong shape of spending — you would be buying flexibility you have no use for.

There is a common argument that builders are bad for being found in search. As a general claim it does not hold: a small, well-organised site with clear text can be found perfectly well on a builder. Where builders do get in the way is narrower — several languages done properly, control over page structure and markup, and page speed on media-heavy sites. If none of those apply to you, that argument should not move you.

• You have one location, and what people need from the site is an address, opening hours, a menu or price list, and a way to get in touch. A builder does this well and you can update it yourself in five minutes.
• Your customers actually find you somewhere else — a maps listing, a marketplace, Instagram, word of mouth — and the site is the place they check before deciding. Fix the listing and the reviews first. That work is free and it matters more than the site.
• You are testing an idea. Spending real money to discover nobody wants the thing is an expensive way to run an experiment.
• The budget is genuinely small and fixed. A cheap site that exists beats an ambitious one you keep postponing.
• You want to make changes yourself, often, without asking anyone. Builders are built for exactly this, and it is a real advantage.
• It is a temporary page — an event, a seasonal offer, a single campaign — where nobody will care about it in a year.

When does a builder start costing you more than it saves?

A builder starts costing you when you need something it was not designed for, because the workarounds accumulate. The usual triggers are a second language done properly, a booking or shop flow with rules of its own, and the point where the site has to hand information to another system — a till, a CRM, an accounting tool.

None of these is an emergency on the day it appears. The reason to think about them early is that leaving is cheapest before you have built a lot inside the platform — the export limits above bite in proportion to how much structure you created.

• A second and third language, where every page, legal text and form has to exist in each one and stay in step. This is where most small-business builder sites quietly become half-translated.
• A booking or ordering flow with real rules: capacity, deposits, cancellation windows, tax handling that has to be right in more than one country.
• Anything that has to talk to another system you already use, in both directions.
• Enough traffic that page speed shows up in your numbers, on a site heavy with photos or video.
• The moment you want to hand the site to someone else to develop further, and discover the answer depends on what the platform allows.

How do you move off a builder if you are already on one?

Moving off a builder is mostly a content-rescue exercise, not a technical migration, because the structure usually cannot come with you. Do it in this order, and do the domain part first — it is the only step where delay can cost you something you cannot get back.

1. 1 Confirm the domain is in a registrar account you control, with an email address you still read. If the domain sits inside the builder's account, move it out or at least get access before anything else.
2. 2 Run whatever export the platform offers and keep the file, even if it only contains text. Read its documentation first so you know what will be missing.
3. 3 Save the site as it looks today: every page as a PDF or a full-page screenshot, and the images at full size. This is your reference for the rebuild, and it takes an hour.
4. 4 Write down the addresses of every page. You will need them to redirect the old addresses to the new ones so that links and search results do not break.
5. 5 Rebuild, then switch the domain across, then put the redirects in place — in that order, so the site is never unreachable.
6. 6 Keep the old subscription running for a few weeks after the switch. It is a small cost against the risk of discovering something you forgot to copy.

What is the weakness of having a site built for you?

A built site has a real weakness and it is not the price: it needs a competent person to look after it, and that person can become unavailable. A builder company is unlikely to disappear next month. The freelancer or small studio who built your site might, and then a site nobody is maintaining slowly becomes a liability.

Reassurance is not an answer to this, and any supplier who offers only reassurance is telling you something. The answer has to be structural: standard, widely-known technology rather than a private system; the domain in your registrar account; a contract that says who owns what and what happens on the way out; and no piece of the setup that only one person can access. Those conditions make you replaceable-supplier-proof, which is a better thing to buy than a promise.

We are a small studio, so this applies to us too. Our sites are built on widely-used open technology precisely so that another developer can pick one up without meeting us, and our contract sets out what transfers and when. That is what we can offer against this risk; it is not a guarantee that nothing will happen, because nobody can sell you one of those.