How to Brief a Web Designer: A Business Owner's Guide

Most web design projects that go wrong don't fail because of bad design. They fail because the brief was bad — vague goals, missing details, and a budget conversation that never happened.

If you're wondering what to tell your web designer before starting a project, this guide answers that question from your side of the table.

Knowing how to brief a web designer is the single most valuable thing you can do before a project starts. A clear brief saves weeks of revisions, protects your budget, and gives your designer a real chance to build something that works for your business.

What a Web Design Brief Actually Does

A web design brief is not a wish list. It is not a template you fill in and forget. It is a thinking tool that forces you to answer questions you haven't asked yourself yet.

Before a designer writes a line of code or sketches a layout, they need to understand what your business does, who it serves, and what the website needs to achieve. That understanding comes from you — not from your logo file or your old site.

A good brief does three things: it aligns you and the designer on what success looks like, it prevents scope creep by defining what is and isn't included, and it gives the designer enough context to make smart decisions without guessing.

A bad brief creates the opposite. Vague goals lead to vague designs. Missing context leads to revisions that cost money — and by the third round, nobody is happy.

Start With Goals — Not Features

The most common mistake in a web design brief is starting with features. "I want a hero section, a blog, a contact form, and an Instagram feed." That is a shopping list, not a strategy.

Start with what the website needs to do for your business. When someone visits this site, what should happen next? Should they book a call, buy a product, request a quote, or subscribe to something?

Every feature on the site should trace back to one of those outcomes. If it doesn't, it probably shouldn't be there.

Write down one or two primary goals. "Generate 20 enquiries per month" is a goal. "Have a nice About page" is not.

The difference matters because it changes every design decision your designer will make — from page layout to button placement to the words on the page.

Most briefs we receive at Vediwood list features without connecting them to a business outcome. The sites that perform best after launch are the ones where the brief started with a clear answer to one question: what does this website need to do that the current one doesn't?

If you're not sure what your goals are, say that in the brief. A good designer will help you clarify them during the discovery phase. But if you hand over a brief that says "I just want a modern-looking website," you're asking your designer to guess — and they will guess differently from you.

Describe Your Audience So Your Designer Can Use It

"Our audience is everyone" is the least useful sentence in a brief. Your designer needs to know who they're designing for — not in abstract demographic terms, but in practical ones.

Think about the people who actually visit your site or enquire about your services. What problem are they trying to solve? What is their first question when they land on your homepage? Are they comparing you to competitors, or have they already decided to buy?

If you have analytics data from Google Analytics or a similar tool, share it. Traffic sources, top-performing pages, and bounce rates all give a designer real data to work with.

If you don't have analytics, describe your best customer. Not their age and income bracket — their behaviour. What convinced them to work with you? What nearly stopped them? What do they always ask about first?

The goal is not a perfect persona document. It is giving your designer enough information to make layout, copy, and navigation decisions that match how real people actually behave on your site. A site designed for "everyone" converts no one.

How to Have the Budget Conversation Before It Becomes a Problem

This is the section most business owners skip. Don't.

Not sharing a budget doesn't protect you — it slows the project down. Without a number, your designer has to guess what's realistic. That leads to one of two outcomes: they scope a project you can't afford, or they under-scope and you get less than you expected.

A budget shapes scope, not quality. A £5,000 budget and a £25,000 budget don't produce "worse" and "better" websites. They produce different websites with different capabilities.

A smaller budget means fewer pages, fewer custom features, and a tighter timeline. That is fine — as long as both sides know it upfront.

Give a range if you can. "We have between £8,000 and £12,000 for the full project" is more useful than "we'll see." It lets the designer tailor the proposal to what is actually possible, rather than guessing at a scope that lands nowhere near your expectations.

If you genuinely don't know what a website costs, ask the designer for a rough estimate based on your goals and scope. That conversation is normal and every good studio expects it. What no designer wants is to spend two weeks writing a proposal only to learn the budget was never realistic.

Be honest. If budget is tight, say so. The right designer will work with you to find a scope that fits — not walk away.

Show What "Good" Looks Like Without Dictating the Design

Reference websites are one of the most useful things you can include in a brief — if you explain why you like them. "Make it look like Apple" tells a designer nothing. "I like how their product pages use large images with minimal text — it feels clean and confident" tells them exactly what to aim for.

Share 3-5 websites you admire. For each one, write one sentence about what draws you to it — the layout, the colour palette, the photography style, the navigation, or the tone of the copy.

Share what you don't like too. "I hate sites with auto-playing video" or "dark backgrounds don't feel right for our brand" is just as useful as positive references.

Don't send a folder of 47 Pinterest pins with clashing styles. That creates confusion, not clarity. The fewer references you share, the more useful each one becomes.

Tell Your Designer What They Cannot Google

