Most businesses do not go looking for a custom website. They go looking for a reason their current site is slow, awkward to edit, and quietly losing enquiries. The answer is usually the same: it was built for a business that no longer exists, and every change since has been a workaround.
So here is the honest version of the template versus custom decision, including the cases where a template is genuinely the better buy.
What a template actually costs
A theme is cheap on the day you buy it. The bill arrives later, in three places.
- Weight you never asked for. Themes ship the code for every feature they advertise, not the handful you use. The page builder, the slider library, the icon set, all of it loads whether you touch it or not.
- Edits that need a specialist. Changing something the theme did not anticipate means working against the theme. A change that should take an hour turns into a quote.
- A ceiling on integration. Wiring a real CRM, booking flow, or inventory system into a theme designed for brochure pages is where most projects quietly stall.
None of that appears in the purchase price. All of it appears in year two.
Pretty websites do not win markets. Performing ones do.
Where custom websites earn their price
Speed you can actually measure. Google treats a Largest Contentful Paint under 2.5 seconds as good, and page experience feeds into how your pages rank. Custom websites hit that mark for a boring reason: nothing loads that does not need to.
A structure that matches how you sell. If your business turns on quote requests, the whole site should be built around getting a good quote request. Templates organise your content around their layout. Custom websites organise it around your revenue.
Room to grow without a rebuild. Adding a portal, a second language, or a payment flow should be a feature, not a replatform. That is a decision made in the architecture, long before anyone picks a colour.
Search visibility built in, not bolted on. Server rendered content, one clean heading structure per page, canonical tags, and structured data that search engines can read. See how we handle SEO and digital marketing alongside the build rather than after it.
On a custom build, a page that needs live data fetches exactly that data on the server and sends finished HTML to the browser:
1// app/quotes/page.tsx2export default async function Quotes() {3 const quotes = await db.quotes.recent({ limit: 20 })4 return <QuoteTable rows={quotes} />5}_