Website Design Brief Template: How to Brief a Designer Properly

A website design brief is a short document that turns the picture in your head into instructions someone else can quote, plan, and build from. It's not a contract, and it's not a technical spec. Think of it as the job description for your website.

Without one, the designer has to guess, and guessing is expensive. They'll quote high to cover the unknowns, quote low and add variations later, or build what they think you want and spend three revision rounds finding out otherwise.

A good brief does three jobs:

• It gets you quotes you can compare. When every designer quotes the same scope, you're finally comparing like with like.
• It gives the designer commercial context. What the site must achieve, not only how it should look.
• It becomes the yardstick. When someone suggests a new feature halfway through, you check it against the brief, not everyone's mood that week.

Scope creep rarely arrives as one big change. It arrives as twelve small "while you're in there" requests, each of which seemed perfectly reasonable at the time.

Writing the brief takes an hour or two. Gathering the inputs is where the real thinking happens.

The customer questions list is the sleeper hit here. The questions people ask on the phone are usually the questions your website failed to answer.

If you already have a website, an honest look at what it gets wrong is the best raw material you can bring. Our guide to the signs your website is costing you customers is a useful checklist to run before you start writing.

Here's the website design brief template. Copy the headings into a document and answer each one in plain English. Short answers are fine. Honest answers are essential.

1. Business overview. What you do, where you do it, how long you've been doing it, and what makes you different, in one or two sentences (bonus points for avoiding the word "passionate").
2. The project. New site, redesign, or a single landing page? What's prompting it now?
3. Goals. The main action you want visitors to take, plus how you'll know the site is working.
4. Audience. Who your best customers are, what worries them, and what they need to see before they get in touch.
5. Offer and services. Your core services, which ones you want more of, and any you'd rather not promote.
6. Pages and structure. A rough list of the pages you think you need, and why each one exists.
7. Content. Who's writing the copy, what photos exist, and what still needs creating.
8. Look and feel. Reference sites, brand assets, and anything you definitely don't want.
9. Technical needs. Booking, payments, integrations, platform preferences, and who controls the domain and hosting.
10. Budget, timeline, and sign-off. Your range, your deadline, and who makes the final call.

Ten sections sounds like homework, but most are a short paragraph and the whole brief usually fits on two pages. A 20-page brief often buries the three things that matter under forty nice-to-haves.

"We want a modern, professional website" describes a mood rather than a goal. Every designer will agree with it, and none will know what to build.

A useful goal names a visitor action and a business outcome. Compare these:

Pick one primary action. A phone call, a booking, a quote form, or a purchase. When everything is a priority, the page ends up with six buttons fighting for attention and the visitor clicks none. Our website call-to-action examples show how that primary action plays out on different page types.

Then add how you'll measure it. Enquiries per month, booking completions, calls that mention the website. You don't need a target number, just a clear idea of what you'll check three months after launch.

You don't need a persona called Marketing Mary with a favourite coffee order. You need three honest answers:

• Who is your best customer? Not everyone. The one you'd clone if you could.
• What are they worried about when they land on your site? Price, quality, trust, timing, or being upsold.
• What do they need to see before they'll enquire? Reviews, photos of real work, pricing guidance, qualifications, a local address.

That third question shapes the design more than any colour choice. A dental patient might need reassurance about pain and cost. Someone hiring a builder wants proof of finished work and confidence the job won't run months over.

Those answers tell the designer which proof belongs near the top of the page and which can sit lower down. For a fuller list of options, see these website trust signals examples.

Content is one of the most common reasons website projects run late. The design gets signed off, the build is ready, and then everyone waits three weeks for the About page.

Your brief should be blunt about who owns each piece:

Be honest about your time. When you're busy running the business, "I'll write the copy myself" has a habit of becoming "I'll write the copy in February." Paying for copywriting is often cheaper than a stalled project.

Design matters. But design without clear copy is just decoration. For the full picture of what turns a page into an enquiry, read what makes a website convert.

Plenty of business owners leave the budget out of the brief because they worry the designer will simply quote to the number. It's a fair worry. Leaving it out usually backfires anyway.

Without a range, a designer can't tell whether you want a five-page starter site or a custom build with booking and integrations. You'll get quotes that don't line up. A range is enough. Here's a rough guide to what budgets typically buy in New Zealand:

These are typical ranges, not quotes. Scope, content, and integrations all move the number. Our guide on how much a website costs goes deeper, and if you're replacing an existing site, website redesign cost and timeline covers the extra migration work.

For the timeline, give a date and the reason behind it. "Live before our open day in March" is useful. "ASAP" is not, because everyone's ASAP is different and nobody's ASAP includes waiting for the copy.

You don't need to speak developer. You only need to list what the site has to do.

The redirect question quietly protects your rankings. If search traffic matters, the brief should say so, so redirects are planned before launch.

On SEO, nobody honest can promise rankings. What you can ask for is a site that search engines can read properly. Google's SEO starter guide covers the basics any competent build should respect, and web.dev's guide to Core Web Vitals explains the loading and responsiveness measures that affect real visitors.

Accessibility deserves a line too. The W3C's WCAG guidelines are the recognised standard, and asking for readable contrast and keyboard-friendly forms costs far less at brief stage than after launch. Our guide to SEO website design explains how to build search in from the start instead of bolting it on later.

Most weak briefs aren't lazy. They're written by busy people who know their business so well they forget a stranger doesn't. A few patterns turn up again and again:

• Describing the design instead of the problem. "Dark blue, clean, lots of white space" tells the designer what you like. It says nothing about why the current site isn't producing enquiries.
• Listing every page you can think of. More pages do not automatically mean a better website. Sometimes it just means more places for the visitor to get lost.
• Copying a competitor wholesale. "Make it exactly like theirs" gets you their positioning, which is the one thing you don't want.
• Leaving out the decision-maker. If your business partner sees the design for the first time at the final review, budget for a second project.
• No definition of done. If the brief doesn't say what launch includes, the project ends whenever someone runs out of patience.

A brief that describes how the site should look gets you a website. A brief that describes what the site should achieve gets you one that earns its keep.

Once your brief is written, send it alongside our list of questions to ask a web designer before hiring. The answers will tell you who actually read it.

Here's what a completed brief can look like. This is a made-up example for a fictional clinic, written to show the level of detail that's genuinely useful. It's not a real client.

Notice what isn't there: no mission statement, no homepage slider, no 15-page sitemap. Every line gives the designer something to build with.

Small businesses rarely need the biggest website. They need the clearest one.

We read every brief with one question in mind: what does this site need to do for the business? Looks come after that. They matter, but they serve the goal rather than replace it.

A half-finished brief is fine. We'll fill the gaps with you, especially goals and audience. Twenty minutes on a call beats three weeks building the wrong thing.

We're a young studio, so we lead with clear scope rather than a wall of case studies, and our concept demos are labelled as concepts. If speed matters, our 48-hour website build process shows what a tight brief makes possible.

Want a head start on your brief? Get a free website audit and we'll show you what your current site does well, what's missing, and what to fix first. Or compare Onyxarro's packages and pricing to see which scope matches what you've written.

A website design brief template won't design your site for you. What it does is make sure the person designing it is solving the right problem.

Be clear about the goal, honest about the budget, and specific about what your customers need to see before they enquire. Keep it to a couple of pages. Name one person who decides.

Do that and you'll get better quotes, a smoother build, and a site judged on enquiries instead of opinions. If you'd like a second set of eyes before you send it, start with a free audit.