We sell themes, so you already know which way we are supposed to argue. Let us not do that.
There are businesses that should not buy a template, including from us. Selling one to them produces a site that fights them for two years and a customer who tells people we were a mistake. That is a bad trade.
The problem is that most advice on this decision is either vendor-shaped or framed around the wrong variable. So here is a framework built around the variable that actually matters.
The wrong framing
The common version of this question is “custom equals quality, template equals budget.” It is wrong in both directions.
Plenty of custom builds are worse than a good template — built by one developer in a hurry, on a stack nobody else understands, with no design system, no documentation, and no maintenance plan. Plenty of templates are faster, more accessible, and more thoroughly tested than a bespoke build, because they have been stress-tested by thousands of installations rather than one.
The price difference is real. The quality correlation is not.
The right question
The variable that decides this is: where does your value actually live?
For most businesses, the value is in the offer, the content, and the credibility — what you sell, what you know, who trusts you. The website communicates that value. It is not the value.
For a smaller group, the website is the product. The interface is the thing customers pay for, or the interaction itself is the differentiator, or the business logic on the site does something no other site does.
If your value lives in the offer, a template is a sound decision and the money is better spent on photography, copy, and traffic. If your value lives in the interaction, a template will constrain the only thing that matters.
Five diagnostic questions
Work through these honestly.
1. Does your business logic exist anywhere else?
Not “do I want a booking form” — everyone has one of those. This is about genuinely unusual mechanics: a quote calculator with rules specific to your industry, a rental system with overlapping availability and deposits, a marketplace with multi-vendor payouts, a subscription with unusual proration, a configurator with hundreds of valid combinations.
If your core workflow does not exist as an established pattern, you will spend more forcing a template to fake it than you would building it.
Unusual logic → custom, or template plus custom development.
2. Is your site the product, or a description of the product?
A restaurant’s site describes the restaurant. A design agency’s site describes the agency — even though it also demonstrates taste. A SaaS application’s marketing site describes the product, while the application itself is the product.
Be careful with the demonstration case. “Our site must be unique because we are a creative agency” is often true, but it usually applies to one or two pages, not to the blog, the contact page, or the careers listing.
Site is the product → custom. Site describes the product → template is likely fine.
3. What is your real content volume and structure?
Templates handle common content shapes well: pages, posts, products, portfolios, events.
They handle unusual shapes badly. A research library with faceted filtering across eight metadata fields. A directory with cross-referenced entities. An editorial operation with embargoes, multiple contributor roles, and complex taxonomies. These are content architecture problems, not design problems, and no amount of theme configuration solves them.
Unusual content architecture → custom.
4. Who maintains this in two years?
The most common failure of custom builds is not the build. It is month eighteen, when the developer who made it is unavailable, nobody documented anything, and the person who inherits it needs a week just to understand how it works.
A widely-used template has documentation, a support channel, and a large pool of people who already know it. A one-off build has whoever wrote it.
If you do not have an ongoing technical relationship, or budget for one, this weighs heavily toward templates.
No maintenance plan → template.
5. What is the honest budget — including year two?
Custom is not slightly more expensive; in most markets it is a different order of magnitude, and rates vary so widely by region that any figure quoted here would mislead someone.
So compare structurally instead. Custom means design, build, testing, and documentation as one-off costs, plus ongoing maintenance because nobody else will patch it. Template means a licence, your setup time, and renewals — with updates and compatibility fixes handled by the studio.
Then include the cost nobody budgets: time to launch. A custom build measured in months against a template measured in days is not just a cost difference. It is months of a business operating without the site, and for a new venture that gap is often the largest number in the comparison.
The answer most businesses actually need
The framing above is a false binary, and the honest recommendation for a large share of businesses is neither pole.
Start with a well-built template. Spend a fraction of the custom budget on targeted custom development for the one or two things that genuinely differentiate you.
In practice: a solid theme handles the pages that are the same as everyone else’s — about, contact, blog, standard product pages — and a developer builds your unusual quote calculator, your specific booking logic, or your one signature interactive page.
This works because the differentiation is concentrated. Most sites have thirty pages where being conventional is fine and two where it is not. Paying custom rates for all thirty to get the two is how budgets disappear before the important work starts.
The prerequisite is a template built to be extended — documented override paths, exposed design tokens, standard content storage. A locked-down all-in-one theme makes the hybrid approach painful, which is a reason to check for that at purchase time.
What each actually buys you
Custom genuinely gives you: exact fit with no compromise; freedom in performance and accessibility decisions because nothing unnecessary was inherited; a codebase shaped around your workflows; and full ownership.
Custom does not automatically give you: good design, speed, accessibility, or maintainability. Those come from who builds it, not from the fact that it was built for you.
Templates genuinely give you: speed to launch; a design already validated across many sites; testing across devices you do not own; ongoing updates; documentation; and a much lower entry cost.
Templates cost you: compromise on the specifics; someone else’s decisions about performance and structure; dependence on a studio’s continued maintenance; and constraints that get more noticeable as you grow.
A rough decision table
| Situation | Start with |
|---|---|
| New business, standard offer, needs to launch soon | Template |
| Established business, unusual core workflow | Custom, or template + custom module |
| Content-heavy publication, conventional structure | Template |
| Content with unusual architecture and taxonomies | Custom |
| Site is the product or the primary differentiator | Custom |
| Agency or freelancer building for a client | Template, priced for judgment |
| Growing store, standard catalogue, needs speed | Template |
| Marketplace, configurator, or complex booking logic | Custom |
| Budget exists but no ongoing technical support | Template |
The question that settles it
If none of the above resolves it, try this one.
Name the single thing your website must do that a competitor’s website cannot.
If you can name it immediately, in a sentence, and it is a genuine interaction rather than a claim — that is your custom scope. Build that. Use a template for everything around it.
If you cannot name it, or the answer is “look better” or “feel more premium,” that is a design and content problem, and a good template plus real photography plus well-written copy will get you further than a custom build ever would, for a fraction of the cost, months sooner.
There is no prestige in a custom build that nobody can tell was custom.
At eThemeStudio, we build themes designed to be extended rather than locked down, and we also take on custom development for the parts a template genuinely cannot cover. If you are weighing this up, describe your situation to us — including the awkward parts. If the answer is that you should not buy a theme, we will say so.
Comments (0)