When you are looking to have a business website built, a finished demo helps you picture the result. Yet an attractive opening screen does not show whether your services will fit, how the form will work or what a second language will require.
A useful question is how much work it will take to turn that foundation into your website. First assess both approaches against the same requirements, then compare proposals from developers.
The short answer: choose by the changes you need
An existing foundation is a good candidate when its pages and blocks already suit your offer, with changes mainly to content, colours and agreed details. Consider custom design if the navigation, most layouts or the enquiry journey would need to be rebuilt.
This is a separate decision from choosing a landing page or a multi-page website. If the format is still unclear, start with our comparison of business website formats. Both a small page and a company website can be designed individually or assembled from suitable existing solutions.
What are you buying when an offer says “ready-made website”?
A search for a ready-made website can lead to quite different offers. This comparison concerns a foundation for a new site, rather than buying an established business with a domain, visitors or orders. Before paying, clarify exactly what will be delivered.
- A design or page template. Starting materials that still need adaptation, content and working functionality.
- A website on a platform. A solution within a particular service. Check its editing rules, recurring payments and migration options.
- Adaptation and launch. A developer’s service that uses an existing foundation to deliver the agreed result on your domain.
A ready-made foundation does not necessarily mean a CMS, and a custom website does not mean writing every element from scratch. Even a bespoke site can use existing components. How content will be edited and how much design is customised are separate decisions.
How to compare a template and custom website development
Use the same list of services, languages and features. For each item, ask what already exists, what will be adapted and what needs additional development. This makes the comparison more useful than a polished mockup and a broad promise to handle everything.
| Criterion | Existing foundation | Custom design |
|---|---|---|
| Structure | Check whether the existing pages and block order fit | Plan pages and their sequence around the customer’s needs |
| Design and content | Try your copy, images and branding in the existing layout | Design the presentation around content and brand requirements |
| Functionality | Establish what works and what is only shown in the demo | Describe and estimate the required journeys before building them |
| Scope and timing | Depend on adaptation and the foundation’s limitations | Depend on planning, implementation and approvals |
| Later changes | Check how the required page or feature can be added | Agree which future changes to allow for in the first version |
Savings come from completed work that can actually be reused. If the foundation needs extensive changes, compare the full adaptation with designing the site separately. Our guide to website development cost explains how to compare the scope of an estimate.
When an existing foundation fits the brief
A service business may need a clear explanation of its offer, examples, answers and an enquiry form. If the foundation already supports that journey, there is no need to change every layout simply to make it different.
- Your services and content fit the existing structure without cutting important explanations.
- The design can be aligned with your brand through a defined set of changes.
- The form and enquiry delivery suit the team’s workflow or have a clear adaptation scope.
- The changes you expect to need next will not require rebuilding the foundation.
For example, when commissioning a landing page for one service, focus on whether the offer is complete and contacting you is straightforward. Your own photos, specific terms and accurate explanations matter whichever layout you start with.
When to commission a custom website
Custom development has a concrete purpose when an existing structure gets in the way of explaining your service or completing an important action. Ask the developer to demonstrate these limitations using your journeys, rather than simply proposing a unique design.
- Different customers need different explanations, supporting content and routes to enquiry.
- You need a specialised comparison, configurator or form with conditional steps.
- Brand requirements would change most of the existing layout.
- A specific upcoming capability cannot be added to the existing solution without substantial changes.
If visitors need to sign in, work with orders or save data, discuss web application development as a separate requirement. Changing the appearance alone will not cover those tasks. You still do not need to build every possible feature in advance.
An illustrative example: a studio offering classes
Imagine a studio offering one type of class for adults. This is an illustrative example, not an XEVOR case study. The first version needs a programme description, instructors, photos of the space and an enquiry to discuss availability. A foundation with those blocks may fit once the actual content has been checked.
Now the studio wants separate programmes for children, adults and companies. Before booking, a visitor needs to compare levels, choose a location and see available places. A single “our classes” block no longer describes the whole journey. The programme structure, selection rules and source of availability data need to be assessed.
The decision depends on what must launch now. If the team can still arrange bookings manually, the first version could contain programme pages and an enquiry form. If selecting an available place online is essential, that needs to be checked as a separate feature. Identical photos in a demo do not make these two projects equivalent.
What to check before commissioning a complete website
Ask to see one key page with your content, or have its adaptation explained through a specific example. A long heading, a portrait photo and a second language quickly reveal questions hidden by a demo with carefully selected content.
- Which pages, languages and design changes are included?
- Who prepares the copy, photos and translations, and checks them once they are in place?
- Do the form, error messages and enquiry delivery work, or are they only mockup elements?
- Which third-party materials and services are used, and which usage terms and recurring payments should be considered?
- Who will edit the site, which access will be handed over and how will migration options be checked?
- How would a new page type or a different feature affect the scope?
The answers should become part of the agreed scope. Our guide to commissioning a business website covers the full process from the first conversation to acceptance. Demonstration and launch dates are agreed once requirements and content readiness are clear.
What to check in both approaches: quality, SEO and growth
On a phone and a computer, visitors should be able to understand the service, find its terms and contact you. Check readability, keyboard navigation, forms and performance with actual content. The name of the development approach does not establish the quality of the finished website.
Search needs clear content, accessible pages and useful links. Google’s SEO Starter Guide explains these foundations and why indexing is not guaranteed. Our article on SEO during website development covers checks before launch. A template being labelled “SEO-ready” does not replace checking your own version.
Choose one likely next change: a service, language or new enquiry route. Ask how it would be implemented and what would need changing. Agree routine work separately; our guide to website support after launch explains how to define it.
Common questions before choosing a development approach
Is buying a ready-made website always cheaper?
Not necessarily. Compare the foundation, adaptation, content, functionality and launch against the same scope. If extensive changes are needed, the initial template price says little about the final estimate.
Can a template-based website have its own design?
Yes, if the foundation supports the agreed changes. Ask whether that means colours, fonts and images or a new page layout. The latter may require separate design and development work.
Does a custom website come with a CMS?
Only if it is included in the agreement. First decide who will edit what, and how often. A content management interface is a separate requirement; neither custom design nor using a template automatically includes one.
What should I provide to choose an approach for my business?
Describe your services, the main customer action, languages and features. Include existing content and a demo of the foundation if you have found one. That is enough to start assessing fit and clarifying the scope.
Planning to commission a website for your business? Tell XEVOR about the brief: what you offer, how customers should contact you and which capabilities are needed at launch. We will discuss a suitable scope, design and implementation.