// deciding · 5 min read

Template or custom: how to decide

Custom development is not always better, and anyone who tells you it is has something to sell. A template is the right answer more often than a custom shop will admit, and the wrong answer in ways that are hard to see until later.

When a template is the right answer

If your website is a brochure, meaning it exists to say who you are, what you do, and how to reach you, a good template will do that job well and for a fraction of the cost of building one.

This covers a surprising amount of the web. A restaurant, a law office, a single-location service business: these are mostly presentation, and presentation is what templates are good at.

When a template starts costing you

The problem with templates is not quality. It is the moment your needs stop matching the template author's assumptions. That moment is predictable, and it is usually one of these.

  • You need the site to do something, not just say something. Booking, quoting, accounts, inventory, or anything that talks to another system.
  • You need a structure the template does not have. Templates assume a shape; if your content does not fit it, you start fighting the tool instead of using it.
  • Performance matters to your revenue. Template sites carry every feature every customer might want, which means your visitors download all of it.
  • You want to own your work. A custom build is yours, including the code. A template ties you to whoever maintains it.

The honest middle path

Plenty of projects are a template with real work around it: a theme, but properly configured, with a fast hosting setup, honest structured data, and custom pieces only where the business actually differs.

This is often the best value available, and it is the answer we give when it is true. What matters is that someone tells you which situation you are in, with reasons, rather than selling the larger job by default.

Signs you have outgrown your template

You are working around the tool instead of with it. You have plugins stacked on plugins to make something behave. Your site is slow and the fix keeps being "remove a feature." You are paying someone repeatedly to fight the platform.

Any one of those is survivable. Two or three together usually means the template is now the most expensive part of your website, and it is worth pricing the alternative before you spend another year on workarounds.

Want help with this?

Tell us the situation you are in. We will give you an honest read, with the reasoning included.

Start a Conversation