Describe the job the website needs to do
Start with the people who use the site and the task you want them to complete. Explain what the business offers, how customers currently find it, and what happens after someone gets in touch.
If you already have a website, share its URL and point to specific issues. “The enquiry form does not ask which location a customer needs” is more useful than “the site needs to be better.”
Use a few straightforward questions
You do not need to specify every technical detail before talking to a developer. A short brief can start with these questions.
- Who is the website for, and what should they do?
- What works now, and what is causing problems?
- Which pages, products, or workflows are essential?
- Which existing systems does the site need to connect to?
- What is ready, who makes decisions, and when is it needed?
Agree on what completion means
Name the concrete things you need to be able to do when the work is finished. That might be editing a service page, routing enquiries to the right team, or publishing a new product without custom development.
These practical acceptance criteria give the project a clear destination and make the final review more useful for everyone involved.
Explore the related website service
Tell me about your project