Put real content into the template first
Choose a template when the actual content and interactions fit its underlying structure. Choose custom design when important, recurring requirements would force the team to dismantle that structure. The deciding factor is not whether the preview looks familiar. It is how much of the purchased foundation survives implementation.
A template can be an efficient starting point for a clear service site, a bounded campaign or an established content pattern. A custom site can be wasteful if the same outcome was already available with modest configuration. Clodron's perspective as a studio does not change that arithmetic.
Separate visual changes from structural changes
Replacing colours, typography and photography is different from changing how content is related or how visitors complete a task. A visual adaptation may leave the template intact. A new permissions model, comparison workflow or editorial hierarchy can require a different foundation.
List each requested change beside the part of the template it touches. If the same shared component needs incompatible behaviour on different pages, the apparent shortcut may become a private fork. Future updates then have to be reconciled with those changes.
The reverse also matters: custom does not mean inventing every button. A sensible custom project reuses reliable foundations while shaping the information architecture and interactions around the actual problem. Paying for originality in invisible commodity work is not a brand strategy.
Test the states the demonstration omits
Preview pages tend to contain ideal images, short headings and complete content. Replace them with long German labels, Turkish copy, missing images, validation errors and realistic mobile content. Check what happens when a section is removed rather than merely filled.
Our guide to designing for different languages explains why text must be allowed to change the layout predictably. A template that only works with the demonstration's sentence lengths is not ready for multilingual publication.
Accessibility also needs evaluation on the assembled site. The W3C evaluation methodology treats representative sampling and complete processes as part of assessment. A polished component gallery is not evidence that the actual enquiry or purchase journey works.
Compare delivery and maintenance together
A template quote should include the licence terms, allowed modifications, required extensions and ownership of future updates. A custom quote should include reusable patterns, editorial controls, testing and documentation. Compare functioning outcomes, not a template purchase against a fully supported application.
Ask who maintains an altered component and whether a later maintainer can distinguish vendor code from project changes. For custom work, ask whether routine content changes remain independent of engineering. Both routes can become expensive through unclear ownership.
Our web platform service is relevant when the required behaviour or content structure warrants that extra design and engineering. It is not necessary merely to avoid recognising a layout used elsewhere.
Run an exception audit this week
Pick the candidate template and populate the pages that are hardest to represent, using approved text and realistic media. Walk through the main task with a keyboard and a narrow screen. Record structural changes separately from cosmetic adjustments.
Keep the template if the important flows work and the remaining changes preserve its foundation. Choose custom when exceptions dominate the core experience, not the decorative edges. Ask for a working prototype of the hardest exception before approving the larger build. That evidence makes the decision more useful than either a low sticker price or a promise of complete uniqueness.