Writing a web design brief for your small business? Here is what to include - from goals and audience to budget and pages - so you get the right result.
If you have ever had a conversation with a web designer that felt like it was going in circles, or received a quote that bore no relation to what you had in mind, the brief is probably where things went wrong.
A web design brief is not a bureaucratic formality. It is the document that stops you and the agency from talking past each other for weeks. It saves time, reduces the risk of expensive misunderstandings, and - done properly - usually results in a better website because the designer starts with a clear picture of what you actually need.
Here is how to write one that works.
A brief is a written summary of your business, your goals, your audience, and the requirements for your new website. It does not need to be a formal document with a cover page and appendices. A clear, honest email covers the essentials. What matters is that it gives the designer enough context to understand your situation before they start making decisions.
A brief should focus on outcomes rather than solutions. You do not need to specify fonts, column counts, or which CMS to use - those are the designer's job. What you need to specify is what you want the site to achieve and who it needs to serve. The how comes later.
Three to four sentences. What you do, who your customers are, and what makes you different. This is not a mission statement - it is a quick way to get the designer to the right starting point.
Include how long you have been running, roughly how many staff you have, and whether you operate locally, nationally, or internationally. These things affect what kind of website you need.
What do you want the website to do? Generate enquiries through a contact form? Sell products online? Explain your services to people who already know your name? Attract new customers through Google search?
A website that is supposed to generate leads looks and behaves differently from one that is primarily there to provide credibility for people who were referred to you. Be specific about the primary goal.
Go beyond age and location. Describe who your ideal customer is, what they know about your product or service when they arrive, what questions they need answered before they trust you, and what makes them choose one provider over another.
If you are not sure how to describe your audience, look at your best current customers and write a short description of them.
A typical small business website includes a homepage, an about page, a services or products section, and a contact page. You might also need a blog, a case studies section, a portfolio, a pricing page, or dedicated pages for individual services.
List every page you need. If you are not sure, describe what content you want to cover and let the designer suggest a structure.
Does the site need an online booking system? A product catalogue? A customer login area? Integration with your CRM? A multilingual option for different markets?
Anything beyond standard pages and a contact form is worth mentioning explicitly. These features affect the cost, the timeline, and sometimes the platform choice, so flagging them upfront prevents surprises.
Do you have a logo, brand colours, and brand fonts you want to carry into the new site? If so, include the files and specify that the design should work within your existing visual identity.
If you are starting from scratch - or if you think the brand itself needs work - say so. Some agencies offer branding and web design together, and it is a reasonable conversation to have at the start rather than when the wireframes are already built.
Share two or three examples of websites you like, with a brief note on what you like about each. It does not have to be from your industry. "I like how clean this one is" or "I like how this one leads you straight to the booking form" gives the designer useful information about your taste and priorities.
This is different from saying "make it look like this" - you are not asking them to copy. You are giving them reference points.
Many business owners resist putting a number in the brief, worried it will anchor the quote artificially high. The opposite is usually true. Sharing a budget range helps a designer propose something realistic rather than pitching an over-engineered solution you will have to scale back, or a stripped-down version that falls short of what you actually need.
If you are genuinely unsure what things cost, our guide to how much a small business website should cost gives a practical breakdown.
If you have a hard deadline - a product launch, an event, a trade show - say so upfront. It tells the designer whether the project is feasible in their schedule and helps everyone plan accordingly.
If you do not have a hard deadline, give a rough indication of when you would like to see the finished site. "Ideally before September" is more useful than silence.
Name one person as the primary contact who will give feedback and sign off on work. Projects that involve multiple stakeholders with no clear decision-maker tend to run late, go over budget, and produce watered-down results as competing opinions get resolved by adding things rather than making choices.
The most common delays in web projects come from two places: unclear requirements at the start, and missing content during the build.
On requirements: a brief that is specific about goals and audience eliminates a lot of back-and-forth. A designer who understands what you need from the outset can make better decisions and needs fewer approval rounds.
On content: if you write "TBD" next to the blog copy, the team photography, and the case studies, those items will become blockers. A good brief acknowledges what content exists and what still needs to be created, with a realistic plan for each.
A brief does not need to be perfect before you share it. You can share a draft and refine it through conversation. What matters is that you have done the thinking about what you need, rather than expecting the designer to work it out for you.
If you are evaluating which agency to work with, our piece on how to choose a web design agency for small business covers the questions worth asking and the red flags worth watching for.
How long should a web design brief be?
As long as it needs to be to answer the key questions - usually one to three pages. Shorter is fine if it covers the essentials. A brief is not a contract; it is a starting point for a conversation.
Do I need a brief before getting a quote?
Not always, but having one makes the quote more accurate. Without it, quotes often come back with a wide range because the designer is guessing what the project involves.
What if I do not know exactly what I want?
That is normal. Describe what you want the website to achieve and who it needs to reach. A good agency will help translate that into a structure and solution. The brief does not need to be a technical specification - it needs to be an honest account of your situation.
A web design brief for a small business does not have to be complicated. It has to be honest and specific enough that the designer understands what problem they are solving and for whom.
The time you spend writing a clear brief at the start of a project pays back many times over in fewer revisions, fewer misunderstandings, and a finished website that actually does what you needed it to do.
CyLizard works with businesses of all sizes across a wide range of industries, building websites that are designed around real goals - not just good-looking templates. If you are planning a new site or a redesign, get in touch. Think bold. Think smart. cylizard.com
