Choose for fit, not for the label on the proposal.
A bespoke website is shaped around a particular business, audience and content system. A template website starts from an existing layout or component structure and adapts it. A page builder gives a business or provider a visual system for assembling pages with less custom development.
Any of those routes can be executed carefully or poorly. The useful question is whether the approach supports the decisions that make your website valuable: how the offer is explained, how people move towards enquiry, how content is managed, how integrations work and what happens when the business changes.
Is a bespoke website always better than a template website?
No. A bespoke website is more appropriate when the brand, content structure, customer journey or functionality cannot be served well by a standard pattern. A well-chosen and carefully adapted template can be the stronger decision for a straightforward site with limited requirements. The weaker choice is paying for custom work without a custom need, or forcing a distinctive business into a layout that cannot support it.
Understand what each route actually means.
Terms such as bespoke, custom and template are used loosely. Ask what will be designed, what will be reused and what you will be able to change after launch.
Page builder website
Pages are assembled inside a visual platform from supplied sections and controls. This can reduce development time and make routine editing accessible, but the platform, available components and quality of the implementation set real boundaries.
Adapted template
An established theme or layout provides the starting structure, then colours, type, imagery and content are changed. It can suit a familiar brochure-site brief, provided the result is tested and does not pretend that surface changes remove structural limits.
Bespoke interface system
The page hierarchy, content modules, navigation and visual system are designed around the business. Reusable components still matter, but they are selected and configured to support this particular offer rather than inherited from an unrelated demo.
Custom functionality
A website may also need calculators, account areas, booking flows, structured directories or integrations. That is a separate scope decision from visual design and should be described in functional terms, including data, permissions and failure states.
Let the business requirements decide the level of custom work.
Start with the difference the website must create. A custom treatment is valuable where it protects meaning, usability or future flexibility.
How unusual is the buying journey?
A simple service enquiry can use familiar patterns. Multiple audiences, complex qualification, product configuration or a long consideration process may need a more deliberate route through evidence, detail and next actions.
How important is brand distinction?
If the website must establish a recognisable market position, inherited visual decisions can become a constraint. Bespoke art direction is useful when the brand needs a distinctive rhythm, hierarchy and interaction language rather than decorative novelty.
How structured is the content?
Case studies, locations, services, resources and team profiles often need repeatable content models. Decide whether editors need to create consistent entries, flexible landing pages or both, and test the proposed editing experience before committing.
What must connect to the site?
CRM systems, email tools, payments, booking platforms, stock, authentication and internal data can change the technical route. Confirm what data moves, which system owns it and how errors or outages will be handled.
Compare the work behind the headline price.
Two proposals can both say bespoke while including very different levels of thinking, production and responsibility. Make the scope visible before comparing totals.
Strategy and content structure
Check whether the work includes audience definition, page planning, navigation, content guidance and calls to action. A unique visual layer cannot rescue an unclear offer or an unresolved page structure.
Design depth
Ask which pages, components and responsive states will be designed. One polished desktop screen plus improvised inner pages is not the same deliverable as a complete interface system with mobile behaviour considered.
Technical quality and testing
Confirm the browsers, screen sizes, keyboard journeys, forms, performance risks and accessibility checks covered. The platform alone does not determine quality; implementation and verification do.
Ownership and ongoing cost
Record who owns the domain, content, design files and custom code, which licences renew, whether the site can move provider and what support is available after the initial launch period.
A practical decision framework.
Use these signals as prompts, not as an automatic score. A capable provider should be able to explain the trade-off for your own brief.
Straightforward offer and modest content
A carefully adapted system may be enough if it remains fast, accessible and easy to manage.
Distinctive positioning or complex story
A bespoke content and visual system is more likely to protect the message across the whole site.
Special workflows or integrations
Scope custom functionality separately and validate the riskiest technical assumptions before committing to a full build.
Frequent publishing by an internal team
Prioritise the content model, permissions, preview process and editor experience, not only the front-end appearance.
Very constrained first release
Reduce page count and functionality before reducing essential quality. Plan what can be added later without rebuilding the foundation.
Unclear future requirements
Choose an understandable architecture and ownership model. Do not pay for hypothetical complexity, but avoid a route that blocks likely change.
Choose the smallest approach that fully serves the brief.
Subtle Standard can help turn an unclear website requirement into a defined structure, interface system and build route before unnecessary complexity is added.
Website approach questions.
What is a bespoke website?
A bespoke website is planned and shaped around a specific business, its audience, content and required journeys. It usually uses reusable components and established technical tools, but the resulting structure and interface are not dictated by a generic demo. Bespoke should describe the fit of the system, not imply that every line of code must be invented from nothing.
Are template websites bad for SEO?
Not inherently. Search performance depends on accessible content, crawlable pages, useful titles, internal links, performance, mobile behaviour and many other implementation choices. A template can support those foundations or undermine them. The important step is to audit the actual output and avoid layouts that force duplicated, thin or poorly structured content.
Can a template website be made to look unique?
Yes, within the limits of its structure. Strong typography, imagery, content hierarchy and considered component choices can create a distinctive result. If the template fixes the most important page relationships or interaction patterns, visual customisation may only disguise the constraint. Review the least glamorous inner pages as well as the homepage before choosing.
How should I compare bespoke website quotes?
Compare the proposed outcome, pages, content work, design states, functionality, integrations, testing, migration, launch support, ownership and recurring costs. Ask each provider to identify exclusions and client responsibilities. A lower total may simply move important work to you or leave it undefined, while a higher total should be traceable to useful scope rather than vague quality claims.