What 'Bespoke' Actually Means for a Website in 2026

If you’ve been quoted for a “bespoke website” in 2026, that word is doing a lot of work. Fifteen years ago, “bespoke” meant one thing: a developer wrote the site by hand. There was no other way to deliver something that looked custom. By 2026 there are four very different ways to put a site together that all credibly call themselves “bespoke” — and the differences only show up later, once your business grows past the original brief.

The four questions every quote should answer

Before getting into the categories, here are the questions worth asking any builder, whichever way they’re going to build it. They’re the spine of the rest of this post — every category section below ends with how it answers each one.

1. Can I move this site later? If you ever change builder, host, or platform, can the website travel with you, or would you need to rebuild from scratch?
2. What happens if I stop paying? Do you keep the website (the code, the content, the customer data), or does it go offline the day the direct debit fails?
3. Can someone else maintain it after you? If your current developer is unavailable in two years — gone quiet, retired, moved on — can another developer pick it up, or is the build only legible to one person or one platform?
4. Is there a hidden monthly fee? Hosting, content updates, software the builder is reselling at a markup, or something less defined — and is it on the same page as the build price, or buried in a separate FAQ or care-plan page? Deep dive on this one in Before You Accept a Website Quote, Ask About the Monthly Fee.

A reputable builder will answer all four plainly, in a single conversation, before you sign. The categories below explain how each kind of build sits on those four questions.

Why one word stopped being enough

In 2010, you couldn’t make a website that looked unique without writing code. WordPress was the only widely-used CMS and most sites that got built sat on a paid theme that thousands of other businesses were also using.

That’s no longer true. Visual builders, AI-assisted platforms, and modern page-builder ecosystems have all caught up to the point where a non-developer can produce something that genuinely looks one-of-a-kind. The visual outcome stopped being the differentiator. What separates the categories now is what’s underneath, and how each one answers the four questions above.

A useful analogy: a platform-built site is a bit like renting a fitted shop unit — quick to move into, but you work within the landlord’s rules. A coded site is closer to owning the fit-out — more effort upfront, but it can move with you later.

The four categories, ranked roughly by how much actual code is being written:

1. Built from scratch in code (the “static-coded” approach)

A developer writes the site by hand. The pages are built once and served as plain HTML files from fast servers around the world. No platform editor sits in the middle.

• Frameworks you might see in a developer-led quote: Astro, Next.js, 11ty, SvelteKit, Hugo. Most small-business buyers won’t see these names — the conversation usually stays at “custom build vs template-based” level.
• Hosting: anywhere. Cloudflare Pages, AWS, Netlify, Vercel — the site is portable.
• Pros: fastest possible page loads (no platform behind it); strong technical foundation for search ranking; full control over behaviour; the source code lives in a git repo you own.
• Cons: every change goes through a developer unless a content management system is added on top; small typo fixes feel slower than typing into a visual editor; higher upfront cost for the same surface look as a builder-based site.
• What it costs to build: roughly £600–£3,000 at the small-business end depending on scope.
• When it fits: brochure or business sites where speed, search ranking, and ownership matter more than self-service editing. Mission-critical pages.

Quick answers to the four questions:

• Move it later? Yes — you own the source; host it anywhere.
• Stop paying? You keep everything (code, content, ownership of the domain).
• Maintainable by someone else? Yes — any developer can read the code and pick it up.
• Monthly fee? Hosting only — typically £5–£30/mo depending on tier.

2. Built on a modern website platform (Flock, Lovable; Webflow as a hybrid)

Visual editors where you drag and drop blocks to build a site that behaves more like an app than a traditional website. The site looks bespoke because the editor is flexible; what’s running underneath belongs to the platform, not you.

