A template gets you live by Friday. The bill for that speed arrives later — a little more each time you try to change something the template never expected you to change.
Every product starts with the same tension: move fast, or build something that holds. Off-the-shelf themes and page builders win the first round easily. They are cheap, they look finished, and they turn a weekend into a launch. For a leaflet-style site that will never really change, that is often the right call — and an honest studio will tell you so.
The trouble starts when the product has to grow. A template is a set of decisions someone else made for an average customer who is not you. The moment your needs diverge from that average — a booking flow with its own rules, an integration nobody anticipated, a content model that doesn't fit the boxes — you are working against the tool instead of with it.
The tax you don't see on the invoice
Bespoke software front-loads the thinking. You pay for the discovery, the data model, the interface designed around your actual workflow rather than a demo. In exchange, the second, third and hundredth change stay cheap, because the system was built to be changed.
Templates invert that curve. The first change is free — it's what the builder is for. But each customisation past the happy path piles workarounds on workarounds, until a five-minute request becomes a two-day archaeology dig through someone else's plugin stack.
The cheapest software to build is rarely the cheapest software to own.
What "built to last" actually means
Durability isn't about writing more code. It's about a few unglamorous disciplines that compound over years:
- A data model that matches reality. Get the nouns and relationships right and most features become small. Get them wrong and every feature fights the schema.
- Boring, obvious code. The next person to touch it — often you, eighteen months from now — should be able to read it without a guide.
- Tests where they earn their keep. Not coverage theatre; a safety net around the parts that would hurt to break.
- No lock-in you didn't choose. Ownership of the code, the data, and the ability to walk away from any single vendor.
When a template is still the right answer
Bespoke is not a religion. If the site is small, static, and unlikely to change, a good template shipped this week beats a custom build shipped next quarter. The skill is knowing which project you have. Teams like Free Range Websites have made a craft of matching the approach to the job rather than selling the same answer to everyone.
For a longer view on the trade-offs behind maintainable systems, the writing of Martin Fowler remains a reliable starting point.
The real question
Don't ask "template or bespoke?" Ask "how much is this going to change, and who pays when it does?" If the honest answer is a lot, and us, then the up-front cost of building something on purpose is the cheaper number — you just see it sooner.
That's the whole case for bespoke. Not that it's fancier. That it's still yours, still legible, and still cheap to change on the day the thing you didn't plan for finally happens.