Template or custom — when each one is actually right

A gym owner came to us two years ago with a site that wasn't working. Slow, hard to update, no booking. When we looked at what he actually needed — class schedule, online signup, a page for each instructor, a way to push last-minute slots — it was clear the problem wasn't the template he'd started with. The problem was that he'd outgrown it and nobody had told him that was even a category of problem. We rebuilt it as a custom build. Six months later, his wife opened a second business: a small beauty salon. She asked whether she needed the same. She didn't. A well-configured template — with a booking widget and decent photos — was the right answer, and we said so.

That gap between those two projects is what this article is about.

What a template actually is

A template is a pre-built design framework. Someone designed the layout, the colour logic, the mobile behaviour, the font hierarchy. You populate it with your content and your photos, adjust the colours, and launch. The bones are shared with thousands of other sites. The face is yours.

That's not inherently bad. A well-made template is the product of serious design work. The problem isn't the template — it's using one when your business doesn't fit its assumptions.

Most templates assume a fairly standard structure: a homepage, an about page, a contact page, maybe a blog. They assume the visitor reads, then calls. They don't assume the visitor needs to book a time slot, check live availability, order something, log into a portal, or trigger anything in a system that runs elsewhere.

When your business is that simple, a template is fast, affordable, and honest. When it isn't, a template becomes a ceiling.

The three situations where a template is the right call

You need to exist online, credibly, this month. A trades business, a new practice, a solo consultant. The site's job is to confirm you're real, show what you do, and give someone a way to contact you. Nothing talks to another system. The owner isn't going to update it weekly. A template, built properly, does all of that at a fraction of the cost of a custom site. Our Starter tier starts at €700 and delivers something like this, live in seven to ten days. That's real and it works.

The business is straightforward and likely to stay that way. A single-location business that books by phone, a portfolio, a landing page for one service. There's no back-office integration, no data to own, no reason to build something that can grow in twenty directions. Building custom here is spending money solving a problem that doesn't exist.

Budget is the binding constraint and simple is enough. Sometimes €700 is what's available and the site genuinely doesn't need more. That's a legitimate choice and we don't push people past it.

The four situations where a template stops working

Booking, ordering, or paying happens on the site. A template can bolt on a Calendly link or a Stripe button. But when bookings need to reflect real availability, when the menu needs to change at 11pm without calling anyone, when a customer's order needs to reach a kitchen system — the bolt-on breaks. Custom is the only way to make that flow work cleanly.

The business has its own data that needs to live somewhere. Client records, job history, documents, appointments, staff schedules. The moment you need a system behind the site — not just a site — a template has nothing to offer. This is where the path from a website to a CRM starts, and it starts with a custom build.

You're doing something the template wasn't designed for. A template for a restaurant doesn't become a template for a veterinary clinic just because someone changes the photos. The assumptions underneath are wrong. A clinic needs appointment types, practitioners, intake forms, possibly patient records. Building that on top of a restaurant template means fighting the structure for every feature, forever.

The site has to scale. Adding a second location, a new service category, a staff portal, a customer login — a template doesn't expand cleanly. Each addition becomes a workaround, and workarounds compound. A custom build starts from your structure and grows the way your business does.

The honest test

Before deciding, answer two questions about your site.

First: does anyone need to do something on it, beyond read and contact? Book, order, pay, log in, submit something that goes somewhere — any of these. If yes, lean custom.

Second: will you need to edit it yourself, regularly, and does the content change in a way a blog can't handle — prices, availability, menus, staff, products? If yes, you need an admin panel that was built for how you actually work, not for a generic site.

If both answers are no, a template is probably the right tool. If either answer is yes, the savings on the template will be spent in workarounds, integrations that don't quite fit, and a rebuild twelve months later.

What this looks like in practice

When someone books an intro call with us, this is one of the first things we work out. Not to push toward the higher price — a business that genuinely needs a Starter site gets told so, plainly — but because the decision shapes everything: timeline, what we need from you, what it costs to run after launch.

The two-day design period we do before writing any code exists partly for this reason. It's where we look at what the business actually does, what the site needs to do, and whether those two things require custom infrastructure or whether a well-executed template would do the job in half the time.

If you're not sure which side of the line you're on, the intro call is free and takes thirty minutes. Come with what the site needs to do — not what it needs to look like — and we'll tell you honestly where the answer lands.