I build custom websites for a living, so you can guess where I land. But the honest answer is that templates are the right call more often than most designers will admit, and pretending otherwise doesn't help anyone decide.
Here's how I'd actually think about it.
What templates are genuinely good at
A good template is a solved problem. Someone has already worked out the responsive behavior, the navigation patterns, the accessibility basics, and the thousand small decisions that make a page hold together. You're buying that work for a fraction of what it cost to produce.
A template is the right choice when:
- You need to be online quickly, and the site's job is mostly to exist and be credible
- Your budget is better spent on photography, advertising, or product than on a custom build
- The business is still finding its shape, and the site will be rewritten in a year anyway
- You have someone in-house who's comfortable maintaining it
None of that is a compromise. It's a sensible allocation of money.
Where templates start costing you
The trouble with a template isn't day one. It's month eight.
A template is a set of decisions someone made for an imaginary business. As long as your needs match those assumptions, everything is fine. The moment they diverge, you start working against the system instead of with it — and the workarounds compound.
The pattern is always the same. You need a layout the template doesn't have, so you fake it with a plugin. The plugin conflicts with another one, so you add custom CSS. The CSS breaks on mobile, so you add a media query. Two years later nobody can safely change anything, and the cheap site is quietly the most expensive thing you own.
The sameness problem
There's also the part that's harder to quantify.
Templates sell thousands of times. In a competitive field, there's a real chance a visitor has already seen your exact layout on a competitor's site — not consciously, but enough that nothing about you registers as distinct. When every business in an industry buys from the same marketplace, the whole category starts to look interchangeable.
For some businesses that genuinely doesn't matter. For anyone whose value depends on being perceived as more considered than the alternatives, it matters a great deal.
What custom actually buys
Not prettiness. Fit.
A custom build starts from what your business does, who it's talking to, and what you need someone to do next — then produces the structure that serves that. The page order is yours. The content types match your real services rather than the ones a template author imagined. Nothing is fought against.
The second thing you're buying is a foundation that grows. A system designed around your content can absorb new services, new case studies, and new sections without anyone bolting on another plugin.
The middle path most people should consider
You don't have to pick a side.
Some of the best outcomes I've seen come from a custom design built on a solid, boring platform. You get art direction and structure that belong to you, on top of infrastructure maintained by someone else. The design is bespoke; the plumbing isn't.
That's often the right answer for a small business that wants to look distinct without owning a software project.
The question that decides it
Ask what the website has to do.
If it's a credible place to point people who already found you, a good template will serve you for years. If the site itself is expected to do persuasive work — to make someone choose you over a cheaper competitor, or to explain something genuinely unusual about how you work — a template will fight you, because it wasn't built to argue your case.
That's the line. Not budget, not taste. Whether the site is a placeholder or a participant.