Start with what needs to change
A new website is rarely the goal by itself. The useful question is what the business needs the website to do differently: make a service easier to understand, help a customer find a product, or remove friction from an enquiry.
Describe the problem in ordinary language. A clear business objective is a better starting point than a long list of features copied from another website.
Name the people who will use it
Think beyond visitors. Who will publish content, update products, answer enquiries, and maintain the system? Their everyday tasks should influence the architecture as much as the visual design.
A beautiful page that is difficult to edit is not a finished solution. Include the internal team's needs in the original brief.
Separate essentials from possibilities
Make two lists: what must work at launch and what could follow later. Identify existing integrations, content that is ready, and anything that still needs an owner.
This makes trade-offs visible and gives the scope a useful boundary. Timing and pricing become easier to discuss when everyone is describing the same deliverable.
Bring context, not perfection
An existing website, a few references, a description of the audience, and honest constraints are enough for an initial conversation. The brief does not need to be polished. It needs to be specific enough to ask better questions.