How to Write a Website Brief That Gets Better Quotes

← Back to Blog

When you approach a web designer with "I need a website for my business," you'll get wildly different proposals — different prices, different timelines, different assumptions about what you need. A website brief fixes this. It's a short document that explains your project clearly enough that any qualified designer can give you an accurate, comparable quote. Here's what to put in it.

What Is a Website Brief?

A website brief (also called a design brief or project brief) is a document that summarizes what you need, who it's for, what success looks like, and any specific requirements or constraints. It doesn't need to be long — two to four pages is typical for a small-to-medium business project. What it needs to be is clear and specific.

Think of it like a job description. A vague job description gets vague applications. A specific one attracts candidates who are actually qualified and gives them enough to work with. The same principle applies here.

What to Include in Your Website Brief

1. Business Overview

Who you are, what you do, and who your customers are. Keep this to a paragraph — designers don't need your full company history, but they do need enough context to understand your industry, your positioning, and what makes you different from competitors.

2. Project Goal

Be specific about what you want the website to accomplish. "I want a professional website" is not a goal. "I want a site that generates inbound consultation requests from local small business owners" is. The more precisely you can define success, the better a designer can structure their proposal around achieving it.

3. Target Audience

Describe the people who will be visiting the site. Age range, profession, technical comfort level, geographic location, and what they're typically looking for when they arrive. Designers make different choices for a site targeting retired homeowners than for one targeting startup CTOs — and those choices affect design, copy tone, and information architecture.

4. Scope: Pages and Features

List the pages you think you need (e.g., Home, About, Services, Portfolio, Contact) and any specific functionality (contact forms, a booking calendar, an e-commerce checkout, a photo gallery, a blog). This is often where projects are most under-specified. The more detail you provide here, the more accurate your quotes will be.

5. Design Direction

Share two or three examples of websites you like and explain specifically what you like about them — is it the color palette? The layout? The photography style? The tone of voice? Also note what you don't want. Providing reference sites is one of the most useful things you can do for a designer — it shortcuts a lot of subjective back-and-forth.

If you have existing brand guidelines (logo files, color codes, typography), include them or note that you'll provide them at kickoff.

6. Content Situation

Will you be providing all the copy and photography yourself, or do you need the designer to write content or source imagery? This has a significant impact on price. Be honest about what you have ready and what you'll need help with — it's better to budget for it upfront than to discover it mid-project.

7. Budget Range

Sharing a budget range feels uncomfortable for many business owners, but it genuinely helps. A designer with a $2,000 budget will propose something completely different than one working with $15,000 — and there's no right or wrong, as long as expectations match. Without a budget, you'll get proposals that range from $800 to $25,000 for "roughly the same thing," which makes comparison impossible.

If you don't have a firm budget, share what you've learned about typical costs for your project type and ask designers to propose what they'd build within that range.

8. Timeline and Key Dates

When do you need the site to launch? Are there hard deadlines (a product launch, a trade show, a seasonal campaign) or is the timeline flexible? Designers plan their schedules in advance — giving them accurate timeline expectations means they can tell you honestly whether they can deliver, rather than overpromising and then scrambling.

Brief Template Checklist

• Business overview (one paragraph)
• Project goal (specific and measurable)
• Target audience description
• Page list and feature requirements
• Design direction with reference sites
• Existing brand assets (or note what's needed)
• Content situation (copy and imagery)
• Budget range
• Timeline and hard deadlines
• Decision-making process (who approves work)

How Long Should It Be?

Two to four pages for most projects. If you're building a simple business site, one well-organized page might be sufficient. If you're building a complex e-commerce platform, you may need more detail. The goal is not to write a technical specification — it's to give a designer enough context to scope the work accurately and write a proposal that genuinely fits your needs.