Start with the people the site needs to serve: a prospective customer assessing capability, a partner considering a relationship, or another stakeholder looking for approved company information. The project identifies their different questions and the pages that answer them. We review existing company material, real work and the current site before proposing a useful information architecture. A larger company description is not automatically a better answer to a specific purchasing question.
The selected engagement can include content planning, a coherent visual system, responsive company and capability pages, genuine project presentation, leadership or resource content, CMS controls and enquiry implementation. An established site adds an inventory of useful material, addresses and working journeys to preserve. Writing, initial content entry, photography and other asset preparation have an agreed extent, with the business approving facts and permitted uses.
The first contact step is part of that design. The receiving team can often assess an initial outline before asking for a detailed specification. We agree which non-sensitive facts help establish fit, what the visitor should leave out, and how a later information exchange is arranged. If the project requires an authenticated portal or controlled document submission, that is a separate, explicit function with its own access and handling requirements. A corporate page and an upload control alone do not establish an appropriate confidential channel.
