1. Name the problem
Describe what is difficult today in plain language. “Enquiries are getting lost between our website and our team” is more useful than “we need a modern system.” A concrete problem helps guide design and implementation decisions.
2. Identify the people involved
Think about both sides of the experience: the person using the website and the team working behind it. Their tasks, devices and information needs shape the flow. A beautiful form is less useful if nobody owns the response.
3. Agree the first complete outcome
Choose a first version that completes a useful journey. Define what the visitor can do, what the system records and what the team does next. Keep later ideas in a separate list so the first launch has a clear purpose.
4. Make ownership practical
Agree who supplies and approves content, who owns the domain and hosting accounts, and who will maintain the website. List the integrations that need credentials or provider approval. Sorting this out early reduces avoidable launch delays.
5. Define how you will review it
Use real tasks to review the work. Can a visitor find the right service on a phone? Does an enquiry save correctly? Can the team find it and follow up? These checks are easier to assess than a general request to make everything feel more premium.
A good project brief connects a clear business problem to a complete first outcome, with named owners and useful checks.