Before a website rebuild, gather the right things.

Start with what has changed. Perhaps the business offers a different service now, the work has become more focused, or the site no longer sounds like the people behind it. Write that change in a few sentences before collecting visual references. It gives the project a reason to exist.

Describe the person the site needs to help. What are they trying to understand? What might make them hesitate? What should they be able to decide after a visit? A specific visitor and a specific decision give the pages a useful job.

Gather evidence you can actually use. Choose photographs of real work, clear service descriptions, and project examples you have permission to publish. Keep the context with each example: what the visitor is looking at and why it matters. Leave out results you cannot support and client comments you do not have permission to share.

Choose a next step that fits the work. A portfolio might lead to a conversation about a collaboration. A specialist service may need a location, a description, and photographs before an estimate is possible. Ask for enough information to make the first exchange useful without making the visitor do the whole project brief at once.

Bring a short list of references, with reasons. A reference is more useful when you can say what you notice: the pace, the writing, the way images are presented, or how easily you found something. The aim is to explain a direction, not to assemble someone else's website.

Finish with the practical boundaries. Note the timing, budget range, people involved in decisions, and any content or account access still missing. A brief can contain open questions. Naming them makes it easier to decide what needs attention first.

You do not need polished copy to start. A rough account of the business, a few strong examples, and an honest description of what needs to change are enough for a useful first brief.