What you pay for
Templates feel like a bargain because the price tag is visible and the alternative isn't. The visible cost, eighty dollars, a year of hosting, two hours of setup, is what gets compared on the spreadsheet. The invisible cost is paid quietly, page by page, for as long as the site is live.
The first invisible cost is sameness. A template's job is to flatter many businesses with one structure. The work that goes into making the structure feel custom, the photography, copy, color, and layout adjustments, is exactly the work the template removes. What remains is a hero with a stock photo and a three-column features grid, and the same hero and grid sit on a thousand other sites in the same trade.
A template's job is to flatter many businesses with one structure. The work that makes it feel custom is exactly what the template removes.
The second tax
The second invisible cost is plugin debt. Templates assume the worst about their owners: that they'll want to add a slider, a popup, a chatbot, a cookie banner, an analytics widget, and a holiday-themed snow effect. Each is one plugin. Each plugin is one more network request, one more dependency to keep updated, one more thing that can break six months from now during a routine update on a Tuesday.
We measure plugin debt the way a building inspector measures load. A site with twelve plugins is not twelve times as risky as a site with one. It's closer to forty times as risky, because the interactions between plugins are where breakages live. Templates encourage plugin accumulation. Custom builds resist it by design.
Speed as a brand
The third invisible cost is the easiest to demonstrate: speed. Templates are heavy. Their authors don't know what features any given user will need, so they ship them all. A typical small-business template loads two to three megabytes of code and assets before the page is interactive. A custom site for the same business, designed for what that business actually needs, loads two hundred kilobytes.
On a phone in a parking lot with two bars of LTE, that's the difference between a customer who stays and a customer who leaves. We talk about that gap as if it's a technical performance issue, but it isn't really. It's a brand issue. Fast sites feel like the business that owns them is paying attention. Slow sites feel like the business doesn't care, or worse, doesn't know.
What custom buys
Building from scratch is not always the right answer. There are businesses for whom a good template, well-photographed and lightly customized, is exactly what's needed. We're happy to recommend that path when it fits.
What custom buys, when it does fit, is the absence of a hidden bill. A site built for the specific decisions of one business doesn't pay sameness tax, doesn't pay plugin debt, and doesn't pay weight. It pays once, up front, and then it works. The math, when you write it out fully, almost always favors the bill you can see.
Ryvoka Studio · April 14, 2026