Website builder, WordPress, or fully custom — how to choose

Most people ask the wrong question first. They ask "which platform is best?" when the question that decides everything is "who is going to look after this in eighteen months, and what will it need to do by then?"

Answer that, and the platform picks itself.

The short answer

If you need a good-looking site with a handful of pages, and you want to edit it yourself on a Sunday evening, use a builder like Squarespace or Wix. If you need content that behaves like data — hundreds of listings, filters, relationships between things — use custom-coded WordPress. If the site *is* the product, or it has to run part of your business, build it bespoke.

Builders: Wix, Squarespace, Shopify

A builder is a rented system. You get hosting, security patches, templates and an editor for one monthly fee, and you get a site live in days rather than weeks.

What you gain: speed, low cost, and genuine independence — you can change your own copy and images without emailing anyone.

What you give up: control over structure and performance. Builders are excellent at pages and weak at systems. As soon as you want "show me every property in this postcode under this price, sorted by newest, and email me when a new one matches", you are fighting the platform. Page speed is capped by their code, not yours, and heavy template sites often lose ground in search to leaner builds.

We still recommend builders regularly. A new consultancy with five pages and a contact form does not need bespoke engineering, and paying for it is a waste. What we do differently is treat the builder as a serious platform: proper information architecture, hand-written CSS where the template resists, real metadata and structured data, compressed imagery, and analytics that answer commercial questions.

Custom-coded WordPress

WordPress is not a template you buy. Done properly it is a content framework, and the difference between a bad WordPress site and a good one is entirely in how it is built.

A build like this typically uses custom post types for each kind of content, Advanced Custom Fields or JetEngine to define the fields for each one, and dynamic listings that query that content rather than repeating it by hand. Every page type is coded as a template, so a new entry automatically renders correctly.

That structure is why WordPress is still the right answer for content-heavy businesses:

• Directories, portfolios, property listings, event calendars, course catalogues
• Editorial sites where multiple people publish, with real editorial roles
• Sites where the client must add new sections without a developer
• Ecommerce via WooCommerce, where you want full control over the checkout

Where it costs you is maintenance. Plugins update, and updates occasionally break things. WordPress needs hosting that is looked after, backups that are tested, and someone responsible for it. Priced honestly, that ongoing care is part of the build.

Fully custom

A bespoke build means the code exists only for you: your data model, your interfaces, your logic. It is the right choice when the site is not really a site.

Signs you are in bespoke territory:

• Users log in and see different things
• Money, bookings, contracts or stock move through it
• Your team will use it daily as a working tool
• It has to talk to other systems — accounting, calendars, payment providers
• Performance and search visibility are commercially critical

The old objection to bespoke was time and cost. That has genuinely changed. AI-assisted development — writing code with models rather than only by hand — has compressed the boring middle of a build: scaffolding, forms, admin screens, tests, migrations. It does not replace engineering judgement, and anything shipped without review is a liability. But used by people who can read what it produces, it means a bespoke platform now lands in the timeframe a heavy WordPress build used to take.

The comparison, plainly

The expensive mistake

The costly path is not choosing wrong once. It is choosing a builder for something that was always going to need logic, spending two years bending it, then rebuilding from scratch anyway — and losing the search authority the old URLs had accumulated.

So the honest test is not "what do we need now?" It is "what will this be asked to do when it works?" If the answer involves data, users or money, build for that from the start.

How we decide with clients

We ask what the content really is, who maintains it, what has to happen when someone interacts with it, and what the business plans to launch next. Then we recommend the cheapest option that will still be true in two years — sometimes that is Squarespace, and we will say so.

If you want that conversation about a specific project, book a meeting and we will scope it properly, including the option where you spend less.