Skip to content
NEWAI search optimizationSee how

Comparison · Approach

Custom website vs template: what you give up either way

A template gets you live sooner for less. A custom build fits your business instead of a demo's. Both of those are true, and neither is the deciding factor — the deciding factor is whether your website has a job that only a layout built for you can do. If it does not, a good template installed properly is a better use of your money, and we will say so.

Get a straight recommendationScore your project
Template strength
Live sooner, less upfront, known risk
Custom strength
Fits your funnel, not a demo's
Most common mistake
A multipurpose theme, heavily modified
Our own budget
1.4s average LCP, Lighthouse ≥ 95

Straight to it

The short answer

If you read nothing else on this page, read this. Custom website vs template, decided in three paragraphs.

Take a template if the site is small, the budget is tight, the content is straightforward, and your brand is not the thing that wins the sale. Being live and credible this month beats a custom project you cannot afford to finish, and that is not a consolation prize — for plenty of businesses it is simply the right call.

Commission a custom build if traffic already arrives and the problem is conversion, if you have a flow no demo site has ever had, if brand distinctiveness is part of why people choose you, or if you have a performance or accessibility obligation to actually meet rather than aspire to.

The thing to understand before you choose: a template is the fast option, not the cheap one. Its visible cost is low and its invisible cost is modification. Every change that fights the template's assumptions is billable time, and that is where template projects quietly become more expensive than the custom build they were chosen instead of.

The decision table

Where the two really diverge

Both columns describe the common case rather than the best or worst one. A well-chosen template installed by someone competent beats a custom site built badly, every time.

Current as of October 2026. 'Template' here covers a marketplace theme, a page-builder template set or a design kit; 'custom' means the design and the content model are built for your business, whatever the platform underneath.
DimensionTemplate or themeCustom build
Cost shapeLow and visible upfront: the licence, plus setup. The part that is not visible is modification — every change that works against the template's assumptions is billable time, and it accumulates quietly.Higher upfront and quoted as a project, because the design, the build and the content model are made for you. Usually lower after launch, because there is less to fight.
Time to launchDays to a few weeks, if you accept the layout as designed and your content is ready. Content is almost always the real bottleneck.Weeks, because discovery, structure, design and content are genuine steps. Our published figure is about three weeks for most builds, longer where commerce, integrations or bespoke design work are involved.
Who maintains itYou, plus the template author. Their updates can overwrite your modifications unless the work was done properly in a child theme or equivalent — and if the author stops publishing updates, you inherit their code.You and whoever built it. Nothing third-party changes under you, and nothing updates itself either, which cuts both ways.
Design and brandProven layouts, and visibly shared. Someone in your market is probably running the same one, which matters in some sectors and not at all in others.Specific to your brand, your proof and the objections your buyers actually raise on the phone.
Performance ceilingBounded by what the template loads. Multipurpose themes ship a page builder, several sliders and an icon set you will never use, and you cannot remove most of it without breaking the theme.Bounded by discipline. 'Custom' is not a performance claim on its own — a custom build is only fast if someone is holding a budget and measuring against it.
AccessibilityVaries enormously and is almost never documented. Assume you will need to audit it and fix what you find, especially focus order, contrast and form labels.Can be built to WCAG from the first component, which is far cheaper than retrofitting. Only happens if it is specified — a custom build is not accessible by default.
Content modelWhatever the template's demo needed. Your case studies get bent into its 'portfolio' fields and your services into its 'features', and the mismatch shows up every time someone adds a page.Designed around what you actually publish, so adding the next case study or location is filling in a form rather than inventing a workaround.
When you outgrow itYou modify until the modifications cost more than a rebuild, then you rebuild. Most template projects that go wrong go wrong here, not at launch.You extend. The next section is new work rather than a fight with someone else's assumptions.
Lock-inLow in theory, because the content is yours. Higher in practice, because the layout is tied to the template's shortcodes or builder, so moving usually means rebuilding every page.Low if it was built on standard, documented patterns. High if it was built as an unreadable one-off, which is a real risk — ask who else could maintain it.
RiskKnown. You can see the demo, read the reviews and check the author's update history before you spend anything.Unknown until you see the work. The quality of the team is the entire variable, which is why references and recent, relevant work matter more than the proposal.

The detail

Six things worth knowing before you commit

A template is the fast option, not the cheap one

The licence is a small number and it is the only number most people compare. The cost that decides whether the project was good value is modification — and modification is priced in hours, not in licences.

