A web design brief is a short document — usually two to four pages — that tells a designer or agency what you're trying to build and why. Most clients don't write one, which is a mistake. The brief is the difference between project conversations that go in circles and project conversations that produce a real estimate, a clear scope, and a faster decision.
I'm David Campbell, founder of Nerd Stack. Across nine years of agency work, the single best predictor of a smooth project isn't the agency's skill or the client's budget — it's whether the client showed up with a clear brief. This guide shows you how to write one, even if you've never run a web design project before. If you're earlier in the buying process, our guide to choosing an agency covers vetting; this is what you bring to the conversation once vetting starts.
Why You Should Write a Brief — Even If the Agency Doesn't Ask
Most agencies will gladly start a project without a brief. They have discovery processes, they'll ask questions on a call, they'll figure it out. So why bother?
Because you'll get better proposals from better agencies, faster. A brief forces you to clarify what you actually want before five different agency reps interpret it five different ways. It gives every agency the same starting point, which means their estimates are comparable. It exposes your own thinking — when you can't write down your goal, you don't have one yet — and it dramatically speeds up the path to a real estimate. Agencies treat clients with briefs more seriously, because a written brief signals you'll be a manageable client.
None of this requires you to be a designer. It just requires you to write down what you already know about your business and what you want this site to do.
What a Web Design Brief Actually Includes
A good brief is short. Two to four pages, not a thirty-page RFP. The sections that matter:
- Project overview. Two sentences: who you are, what you want built (new site, redesign, rebuild).
- Goal. The one outcome the site has to produce — more leads, more bookings, more sales. Be specific: "I want to go from 4 inquiries a month to 12."
- Audience. Who the site is for. Your actual best customers, not "everyone."
- What's wrong with the current situation. Concrete: "the site is invisible on mobile," "I can't edit it myself," "it doesn't reflect what I charge now."
- Scope. Roughly how many pages, what major sections, what functionality (forms, booking, e-commerce, member areas).
- Must-haves vs. nice-to-haves. Separate the two. This is the single most useful list in the document — it lets the agency scope to your budget without guessing what to cut.
- Brand and style direction. Three to five sites you like and a sentence per site on why. Specific reactions guide a designer; "make it pop" does not.
- Budget range. An honest one. Hiding the budget gets you proposals that miss it in both directions. See our pricing guide for current ranges if you don't know yet.
- Timeline. When you want to launch. "Sooner is better" isn't a timeline — pick a target.
- Decision-maker. Who at your business will give final approval at each phase. If it's a committee, say so — agencies need to know.
- Constraints. Anything that limits the project — an existing CMS you must keep, a hosting requirement, a brand guideline, a compliance regime.
The Sections That Move Estimates the Most
Of the sections above, three carry disproportionate weight in how an agency will estimate the project. Spend the most time on these:
- The goal. A vague goal produces a vague proposal. A specific, measurable goal — "double our service-page bookings" — lets an agency scope the work around producing that outcome.
- Must-haves vs. nice-to-haves. The single fastest way to keep a project in budget is a clearly-prioritized scope. Without it, an agency either over-quotes to cover every possibility or under-quotes and surprises you with change orders.
- Budget range. Agencies don't quote in a vacuum. Tell them roughly what you've allocated and they'll scope to fit.
Common Mistakes in Web Design Briefs
- Writing it as a feature wishlist. A brief is about goals and outcomes, not a list of "needs to have a slider, needs a chatbot, needs animations." The agency proposes the features; you describe the problem.
- Hiding the budget. Almost every reason owners hide their budget — "I want to see what they suggest," "I'm worried they'll inflate" — produces worse proposals, not better ones. Be honest.
- Writing for an audience of consultants. Plain English. The agency will translate it into their own scope; they'd rather have your real words than a polished RFP.
- Skipping the "who decides." Projects stall when nobody knows who has final say. Name that person in the brief.
- Skipping the constraints. If you'd be unable to switch off WordPress, say so. If you have compliance constraints, say so. Constraints that surface late blow up timelines.
Who Should Write the Brief
You. Whoever inside your business will be the decision-maker on the project should write the brief — or at least sign off on it. Agencies will sometimes write a brief on your behalf in early discovery, and that's fine — but it's slower, it produces an agency-flavored brief rather than a business-owner-flavored one, and it costs you the clarity-forcing effect of writing it yourself.
A founder can write a usable brief in a focused 90 minutes.
Use the Brief as a Filter
The brief isn't just an input for the agency. It's a useful filter for the agency. The way an agency responds to your brief is one of the best signals you'll get about whether to hire them:
- A good agency reads the brief, asks clarifying questions about your goals and constraints, and proposes a scope that respects your priorities and budget.
- A poor agency ignores the brief and starts pitching a generic package — or tries to upsell you into "nice-to-haves" without acknowledging you said they were nice-to-haves.
You'll learn a lot in a single brief-to-proposal cycle. For more on what to evaluate, our guide to choosing a web design agency covers vetting in detail, and our companion post covers what to expect on a discovery call.
Frequently Asked Questions
What is a web design brief?
A web design brief is a short written document — usually two to four pages — that tells a designer or agency what you're trying to build, who it's for, and what success looks like. It includes your goals, audience, scope, budget, timeline, brand direction, and constraints.
Do I need to write a brief if I'm hiring a freelancer?
Yes, ideally. The same clarity-forcing benefit applies regardless of who you're hiring, and the brief shortens the path from first conversation to a usable estimate. For a freelancer it can be slightly shorter — but the same sections matter.
How long should a web design brief be?
Two to four pages is plenty for most small-business projects. Long RFPs are for enterprise procurement and tend to slow projects down rather than improve them. The goal is clarity, not exhaustiveness.
Should I include my budget in the brief?
Yes. Hiding the budget produces worse proposals, not better ones — agencies either over-scope to cover possibilities or under-scope and surprise you with change orders later. Include a real range; if you don't know what's realistic, see our pricing guide.
What if I don't know my goals yet?
That itself is useful information for the brief, and a good agency will help you sharpen them in discovery. Write what you do know — the symptom you're trying to fix ("we lose prospects on mobile," "I can't edit my site"), the audience you serve, the budget you have — and a good first call turns that into a real goal.
Bottom Line
Writing a brief takes 90 minutes and saves you weeks of project drift. It speeds up estimates, makes proposals comparable, exposes your own thinking, and quietly signals to good agencies that you'll be a good client. If you've ever been frustrated by vague proposals or projects that drifted off-scope, the cause is almost always a missing brief.
At Nerd Stack, we work alongside clients whether they arrive with a polished brief or a blank page. See our web design service or book a free call and we'll help you turn what you know into a real scope.
Sources: AIGA — Standard Form of Agreement for Design Services.
