Key Takeaways
- Choose from customer tasks and operating constraints, not the word bespoke.
- A template can support a serious business; custom development should solve a specific limitation.
- Compare content, maintenance, licences and migration as well as the initial build.
- Check the actual site's accessibility, speed and search setup: neither approach guarantees rankings.
A custom website and a template are two ways of delivering a customer experience, not two levels of business ambition. A well-chosen template can be a sensible long-term platform. A bespoke build can be valuable when the business needs a different journey, integration or content model. Either can fail if the brief is unclear.
This guide is for a UK business comparing proposals, planning a first site or deciding whether to replace its current one. It focuses on what you will buy, operate and be able to change. If your question is specifically about generating a website with AI, read the separate AI builder versus developer guide.
Start with the work the website must do
Write down three tasks a customer must complete. A consultancy might need visitors to identify a suitable service, assess a relevant case study and request a conversation. A retailer may need product filtering, delivery information and checkout. A membership organisation might need event booking, account access and renewals.
Then identify what the team must do behind the scenes: edit prices, add projects, process orders or pass enquiries to a CRM. These tasks become acceptance tests. Ask each supplier to demonstrate them using representative content, not an empty theme demonstration.
Separate an actual requirement from a preference. An unusual animated menu is a preference unless it solves an observed problem. A reliable stock integration may be a requirement. Making that distinction protects the budget and prevents a visual decision from becoming unnecessary software development.
What the three common routes involve
| Route | What is being adapted or built | Useful when | What to check |
|---|---|---|---|
| Hosted builder and template | Platform features and existing layouts | Your content and journeys fit the platform | Export options, plan limits and integrations |
| Professionally adapted CMS theme | An existing theme configured around your brief | You need tailored content and professional delivery without a new theme | Theme dependencies, editing and maintenance |
| Custom theme or application | Layouts, components and selected behaviour built for the brief | Required journeys or integrations do not fit the other routes | Scope, documentation, handover and support |
These routes overlap. A developer can build on a hosted platform; a custom WordPress theme still depends on WordPress and other software. Ask what is custom, what is reused and what is licensed. Those answers are more useful than a proposal that simply labels the whole site bespoke.
Two projects that show why the brief matters
For Liz Patey Makeup, we replaced an off-the-shelf theme with a custom-coded WordPress theme while preserving a photography-led presentation. The relevant problem was how to support a premium visual portfolio, distinct services and responsive layouts within an editable site.
For GTS Reading, the work was a theme-based WordPress redesign with service, industry and fleet content and a quote journey. That brief needed a clearer structure for a broad logistics offer. It did not require us to describe the implementation as a custom theme.
Both are website deliveries, not evidence that one route always generates more revenue. The case studies document what was built. When evaluating your own options, identify which problem resembles yours and ask how the proposed approach resolves it.
Compare the full cost, not just the launch invoice
Request a like-for-like three-year cost schedule. Include discovery, design, content preparation, development, migration, testing and training. Then include hosting, platform subscriptions, domain renewal, paid extensions, maintenance and likely changes. Confirm whether each figure includes VAT and whether the quotation assumes you supply final copy and images.
A cheaper initial build can become expensive if ordinary changes repeatedly require outside help. A more expensive build can also be wasteful if it introduces technical complexity the business does not need. There is no reliable universal payback period for either route.
Use a simple comparison: initial delivery cost plus recurring costs over the chosen period plus an allowance for planned changes. Keep optional SEO campaigns or advertising separate from the platform's running costs. Otherwise one quote may appear more expensive simply because it includes more ongoing work.
Ask for examples of future change costs: adding a service, changing a booking provider, creating a new page type or moving the site. These are scenarios to price, not predictions that every change will be necessary. A supplier who can explain the assumptions makes the comparison easier.
Check ownership and the exit route in writing
Custom does not automatically mean that you exclusively own every line of code. Software, stock images, typefaces, themes and third-party integrations can carry their own licences. WordPress explains its GPL licence; your project's contract still needs to explain the deliverables and rights you receive.
Confirm who controls the domain registration, hosting account, analytics property and content. Ask whether you receive source files, a repository, editable design assets, database exports and deployment instructions where applicable. Check what stops working if an agency subscription or support agreement ends.
For a hosted platform, investigate what can be exported and what would need rebuilding elsewhere. For a custom application, ask whether another competent developer could maintain it. A theoretical right to move is less useful without documentation, account access and a workable handover.
Make editing a demonstration, not a promise
Ask to add a service and change a photograph during a demonstration. Can an editor preview the result, provide image descriptions and recover a previous version? Can they accidentally damage navigation or duplicate important search settings? What permissions will different team members have?
Do not confuse unlimited layout control with a better editing experience. A constrained set of well-designed components can help a small team publish consistently. Equally, a rigid template can be frustrating if ordinary content does not fit. The right balance depends on what your team updates and how often.
Include training and a short written guide in the handover. Name an internal content owner. A technically editable website will still become stale if nobody is responsible for checking services, prices, project information and enquiry routes.
Test performance and accessibility on the actual pages
Neither a framework name nor a template label proves speed. Images, scripts, hosting, caching and implementation choices all affect the result. Web Vitals describe loading, responsiveness and visual stability; check representative pages rather than treating one homepage score as the entire website.
Test the site with a keyboard and on a phone. Open the menu, read the service information, complete a form and correct an error. Check that images are readable without forcing visitors to download unnecessarily large files. Your acceptance criteria should describe observable behaviour, not simply request a modern website.
If an existing WordPress site is slow, first identify the bottleneck. The WordPress speed guide explains a staged approach. Rebuilding is one possible response, not the first diagnosis.
Protect existing content when changing platforms
Before a migration, inventory current URLs, search performance, useful inbound links and downloadable files. Keep valuable pages at their current addresses where practical. When a URL must change, map it to the closest relevant replacement and test the redirect.
Google's site-move guidance covers URL mapping, redirects and monitoring. Treat migration as a separately tested workstream, not a switch made after the design is approved. A new sitemap cannot compensate for lost content or inappropriate redirects.
Also test form delivery, consent behaviour, analytics and integrations after launch. A visually successful migration can still lose enquiries if submissions go to the wrong inbox or measurement breaks. Compare complete periods and keep a dated change record so later performance reviews have context.
A practical decision meeting
Bring the customer tasks, editing needs, integration requirements and cost comparison into one meeting. Ask the supplier to identify what their proposed route cannot do without additional work. Discuss which limitations are acceptable now and which would block the business.
Choose the least complicated approach that reliably meets the agreed brief. If a template fits, invest the remaining budget in strong copy, photography, proof and testing. If it does not, specify the custom work precisely and keep a separate list of later enhancements.
At MattDarm, custom website design starts with that assessment. If you already use WordPress, our WordPress development service can examine whether to improve the current site or rebuild. Send us your brief with the tasks the website needs to support, and we can discuss the trade-offs without assuming the most expensive route is the right one.
Frequently Asked Questions
Can a template website rank well on Google?
Yes. A template is not a ranking disqualification. Assess the site's useful content, crawlability, internal links, performance and relevant external signals rather than assuming a custom build will rank better.
Does custom development mean I own everything?
Not automatically. Your contract and the licences for software, images and fonts determine the rights you receive. Confirm source access, account control and the handover before commissioning work.
When is a custom website worth considering?
When important customer journeys, content structures or integrations cannot be delivered satisfactorily with the simpler alternatives. Ask the supplier to show the specific limitation and the proposed solution.
Can I keep WordPress and change the theme?
Often, yes. Audit the content and any theme-dependent functionality first, then test the replacement on staging. Preserve valuable URLs and verify forms, editing and search settings before release.
How should I compare quotations?
Use the same requirements and time period. Compare delivery, content, migration, licences, hosting, maintenance and likely changes, and confirm VAT and exclusions. The initial build price is only part of the decision.
