Templates are cheap because they assume every business is the same shape. Most are not.
Templates are cheap because they assume every business is the same shape. Most are not.
A template is a set of decisions someone else made for an average business that does not exist. It fixes your navigation, your page structure, the order of your argument and often the tone of your imagery before anyone has asked what you sell or who buys it.
That is fine when the content is genuinely generic. It stops being fine the moment your business has a real differentiator, because the template has nowhere to put it.
The usual failure is not visual. It is structural. You end up bending the way you describe your work to fit the boxes the theme provides, and the thing that makes you worth hiring gets flattened into a three-column feature grid.
The second failure is cost. Heavily customising a template is often slower than building the same thing properly, because you spend the time fighting decisions rather than making them.
Start from the business, not the layout. Decide what a visitor has to understand and in what order, then build the structure that carries that argument. The design follows from the structure rather than the other way round.
This does not mean everything is bespoke. Components repeat, patterns repeat, and they should. What should not repeat is somebody else's idea of what your business is.
Teams rarely accept a template as shipped. They customise it, and that is where the budget quietly goes: overriding decisions instead of making them, fighting a layout system that was built for somebody else's content and somebody else's argument.
Past a certain amount of override you are maintaining a bespoke site with none of the benefits of having designed one. The theme's update path is effectively closed, because updating would overwrite your changes. You now own a fork of someone else's product and you are the only person who understands it.
We have inherited several of these. The rebuild is rarely harder than the last round of customisation would have been, which tells you something about where the money went.
Components are reusable. Patterns are reusable. A type scale, a spacing system, a card, a form field, a navigation pattern — those should absolutely be built once and used everywhere, and we do exactly that on every project.
What is not reusable is the argument your homepage makes. The order in which you introduce what you do, the proof you lead with, the objection you handle first: that is specific to what you sell and who you are selling it to. A template has already decided all of it on your behalf.
So the question is not bespoke versus reusable. It is which layer you are willing to inherit and which layer has to be yours.
Write down the three things a visitor must understand before they will contact you, in order. Then look at the template you are considering and try to place those three things in that order without fighting it.
If you cannot, you have two options: change your argument to suit the template, or change the template. Most businesses discover they have quietly done the first without ever deciding to.
A template demo is the best-case version of that template: photography shot for it, copy written to the exact length each box wants, a product range that happens to divide neatly into three. Your business will not arrive that way. You will have nine services rather than six, one case study that needs a thousand words and four that need two hundred, and a founder photograph taken on a phone.
The moment real content lands, the design starts absorbing damage. Headlines wrap onto a third line and break the vertical rhythm. A section built for a short paragraph gets nine hundred words. The hero image slot is sixteen-by-nine and your best photograph is portrait. None of this is fatal on its own, but the accumulation is what makes a site look homemade despite having started from something polished.
A structure designed around your actual content simply does not have those failure modes, because the content came first and the boxes were drawn around it.
The usual claim is that templates hurt search rankings because the code is bloated. That is only occasionally true, and it is not the important part. The important part is that search engines increasingly reward pages that answer a specific question completely, and a template pushes you towards generic pages because generic pages are what fits.
If your differentiator has nowhere to live, it does not get written down. If it does not get written down, it cannot rank, and it cannot be quoted by a language model summarising your industry. The structural constraint becomes a content constraint, and the content constraint becomes an acquisition problem.
We have seen the same business go from invisible to competitive on the strength of three pages that could not have existed inside their old theme.
It does not mean every project deserves a bespoke build. A local business that needs six pages and a contact form should buy a good template, spend the saved money on photography, and get on with running the business. We tell people that regularly, and it costs us work.
It also does not mean bespoke equals expensive forever. A well-built custom site gets cheaper to change over time, because each new page inherits decisions already made. A heavily customised template gets more expensive to change over time, because each new change fights the ones before it.
The question is not template versus custom. It is whether the constraints you are buying are ones you can live with for the next three years.