Custom-built site or template: how to choose for your business
Every business website starts with the same choice: use a template or page builder, or have a site built to your requirements. Each side has people who swear by it, and both are sometimes right.
We build websites and web apps from scratch at ARTH, so we have a view. This post lays out the trade-offs fairly, including the cases where we would tell you to use a template.
When a template or page builder is the right call
If you need something live quickly on a small budget, a template can be the sensible answer. It suits a simple brochure site, a personal page, a short-lived campaign or a business that wants to edit everything itself without a developer.
The trade-offs are real but manageable: a look shared with other sites, limits on what you can change, and a platform that decides how fast your pages load. For many small businesses that is an acceptable bargain.
What a custom build buys you
A custom build starts from your customers and your next step rather than from a pre-made layout. You control the structure of every page, the performance budget, the markup that search engines and AI systems read, and the code itself.
It also costs more up front and usually needs a developer for changes unless a content system is built in. That is a real cost, and it is the main reason not to choose it by default.
Speed and findability are where the gap shows
Builders and themes differ widely, so measure rather than assume. A page that ships a lot of plugin code is slower on a weak mobile connection, and slower pages lose visitors and can score worse on Core Web Vitals.
Clean, plain HTML with sensible headings and structured data makes a page easier for search engines and AI assistants to read. On a custom build you control this directly; on a template you work within what it allows.
The middle path: stores and content systems
Not everything should be custom. For online stores we often use Shopify, because payments, inventory and checkout are better handled by a mature platform than rebuilt. Several of the stores in our work are Shopify for that reason.
Another option is a custom front end with a content system behind it, so staff can edit text and images without touching code.
Questions that decide it
Ask five things. How often will content change, and who will change it? Do you need features a template cannot do? How much does speed and search visibility matter to your revenue? What is the three-year cost, including changes and hosting, not just the first invoice? And who will own the code and the domain at the end?
If the honest answers are “rarely”, “no”, “not much” and “as little as possible”, a template is probably fine. If several point the other way, a custom build starts to pay for itself.
Frequently asked questions
Are template websites bad for SEO?
Not automatically. Many rank well. They do make some things harder, such as controlling page speed and markup, and results vary a lot between platforms.
What technology does ARTH use?
Websites and web apps are built with Next.js and React and hosted on Vercel. Online stores are often on Shopify. Mobile apps have used Flutter, Kotlin and React Native depending on the project.
Can you rebuild my existing Wix or WordPress site?
Yes. Rebuilds are common. The first step is deciding what to keep, what to fix and whether a custom build is justified at all.
Is a custom website always faster?
No. A badly built custom site can be slow. The advantage is that you can set and keep a performance budget, which you cannot always do on a template.
Have something worth building?
Tell us what you're trying to make happen. We'll reply with a plan, not a brochure.
Start a project