Custom Website Redesign Powered by Generative AI

Four things sold as custom

A template with your branding applied. A template substantially restructured. A bespoke design built on a standard platform. And a fully bespoke site with its own design system and codebase.

All four are described as custom by someone. The price range across them is enormous and so is the maintenance profile.

When comparing quotes, establish which of the four is being offered. It explains most price differences in this market, and buyers frequently compare a restyled template against a bespoke build without realising they are different purchases.

What custom genuinely buys

Fit, primarily. A template imposes a structure and your content adapts to it — which works when your content resembles what the template expected and produces awkward compromises when it does not. Three services where it expects six; a product that needs an explanation the layout has no room for.

It also buys distinctiveness, which matters if your positioning is partly aesthetic, and it buys the absence of constraints you did not choose.

What it does not automatically buy is quality. A poorly executed bespoke site is worse than a well-chosen template, and that combination is common.

The ongoing cost nobody quotes

Custom sites carry a maintenance profile that is rarely discussed at the point of sale.

Nobody else knows how it works. Changes require someone who understands the specific implementation, and if that was one contractor who has moved on, ordinary edits become investigations. There is no community, no documentation, and no plugin ecosystem — every requirement is built.

A template site can usually be handed to any competent developer familiar with the platform. That difference compounds over years and is frequently larger than the original price gap.

When custom is the right call

Genuinely unusual content or functionality that no template anticipates — a configurator, an unusual catalogue structure, a data-driven interface.

When design is part of the product. A studio, a brand whose positioning is aesthetic, anything where looking like other sites is a competitive problem.

At sufficient scale, where the efficiency of a system built exactly for your content outweighs the maintenance overhead.

Outside those, the honest answer is that most businesses are well served by a good template applied thoughtfully, and much of what is sold as custom is a template with a premium attached.

The middle path most sites should take

A standard platform with a custom presentation layer.

You keep the maintainability, the ecosystem and the pool of people who can work on it, and you get a design fitted to your content rather than one you adapt to. This is what most "custom" projects actually deliver, and it is usually the right answer even when it is not what was promised.

Generation fits this pattern well: it produces a presentation layer specific to your content without a bespoke codebase underneath it, which is the expensive and hard-to-maintain part.

• Establish which of the four — before comparing any two quotes.
• Ask who else can maintain it — if the answer is one person, price that in.
• Check for a platform lock — can you move it, and at what cost?
• Prefer custom presentation — over a custom codebase, unless functionality demands it.

The question to ask a supplier

"What exactly is custom about this, and who else could maintain it?"

The first half establishes which of the four you are buying. The second establishes your exposure — whether you are acquiring a site or a relationship you cannot leave.

A good supplier answers both directly. Evasion on the second is the more informative signal, because it usually means the answer is nobody.