Last Updated: 16th July 2026
“We need a website that looks modern” is not a brief. It is a starting point for a conversation, but it gives a designer very little to work with. Knowing how to brief a web designer properly helps turn a subjective design exercise into a focused project that supports enquiries, sales, credibility and long-term growth.
A strong brief does not need to be a lengthy document full of technical language. For most small and medium-sized businesses, it needs to explain what the website must achieve, who it needs to serve, what information it needs to include and how decisions will be made. The clearer these fundamentals are, the less time is lost on assumptions, revisions and features that do not add commercial value.
How to brief a web designer: start with the business outcome
Begin with the reason for investing in the website. A new site may need to generate more qualified enquiries, make a service business look more established, sell products online, reduce repetitive customer questions or give a growing team a platform they can update easily. These are very different jobs, and they lead to different decisions about structure, content, user journeys and functionality.
Be specific about what success looks like. Rather than saying you want “more leads”, explain whether you need visitors to request a quote, book a consultation, call the office, complete an application or make a purchase. If the business has an existing website, share what is not working. It may be difficult to update, poorly structured on mobile, slow, unclear about your services or attracting the wrong type of enquiry.
Commercial goals should guide the design, not be added after the visuals are approved. A polished site that does not make the next step obvious can still underperform.
Give the designer useful business context
A web designer needs enough context to understand the business behind the pages. Explain what you do, where your revenue comes from, which services or products matter most, and what makes clients choose you over alternatives. This is not about producing a sales pitch. It is about identifying the messages a visitor needs to see before they trust you enough to get in touch.
Describe your priority audiences in practical terms. Who are they, what problem are they trying to solve and how much do they already know? A website aimed at procurement teams will need a different structure and level of detail from one aimed at homeowners looking for a local specialist. If you serve several groups, say which one should take priority when there is a trade-off.
It is also useful to be honest about where prospects hesitate. They may be unsure about pricing, timescales, quality, credentials or whether you cover their area. These concerns often point directly to the content, proof and calls to action the site needs.
Share your key messages and proof points
Provide the facts that substantiate your claims: qualifications, accreditations, years of experience, case studies, testimonials, awards, delivery process, guarantees or specialist capabilities. A designer cannot invent credible proof, and it is much easier to plan space for it early than try to force it into a finished layout.
If your organisation already has a logo, colour palette, photography, written tone of voice or brand guidelines, include them. Equally, flag anything that is off-brand or inappropriate for your sector. Clear boundaries help the project move faster without restricting useful creative thinking.
Define the scope without trying to design the site yourself
Your brief should identify the pages and functions you expect, but it does not need to dictate every layout decision. List the essential sections, such as core service pages, an about page, contact information, case studies, product categories, resources or frequently asked questions. Mark which are essential for launch and which could be a later phase.
Then describe the functionality in plain English. For example, you may need an enquiry form that routes messages to the right person, a booking request process, a searchable product catalogue, an online payment option, a members-only area or integrations with an existing business system. The designer or developer can advise on the most suitable technical route once they understand the purpose.
Be careful not to treat features as automatic improvements. A complex animation, custom calculator or extensive filtering system can be valuable when it solves a real user need. It can also add cost, maintenance demands and potential points of failure. The right question is not “Can the website do this?” but “Will this help visitors take the action we need?”
Bring examples, but explain what you like about them
Examples are useful when they give direction, not when they become a request to copy another business. Share a small selection of websites you admire and explain why. Perhaps the navigation is clear, the service pages feel authoritative, the photography is strong, or the purchase journey is straightforward.
It is just as helpful to show examples that miss the mark. You may find them too corporate, overly busy, difficult to read or too reliant on generic imagery. These observations give a designer insight into your preferences while leaving room to create a site that fits your own business.
Remember that a website is judged on more than desktop appearance. A good brief should recognise mobile use, page speed, accessibility, search visibility and ease of updating. An attractive layout that is awkward on a phone or difficult for your team to manage is not a finished solution.
Plan content early, not after design approval
Content is one of the most common causes of website delays. Before work begins, agree who will provide page copy, service details, images, product information, legal text and approvals. If content needs to be written or refined, establish this as part of the scope rather than leaving blank sections until the final weeks.
The quantity and quality of available material affects the design. A service page with detailed expertise, customer outcomes and clear next steps can support a richer layout than a page containing two short paragraphs. Original photography can make a substantial difference too, particularly for businesses where people, premises, projects or products build trust.
It is sensible to share existing materials even if they are imperfect. Brochures, presentations, proposals, customer questions and internal documents can reveal useful language and detail. They also help prevent important information being missed simply because it was not obvious in an initial meeting.
Set technical, SEO and support expectations
A website brief should cover the practical requirements that sit behind the design. State whether you need WordPress, whether the site must work with existing systems, who owns the domain and hosting arrangements, and whether there are any security, compliance or accessibility expectations specific to your business.
If your current site has useful pages that already appear in search results, make this clear. The project may need a considered migration plan, page redirects and preservation of established content rather than a simple replacement. Search performance is built into a site’s structure, content and technical foundations, so it should be considered from the outset.
Also discuss what happens after launch. Some businesses want their team to make routine updates. Others prefer an agency to handle maintenance, security updates, troubleshooting and ongoing improvements. Neither approach is universally better. It depends on internal capacity, the complexity of the website and how critical it is to day-to-day operations.
Agree the decision-making process before work starts
Many projects slow down because feedback arrives from too many people, too late. Name one main contact and identify who has final approval. If directors, colleagues or external partners need to contribute, agree when they will review the work and how comments will be consolidated.
Constructive feedback is tied to the agreed goals. “This section does not make our priority service clear” is actionable. “I do not like it” may be true, but it does not tell the designer what needs to change or why. Where opinions differ, return to the audience and desired action rather than personal taste.
A good brief should also set a realistic budget range and target launch date. These details let the agency recommend an appropriate level of design, functionality and phased delivery. A fixed deadline may be achievable, but only if content, approvals and technical access are available when needed.
Avoid these briefing mistakes
A few issues repeatedly create avoidable friction:
- Treating the design as separate from business goals and customer behaviour.
- Providing a long wish list without identifying what is essential for launch.
- Leaving content ownership and approval responsibilities unclear.
- Requesting a replica of a competitor’s website rather than explaining the outcome you want.
The best brief is not the one with the most pages. It is the one that gives your designer enough clarity to make informed recommendations, challenge weak assumptions and build a website that earns its place in the business.
If you can explain your audience, priorities, proof, practical requirements and decision process, you have given the project a sound foundation. From there, the conversation can focus on creating a website that is not merely new, but genuinely useful to the people you need it to reach.
Have your say