The pattern is consistent. The template looks right in the demo, which was built with the demo's photography, the demo's copy length and the demo's six sections. Your content is a different shape. So the homepage hero needs a second call to action, the services grid needs four items instead of three, the case study template needs a results panel the theme has no field for, and each of those is a negotiation with someone else's code. Three or four of them and you have spent the difference.

This is not an argument against templates. It is an argument for choosing a template whose demo is genuinely close to what you need and then changing almost nothing — which is a real discipline and the thing that makes template projects succeed.

Where templates genuinely win

Templates win on speed, on risk and on budget, and those are not small things. You can see exactly what you are buying before you spend, which is the opposite of commissioning design work. You can be live in days. And the layouts are usually proven, because a theme that sells well has been through more real-world use than any single agency's first draft.

There is a second, less obvious win: a template forces decisions. A business that has spent four months failing to agree on a homepage will often ship a good site in a fortnight once the layout is a given and the only remaining question is what the words say.

  • You can evaluate the actual product before you pay for it
  • Live in days rather than weeks, which matters for an event or a funding deadline
  • Layouts that have survived thousands of real sites rather than one design review
  • It converts an open-ended design argument into a content task

The question is whether your website has a job only you can do

Here is the test that actually separates the two. Write down, in one sentence, the thing your website has to do that a competitor's website does not. If you can name it — a quoting tool, a multi-step enquiry that qualifies leads, a configurator, a members area, a proof structure specific to how your market buys — then you need a layout and a content model built for that, and a template will be modified until it is a custom build at a worse price.

If you cannot name it, your website's job is to be credible, be found and be contactable. That is a job templates do well. Spend the difference on photography, copy and the advertising that brings people to it, all three of which will move your numbers more than a bespoke layout would.

We ask this question on discovery calls and it talks businesses out of custom work several times a year. That is the correct outcome when it happens.

'Custom' is a claim about who made it, not about quality

A custom build is not automatically fast, accessible, well structured or easy to maintain. It is automatically none of those things — each one has to be specified, built and measured. 'Custom' only tells you the work was made for you, which is a statement about provenance rather than about standard.

This matters because it is the main way custom projects disappoint. The client assumes they bought performance and conformance because they bought bespoke, and nobody wrote either down. So ask for the specifics: what performance budget will the site be held to, which WCAG level, measured with what, and what happens if it misses. On our own builds we hold a budget and publish it — 1.4 seconds average for Largest Contentful Paint and Lighthouse at or above 95 — precisely so it is a commitment rather than an adjective.

  • Ask for a performance budget with a number and a measurement method
  • Ask which WCAG conformance level, and who verifies it
  • Ask who else could pick this codebase up — a one-off nobody can read is its own lock-in
  • Ask what the content model looks like before you approve any visual design

The multipurpose theme is where most of the money goes missing

The worst outcome in this comparison is not a template and it is not a custom build. It is a multipurpose theme bought for its forty demos, modified heavily by several different people over two years, carrying a page builder and a dozen plugins that each add their own stylesheet.

You end up paying custom prices for a site you do not own the architecture of, with a performance ceiling you cannot raise and an upgrade path that breaks your layout. Every change costs more than the last one because each one is applied on top of the previous workaround.

If you recognise your current site in that description, the useful question is not 'template or custom' — it is whether a rebuild on a clean foundation now costs less than another two years of modifications. Usually it does, and the honest way to find out is to price both.

What we actually advise when the budget is small

Buy a good template, have someone competent install it, and spend the money you saved on the three things that will move your numbers more than the layout: real photography of your actual work, copy written by someone who understands what your buyers are afraid of, and whatever brings qualified people to the site in the first place.

Then revisit the site in a year with data. You will know which pages people land on, where they leave, and what they ask before they buy. A custom build commissioned with that information is a far better project than one commissioned from guesses — and you will be spending from revenue rather than from hope.

Honest scoping

When each one is the right answer

Choose a template if…

Speed, budget, known risk

  • Your budget is tight and being live and credible matters more than being distinctive
  • The site is small — roughly five to ten pages — and the content is straightforward
  • You are validating a new venture and do not yet know what the site needs to say
  • Your brand is not the thing that wins the sale; your price, your location or your referral network is
  • You need to be live in days for an event, a launch or a funding deadline
  • Someone competent will choose and install it and then change almost nothing. Most of the damage comes from the wrong template heavily modified, not from templates

Choose a custom build if…

