Explain the business. Build a website your team can use.

A business website should explain what you provide, who it serves and how someone can begin a useful conversation. We start with those questions, the material available and the systems already in use. A preferred visual reference can help, but it does not replace the page plan or the facts the business needs to approve.

The scope can bring together information structure, copy organisation, visual design, responsive development, CMS controls and enquiry paths. Supporting work such as a catalogue, resource collection or selected integration is identified explicitly. A public website and a private customer workspace may connect, but they have different users and responsibilities.

Your proposal should make the release understandable: which pages and templates are included, what the business supplies, which functions are being implemented and how each is accepted. We discuss implementation options after that scope is clear.

Ask an editor to describe the updates they expect to make after launch: adding a service, changing a contact detail or replacing an approved image. Some facts belong in a shared setting; other content needs a page-specific explanation. Those choices affect the CMS and the effort required to keep the site coherent.

Agree who can prepare a change, who approves it and what the preview represents. A draft review should identify the exact content being accepted. Include time for the receiving team to check contact details and enquiry handling, rather than treating a visually finished homepage as the whole release.

Imagine a business approving a new telephone number. The header is updated, but an older number remains inside two service pages and a contact button still opens the previous destination. The website looks consistent until someone follows the affected route.

During planning, identify which contact facts should have a shared source and which need a specific local explanation. Review an ordinary update through the CMS and follow its affected buttons as well as reading the visible text. The acceptance case is a consistent approved change across the agreed website scope.

This is a hypothetical editing example, not a Washington DC client incident or a claim that every item of website content should be centrally controlled. It illustrates one decision within the wider design and development service.