It's tempting for any development studio to recommend fully custom work by default. But the honest answer, for a lot of small businesses, is that a well-chosen template, set up properly, is genuinely the right call — and saying so builds more trust than pretending otherwise.
When a template genuinely makes sense
When your business is a fairly standard shape — a service business, a local shop, a restaurant, a consultant — where the site's job is to look professional, load fast, and make contact easy, without needing functionality that doesn't already exist as a common pattern.
When custom development actually earns its cost
When the business has requirements a template genuinely can't serve: a booking system with specific rules, a members-only area, an unusual catalogue structure, real integrations with other business systems, or a brand experience specific enough that a template would visibly constrain it.
The middle ground most people don't know exists
A customised template — starting from a strong, well-coded theme and modifying it meaningfully (custom sections, real brand design, specific functionality layered on), rather than either an untouched template or a fully-from-scratch build. This is often the actual right answer for a growing small business.
A useful honesty check for any studio quoting you: if every conversation defaults straight to "we'll build this fully custom" without first asking what the site actually needs to do, that's worth a follow-up question. The answer should follow from your requirements, not from whatever's most profitable to build.
The real question was never "custom or template" in the abstract. It's what your business specifically needs that it doesn't already have — and letting that answer determine the approach, rather than assuming the more expensive option is automatically the better one.