---
title: What a website costs in 2026
canonical: "https://elliotli.dev/blog/website-cost-template-vs-custom/"
pubDate: "2026-10-13T00:00:00.000Z"
author: Elliot Li
description: "A template costs a fraction of a custom build and ships in days. Here is what actually drives website pricing in 2026, and when paying for a custom build is genuinely worth it."
tags: [pricing, framer, guide]
---

import ProsCons from '../../../components/blog/ProsCons.astro';

**A website template usually costs between nothing and a few hundred dollars and ships in days. A custom build usually costs thousands and takes weeks to months.** The gap is not about quality — it is about how much of the work is yours to define.

That is the honest short answer. The rest of this guide is about the part people get wrong: assuming the cheaper option is always the worse one, or the expensive one is always the safer one. Neither is true.

## What actually drives the price

Every route to a website is priced on the same four things. Once you can see them, the numbers stop being mysterious:

- **Design** — is someone designing a layout for you, or are you choosing one that already exists?
- **Build** — is the site assembled from scratch, or is it already assembled?
- **Content model** — does the site just show content, or does it store and structure it so you can change it without breaking anything?
- **Operational flows** — does anything actually happen — bookings, inquiries, payments — or is it a brochure?

A $29 template and a $30,000 custom build differ almost entirely on the last two. The first two get cheap the moment work is reused.

## The three honest routes

### 1. Buy a template

You are buying a finished design and build that has already been paid for many times over, which is why the price reflects your copy of it rather than the whole project. You replace the words and images, restyle it to your brand, and publish.

The trade-off is the ceiling. A template does what it does, and pushing it far from that costs more than starting clean.

### 2. Buy a template and finish it

This is what most small businesses actually do, and it is where the real value sits. You start from a template that already covers the hard parts — the pages, the CMS, the booking or inquiry flow — and spend your budget on the last 20% that is genuinely specific to you.

### 3. Commission a custom build

A custom build is worth it when your requirements do not exist off the shelf: a bespoke booking engine, an unusual integration, or a design that *is* the product. Otherwise you are largely paying for novelty — the same buttons, placed differently.

<ProsCons name="Buying a template"
	pros={[
		'Live in days, not months',
		'The design and build are already proven',
		'One-time cost — no project to manage',
		'You keep the budget for the parts that are yours',
	]}
	cons={[
		'A ceiling on how far you can push it',
		'Some finishing in the editor is usually required',
		'Less unique than a bespoke design',
	]}
/>

<ProsCons name="Commissioning a custom build"
	pros={[
		'Exactly the features you need, nothing extra',
		'No ceiling on design or structure',
		'A design that can be genuinely distinctive',
	]}
	cons={[
		'Costs an order of magnitude more',
		'Weeks to months before launch',
		'Ongoing cost to maintain bespoke code',
	]}
/>

## Where a template stops being enough

Templates are bad at three things, and it is worth knowing them before you buy:

1. **Unusual functionality.** If your site needs to *do* something no one else's does, buy the custom build.
2. **Very large content sets.** A template's CMS is usually built for marketing content — dozens to low hundreds of entries. Beyond that, structure matters more than design.
3. **A design that has to be unlike anything else.** A template can be restyled; it cannot be un-recognised.

If none of those apply, a template is almost always the better use of money — because the money you save is better spent on the parts only you can supply: good photography, clear copy, and the small operational details that make a site convert.

## What "free" really means

A genuinely free template is not a demo. The good ones are complete, responsive sites you can publish as they are and use for client work. What they usually lack is not quality but scope — fewer pages, and none of the operational machinery like bookings, itineraries, or a client-editable CMS.

Free is the right answer when a single strong site is all you need, and a sensible first step when you are not yet sure.

## How to decide in five minutes

1. Write down what the site must **do**, not what it should look like.
2. If everything on that list is common — pages, a menu, a booking link, an inquiry form — buy a template.
3. If one item on the list is genuinely unusual, that item decides the route.
4. Budget for finishing, not just buying: photography and copy move the outcome more than the template you pick.

The full set is on the [templates page](/templates/), and if you would rather ask than guess, [get in touch](/inquire/).