• Platform examples: Flock, Lovable, and the wave of AI-assisted site builders that emerged in 2024–2025. Webflow sits in this category by default but is a hybrid — paid Workspace plans support a static code export (HTML, CSS, JavaScript, assets), though per Webflow’s own docs the dynamic features (CMS, ecommerce, forms, search) don’t fully export. So the structural code is portable on paid plans; the dynamic features aren’t.
• Hosting: tied to the platform by default. Webflow is the exception — paid Workspace plans let you host the static export elsewhere (with the dynamic-feature caveat). Flock and Lovable are platform-only.
• Pros: very fast to launch — you can be live in days; designs often look modern out of the box; the AI assistance is real and useful.
• Cons: the browser has to download more to render the same page than a hand-coded equivalent, which slows things down on mobile data; how Google sees the site depends on the platform’s behind-the-scenes setup, which varies by provider; you’re locked into the platform’s hosting and pricing tiers; rebuilding is required to move elsewhere on Flock and Lovable.
• Two cost-structure points worth knowing: the builder is themselves a paying customer of the platform, so part of your monthly fee covers their platform subscription plus their margin on top — you’re effectively paying two providers for one site (the builder, plus the platform underneath). And AI-generated designs from the same platform often share visual DNA — “bespoke” sites from one provider can look more alike than the marketing suggests; it’s worth comparing several of the builder’s portfolio examples side-by-side to see whether each really has its own design language, or whether the same template shapes keep appearing.
• What it costs: build typically £400–£1,200; hosting £15–£40/mo on the platforms that publish their pricing. Year-1 totals often land at £600–£1,700 once both are added up.
• When it fits: businesses prioritising speed-to-launch over long-term ownership; marketing surfaces that won’t outlive the campaign; founders who want a working site this week and aren’t worried about year-3 lock-in.

Quick answers to the four questions:

• Move it later? Mostly no — Flock and Lovable lock you to the platform. Webflow paid plans give you a partial export.
• Stop paying? On Flock/Lovable the site usually goes offline. Webflow gives you the exported static files (without the dynamic features).
• Maintainable by someone else? Within the platform — anyone with the editor login can pick it up. Outside the platform, no.
• Monthly fee? Platform hosting + plan tier — £15–£40/mo, can’t be unbundled.

3. Built with a DIY website builder (Wix, Squarespace)

Hosted website-as-a-service. The visual editor and the hosting are bundled — you can’t separate them.

• Platform examples: Wix, Squarespace, Weebly, Shopify (for shops).
• Hosting: bundled, can’t be exported.
• Pros: cheapest entry point, very accessible if you’re starting solo, useful templates for restaurants, photographers, and portfolios.
• Cons: there’s a ceiling on how high the site can climb in search — the page tends to be heavier and the underlying structure isn’t optimised the same way as a custom build; locked in (export rarely works cleanly); plan tiers gate features (can’t take payments below a certain tier, can’t connect a custom domain below another).
• What it costs: £10–£30/mo on the public plans. Two years works out at roughly £240–£720, but you don’t own the build at the end of it.
• When it fits: hobby projects; very early-stage testing of a business idea; service businesses where ranking on Google isn’t load-bearing.

Quick answers to the four questions:

• Move it later? No — exports rarely work cleanly.
• Stop paying? Site goes offline; export is partial at best.
• Maintainable by someone else? Within the platform — anyone with a Wix/Squarespace login can edit it. Outside, no.
• Monthly fee? Bundled platform fee — £10–£30/mo. Hosting and editor are inseparable.

4. Built on WordPress with a page builder (Elementor, Divi)

WordPress core plus a plugin that lets you compose pages visually without writing code. About 40% of all websites are WordPress-based — this is the largest category by a wide margin.

