Start with the next action
A website brief becomes more useful when you can say what visitors should do next. That might be requesting a quote, booking a consultation or exploring products. Pick the primary action, then identify the information someone needs before taking it. A clearer decision at this stage makes page structure and design reviews easier.
Collect the content you already have
Gather your service descriptions, product information, contact details, brand files and approved photographs. Mark what is current and what needs rewriting. You do not need polished copy for every page to start a conversation, but an organised content inventory helps reveal the real scope of the project.
Describe the jobs behind the pages
Think beyond the homepage. Who will update a service? Where does a form enquiry go? Will a customer need an account? Which systems must connect to the website? These operational questions often influence the technical approach more than a preferred colour or animation does.
Separate essential features from later ideas
Write two lists: what the first release needs and what could follow. A clear first release is easier to review and launch. Useful later ideas can remain in the plan without becoming dependencies for every design decision. Discuss the expected timeline and budget alongside both lists.
Agree on review and handover
Identify who can approve content and design, and how feedback will be collected. Before work begins, ask what the handover includes: files, editing guidance, access, training and any ongoing support. A project finishes more smoothly when those expectations were discussed at the start.
We can turn these questions into a practical conversation about your business.
Talk to the studio
