A website template looks finished before you enter your first paragraph. It has suitable images, short headings and a tidy offer list. Your real content reveals the decisions the template has not made for you.

A builder can be a useful foundation. The question is who handles content, design and technical setup. An agency may also use a builder, so the terms do not describe a simple either-or choice.

Decide what work you want to do

For your decision, a task list can cover the work from explaining the offer through copy, images and page creation to a checked enquiry flow. You can mark what your team can and wants to handle, who will maintain the site and who responds when something fails. This reveals which work you still need to commission.

An existing template may help if you have the time and a suitable scope. If structure or service explanations remain unclear, an editor will not resolve them automatically. An agency quotation should identify that work and its outcome.

Also consider the support you expect. A technical help centre may explain how a system works. It does not automatically design your service page or determine what customers need to know before enquiring.

Build a real sample instead of relying on the demonstration

You can try the template with a representative page containing your own material, such as the longest service name, necessary price information and an existing image. Viewing it on a phone then shows whether the order still makes sense with that real content.

A page that does not fit neatly into equal-length cards is particularly useful for this trial. If your services have different prerequisites, the template needs room to explain them and a workable way to maintain those details consistently.

Complete the contact flow too. What message reaches the team? What does the sender see after an error? Which data goes to an external service? An attractive preview does not demonstrate those connections.

Check functionality and future constraints

Necessary extensions, recurring charges and work that would need repeating after a system change all belong in your actual scope. Knowing these items lets you compare a configured website with the equivalent self-build rather than an empty entry-level plan.

Test export separately. WordPress documentation, for example, describes exporting content data in WXR format. Content data differs from a complete website that can run on any other system. Ask the proposed provider to show exactly what is exported.

Also establish who manages domains, accounts and licences. If an agency handles setup, the quotation should explain what you can edit afterwards and where continued assistance is needed.

Choose between defined divisions of work

The sample page and task list together reveal which work remains. Once you know who handles each task, whether the quotation includes it, and what recurring charges and later changes involve, you have a basis for comparing self-build with commissioned implementation.

An existing sample page is useful when enquiring about a new website or shop: it shows what already works and which tasks you want to hand over. If you only need individual designs or templates, see the focused work under web design.