Template Website vs Custom Website for Local Shops
Templates are the right call for most local businesses. Here is how to tell when yours has stopped working and what to build instead.
A template website is a good deal for a lot of businesses, and anyone who tells you otherwise is usually selling something. If you run a barbershop with one location, take bookings through a tool your staff already knows, and mostly need people to find your hours and your address, a template site does that job. It will keep doing that job for years. Spending money to rebuild it from scratch would be a waste.
So let's start there, honestly. Then let's talk about the exact point where templates stop working — because it is a specific point, not a vague feeling, and most owners cross it months before they notice.
What you're actually buying with a template
A template is a pre-built layout with the decisions already made. Squarespace, Wix, Shopify themes, a WordPress theme you bought for sixty dollars — same idea. Somebody else decided where the logo goes, how the menu behaves on a phone, what the contact form looks like. You pour your content into the shape.
That is genuinely valuable. You get:
- A site that works on phones without anyone testing it
- Hosting, security patches, and backups handled by the platform
- A place to publish that you can edit yourself at 11pm
- Speed. Days, not months.
For a huge share of local businesses, that list is the whole requirement. Your website's main job is to confirm you are real, say what you do, and get someone to call or walk in. A template does that. Your Google Business Profile is probably doing more work than your website anyway.
If that describes you, stop reading and go fix your hours listing instead. This post is for the other group.
The line: one thing the template cannot do
Here is the pattern we see over and over. A business runs fine on a template until it needs one specific thing the platform does not do. Not ten things. One.
Examples of the one thing:
- Online ordering where the modifiers actually match your kitchen — half-and-half toppings, a substitution that changes the price, a combo that pulls from three menu sections
- Pickup time slots that throttle by capacity, so you don't take fourteen orders for 6:15
- A booking system that knows Maria does colour and Josef doesn't, and that colour needs a 45-minute gap after
- Prices that change by location when you open the second shop
- A quote form that asks different questions depending on whether it's a repair or an install
- Orders that land in your POS instead of an email you have to retype
Notice what these have in common. They are all about how your business actually runs. Templates are built to handle the average case for thousands of businesses. Your one thing is the part where you are not average — and that part is usually the part that makes you money.
What happens next is the expensive bit
Nobody rebuilds when they hit the line. What they do is patch.
You add a plugin for ordering. It doesn't handle modifiers, so you add a second plugin. The second plugin fights the theme on mobile, so you pay someone a few hundred dollars to fix the checkout button. The plugin vendor raises prices annually. The ordering system emails you a PDF, so a staff member retypes every order into the POS, and once a week they mistype one. You add a booking tool that lives on a different domain, so customers click through to a page that doesn't look like your site and half of them bounce.
Now you have three vendors, two logins nobody remembers, and a monthly bill that crept past what a real system would have cost. Worse, you have a support problem with no owner. When ordering breaks on a Friday night, the plugin company says it's the theme, the theme developer says it's the plugin, and you are the one apologizing to customers.
That is the plugin tax. It doesn't show up as one big invoice, which is exactly why it goes unnoticed.
How to tell which side of the line you're on
Forget how the site looks. Ask these questions about the last ninety days.
Are you or your staff retyping information between systems? Orders from a form into the POS. Bookings from an email into a paper book. Every retype is a job you are paying a person to do because two pieces of software won't talk.
Do you say "just call us for that" about something a customer wants to do online? That is a request your site can't handle. Count how often it comes up.
Have you changed how you operate to fit the software? Turning off a popular menu option because the ordering plugin can't price it. Not offering a service because the booking tool can't schedule it. This is the loudest signal and the easiest to miss, because it feels like a business decision rather than a software limitation.
How many separate tools does one customer touch? If ordering food means going from your site to a third-party ordering page to a payment processor with a different name on it, you are losing people at each hop.
What breaks when you grow? A second location, a catering line, a delivery zone. If the honest answer is "most of it," you are already past the line.
Zero or one of these: stay on the template. Three or more: you are paying for custom already, in staff time and lost orders. You just aren't getting it.
What "custom" should actually mean
Custom does not mean a designer redraws your homepage. A prettier homepage does not fix a retyping problem.
Custom means the software matches how you operate. Your modifiers. Your prep times. Your staff skills. Your pickup windows. The site and the ordering and the phone all feed the same place so nothing gets retyped. When you change a price, it changes everywhere.
And it rarely means rebuilding everything. The cheapest good answer is usually a hybrid: keep the template for the pages that are just pages — about, hours, gallery, blog — and build custom only the one thing that carries the money. A restaurant might keep a template site and put a real ordering system on it. A trades business might keep its pages and add a quote flow plus an AI phone agent that answers when the crew is on site.
Scope the build around the one thing. Not around a redesign.
Questions to ask before anyone builds anything
Whoever you hire, template or custom, get answers to these in writing.
- When a customer orders, where does that order physically appear? A printer, a tablet, the POS, an email. If the answer is email, ask who retypes it.
- What happens when my menu or price list changes? Can you do it yourself in under five minutes, or is it a support ticket?
- Who owns the domain and the data? It should be you. Ask to see the login.
- What is the monthly cost in year three? Include every plugin, subscription, and per-order fee. Compare that number, not the build fee.
- When it breaks at 7pm Saturday, who picks up? One name.
If a vendor gets vague on number one or number five, that is your answer. We wrote more on vetting this in how to choose a web agency in Toronto.
The decision, stated plainly
Templates are right when your site's job is to inform. Custom is right when your site's job is to transact in a way that is specific to you.
Most local businesses start in the first group and some move into the second — usually the moment ordering, booking, or scheduling becomes how revenue arrives. Moving is not a failure of your old site. It means the business outgrew it.
If you want a second read on which side you're on, that is the conversation we have with most people who call our Toronto studio — and a fair number of them leave with "keep your template, fix these two things." We run a restaurant ourselves, so we know what a workaround costs on a Friday night. Sometimes the honest answer is that you don't need us yet.