Start with the action, not the page count
A website brief often starts with a list of pages. A more useful starting point is the action a customer needs to take: understand a service, compare an option, ask a question or begin a purchase. Page structure, content and development should support that action.
For a service business, map a typical enquiry from the first visit to the first sales conversation. Note what information the visitor needs, what the form asks and who receives the result. This shows where design and operations need to connect.
Plan the enquiry handoff
A form is only the beginning of enquiry handling. The record needs a clear destination and a person responsible for the next step. The website should also confirm receipt accurately, preserve the enquiry if confirmation fails and offer another way to contact the business.
- Collect enough information to understand the request, without asking for unnecessary details.
- Record the service interest and appropriate source context.
- Assign the enquiry and record its status and next action.
- Distinguish a saved enquiry from a successful email notification.
Treat trust and accessibility as part of the journey
Clear service descriptions and real project examples help a visitor evaluate fit. A useful case study explains the business context, the delivered work and the limits of what is known. Unsupported metrics make the evaluation harder.
The same journey should work on a small screen and with a keyboard. Labels, visible focus, readable contrast and clear error messages help people complete the action. Content should remain available when an animation or enhancement fails.
Agree what happens after launch
Before launch, identify who owns the domain, hosting account, content updates and form destination. Decide how maintenance requests and access changes are handled. A redesign also needs a plan for important existing URLs and redirects.
Useful measures include completed enquiries, enquiry quality and the ability to act on them. Traffic is context; it is not a substitute for knowing whether the website supports the intended business task.
A practical website brief
- Describe the business and the customers it serves.
- Name the primary action and the information needed before it.
- List required pages, assets and integrations.
- Map who handles enquiries and ongoing changes.
- Agree acceptance checks for mobile layouts, forms, accessibility and launch.
For accessibility guidance, see the W3C forms tutorials.