Canonical: https://1968labs.com/blog/template-vs-custom-website > A practical comparison of template and custom websites: customer journeys, ownership, launch checks and first-year costs. [← All guides](https://1968labs.com/blog) Website planning # Template vs custom website: compare the work, not just the look A practical comparison of template and custom websites: customer journeys, ownership, launch checks and first-year costs. 1968 Labs / 22 September 2026 / 3 min read A template gives you an existing layout to adapt. A custom website starts from your business’s content and customer tasks. Either can be effective; the right choice depends on how much of your actual work fits the starting point. **Our recommendation** Use a template when its structure already fits and your team can maintain it. Consider custom work when the important customer journey keeps requiring workarounds. Ask for a demonstration of that journey before comparing visual polish. ## Compare the same scope | Question | Template route | Custom route | | --- | --- | --- | | Layout | Choose a strong starting design and adapt its components. | Design around your content, brand and required journeys. | | Content | You still need suitable copy, images and approvals. | Content planning may be included; confirm who writes and supplies it. | | Inquiry flow | Check the included form against the fields and handoff you need. | Specify the field logic, delivery and failure behavior in the scope. | | Editing | May have an established editor; try a real change yourself. | Agree an editing system and handover that suit the team. | | Costs | Include setup, licenses, plugins and ongoing changes. | Include build, hosting, integrations, support and ongoing changes. | ## Try one difficult customer task Pick the request your current site handles poorly. A print shop might need quantity, finished size, artwork readiness and a delivery deadline. A cabinetmaker might need the room, rough dimensions and project timing. Those are different forms even if both websites have five pages. Test how the proposed template handles that task on a phone. Does it carry the selected service into the inquiry? Can someone answer “not sure”? Can the team read the resulting email without visiting several dashboards? A small prototype will reveal more than a collection of homepage screenshots. Use the [print job brief](https://1968labs.com/resources/print-job-intake-template) or [cabinetry project brief](https://1968labs.com/resources/cabinetry-project-brief) to specify the required information before you ask for a quote. ## Separate design from delivery quality Custom does not automatically mean accessible, fast or easy to edit. A template does not automatically mean generic or unsuitable. Ask both providers how they test the navigation, forms, mobile layout and keyboard operation, and what happens when something fails. Compare the deliverables in writing: pages, content responsibility, revisions, integrations, redirects, launch checks, ownership and support. “SEO included” needs a list of actual work. “Responsive” needs evidence from the pages you will launch. ## Compare first-year and ongoing cost Use the [website quote comparison tool](https://1968labs.com/resources/website-quote-comparison) to total the amounts in two real proposals. Enter the setup fee, monthly and annual charges, and known one-off extras. Keep unknown items separate rather than treating a missing price as free. The lower total is not automatically the better choice. A cheaper proposal that omits content migration or inquiry delivery may need extra work before launch. Equally, a custom build with features your team will not use can add avoidable cost. ## Agree the handover before choosing Confirm that the business will own the domain and required accounts, receive the agreed source or content exports, and know how to request changes. Use a [handover checklist](https://1968labs.com/resources/website-handover-checklist) to make those responsibilities visible. For a focused custom build, see our [website scope and starting price](https://1968labs.com/services/websites) . If the existing design is already doing its job and only the inquiry breaks, a [form repair](https://1968labs.com/services/contact-form-repair) may be a smaller, more useful engagement. ## Keep reading. Website planning ### Catalog website vs ecommerce: which does your business need? Compare a product catalog with a quote request against an online store. Choose around pricing, availability, product selection and order handling. Read the guide [View Catalog website vs ecommerce: which does your business need?](https://1968labs.com/blog/catalog-website-vs-ecommerce) Website planning ### Website redesign SEO checklist: what to keep, change and test Plan a small business website redesign with a page decision sheet, redirect checks, launch acceptance criteria and a useful post-launch review. Read the guide [View Website redesign SEO checklist: what to keep, change and test](https://1968labs.com/blog/website-redesign-seo-checklist) ## Put this into practice. [Websites](https://1968labs.com/services/websites) [Website quote comparison](https://1968labs.com/resources/website-quote-comparison) [Studio work](https://1968labs.com/work) Work with us ## Discuss the changes your website needs. Tell us what you’re trying to improve. We’ll reply within 24 hours. [Services and starting prices](https://1968labs.com/services) Form fields: Your name; Your email; Phone number; Your question. [Use the form on the website.](https://1968labs.com/blog/template-vs-custom-website)