Website Template or Tailored Delivery for a Small Business?

Neither a website template nor a tailored build is automatically the better choice for a small business. The right route is the smallest one that can accurately explain the offer, support the required customer journey and be tested against clear standards.

The label on the proposal is weak evidence. A template can be carefully adapted, fast and effective. It can also be overloaded, generic or difficult to change. A tailored build can solve an unusual problem well. It can also spend time and budget on visual novelty while leaving basic content, accessibility or performance unresolved.

A more useful decision is: which parts of this website genuinely need to be tailored, and how will the supplier prove that the finished site works?

First, separate three different delivery routes

“Template website” can describe several different products. Ask the supplier which of these it actually means.

Self-serve template

You choose a theme or site-builder layout and supply most of the planning, copy, images, configuration and testing yourself. This can suit a new business with one straightforward offer, limited evidence and someone who has time to learn and maintain the platform.

The subscription price is not the complete cost. Your time, paid extensions, premium assets, domain, support and future changes still matter. Confirm which capabilities remain available if you change plan or provider.

Template-led professional delivery

A supplier starts with a proven design or code system, then adapts the structure, identity, content and customer journey to the business. Reuse can reduce avoidable design and engineering work, but the result is only genuinely tailored where the important decisions respond to this business rather than to placeholder content.

Ask what is fixed, what is configurable and what will be created for you. Replacing a logo and colours is different from restructuring services, writing accurate copy, selecting genuine proof and testing a complete enquiry journey.

Bespoke delivery

The supplier defines the information architecture, design system and functionality around a written brief. This route can make sense when the business has distinct audiences, complex content, unusual interactions, specialist integrations or a strong art-direction requirement that a reusable system cannot meet cleanly.

Bespoke should describe the work and decisions included, not act as a synonym for “premium”. A familiar layout may still be the clearest solution. Custom code is not evidence that the final page is accessible, fast or easy to operate.

Compare the outcome across five tests

Use the same tests for every proposal, regardless of how the site will be built.

Test	What to establish before choosing
Fit	Can the route support the real services, audiences, evidence and enquiry steps without forcing them into the wrong structure?
Accessibility	Who will test the complete responsive experience, with keyboard and human checks as well as automated tools?
Performance	What will be measured on representative mobile pages, and who fixes problems caused by images, scripts or interactions?
Ownership and exit	Who owns the domain, supplied content, design and code; what is licensed; and what happens if the agreement ends?
Operating fit	Who can update the site, what changes cost, and which external services or subscriptions must be maintained?

The route that answers those questions clearly is usually safer than the one with the most impressive label.

1. Choose for content fit, not visual novelty

Start with the decisions a suitable customer needs to make. A focused business may need one clear page covering its offer, service area, genuine proof, process and contact route. Another may need separate pages because its services, audiences, eligibility rules or evidence are materially different.

A reusable system is a sensible fit when it can accommodate that information without distortion. Warning signs include:

• important services reduced to identical cards with no useful explanation;
• a forced section order that hides the next step;
• placeholder statistics, testimonials or badges the business cannot substantiate;
• near-duplicate pages created only to fill a navigation menu; and
• a contact component that collects the wrong information or has no reliable delivery process.

Tailored delivery earns its cost when it resolves a real constraint. Examples include different enquiry routes for distinct audiences, substantial technical content, permissioned case-study structures, complex product selection or an integration that changes the customer journey. “We want to look different” is a useful creative ambition, but it is not a complete functional brief.

Write the required content and actions before approving a visual direction. That makes it easier to see whether a template fits the business or whether the business is being squeezed into the template.

2. Treat accessibility as a tested result

The Web Content Accessibility Guidelines (WCAG) 2.2 are written as testable, technology-neutral success criteria. They apply to the web content people actually use, not to whether a supplier started from a theme, a component library or a blank file.

W3C also makes clear that conformance concerns complete pages and includes responsive variations. A desktop screenshot or an automated score cannot prove the whole customer journey works.

Ask how the supplier will check:

• page structure, headings and meaningful link text;
• text alternatives for informative images;
• keyboard navigation and visible focus;
• colour contrast and content at zoom;
• labelled inputs, error messages and confirmations;
• menus, accordions and dialogs without a mouse; and
• the complete journey at common phone widths.

A mature template may begin with good patterns, but later colour, content and plugin changes can introduce barriers. A bespoke interface may have more freedom, but every novel interaction needs careful implementation and testing. Neither route inherits accessibility from its description.

3. Measure the page customers receive

Performance claims should refer to the finished website with its real images, fonts, analytics and interactions. A fast empty demonstration does not prove the completed site will stay fast, and a custom build is not automatically lighter than a template.

web.dev's business guidance on Core Web Vitals describes three different aspects of user experience: loading performance through Largest Contentful Paint, visual stability through Cumulative Layout Shift, and interaction responsiveness through Interaction to Next Paint. It also explains that field results come from real users whose devices, networks and visited pages vary.

Before signing off, agree which representative pages and devices will be tested. Ask the supplier to account for large hero media, third-party widgets, consent tools, tracking scripts, fonts and anything added after the initial build. A reusable system with disciplined asset delivery may outperform an undisciplined bespoke site; a lean tailored build may outperform an overloaded site-builder theme. Test the outcome.

