A great web design brief is a short, specific document that tells an agency what you want to achieve, who you are trying to reach, what the site must do, and how success will be measured. The best briefs are not long, they are clear. Aim for two to four pages that cover your goals, audience, scope, must-have features, examples you admire, the state of your content, your budget and timeline, and the metrics you will use to judge the result. This guide walks through each of those sections, gives you a copy-and-paste template, and flags the mistakes that quietly derail projects before they begin.

If you are commissioning a website, a first site, a rebuild, or a redesign, the quality of your brief has an outsized effect on the quality of what you get back. A vague brief produces vague proposals, mismatched quotes, and a build that drifts. A sharp brief lets an agency scope accurately, price fairly, and design with intent. It also protects you: when everyone agrees up front on what is being built and why, there are fewer surprises, fewer change requests, and far less friction near the deadline.

Start with goals, not features

The most common briefing mistake is to lead with a feature list, “we need a mega-menu, a blog, a booking form”, before anyone has explained what the site is for. Features are solutions. A brief should start with problems and outcomes, then let the agency propose the features that solve them. If you tell a designer you want a booking form, you get a booking form. If you tell them you are losing enquiries because people cannot easily reach you outside office hours, you might get a booking form, a live chat widget, a clearer contact strip, and a rethink of your opening hours copy.

Write your goals in plain business language and, where you can, attach a number or a direction. “Increase online enquiries” is good. “Increase online enquiries by roughly a third within six months of launch” is better, because it gives the agency something to design towards and to measure against later. Distinguish between your primary goal, the one thing the site must do, and secondary goals that would be nice to support. A single, dominant objective focuses every design decision that follows.

Useful goal prompts to answer:

• What is the single most important thing this website must achieve in the next twelve months?
• What does the site do badly today, and what does that cost you?
• What action do you most want a visitor to take? (Enquire, buy, book, download, subscribe, apply.)
• How would you know, six months after launch, that the project was worth it?

Describe the audience you are actually designing for

A website is not built for you or your board, it is built for the people you want to reach. Yet many briefs skip the audience entirely, which forces the agency to guess. Be concrete. Describe who your visitors are, what they are trying to do when they land on your site, what they already know about you, and what might make them hesitate. If you serve several distinct audiences, say, prospective clients, existing customers, and potential hires, rank them, because you cannot make every page equally important to everyone.

Think about context as much as demographics. Are people finding you on a phone during a commute, or researching carefully on a laptop? Are they in a hurry or comparing three suppliers side by side? Do they arrive knowing your brand, or is this their first encounter? A charity’s donor, an enterprise procurement lead, and a walk-in retail customer need very different journeys, and the brief is where you tell the agency which journeys matter most.

• Who are your primary and secondary audiences, in order of priority?
• What is each group trying to accomplish when they visit?
• What objections, doubts, or questions do they typically have?
• What devices and situations do they use to reach you?
• What language do they use, and does it differ from your internal jargon?

Define the scope clearly

Scope is where budgets are won or lost. Two agencies quoting on the same project can land pages apart simply because the brief left the scope open to interpretation. Be explicit about how big the site is, what needs to be built versus reused, and where the boundaries of the project lie. A rough page count, a list of templates, and a note on any integrations will let an agency scope with confidence rather than padding the quote to cover the unknown.

Templates matter more than raw page count. A 40-page site built from six repeatable templates is far less work than a 15-page site where every page is bespoke. Try to describe your site in terms of page types, home, service, case study, about, contact, blog listing, blog article, and note roughly how many of each you expect. Then flag anything that connects to the outside world: a payment gateway, a CRM, an email platform, a booking system, a members’ area, or a multi-language requirement. These integrations are often where hidden complexity lives.

• Is this a new build, a rebuild on a new platform, or a redesign of an existing site?
• Roughly how many pages, and how many distinct page templates?
• What platform or CMS do you want, or are you open to a recommendation?
• What must integrate with the site (payments, CRM, email, booking, analytics)?
• Do you need multiple languages or region-specific versions?
• Who will maintain and update the site after launch, you or the agency?

List the must-have features, and separate them from the nice-to-haves

