We build custom sites for a living, so treat what follows with the appropriate suspicion. We're going to argue against ourselves for the first half anyway, because the honest version is more useful than the sales version.
Templates are genuinely good now
The case against templates used to be that they looked cheap and broke on phones. That stopped being true years ago. A modern template is responsive, reasonably fast, accessible enough, and designed by someone competent.
If you are a two-person business that needs to exist online by Friday, a template is not a compromise. It is the correct engineering decision. Anyone who tells you otherwise is selling something — us included.
Use a template when:
- You are testing whether the business works at all
- The site's job is to be found, be legible, and list a phone number
- You need it live in days, not weeks
- Nobody on your team will ever need to change how it works, only what it says
Where the cost actually shows up
The bill for a template rarely arrives at purchase. It arrives later, in four places.
1. You inherit someone else's decisions
A template is a set of answers to questions about a business that isn't yours. Every time your business doesn't fit the template's assumptions, you bend your business rather than the site — and you usually don't notice you're doing it.
2. The weight you didn't ask for
Templates ship every feature every buyer might want, and you load all of it. That's the page-builder tax: a site with four visible sections carrying the code for forty. It shows up as slow loading on Indian mobile networks, which is where most of your traffic is.
3. The ceiling
Everything is easy until the first thing the template didn't anticipate. A returns flow, a booking rule, a pricing structure with a genuine exception. Then you are paying a developer to fight the template — which costs more than building it properly would have.
4. It looks like the others
This matters less than designers claim and more than founders think. Nobody consciously notices your template. But if you're asking for a premium price, a layout your customer has already seen on four other sites quietly undermines it. Distinctiveness isn't vanity when your positioning depends on it.
What custom actually buys
Not beauty. A good designer makes a template beautiful too. Custom buys three specific things:
- Only the code you need, which is why custom sites are usually faster than templated ones despite doing more
- No ceiling — the answer to "can it do this?" is always yes, it's only ever a question of budget
- Ownership — no licence, no plugin subscriptions, no platform that can change its pricing on you
It costs more upfront and takes longer. Both of those are real and shouldn't be argued away.
The four questions that decide it
Skip the philosophy. Answer these:
- Does anything need to remember something? Accounts, orders, bookings, stock. If yes, you will outgrow a template.
- Is the site the product, or a brochure for it? Brochure, template. Product, custom.
- Would a customer paying premium prices judge you on it? If yes, distinctiveness is doing commercial work.
- Will you need something unusual within a year? If you already know what it is, build for it now. Retrofitting costs more than including it.
Three or four noes, buy a template and spend the difference on marketing. Two or more yeses, custom will be cheaper by the second year.
That's the whole decision. Everything else is taste.
A paid site audit gets you a straight answer and what it would take either way — including "keep what you have", if that's the honest call.
See The Pricing →