Most people asking "custom website vs WordPress" are really asking a different question: how do I avoid paying for something I do not need, or building something I will regret in a year?

We build all three approaches, so we have no reason to push you towards one. Below is how we actually decide, based on what a project needs to do rather than what is fashionable.

The three options, defined properly

The words get muddled, so let us be precise.

Template. You buy a pre-built design (Squarespace, Wix, a Webflow template, a WordPress theme) and pour your content into it. You are editing within fixed rails. Fast and cheap to start.

WordPress. A content management system that runs a large share of the web. It can mean a themed site with plugins, or a heavily customised build. "WordPress" covers a huge range, from a £500 template job to a bespoke platform, so treat the word with suspicion when someone quotes it.

Custom website. Designed and built specifically for you, usually on modern frameworks, with a content editor chosen to fit your team rather than the other way round. Every decision serves your goals.

The honest truth is that the boundary between "WordPress" and "template" is blurry, and the boundary between "custom WordPress" and "custom build" is blurry too. What matters is the trade-offs underneath.

When a template is the right call

We genuinely recommend templates more often than you might expect. Reach for one when:

• You need a presence live this month and cash is tight.
• The site is a brochure: a few pages, occasional edits, no complex functionality.
• You are testing an idea and do not yet know what the business will become.
• Nobody on your team wants to touch code, and you want to edit everything yourself.

A well-chosen template on Squarespace or Webflow can look clean and load quickly. The trap is outgrowing it. Templates fight back the moment you want something they were not designed for: a booking flow, a members area, a specific integration with your CRM. You end up bolting on tools that do not quite fit, and the whole thing gets brittle.

If you are early and unsure, start with a template and treat it as a deliberately temporary decision.

When WordPress makes sense

WordPress earns its place when content is the point. If you publish often, run a blog with many authors, or need a large library of pages with editorial workflow, the content tooling is mature and familiar.

It is also sensible when you want a big ecosystem of plugins for a specific job, or when you will hand the site to a marketing team who already know the admin screens.

But WordPress has a cost that quotes rarely mention: maintenance. Plugins update, sometimes conflict, and occasionally introduce security holes. A WordPress site is a garden that needs weeding. If nobody is responsible for updates, backups, and security, you are one abandoned plugin away from a defaced homepage or a slow, bloated site.

So choose WordPress with your eyes open. It is a strong content platform, not a set-and-forget one.

When a custom website is worth it

Custom is the right choice when the website is doing real work, not just describing your business.

We reach for a custom build when a project involves:

• Functionality no template offers cleanly: a quoting tool, a portal, a calculator, a bespoke booking system.
• Performance that genuinely affects revenue, where every second of load time costs conversions.
• A design that has to be distinctive because the brand is a differentiator.
• Integrations with your own systems that need to be reliable rather than duct-taped.
• A plan to grow the site over years, where a solid foundation saves money later.

The advantage of custom is that nothing is fighting you. There is no theme to override, no plugin doing 80 per cent of what you need. The code does exactly one job: yours. That tends to mean faster pages, fewer security surfaces, and cleaner accessibility, because you controlled every decision.

The cost is higher up front and you need a partner to maintain it. But for a site that is central to how you win customers, that is the point. This is the kind of work our engineering team exists for.

The comparison that actually matters

Forget feature checklists. Judge the three options against four questions.

Speed to launch. Template wins, WordPress is middling, custom is slowest. If launch date is everything, that ranking decides it.

Total cost over three years. A template looks cheapest until you outgrow it and rebuild. WordPress has ongoing maintenance. Custom costs more day one but often the least across three years if the site is core to the business. Cheap and rebuilt-twice is not cheap.

Performance and Google. A lean custom build usually wins on Core Web Vitals, and that feeds directly into rankings and conversions. Heavy WordPress installs with a dozen plugins are the usual culprits behind slow sites. If organic traffic matters, this is not a small detail.

Flexibility as you grow. Custom bends to you. Templates make you bend to them. WordPress sits in between, flexible until a plugin decides otherwise.

How we actually decide with clients

We start with the job, not the technology. We ask what the site has to achieve in twelve months, who will edit it, what it has to connect to, and how much traffic depends on speed and search.

If the honest answer is "a smart brochure that we barely touch," we will not sell you a custom platform. If the answer is "this is how we generate and convert leads and it will grow every quarter," a bargain template is a false economy.

A useful gut check: if your website going down for a day would cost you real money, you probably want something built and maintained properly. If it would be a mild inconvenience, a template is fine.

It also pays to understand why a site fails to earn its keep in the first place, which is often about strategy rather than platform. Our take on why a website isn't generating leads covers that ground.

Our recommendation

Do not start from the tool. Start from the decision above, then pick the cheapest option that comfortably meets it, with a little room to grow.

For most small businesses testing the water, a template is a sensible first step. For content-heavy publishers, WordPress with a proper maintenance plan works well. For anything where the website is a core commercial asset, custom pays for itself.

And if you are genuinely unsure, ask a studio that builds all three to tell you the honest answer. If someone only sells one, that is the answer you will get regardless of what you need. You can see how we approach website projects and where each option fits.

Signed, Lewis, Technical Director.