Compare your real pages with the demo
Template demos are carefully staged. Short headlines, matching photographs and evenly sized descriptions make a layout look settled. Replace those ingredients with your own before deciding. Try the longest service name, a portrait image, an unusually short description and the actual navigation labels. A promising design should still work when the content is ordinary.
Begin with three representative pages: the home page, the most important service or product page, and contact. Sketch what each must explain. Then compare that structure with the template. If you repeatedly need to remove half a page and invent the other half, the apparent shortcut may offer less value than expected.
Separate visual changes from structural changes
Changing colour, type, imagery and spacing can significantly alter a website while preserving its underlying structure. Rebuilding navigation, replacing a booking journey or creating a searchable catalogue changes how it works. Make two lists before asking for a quote. This makes the amount of adaptation visible.
Consider an illustrative example: a photographer wants project galleries, an about page and an enquiry form. A template already designed for those tasks may be a useful fit. A membership business that needs different account permissions, recurring bookings and member-specific content has a different problem. The important comparison is the journey each needs, rather than how expensive either homepage looks.
Inspect the experience beyond the first screen
Open the demo on a phone. Read an entire page. Navigate with the keyboard. Try the menu and every form state. Look for text that becomes too small, buttons that disappear without a mouse and motion that gets in the way of reading. A screenshot cannot tell you whether a design works through a complete task.
Check how headings, links and instructions are written. W3C guidance recommends meaningful headings and link text because they help people understand and navigate content. These details matter in both template and custom work. Neither purchasing a template nor commissioning a build automatically delivers an accessible website.
- Does the mobile version support the same important tasks?
- Can the layout handle your actual amount of content?
- Are required components included, or only shown as mockups?
- Does the licence cover your intended use and included assets?
Price the website after launch
Ask who will change text, add images and fix a broken integration. Include the work of replacing demo content, configuring forms, setting up redirects and checking the site on different screens. Compare the complete first release and its ongoing responsibilities, rather than the template price against the entire custom project.
Ownership matters too. Find out where the source lives, which accounts you control, what subscriptions are required and how you can export your content. A design that is inexpensive to buy can still be awkward to maintain if every small change needs unfamiliar software. Conversely, a custom build without clear documentation can create exactly the same difficulty.
Use a small trial to settle the choice
When the decision is close, adapt one representative page before committing to the whole website. Use approved copy and realistic images. Ask someone unfamiliar with the business to explain the offer and complete the main action. Record the confusing parts, then estimate the changes needed to fix them.
Choose a template when its structure supports the business and its constraints are acceptable. Choose custom work when the customer journey or content system needs a different foundation. A hybrid is also possible: keep a proven publishing system and build a distinctive interface around it. The best choice is the one you can explain in terms of useful work and manageable upkeep.