What a bespoke website means, and when it is worth paying for

A bespoke website is designed and written for one business, from its own structure and its own code, instead of being fitted into a layout somebody else designed for a general audience. The pages exist because that business needs them, and the admin area holds the fields its staff actually fill in. Nothing has to be worked around because a theme does not allow it.

A template is a ready made design you fill with your content. It is quick and cheap, and the same layout is running on thousands of other sites. Changing anything structural means fighting the theme.

A page builder sits on top of a platform, WordPress most often, and lets you drag blocks around. The flexibility is real, but so is the weight: plugins to update, licences to renew, and performance that drops as the stack grows.

Bespoke starts with the structure rather than the layout. Somebody decides which pages exist, what each one has to achieve, and what the site has to connect to. Then it is built.

All three produce a website. What differs is what happens in year two, when you need something the original choice did not anticipate.

1. Which theme or template is this based on? A straight answer either way is fine; no answer is not.
2. Can you change the admin fields to match how we work, or do we adapt to the panel?
3. What has to keep being paid after launch for the site to stay online?
4. Who owns the code, the content and the admin access once the invoice is settled?
5. What happens if we want a feature the platform does not support?
6. Can you show a site you built for a business whose mechanics resemble ours?

If most answers are about which plugins will be installed, the quote is for assembly. That can still be the right purchase, but it should be priced as assembly.

Speed improves because the site loads what it needs and nothing else. A generic theme ships code for every use its author imagined, and most of it is not yours.

Security changes shape rather than disappearing. There is no popular plugin stack for everybody to scan, but the code still has to be maintained.

Updates are the real difference. On a bespoke build, adding a service, a field or a step means changing that thing. On a template, it means checking whether the theme permits it and what breaks when the theme updates.

When the site is one page with your name, a phone number and a photograph. Pay for a template.

When the budget only covers the build and nothing afterwards. A bespoke site with nobody maintaining it ages faster than a template that updates itself.

When the deadline is next week. Bespoke needs a brief, decisions and approvals, and those take calendar time even when the work is quick.

When nobody on your side can decide what the site is for. No amount of development fixes an unwritten brief.

Bespoke is the top of the three price levels, and the gap is work rather than badge value. Someone researches, structures, designs, writes and tests instead of installing.

We publish our prices in euro because that is the currency we invoice in: a presentation site starts at €29 a month, an online shop at €59 a month, and the setup and any bespoke build are quoted at a fixed price. We have not converted those into pounds here, because a rate invented for an article is worse than no figure at all. Nothing is added on top of those figures.

The detailed breakdown by project type sits on our page about website design cost in the UK.

The code, the content, the domain and every admin credential, all yours once the project is paid. You can take the lot to another supplier without asking us.

An admin area you can use without ringing anyone, plus a written guide and a call to walk through it.

The measurement setup, and the technical groundwork: titles, descriptions, structured data, sitemap and redirects from the old addresses.

Related pages: bespoke build compared with WordPress