• Platform examples: WordPress with Elementor, Divi, Beaver Builder, or WPBakery. Sometimes paired with a theme like Astra or GeneratePress.
• Hosting: anywhere — shared hosting (£3–£8/mo), managed WordPress hosts like WP Engine or Kinsta (£25–£50/mo), AWS, your own server.
• Pros: huge plugin ecosystem; you actually own the site (it’s portable to any host); admin panel is approachable for non-technical owners; mature content management system for frequent self-edits.
• Cons: page-builders ship more code than hand-written equivalents (so pages tend to be heavier); plugin updates can occasionally break things; switching to a different page-builder later usually means rebuilding the layouts.
• What it costs: £300–£2,000 build; £20–£50/mo hosting if you want managed maintenance, or £5/mo on shared hosting if you’re maintaining it yourself.
• When it fits: businesses that need a CMS for frequent self-edits, and have either an in-house person or an agency on retainer to keep WordPress and its plugins healthy.

Quick answers to the four questions:

• Move it later? Yes — you own the site files and database; any WordPress host can take them.
• Stop paying? You keep everything; you’d need to arrange new hosting.
• Maintainable by someone else? Yes, broadly — though heavily-customised page-builder layouts are easier for some developers than others to pick up.
• Monthly fee? Hosting + (optional) maintenance retainer. £5–£50/mo depending on who’s keeping the plugins healthy.

Quick comparison — same four questions, all four categories

	Built from scratch	Modern platform	DIY builder	WordPress + builder
Looks unique	yes	yes	yes (within templates)	yes
Coded for you	yes	partial	no	partial
Page size	lightest	heavy	medium-heavy	medium-heavy
Search-ranking ceiling	highest	platform-dependent	lowest	medium
Move hosts later	anywhere	platform only (Webflow: partial)	no	anywhere
Lock-in	low	high (Webflow: medium)	high	medium
Edit it yourself	needs CMS layer	yes	yes	yes
Maintainable by others	any developer	platform users only	platform users only	most WP developers

Speed and search-ranking ceiling are real differences, but they’re not the whole picture. Faster, lighter pages give Google a better technical foundation to work with — but content, competition, and local reputation still matter more than the build technology. A well-written, frequently-updated WordPress site will out-rank a thinly-written hand-coded one. The build category sets the ceiling; the work you put into the site sets where you land under that ceiling.

Which one fits your business?

Some honest filtering questions:

1. Will the site change weekly? A platform with a built-in editor (DIY builder, modern platform, or WordPress) saves developer time on routine edits.
2. Will you ever want to move providers? Built-from-scratch and WordPress travel; modern platform (mostly) and DIY builder don’t.
3. Do you have a developer or agency relationship? If yes, built-from-scratch is usually the cheapest over a 3–5 year horizon. If no, WordPress or a builder is more realistic.
4. Is the website mission-critical revenue, or marketing-only? Mission-critical pushes toward built-from-scratch or robust managed WordPress; marketing-only is comfortable on a modern platform or DIY builder.

There is no wrong category. There’s a wrong fit, and the wrong fit usually shows up around year 2 — when you need a feature your platform doesn’t support, or your hosting bill outgrows the original build cost, or your developer goes quiet and nobody else can pick the site up.

What if you can’t get a clear answer

Most builders will tell you which category they’re working in if you ask. But if you’re getting “everything is custom” or “we build bespoke websites” without specifics, here are buyer-side checks that don’t depend on the builder’s disclosure.

1. Run a free detection tool on their portfolio. BuiltWith.com or the Wappalyzer browser extension reveals what platform any site is built on in one click. Run it on a few of the builder’s published examples — you’ll see whether it’s WordPress, Webflow, Wix, Squarespace, a platform-built site, or a hand-coded build.

2. Look at the URL of staging or portfolio sites. Live URLs at *.webflow.io, *.flockcdn.com, *.lovable.app, *.wixsite.com, or *.squarespace.com are platform-bound — that’s the platform, even after a custom domain is connected on top. Many builders’ own portfolios still use the platform URL.

3. View the page source. Right-click any page → View Source. You don’t need to read code, just scan for clues. wp-content/ means WordPress; webflow or wf- class names are Webflow; one large JavaScript file that loads the whole site after the page first renders points to a platform builder; clean HTML with minimal JavaScript points to a hand-coded site.

