What a template actually saves you
Let's be fair to templates first, because the pitch against them usually skips this part: a good template genuinely saves time and money, and for a lot of businesses that's the right trade. If you need one clean page online this week — a menu, a portfolio, an address and a phone number — a template will get you there for less than a custom build costs, and it will look perfectly fine doing it.
Templates are built by people who design pages for a living, so the typography, spacing and layout are usually better than most businesses would produce from scratch. That's real value, and it's not the part that goes wrong.
Key takeaway
A template isn't a compromise when your site is genuinely simple. The problem only shows up when the business behind the site isn't simple, and the template can't tell the difference.
Where it starts costing you instead
A template is built to be one thing for everyone, which means it's built around a set of assumptions — a standard booking flow, a standard product grid, a standard "About" page — and every one of those assumptions is a small bet that your business works the way the template imagined it would. Most of the time it's close enough. Sometimes it isn't, and that gap is expensive in ways that don't show up on the invoice.
- The booking flow doesn't match how you actually take bookings. A salon that books by service and stylist, a clinic that books by practitioner and insurance type, an events venue that books by date and guest count — templates offer one generic calendar, and you end up bending your business to fit it instead of the other way round.
- The content structure fights what you're actually selling. A product grid built for physical goods handles a service menu badly, and a portfolio builder handles a product catalogue worse — the template wasn't wrong, it just wasn't built for you.
- Every customisation costs more than the template did. The moment you need something the template's editor doesn't offer, you're either paying a developer to hack around its limits or living with the workaround forever — often both.
- You're renting the platform, not owning the site. Move providers later and you're rebuilding from nothing, because the template locks your content inside its own system rather than in something portable.
How to tell which one you actually need
You don't need to guess. A handful of honest questions about your own business will tell you which side of the line you're on, before you've spent anything.
- Does your business run on a standard flow? If "browse, add to cart, checkout" or "read, contact, done" genuinely describes how customers use you, a template's assumptions probably match yours.
- Will you need something the platform doesn't offer within the first year? Multi-practitioner booking, a membership tier, an industry-specific calculator — if you can already name it, you'll hit the template's ceiling fast.
- Does your site need to do more than one job? Booking and payment and portfolio and blog, all working together, is exactly where generic templates start showing seams.
- Do you care about owning what you build? If switching providers in three years should mean an export, not a rebuild, that's a custom-site answer, not a template one.
The honest answer, either way
If your business is genuinely simple, say so and buy the template — it's the right call, and anyone telling you otherwise is selling something. But if you recognised your business in the questions above, the template isn't saving you money, it's deferring a cost to a worse moment: after launch, after customers are already used to the workaround, after you've outgrown the thing you paid for.
That's the judgment call we make with every project — matching what we build to what the business actually needs, not what's fastest to hand over. See how our custom website builds handle the flows a template can't, or look at how it plays out by industry if you want to see your own business's version of this problem.