How to Brief a Web Designer: A Template That Actually Works

Most web design projects go wrong before the designer writes a single line of code. The client hands over a one-paragraph email, the designer fills in the gaps with guesses, and three revision rounds later everyone is frustrated. A good brief fixes this before it starts.

I’ve read hundreds of these briefs over the years, from a single WhatsApp message to twelve-page documents nobody read. The short ones waste time in the discovery call. The long ones bury the one detail that actually matters. Here’s the format that gets a project moving fast, with a template you can copy today.

What a brief needs to answer

A brief isn’t a wishlist. It’s the set of facts a designer needs before they can quote and plan the work properly. Five things cover most of it.

What the site needs to do. Not “look modern” or “reflect our brand,” but the actual job. Take bookings. Sell products. Generate enquiries from a specific service. Every design decision should trace back to this.

Who’s going to use it. A landscaper’s customer searching on their phone in the rain behaves nothing like a B2B buyer comparing three suppliers at a desk. Name the audience and how they find you.

What exists already. Send the current site if there is one, three competitor sites you like or don’t, your logo and brand assets, and any existing copy or photography. Designers work faster from references than from descriptions.

What the budget and timeline are. Vague budgets produce vague quotes. If you genuinely don’t know, say what you’d expect to pay for a similar project and let the designer tell you if that’s realistic.

Who signs off. One decision-maker or a committee changes how a project runs. Say who approves each stage before the project starts, not halfway through revisions.

The template

Copy this into a document and fill in each section in a sentence or two. Don’t pad it out. A tight one-page brief beats a padded five-page one.

Business: [name, what you sell, who to]
Goal of this project: [the one job the site must do]
Current site: [URL, or "none"]
Audience: [who visits, how they find you, device they use]
Must-haves: [booking system, shop, specific integrations]
Content ready: [yes/no, who's writing copy, who's supplying photos]
Sites you like: [2-3 links, and why]
Sites you don't like: [1-2 links, and why]
Budget range: [figure, or a comparable spend]
Timeline: [launch date, and anything driving it]
Decision-maker: [name]

That’s eleven lines. Most clients can fill it in during a single coffee.
Not sure how to answer some of these? Our free Website Brief Builder walks you through each question in under two minutes and hands you a ready-to-send brief.

Common gaps that slow projects down

Content is the one most people miss. A designer can build a page in a day. Writing the copy for it, sourcing the photos, and getting sign-off from three stakeholders can take weeks. Decide who’s writing before the project starts, not after the design is signed off and the site is sitting empty.

Integrations are the second gap. If the site needs to talk to a booking system, a CRM, or a payment provider, say so in the brief. Finding out in week four that the site needs to sync with a scheduling tool nobody mentioned adds cost and delay that a five-minute conversation upfront would have avoided.

The third gap is examples without reasons. “I like this site” tells a designer almost nothing. “I like how this site’s homepage gets straight to a quote form without three scrolls of stock photography” tells them exactly what to build toward.

What good looks like from the designer’s side

A brief this short only works if the designer asks the right follow-up questions on the discovery call. At Nimble we run a short call after every brief to test assumptions before any design work starts: what happens if the booking volume doubles, who maintains the site once it’s live, does the current hosting need to move. That call catches details a written brief never surfaces on its own.

If you’re comparing designers, ask what their discovery process looks like before you sign anything. A designer who starts sketching before asking questions is guessing. A designer who spends an hour understanding the business before quoting is doing the job properly. Have a look at our web design services to see how we run that process end to end.

Get the brief right and the rest gets easier

A clear brief saves rounds of revisions, protects your budget, and gives the designer what they need to quote accurately the first time. It won’t remove every surprise from a build, but it removes the ones caused by guesswork rather than genuine complexity.

If you’ve got a project in mind and want a second pair of eyes on the brief before you send it out, get in touch. We’re happy to look it over, no obligation.

Frequently Asked Questions

How long should a web design brief be?
One page is usually enough. Cover the goal, audience, must-haves, budget, timeline, and who signs off. Longer briefs tend to bury the important detail rather than clarify it.

Do I need to know my budget before briefing a designer?
A rough range helps more than an exact figure. If you don’t know what’s realistic, tell the designer what you’d expect a similar project to cost and ask them to confirm or correct that.

Should I include competitor websites in my brief?
Yes, with a reason for each one. Two or three sites you like, one or two you don’t, and a sentence on why each earns its place. That’s more useful to a designer than a long list with no context.

Who should write the website copy: me or the designer?
Either can work, but decide before the project starts. Copy is usually the biggest cause of delay because it depends on stakeholders who aren’t in the design meetings.

What’s the biggest mistake people make when briefing a web designer?
Describing the look they want rather than the job the site needs to do. “Modern and clean” tells a designer nothing about whether the site needs to sell, book, or generate enquiries. Start with the goal, and the look follows from that.