4. Ask about AI in the design process. Many modern platforms (Flock, Lovable, most of the 2024–2025 AI-builder wave) generate the design and layout from a prompt — the design may be AI-generated or AI-assisted. That’s not a problem in itself; we use AI ourselves and have written about it in How we use AI to build better websites. The point is the buyer deserves to know whether a “bespoke design” was a human designer’s work, an AI prompt, or a mix. Sites built on the same platform from similar prompts also tend to share visual DNA — flashy and modern, but with a recognisable family resemblance once you compare the builder’s portfolio examples side-by-side.

5. Ask about portability in writing. “If we part ways in 12 months, can I download the website’s source code and database, and is there anything I’d need to rebuild?” The answer — and how readily it’s put in writing — tells you which category they’re operating in better than any framework name.

If a builder won’t engage with most of these, that’s information.

What we build at GrantOps

Brochure and business sites at GrantOps are built from scratch in code, hosted on AWS. We chose that because brochure and business sites tend to get built once and need to perform for years; the maintenance overhead of a page-builder isn’t worth it at that tier, and the speed and ownership benefits compound for the whole life of the site.

For online shops, we use WordPress with WooCommerce when self-service catalogue management matters (it usually does on a shop) — same hosting, different tooling, same ownership.

If you’d like the Year-1 maths behind website quotes with required monthly fees — where the headline price is only part of the story — we’ve laid that out separately in Before you accept a website quote, ask about the monthly fee. Or for a broader cost survey across the Scottish market, How much does a website cost in Scotland.

View packages or get a free quote.

Frequently asked questions

What does 'bespoke' actually mean for a website in 2026?

Almost every modern platform — Wix, Squarespace, Webflow, Flock, Lovable, and WordPress with Elementor or Divi — can give you a layout that looks unique to your business. What changes between them is how the site's actually built underneath, and what happens when you outgrow the platform or stop paying. The four questions every quote should answer: can I move this site later, what happens if I stop paying, can someone else maintain it, and is there a hidden monthly fee.

Is a Wix or Squarespace site bespoke?

It can look unique — yes. But you don't own the build: the editor and the hosting are bundled, and exporting the site rarely works cleanly. That's not a flaw at the hobby or early-stage tier, but it caps how far you can take the site without rebuilding somewhere else.

Is WordPress with Elementor or Divi bespoke?

Partially. The page-builder lets you compose unique layouts, and you actually own the site (you can move it to any host). But the page-builder ships more code than a hand-written equivalent, and switching to a different builder later usually means rebuilding the layouts.

Why does the difference between these categories matter?

Three things, in plain terms. First, can you move the site later if you change builder or platform. Second, what happens to the site if you stop paying. Third, who else can pick it up and maintain it if your current developer goes quiet. Faster, lighter pages also give Google a better technical foundation to work with — but content, competition, and local reputation still matter more than the build technology.

How can I tell which type a builder is selling me?

Ask the four questions in this post: (1) Can I move this site later? (2) What happens if I stop paying? (3) Can someone else maintain it after you? (4) Is there a hidden monthly fee? The answers, plus the platform name (Wix, Squarespace, Webflow, Flock, Lovable, WordPress + Elementor/Divi, or hand-coded by a developer), tell you what's actually on the table. If a builder won't name the platform, free tools like BuiltWith.com or the Wappalyzer browser extension reveal what any site is built on in one click — run them on the builder's portfolio examples.

Was my website designed by a human or by AI?

Worth asking your builder directly. Many modern platforms (Flock, Lovable, most of the AI-builder wave) generate the design and layout from a prompt — the design may be AI-generated or AI-assisted. Sites built on the same platform from similar prompts also tend to share visual DNA, so 'bespoke' sites from one provider can look more alike than the marketing suggests. That's not a problem in itself, but the buyer deserves to know whether a 'bespoke design' was human-led, AI-led, or a mix. We use AI in our own process and have written about it in 'How we use AI to build better websites' — the design direction and content choices stay human-led; AI helps at specific implementation steps.