Website templates: why "start from a template" costs more later
What happens when a business website begins from a bought template, where the costs surface, and when a template still fits.
The short answer
Starting a business website from a bought template looks like the sensible economy: a professional design for a small price, ready to fill with content. What the price buys is a starting point built for nobody in particular, with the author’s layout decisions, their palette, features and scripts for every buyer’s possible need, and a structure that every change will have to work around. The costs arrive later and spread out: overrides that fight the template and break when it updates, unused weight that slows every page and every ranking, features hidden rather than removed, accessibility that cannot be fixed from outside, and eventually a rebuild when the template is abandoned or the business has outgrown it. A template is cheapest in month one. It becomes the more expensive of the two from the point where the hours spent working around its decisions, plus the rebuild it eventually forces, exceed the difference in the first invoice. Templates suit short-lived or low-stakes sites. A business site meant to carry the brand for years is not one.
Where the cost surfaces
| Year | What happens | The cost |
|---|---|---|
| Launch | The template is filled and customised; brand colours applied over its palette | Low price; customisation hours already exceed the template’s price |
| Year one | Changes fight the template; each is an override; unused sections hidden | Slow changes; mobile speed score drifts down |
| Year two | A template update breaks customisations, or is skipped; a needed feature does not fit | Either a broken site or a frozen, unpatched one; plugins bolted on |
| Year three | Accessibility audit or client questionnaire; the template’s markup cannot be fixed from outside | Remediation limited; risk accepted or a rebuild considered |
| Year four | The template author stops updating; the business has new services and markets | Rebuild, with the content migrated out of the template’s structures |
| Total | A low price, three years of friction, and a rebuild | More than the owned build would have cost, and less delivered |
What the owned alternative looks like
- A design for this business, expressed as tokens: colours, type, spacing.
- Components built from a proven foundation, styled by those tokens, only what the site needs.
- Structured content independent of any presentation, so it moves freely.
- A pipeline that tests accessibility, performance and visual consistency on every change.
- Code in the business’s repository, documented, changeable by anyone competent.
- Changes that are changes, not negotiations with a template.
Where templates still make sense
An event site that lives for a month. A landing page to test whether anyone wants a product. An internal page. A placeholder while the real site is built. In each case the site’s life is short or its stakes are low, and the template’s price is the whole cost. The mistake is applying that logic to the site that will represent the business for five years.
What this means for you
A template is a low price for a structure you will fight for years and eventually replace. For a business website meant to last, count three to five years on both sides, including the friction and the eventual rebuild, and see where the lines cross for you. An owned build is faster, more accessible and yours. Use templates for short-lived pages; build the site that carries your business.
Frequently asked questions
Templates look professional and cost almost nothing. What is the catch?
The demo is the template at its best, with the author's content and no changes. Your site is the template with your content, your brand colours forced onto its palette, its unused sections hidden rather than removed, and each change made through overrides. The professional look degrades with every customisation, and the low price is recovered by the hours spent fighting the template over the years.
Can a developer customise a template heavily instead?
Yes, and that is where the cost surfaces. Heavy customisation of a template means working against its structure, carrying its weight, and losing the ability to update it safely. At some point the developer is spending more effort accommodating the template than they would have spent building the needed components from a foundation, and the result is still someone else's structure underneath.
When is a template the right choice?
For a site with a short life or low stakes: an event, a quick test of an idea, an internal page, a placeholder while the real site is built. Where the site does not need to carry the brand for years, be extended, be fast and accessible by construction, or be owned as code, a template's low price is simply a low price.