A website brief should make decisions easier. You do not need to arrive with a technical specification or a folder of perfect references. Start with the people who will visit, the problem they want to solve, and the action that would make the visit worthwhile. Those three answers give design and development a direction.
Choose one job for the first visit
Imagine a customer discovering your business for the first time. Should they book an appointment, compare products, request a quote, or understand a specialist service? Pick the most valuable action and make the route to it clear. A site can support several goals, but every page should have a reason to exist.
A local repair business, for example, may need a clear service area and a quick enquiry more than a large catalogue. A consultant may need a convincing explanation of their work and a small number of relevant examples. Begin with the decision your visitor faces, not the number of pages you think a website ought to have.
Gather the material that builds confidence
List what a visitor needs before taking that action: the service, who it is for, how it works, and what happens next. Collect your real logo, contact details, product photographs, and any work you are permitted to share. Where information is missing, write down who will provide it.
Content is part of the design. A layout built around a short promise will behave differently when the final text is three paragraphs long. Even rough, accurate copy is more useful than polished placeholder text.
Separate launch needs from later ideas
Make two lists: essential for launch and useful later. An appointment request may be enough initially; live availability and automatic reminders add a different level of complexity. A product catalogue and a working checkout also have very different operational requirements.
For each feature, identify the person responsible after launch. Who updates stock, responds to enquiries, or corrects opening hours? Planning those tasks early helps keep the website useful when the project is finished.
Agree on what ready means
Define a short acceptance checklist before choosing a launch date. It might cover the enquiry journey, mobile navigation, readable content, working external links, and the ability to update key information. Include time to test on a real phone.
Share a budget range and a target date, then ask which scope is realistic within them. A smaller, complete experience gives visitors a clearer path than a larger site with unfinished sections. In Build Yours, your choices become the starting point for that conversation.
Before you build
- Name the main visitor and their next action.
- Gather accurate content and official brand assets.
- Separate essential features from later improvements.
- Agree on launch checks and ongoing responsibilities.