Conversion, fit, longevity

  • Traffic already arrives and the problem is conversion rather than visibility — at that point the layout is the product
  • You have a flow no demo site has ever had: a quoting tool, a multi-step qualifying enquiry, a configurator, a members area
  • Brand distinctiveness is part of why people choose you over the alternative
  • You have a performance or accessibility obligation to meet and verify, not just an aspiration
  • You publish enough that the content model matters more than the homepage does
  • You expect the site to last five years and be extended repeatedly rather than replaced

Do this yourself

How to decide without a proposal

Five steps you can do yourself, in an hour, before you talk to anybody who is selling either option.

  1. Write what the site is for in one sentence

    Not 'to look professional'. Something you could measure: book more consultations, get enquiries from a second city, sell a catalogue, qualify leads before they reach a salesperson. If the sentence is about appearance, a template will satisfy it. If it is about a commercial mechanism, keep going.

  2. Count the pages and the content types

    Pages first, then the kinds of thing you publish: services, case studies, locations, products, team members, posts. Five pages and one content type is template territory. Four content types that cross-reference each other is a content model, and content models are what custom builds are for.

  3. Name the thing a template cannot do

    One specific capability, written down. A deposit payment at the end of a booking flow. Pricing that changes by trade account. A comparison table generated from a database. If you cannot name one, you probably do not need a custom build yet — and that is a useful thing to find out for free.

  4. Add the modification budget to the template price

    List every change you already know you want from the demo, honestly, including the ones you think are small. Get those priced as hours before you buy the licence. That total is the real comparison figure, and it is often much closer to a custom quote than anyone expects.

  5. Compare the two at year three, not at launch

    Add maintenance, the modifications you will accumulate, and the likelihood of a rebuild. A template that gets rebuilt in year two was more expensive than the custom build it replaced. A template that is still doing its job in year four was the better decision, obviously and by a wide margin.

If steps one to three all point at a template, buy a template. Our pricing page shows where our own tiers sit if you want to sanity-check the other side of the comparison, and the cost calculator will tell you roughly how complex what you are describing actually is.

Questions

The ones people actually ask

What comes up on calls about Custom website vs template. If yours is not here, ask it directly — you will get a straight answer rather than a brochure.

Ask a question

Is a custom website better for SEO than a template?

Not inherently. Search engines do not know or care whether a layout was bought or built. What they respond to — crawlable structure, fast loading, content that answers the question, clean internal linking, correct canonicals — can be done on either. The practical difference is that a bloated multipurpose theme makes the speed and structure work harder, and a custom build with no SEO specification can be just as bad.

Can you customise a template we have already bought?

Usually, yes, and we will tell you honestly whether it is worth it. The deciding question is whether your changes work with the template's assumptions or against them. Working with them is good value. Working against them means paying custom rates for a result that is harder to maintain than a custom build would have been, in which case we would rather say so than bill the hours.

How much more does a custom site cost?

We do not publish a multiple, because the honest answer depends entirely on scope — a five-page custom site and a forty-page custom site with a quoting tool are not the same project. Our tiers and what each includes are on the pricing page, and the cost calculator will show you which tier the scope you are describing tends to land in. The figure that matters is total cost at year three, including modifications and maintenance.

Will a custom site be faster?

It can be, and it is not automatic. A custom build has a higher ceiling because nothing is loading code you did not ask for, but only a build held to a measured budget actually reaches it. We publish ours — 1.4 seconds average for Largest Contentful Paint and Lighthouse at or above 95 — so it is a commitment with a number rather than a claim. Ask any vendor for the same thing.

What about accessibility?

Templates vary enormously and almost never document their conformance, so assume an audit and a round of fixes. A custom build can be built to a WCAG level from the first component, which is substantially cheaper than retrofitting, but only if it is in the specification. Neither approach is accessible by accident.

We outgrew our template. Is a rebuild the only option?

Not always. Sometimes the right move is to keep the platform and the content and rebuild only the templates that are holding you back, which preserves your URLs and your rankings. That is a redesign rather than a replacement, and it is often a smaller project than people assume. The test is whether the foundation is sound and only the layer on top is wrong.

Sources and currency

Everything this page says about a third-party platform was checked in October 2026. Plans, limits and feature sets change, so verify the specifics at the source before you commit money to a decision.

Keep going

The next decision along

Tell us the scope and we will say which one you need

Describe the site in a paragraph — pages, what you publish, and the one thing it has to do that a competitor's does not. We will tell you whether this is a template job, and we will tell you plainly if it is.

Get a straight recommendation+1 (520) 262-4954