HOUSE 813 | NOTES ON BRANDING / 08 | WEBSITE

Planning a business website: pages, content and enquiry paths

Planning a business website: pages, content and enquiry paths

A website brief often starts with a page count: five pages, eight pages, a homepage and a contact form. That describes the size of the build, but not what the website needs to do. A better starting point is the visitor: what do they need to understand, and what should they be able to do next?

A website brief often starts with a page count: five pages, eight pages, a homepage and a contact form. That describes the size of the build, but not what the website needs to do. A better starting point is the visitor: what do they need to understand, and what should they be able to do next?


Illustration of a website plan with a service page, content notes and an enquiry button.

Before choosing a layout, map the questions your website must answer. Then decide which pages, content and enquiry routes will answer them. This makes the design brief more useful and helps separate essential work from features that can wait.

Give the website a clear job

Write down the main action the website should support. It might be an enquiry about a service, a booking request or a conversation about a project. Choose the action that fits how your business actually sells, rather than adding every possible button.

Next, identify what someone needs to know before taking that action. A visitor comparing service providers may need to understand the offer, see relevant work and learn what happens after they get in touch. Someone checking a local business may first need its location and opening information.

These are different journeys. A useful brief names the important ones instead of treating every visitor as someone who will read every page in order.

Plan pages around questions, not a template

List the questions first: what do you offer, who is it for, what can you show, how does the process work and how can someone enquire? Group related answers into pages with clear names.

A small business might use Home, Services, Work, About and Contact. That is an example, not a required five-page formula. Separate service pages can make sense when the offers answer different needs and each has enough useful content. Creating near-identical pages just to increase the count does not make the site more helpful.

Draw a simple page map, then add the links a visitor needs between those pages. A service page might lead to a relevant project and then to an enquiry. A map shows the structure; the labels, content and navigation still need their own decisions.

Prepare real content before polishing the layout

For each page, name its purpose, main heading, key information, supporting images and next action. Mark who will supply the content and who can approve it.

Gather approved identity files, accurate service descriptions, usable photographs and work you have permission to show. Check names, captions, contact details and any claims about the business. A template testimonial or an attractive placeholder is not evidence about your company.

Use real copy early. A layout designed around a short sample headline can change when the actual explanation arrives. If writing, photography or editing is part of the project, include it in the scope rather than assuming the website build covers it.

Make the enquiry path work from beginning to end

Choose the right route for the action: a form, an email link, a phone number or a booking tool. Give the button a label that describes what happens next. "Discuss your project" and "Book a call" set different expectations.

For a form, ask for the information needed to handle the enquiry. Agree which fields are required, where submissions go, who checks them and what the visitor sees after submitting. Decide what happens if an upload fails or a required field is missed.

Test the full route on a phone as well as a larger screen. A working button is only the beginning. Check that the destination opens, the form can be completed, the submission reaches the right place and the business has a plan to respond. Use an agreed test enquiry rather than a real customer's details.

Separate launch needs from ongoing needs

Decide what must be editable after launch. A changing portfolio or a regular blog may need a content collection and an editing handover. A fixed information page may have different maintenance needs.

Record domain, hosting, paid tools, account ownership and renewal responsibilities separately. Agree who maintains the content and who handles future changes. Basic search setup is a foundation, not a promise of a particular ranking.

At House813, website scope varies by page count, content needs and enquiry features. The useful question is not which package has the most pages. It is which scope supports the visitor's journey and leaves the business able to use the website after handover.


Example website journey from a visitor question through a service page and supporting work to an enquiry.

Bring a brief that can be discussed

Start with the website's main job, the questions it must answer, a draft page map, a content list and the enquiry route. Add the features you need at launch and those you can leave for later.

That is enough to have a practical conversation about scope without pretending every detail is settled. Explore House813 and share what your website needs to help people understand and do.

HOUSE 813 / NOTES ON BRANDING 08

Website