Your designer will research your industry. They will look at your competitors and study your existing site. But there are things they cannot find on their own — and these are the details that separate a generic site from one that fits your business.

Include in your brief:

• Brand assets: Logo files in vector format, brand colours with hex codes, fonts, and any existing style guides
• Tone of voice: Is your brand formal or conversational? Technical or plain-spoken? Share examples of copy that sounds like you
• Technical requirements: Does the site need to integrate with a CRM, email marketing tool, or payment gateway? Are there WCAG 2.2 accessibility standards you need to meet?
• Decision-makers: Who approves the design? One person or a committee? How many revision rounds are realistic?
• Hosting: Do you have existing hosting, or does the designer need to recommend a provider?

These details feel mundane compared to homepage layouts and colour palettes. But they are the details that prevent delays, surprise costs, and awkward conversations halfway through the build.

Content — The Part Everyone Leaves Until Last

Content is the most underestimated part of a web project. Most project delays are not caused by design or development — they happen because the content wasn't ready.

Before the project starts, decide:

• Who is writing the copy for each page? You, your team, or the designer's copywriter?
• Do you have professional photography, or will you need stock images?
• How many pages will the site have? What content already exists, and what needs writing from scratch?
• Do you have testimonials, case studies, or team bios ready to use?

If you're providing the content yourself, commit to a deadline and treat it like any other project milestone. Designers cannot design pages without content. Layouts built around placeholder text break the moment real copy goes in — paragraphs overflow, sections collapse, and the design loses its structure.

If you need help with content, say so upfront. Many studios offer copywriting as part of the project or can recommend a specialist. The earlier this is sorted, the smoother the build will be.

Set a Timeline That Does Not Fall Apart

"As soon as possible" is not a timeline. Neither is "we're flexible." Both signal that you haven't thought about what a realistic schedule looks like — and that makes it harder for your designer to plan.

Is there a hard deadline? Product launch, rebrand, seasonal campaign — if you have one, share it early so the team can plan backwards from it.

A realistic timeline for a standard business website is 8 to 12 weeks from kickoff to launch. That includes discovery, design, development, content entry, testing, and revisions. More complex sites with e-commerce, integrations, or custom functionality take longer.

What speeds a project up: clear briefs, fast feedback, and content delivered on time. What slows it down: late approvals, changing scope mid-project, and the phrase "actually, can we also add..."

A structured design process helps prevent most delays. But even the best process needs a solid brief to start from.

What Business Owners Always Forget to Include in a Web Design Brief

Even a solid brief can miss things that only surface later — usually at the worst possible time. These are the details that cause scope creep, surprise invoices, and post-launch regret.

• Success metrics. How will you know if the new site is working? Define this before launch, not after. It might be enquiry volume, conversion rate, page speed scores, or search rankings. Set up Google Analytics tracking from day one so you have a baseline to measure against.
• Post-launch ownership. Who updates the site after it goes live? Who fixes bugs? Who handles ongoing SEO? If the answer is "we haven't thought about that," think about it now. A website without maintenance degrades faster than most business owners expect.
• Mobile experience. Don't assume responsive design is included unless you specify it. State it clearly in the brief. More than half of all web traffic comes from mobile devices — your site needs to work on every screen size.
• Legal and compliance. Privacy policies, cookie consent banners, GDPR compliance, and accessibility requirements are not optional extras. They are legal obligations. If you're unsure what applies to your business, flag it in the brief and ask your designer to advise.
• SEO foundations. If you expect the site to rank on Google, say so. SEO affects everything from site architecture to page speed to how headings and content are structured. A designer who knows this upfront builds SEO into the foundation rather than trying to retrofit it after launch.

These items are the difference between a brief that covers the obvious and a brief that prevents problems.

The One-Page Brief Checklist

Every brief is different, but every brief should cover these ten things:

1. Business overview — who you are, what you sell, what makes you different
2. Primary goals — what the website needs to achieve, in one or two clear outcomes
3. Target audience — who visits, what they need, how they behave
4. Budget range — even a rough range is better than silence
5. Timeline — hard deadline or flexible, with any key dates
6. Content plan — who writes, who photographs, when it is due
7. Brand assets — logos, colours, fonts, tone of voice
8. Reference sites — 3-5 with one sentence on why you like each
9. Technical requirements — integrations, hosting, accessibility, legal compliance
10. Success metrics — how you will measure whether the site is working

A clear, honest two-page brief that covers these ten points will outperform a vague ten-page document every time. You don't need length. You need clarity.

When You Are Ready to Start Your Web Project

If you have worked through this thinking and written it down, you already have a better brief than most designers receive. The next step is finding a studio that reads every word of it — and responds with questions, not just a quote.

If you're looking for a team that takes briefs seriously and builds websites around business goals, not templates — book a free discovery call with Vediwood. No pitch, no pressure. Just an honest conversation about what your project needs.