Custom website or template: what actually decides the result

What the two words actually mean

A template is a finished layout somebody else designed, which you pour your own content into. That is what a theme on WordPress is, and what the templates inside Squarespace, Wix and Shopify are. Somebody has already decided where the heading sits, how the type scales down, what the spacing is, and how the whole thing reflows on a narrow screen.

Custom means the layout was decided for this business. It does not mean every line of code was written from nothing. Almost nobody does that, and you would not want to pay for it: a custom build sits on a framework and a set of components the same way a custom house sits on standard lumber and standard windows. What is custom is the plan, not the raw material.

In between is where most small business work actually lives: a template restructured until the order of the page is decided by the business rather than by the demo content it shipped with. That is a legitimate route and it is often the sensible one. It only becomes a problem when it is sold to you as the first thing while being the third.

Worth asking: if somebody tells you their work is fully custom, ask what that means in practice. A straight answer sounds like "we start the layout from your services rather than from a theme, and we build it on our own component set". A vague one is a label.

What a template does well

A good template is not a lesser version of a designed site. It is somebody else's design work, already finished and already tested, sold to you at a fraction of what it cost to make. That is a real thing to be buying.

• Hundreds of small decisions are already right. Line height, the gap between sections, how a three-column row becomes one column on a phone. None of it is interesting and all of it is visible when it is wrong.
• You can see what you are buying. A template has a demo you can open on your own phone before any money moves. A custom design is a description and a mockup until it is built.
• The cost and the timeline are predictable. Most of the uncertainty in a website project is in the design phase, and a template removes it.
• Somebody else maintains it. Browsers change, platforms change, and a maintained template gets updated for both without you commissioning anything.
• It has been tested on more devices than one person can own. A template with thousands of users has been opened on phones nobody in Niagara has ever held.

Where a template runs out

The limit is not visual quality. It is that the template does not know what you sell, so its structure is designed around the demo content, and the demo content is nothing like yours.

• The order of the page belongs to the demo. Templates lead with whatever photographs best. If the thing that actually wins you the job is that you answer the phone and quote the same week, the template has no slot for that and it ends up three screens down.
• It was built around photography you do not have. Template demos run on professional stock imagery. The same layout with real photographs of a real van on a real driveway can look worse than a plainer design would have.
• Anything unusual about how you sell fights it. Service areas rather than a shop address, quoting instead of prices, a booking flow, seasonal work that flips twice a year. Each of those is a small fight with a layout that was not expecting it.
• The fixes accumulate as plugins. Every missing piece becomes an add-on, and a site running twenty plugins has twenty things that can break independently and twenty things to keep updated.
• You carry code for features you do not use. Templates ship everything so they can sell to everyone, and the parts you switched off are usually still being downloaded by the person looking you up on a phone.

The phone is where the difference shows

Responsive design means one site whose layout reflows to fit the screen it is on, rather than a separate stripped-down mobile version at a different address. It was the important question about ten years ago. It is not any more, because every serious template today is responsive by default, and so is every framework a custom build would use. Asking "is it responsive" now tells you almost nothing.

The question that still tells you something is whether the phone layout was decided or merely inherited. Both a good template and a careless custom build will pass a responsive test. Only one of them has had somebody look at the narrow version and ask what a person standing in a driveway actually needs from it.

There is a search consequence too, and it is the part most people miss. Google predominantly indexes the mobile version of a page. What is in your phone layout is what gets read and ranked. So if something was hidden on small screens to tidy the design up, a block of service copy collapsed away or a section dropped entirely, it is not just hidden from the person holding the phone. It is largely hidden from search as well.

Open your own site on your own phone and check these, whoever built it:

• Is the phone number tappable, and is it visible without scrolling?
• Can you read the body text without pinching to zoom?
• Does anything slide sideways when you scroll straight down?
• How many taps from landing to doing the thing you want people to do?
• Does the menu work with a thumb, or does it want a mouse hovering over it?
• What did the layout leave behind on its way down from the desktop version, and did you want that gone?

The longer version of that check, including what to do with the list it produces, is in do you need a new website, or does yours just need fixing.

The distinction that matters: a responsive template left at its defaults and a site designed for the phone first both fit the screen. Only one of them puts the phone number where a thumb already is.

What actually decides the result

Across every site we have worked on, the things that separate one that earns its keep from one that does not are the same short list, and none of them appear in the custom-or-template argument.

• What is at the top of the page, and whether it is the thing that wins you work.
• What the page asks people to do, and whether it asks once and clearly.
• Whether the words are about the reader's problem or about the business's history.
• Whether the photographs are of the actual work.
• Whether any of it is still true in a year.

That is why a well-run template site beats a neglected custom one so regularly. The label decides where the layout came from. The list above decides whether the site does anything.

Three questions that usually settle it

1. Is there anything unusual about how I sell? Service areas instead of a storefront, quoting instead of prices, bookings, seasonal switches. If nothing on that list applies, a template is unlikely to fight you.
2. Do I already have photographs and words, or am I expecting the site to supply the impression? A template running on stock imagery looks like every other business running the same template.
3. Who is going to change this in six months, and can they? If the answer is you, the route that leaves you able to edit it matters more than the route with the better design story.
4. In two years, could somebody else pick this up? A template on a mainstream platform is easy to hand over. So is a well-built custom site. A custom site nobody documented is not.

If the honest answers are no, yes, me and yes, then a good template restructured properly is the right place for your money, and anybody telling you otherwise is selling you the label rather than the outcome.

What we do, for the record

We start the layout from what the business sells and who it sells to, rather than dropping the content into a stock theme. We do not start the code from nothing: the build sits on a component set we reuse across projects, and pretending otherwise would be a strange claim to make, because reusing what already works is part of why the price is what it is. What does not get reused is the order of the page, the words and what the page asks people to do.

If a template is genuinely the better spend for your situation, we will say so on the call. The related reading is website builder, one person, or an agency for who should do the work, and what a small business website actually costs in Ontario for what each route is published at. Our own prices are on the pricing section.