Available worldwide
Posts

Custom website or template? An honest decision guide

November 20, 2026
A template is the right choice when you need a standard site quickly, the budget is small, and looking like the other businesses in your category does not cost you customers. A custom website is the right choice when the site is a real sales channel rather than a business card, when your offer or buying process does not fit a theme, and when you want to own the result outright. Most businesses sit clearly on one side of that line. The trouble starts when the decision is made on sticker price alone. I build custom websites for a living, so you would expect me to say custom is always better. It is not. I have steered people toward a template when that was the honest answer. Here is the guide I wish more people had before they emailed me: cost, speed, differentiation, maintenance and ownership, with a straight answer on each. A template in 2026 is one of three things: a WordPress theme, usually driven by a page builder or the block editor; a Shopify theme with its sections and settings; or a hosted builder like Squarespace, Wix, Webflow or Framer. In every case someone has already made the layout decisions for a hypothetical business, and you pour your content into the slots they left. A custom website inverts that. The page structure, the content model, the design and the code are decided around your business. That does not mean hand-writing every line from nothing: I build on Next.js and React most of the time, and on WordPress or Shopify when that fits better. The custom part is the decisions, not the absence of a framework: every page exists because your business needs it, and nothing ships that does not earn its place. The grey zone is the heavily customised theme: bend a template far enough and you get its constraints with a custom build's invoice. If you are paying a developer to fight a theme for weeks, you have already chosen custom, just the expensive way. On day one there is no contest. A theme is a one-off licence or a monthly subscription; a custom website is a project with a proposal attached. The real cost shows up later: the hours you or your staff spend inside a page builder nudging a layout that never quite fits; the plugins bought to fill the gaps the theme left, each with its own renewal; the developer hired in year two to make the theme do the one thing it was never designed for. And the cost nobody puts on a spreadsheet: a site that gets visits and produces no enquiries. The most expensive website I see is the cheap one that does nothing. Custom cost drivers are predictable: the number of pages, whether you need a CMS, languages, integrations, and how much content already exists. Where custom budgets explode is hourly billing on a vague brief. That is why I scope the project in a short intake and quote one fixed price, so the number you agree to is the number you pay. If the budget covers a template and nothing more, a well-chosen template beats a half-finished custom site every time. Half a custom website is worth nothing. A template can be live in days if your content is ready. That is a real advantage and I will not pretend otherwise. A custom build takes weeks: a compact business site typically goes from first call to launch in a few weeks, a larger service site or a shop in a couple of months. The bottleneck is rarely the code. It is content and feedback, and that bottleneck exists for templates too; it just hides behind the placeholder text until launch day. There is a second kind of speed. Template sites launch fast and then stall at the first thing the theme cannot do. Custom sites launch slower and then change cheaply, because the code was written for exactly this structure. Decide which speed matters more: the next two weeks or the next two years. Page speed is a third thing. A theme ships CSS and JavaScript for every layout any buyer might pick, and page builders add a layer on top. You can get a template to pass Core Web Vitals, but it is tuning work that you redo after updates. A custom site built properly passes without that tuning, because nothing loads that the page does not use, and on a phone on mobile data the difference is visible. For a lot of businesses, looking standard is a feature. A dentist, an accountant, an electrician: the visitor wants to know you are credible, open, nearby and reachable, and a clean, conventional layout signals exactly that. If that is your business, a template does not cost you a single customer, and the money is better spent on photography and copy. For other businesses, looking like everyone else is fatal. When I built the site for Bubba, a bubble tea and mochi brand in Ecuador, the entire brand was delight: a mascot, neon over purple, an animated cup that fills when you hover over a drink. No restaurant theme does that, and a tasteful one would have quietly deleted the thing customers love. When the brand is the product, the site has to carry the brand, and a template cannot. Differentiation is also structural. For EVH Renovatie, a windows and doors installer in Belgium, the win was not the visual design. It was giving each of nine services its own page with its own metadata and structured data, so each one ranks on its own for a local search. A theme's single services page with anchor links would have ranked for nothing. That is a custom content model, invisible until you look at where the enquiries come from. Templates are not maintenance-free, and this is the part the sales page skips. A WordPress theme means theme updates, plugin updates, PHP version bumps and security patches, every month, plus a page builder whose interface changes under you. Hosted builders do handle that for you, and for an owner who will never touch the site, paying a subscription to make maintenance someone else's problem is a reasonable trade. A custom site, built properly, has fewer moving parts. A static or server-rendered Next.js site has no plugin ecosystem to patch; dependencies get updated a few times a year rather than weekly. The honest risk is different: the person who built it has to be reachable, or the code has to be clean enough for another developer to pick up. The question that matters most, though, is who updates the content. For the photography studio site I built for my wife, I chose WordPress on purpose, because she needed to publish a new shoot from her phone without a developer in the loop, and the stack I enjoy more would have made me the bottleneck. For QMP Cars, a used-car dealership, the answer was the opposite: a custom admin where the dealer manages every listing, photo and price, because a generic dealer theme models the inventory its author imagined, not this dealer's. Both are custom decisions. Only one of them is custom code. With a hosted builder you are renting. Cancel the subscription and the site is gone. Your domain and your text are yours, but the site itself lives on their servers in their format, and exports are partial at best. Fine for a first-year experiment; uncomfortable once you have years of rankings on it. A WordPress theme is better: you own the files. But the layout usually lives inside a page builder's blocks or shortcodes, so the day you switch themes every page falls apart. Lock-in by a thousand plugins is still lock-in. A custom site is a repository you own, deployable on any host, that any competent developer can take over. The question to put to anyone building your site, me included: if we part ways next year, what do I walk away with? The right answer is a domain, a codebase and the content, with nothing that stops working when the relationship does. A proper WordPress theme without builder dependencies can pass that test too. If most of these are true, buy a theme and do not look back:
  • You need a site this month and the budget is small.
  • The site is a business card: who you are, what you do, opening hours, a phone number and a map.
  • You are validating a new idea and might change the whole offer in six months.
  • You sell standard products in standard ways, and a Shopify theme already does what your shop needs.
  • Nobody in the company will ever touch the site, and a subscription that makes maintenance disappear is worth more to you than owning the code.
If you go this way, pick a theme that is actively maintained, keep the plugin list short, and spend the savings on photographs of your actual work and copy written by a human. And if most of these are true, a template will cost you more than it saves:
  • The website is your main acquisition channel, so a better conversion rate pays for the build many times over.
  • Your offer does not fit a theme: configurators, booking flows, quote forms with real logic, member areas or an admin for your own data.
  • You need to rank for many services, regions or languages, which takes a real content model and correct hreflang.
  • Your brand is the product, and a tasteful template would erase it.
  • You need integrations with a CRM, payments, a booking system or internal tools.
  • You have outgrown a template site. The second website is very often the custom one.
If you recognised yourself in the second list, that is what my custom website design and development work is for: one person from strategy to production code, remote, with a fixed price agreed before anything is built. The simplest next step is to tell me what your business does and what the site needs to achieve, and I will say plainly whether custom is worth it for you. And if you recognised yourself in the first list, good. You just saved yourself a project. Buy the theme, take the photos, write the copy, and come back when you have outgrown it.

Custom website design

Tell me in a few lines what your business does and what you want to achieve. You get a reply within two working days with an honest assessment and a proposal for a 30-minute intake.

Get a proposal