Now, and only now, is the time for a feature list. The trick is to sort it ruthlessly into two columns: features the site cannot launch without, and features you would like if budget and time allow. This single act of prioritisation does more to keep a project on track than almost anything else, because it tells the agency where to spend effort and gives everyone a shared vocabulary when trade-offs arise later.

Be specific about how a feature should behave, not just that it exists. “A contact form” could mean a two-field form or a multi-step enquiry flow that routes to different departments and syncs to your CRM. Where a feature is business-critical, an event calendar for a venue, a portfolio filter for a studio, a resource library behind a signup, say so, and explain the outcome it drives. Save the wish list for the second column so it does not quietly inflate the core quote.

Show examples you like (and dislike)

Words describe intent; examples reveal taste. Gather three to six websites you admire, ideally a mix of competitors and sites from outside your sector, and, crucially, write a sentence about why each one works for you. “I like this one” tells a designer nothing. “I like how this homepage gets to the point in one screen and uses real photography instead of stock” tells them a great deal. Comment on layout, tone, imagery, typography, and how the site makes you feel, not just on colours.

Counter-examples are just as valuable. Sharing two or three sites you dislike, with reasons, sets a boundary that saves rounds of revision. Be honest about existing brand constraints, too: if you have a logo, a palette, and brand guidelines that must be respected, say so; if the brand is up for reinvention as part of the project, that is a very different conversation and a different budget. As a point of reference, Monk Creatives builds websites end to end, design, build, and content, and has delivered work such as the Baros Trust site, so an agency that handles the full stack can advise on where your examples are realistic and where they would balloon the cost.

Be honest about content readiness

Content is the most underestimated part of a web project and the single biggest cause of delay. A beautifully built site launches late not because the code was hard, but because the copy, photos, and product data were not ready. Your brief should state plainly what content exists, what needs writing or reshooting, and who is responsible for producing it. If you expect the agency to write copy or art-direct photography, that is a service to scope and price, not an afterthought.

Do an honest inventory. Which pages have final, approved copy today? Which have rough drafts? Which are blank? Do you have professional photography, or will the site lean on stock unless someone commissions a shoot? Is there a tone-of-voice guide, or will one need to be created? Naming a single person who owns content sign-off, and giving them a realistic deadline, prevents the classic scenario where a finished build sits waiting for words for weeks.

• Which pages have final copy, which have drafts, and which are empty?
• Do you have photography and imagery, or is a shoot required?
• Do you need help with copywriting, and in what tone of voice?
• Who signs off content, and by when can they deliver it?
• Is any existing content being migrated, and how much of it?

Set a realistic budget and timeline

Sharing a budget range is not naive, it is efficient. A budget lets an agency propose the right solution instead of guessing at the ceiling, and it prevents both sides from wasting time on a proposal that was never affordable. You do not need a precise figure; a sensible range works. If you genuinely do not know what your project should cost, ask agencies to quote against your scope and say so explicitly, but be prepared for a wide spread of numbers until the scope is pinned down. Because costs vary widely by region and currency, describe the range in whatever currency you work in and note if you are comparing quotes across markets.

Timelines deserve the same honesty. Note any fixed deadline and, importantly, why it exists, a trade show, a funding round, a product launch, the end of a lease on your old site. A deadline with a reason behind it helps an agency plan; an arbitrary “as soon as possible” does not. Remember that your own review cycles, content delivery, and internal approvals are part of the timeline. Many projects run late because of client-side delays, not agency ones, so build your own response time into the schedule.

Agree on how success will be measured

A website that everyone likes but no one can prove works is a missed opportunity. Decide before the build how you will judge the finished site, and write those metrics into the brief. Tie them back to the goals you set at the top: if the goal was more enquiries, the metric is enquiry volume and quality; if the goal was faster sales cycles, it might be time-to-conversion or bounce rate on key pages. Agreeing metrics up front also shapes the build, because an agency that knows you care about conversions will design and instrument the site accordingly.

• What one or two numbers will tell you the site is succeeding?
• What is the current baseline for those numbers, if you have one?
• How will you track them, analytics, form submissions, sales data, call tracking?
• When will you review performance after launch, 30, 60, 90 days?

The copy-and-paste web design brief template

