Website builder vs custom website

  • Builder: fastest and cheapest to start
  • WordPress: the usual middle, and portable
  • Custom: only when the site is the product

Three routes, and the question that decides between them

Builder, WordPress, or built from scratch. The honest answer depends on one thing most comparisons never ask: who will change the site in a year, and what happens if the person who built it is not around.

What each route costs

The three routes, honestly

Including when the cheapest one is the right answer.

What each route is good for

A website builder

Drag and drop, hosting included, live the same day. Right for a first site, a single landing page or a business whose site is a brochure. The limit is that you work within what the builder does.

WordPress

The usual middle. You own the files and database, anyone can be hired to work on it, and almost anything you need exists as a plugin. In exchange it has to be kept updated, which is a real and ongoing cost.

A custom build

Worth it when the website IS the product - unusual logic, an application, an integration nothing off the shelf does. For a brochure site it is a large bill for something a theme does equally well.

AI-generated as a starting point

An AI builder produces a real first draft in minutes, which is genuinely useful for getting past a blank page. Treat the output as a draft to edit, not as a finished site nobody needs to read.

The question that actually decides it

Four things to ask before you choose, in the order they will bite.

Ask these before you commit

Who edits it in a year?

If the answer is somebody non-technical in your own office, that rules out most custom builds and points at a builder or WordPress.

Can you take it with you?

A WordPress site is files and a database you can move to any host. Most builders are a subscription you cannot export in any useful form. Ask this before you start, not when you want to leave.

What happens if the builder disappears?

For a custom build, ask who else could pick it up. A site in a widely-known stack is cheap to hand over; a bespoke framework with no documentation is not.

Does it need to do something unusual?

If the site has to calculate, integrate or enforce something specific, say so early. That requirement is usually what moves the answer from builder to WordPress, or from WordPress to custom.

Builder, WordPress or custom: common questions

For a brochure site that presents what you do and how to get in touch, yes, and the money saved is better spent on the content. Builders become limiting when you need something specific the tool does not do, or when you want to move the site elsewhere - most builder sites cannot be exported in any useful form, which is the question to ask before you start rather than when you want to leave.

WordPress unless the website is the product. It gives you ownership, a non-technical editing interface, a huge plugin library and an easy hiring market, which covers almost every business site. A custom build earns its cost when there is unusual logic, an application behind the pages, or an integration nothing off the shelf handles - not simply because the design is distinctive, which a WordPress theme can also be.

An AI builder is very good at the first draft and at getting past a blank page, which is a real problem it genuinely solves. It is weaker at the things that make a site convert: knowing which objection to answer first, what proof to put next to the button, and what to leave out. The practical answer for most businesses is to use AI for the draft and a person for the decisions.

A builder, by a wide margin, because the subscription includes hosting and there is no build fee. WordPress sits in the middle - either your own time or a build fee, plus hosting and maintenance. A custom build is the most expensive and the gap is large. Our breakdown of what a website costs has the current figures for each.

Yes, and it is a common and sensible route - start cheap, prove the idea, move when the limits start to bite. Be aware that most builders cannot export in a form another system can read, so in practice the content is rebuilt rather than migrated. We handle that move, including the redirects that keep your existing search rankings.

No, not by virtue of being custom. Google ranks pages on content, speed, mobile behaviour and links, none of which require a bespoke build - a well-configured WordPress site on good hosting competes perfectly well. Where a custom build helps is when the site needs to do something unusual that an off-the-shelf stack makes slow or impossible.

Where to go next

Prices and plans for each of the three routes.