Do not turn one performance score into a ranking or sales promise. Speed is one part of a usable experience, not proof that Google will rank the site or that a visitor will become an enquiry.

4. Put ownership, licences and exit terms in writing

Paying for a commissioned website does not by itself answer who owns every part. The UK Intellectual Property Office's copyright guidance says the creator is generally the first owner of a commissioned copyright work unless a different arrangement is agreed in writing. Where a contract is silent, a commissioner may have only an implied, limited licence rather than ownership.

This is general guidance, not legal advice, and websites can combine several rights and licences. Ask for written terms covering:

• the domain account and DNS access;
• business-supplied copy, logos, photography and data;
• the website design and source code;
• reusable supplier systems or licensed templates;
• fonts, stock media, plugins and other third-party assets;
• access to analytics and other service accounts;
• whether the site can be moved; and
• what remains available after cancellation or handover.

Template-led delivery often depends on platform or theme licences. Bespoke work may still use open-source packages, licensed fonts, stock media and reusable supplier components. “Custom” does not mean every underlying element transfers to the customer, while “template” does not mean the business lacks rights to its own domain, content or data. The written agreement should distinguish them.

5. Match the site to the way the business will operate it

The initial build is only one part of the decision. Decide who will update prices, services, opening hours, team information and proof after launch. Confirm who manages hosting, backups, security updates and failed integrations, but keep those responsibilities separate from vague promises of “ongoing support”.

A self-managed template can be appropriate when someone in the business has time, access and a clear publishing process. Managed delivery can be more suitable when the business wants one accountable route for changes and maintenance. Bespoke functionality needs an owner and a realistic support route; otherwise the feature that justified the build can become the hardest part to maintain.

Ask for the cost and process for a small text edit, a new section, a new page and a new integration. Those are different kinds of work. A low starting price can become a poor fit if common changes are blocked, while a larger build can be wasteful if the business will never use its flexibility.

When each route is likely to fit

A self-serve template may fit when

• the offer and customer journey are simple;
• the business has usable copy and genuine images or proof;
• no specialist integration is required;
• someone can learn, test and maintain the platform; and
• accepting the platform's structure and ongoing terms is reasonable.

Template-led professional delivery may fit when

• the underlying layout pattern suits the business;
• professional planning, copy, adaptation and launch support are still needed;
• speed and budget predictability matter;
• the proposal identifies what will be tailored; and
• the finished site will receive full accessibility, performance and enquiry testing.

Bespoke delivery may fit when

• distinct audiences or services need a new information structure;
• the customer journey cannot be handled cleanly by the available system;
• original interaction or art direction has a defined business purpose;
• integrations or technical constraints are understood before design begins; and
• the budget covers testing, documentation and ongoing support as well as creation.

These are selection clues, not rules. A careful discovery process may show that only one part of the website needs custom treatment while the rest can reuse established patterns.

How Novas describes its current routes

Novas uses explicit scopes rather than claiming every project needs the same level of custom work:

• Starter: a professionally designed, tailored but template-led one-page website with up to six sections, currently £499 as a limited-time launch price.
• Growth: up to six pages including the homepage, from £1,495.
• Signature: a bespoke scope agreed in the written proposal, from £3,495, with no public page cap.

Those are current Novas prices, not UK market averages. Each package includes responsive design, copywriting within the agreed scope, enquiry or contact routes, basic launch SEO, analytics setup where access is provided, domain connection and launch, and licensed stock imagery where suitable client images are unavailable. The package and proposal still need to state the exact pages, revisions, responsibilities, exclusions and commercial terms.

The useful Novas question is not “template or custom?” in isolation. It is what is the smallest complete delivery scope that fits the business and can be evidenced at launch?

A quote checklist that exposes the real difference

Ask every supplier to answer these questions in writing:

1. Which parts of the structure and design are reused, configured or created for this business?
2. What copy, imagery, proof and business information are included?
3. Which pages, sections, forms and integrations will be delivered?
4. How will responsive, keyboard, accessibility and performance testing be evidenced?
5. What happens when a form, booking route or external service fails?
6. Which accounts, assets and intellectual-property rights belong to each party?
7. Which licences, subscriptions or platform limits continue after launch?
8. How can the site be changed, moved or ended, and what would that cost?
9. Who maintains the operational and security responsibilities?
10. Which desired features are deliberately outside the current scope?

You can compare the current Novas website packages, see how delivery is structured, inspect the clearly labelled concept portfolio, and review the editorial evidence policy. If the required outcome is clear, send a project outline for a written scope. That conversation does not guarantee rankings, traffic, calls or enquiries.

Source ledger

• Web Content Accessibility Guidelines (WCAG) 2.2, World Wide Web Consortium, accessed 14 August 2026 — used for the technology-neutral, testable nature of the criteria and the need to assess complete pages, including responsive variations.
• Optimize Core Web Vitals for business decision makers, web.dev, accessed 14 August 2026 — used for the definitions of LCP, CLS and INP and the distinction between real-user field experience across devices, networks and pages.
• Ownership of copyright works, UK Intellectual Property Office, accessed 14 August 2026 — used for the general commissioned-work ownership and written-agreement guidance. It is not a substitute for legal advice on a specific contract.