Use the labelled prompts below as the skeleton of your brief. Copy them into a document and answer each one in a few sentences. If a prompt does not apply, write “not applicable” rather than deleting it, the fact that something is out of scope is itself useful information for the agency.

• Company snapshot: Who you are, what you sell, and where you operate.
• Project in one sentence: What you are commissioning and why, now.
• Primary goal: The single most important outcome this site must deliver.
• Secondary goals: Two or three supporting outcomes.
• Primary audience: Who they are and what they are trying to do.
• Secondary audiences: Other groups, ranked by importance.
• Desired visitor action: The main thing you want people to do.
• Project type: New build, rebuild, or redesign.
• Scope: Approximate page count, page templates, and platform preference.
• Integrations: Payments, CRM, email, booking, analytics, languages.
• Must-have features: Everything the site cannot launch without.
• Nice-to-have features: Everything you would add if budget allows.
• Sites you like: Three to six examples, each with a reason.
• Sites you dislike: Two or three, with reasons.
• Brand assets: Logo, palette, guidelines, fixed or open to change.
• Content status: What copy and imagery exist, and what is needed.
• Content owner: Who signs off, and by when they can deliver.
• Budget range: A sensible range in your currency.
• Timeline: Any fixed deadline and the reason behind it.
• Success metrics: How you will judge the site after launch.
• Decision-makers: Who approves work and how feedback will flow.
• Anything else: Constraints, sensitivities, or context the agency should know.

Common briefing mistakes to avoid

Even experienced teams fall into the same traps. The first is confusing features with goals, which we covered above, it produces a shopping list rather than a strategy. The second is writing the brief by committee without naming a single decision-maker, so the agency receives contradictory feedback and no one can break a tie. Appoint one person to own the relationship and to consolidate internal opinions before they reach the agency.

A third mistake is hiding the budget, in the hope of getting a lower price. In practice it wastes everyone’s time and often produces proposals that solve the wrong problem at the wrong scale. A fourth is under-scoping content: assuming the words and pictures will “sort themselves out” while the design proceeds. They rarely do. A fifth is over-specifying the solution, dictating exact layouts and technologies, which removes the very expertise you are paying for. Describe the problem and the outcome; let the agency bring the craft.

Finally, beware the moving brief. It is natural for thinking to evolve, but changing goals, audiences, or scope mid-project without acknowledging the impact on time and cost is the fastest route to a strained relationship. Agree a change process at the start, so that when new ideas arrive, and they will, everyone knows how they are evaluated, priced, and scheduled rather than quietly absorbed until the deadline slips.

Frequently asked questions

How long should a web design brief be? Long enough to be clear and short enough to be read, usually two to four pages. Depth matters more than length. A tight brief that answers the prompts above beats a twenty-page document that buries the goals in detail. If a section genuinely does not apply, say so briefly and move on.

Should I really share my budget? Yes. A budget range helps the agency propose a solution that fits, rather than guessing and either over-building or cutting corners. It also filters out mismatches early. You are not committing to spend the top of the range, you are giving the team the information they need to advise you honestly.

What if I do not know exactly what I want? That is common, and a good agency expects it. Focus on what you can articulate clearly: your goals, your audience, and the problems with your current site. Then invite the agency to recommend scope, platform, and features. A discovery phase early in the engagement exists precisely to turn uncertainty into a concrete plan.

Who should write the brief? Ideally one person who understands the business goals and can gather input from colleagues, then consolidate it into a single voice. Involve stakeholders while drafting, but do not send the agency a patchwork of conflicting notes. Naming a decision-maker up front prevents feedback deadlock later.

How much detail should I give about design? Enough to convey taste and constraints, not so much that you dictate the solution. Share examples you like and dislike with reasons, note any fixed brand assets, and describe the feeling you want the site to create. Then leave room for the agency to design, that craft is what you are hiring.

What happens after I send the brief? A good agency will read it, ask clarifying questions, and often propose a discovery or scoping conversation before quoting. Expect the brief to sharpen through that dialogue. Treat it as the start of a collaboration rather than a fixed specification handed over the wall.

Ready to turn your brief into a website that performs? Send it to the team at Monk Creatives at info@monkcreatives.com and we will help you refine the scope, plan the build, and bring it to life end to end.