How to Brief a Web Design Agency: What to Prepare Before You Have the First Conversation

Most web design projects go wrong before a single pixel is placed. Not because of budget, or timelines, or even design taste. They go wrong because the brief was vague, rushed, or never written down at all.

A strong brief is not a wish list. It is a document that compresses your business context, your audience, your goals, and your constraints into something a design team can actually act on. The better your brief, the better your site.

Here is what to prepare before you approach any web design agency.

Know what problem the website needs to solve

This sounds obvious. It rarely is.

Most clients come in with a solution already formed — "we need a new website" — without diagnosing the underlying problem. Is your current site underperforming because it looks dated? Because it is slow? Because visitors cannot work out what you actually do? Because you are attracting the wrong type of lead entirely?

Before you write anything, spend time on the real question: what is this website failing to do, and what does success look like in twelve months? Concrete answers to that question are worth more than a lengthy list of features you think you want.

Define your audience with specificity

"Our customers are businesses of all sizes" tells a design team nothing useful. "Our primary buyers are procurement leads at manufacturing firms with 50 to 500 employees, who compare three to five vendors before making a decision" tells them a great deal.

The more specifically you can describe who will land on this website, what they already know, what they are sceptical about, and what they need to feel confident before reaching out — the more precisely the design and copy can be calibrated to that person.

If you have existing customer data, bring it. If you have sales call recordings or common objections from your team, even better. Real customer language always outperforms internal assumptions.

Be honest about what you have

Agencies need to know what they are working with. That means telling them:

• Whether your brand is established or still evolving
• Whether you have existing copy or need it written from scratch
• Whether your photography and assets are ready, or whether that is still outstanding
• Whether there are technical requirements — integrations, CMS preferences, existing platforms you are locked into

These are not embarrassing admissions. They are essential information. A site that launches with placeholder copy and stock imagery because no one flagged it early enough is a site that will need fixing in six months.

Set a realistic scope and budget

Sharing your budget is not a negotiating weakness. It is a filter. It tells the agency whether what you want is achievable, and it lets them recommend the right approach rather than the one that fits an unstated number they are guessing at.

For context: a well-built marketing site of three to five pages with solid motion work sits at a different investment level than a single landing page, and different again from a flagship site with advanced 3D or WebGL. Knowing where you sit in that range means the agency can tell you honestly whether your expectations are aligned with what you are prepared to spend — before anyone has done any work.

Gather reference sites — but explain what they are references for

A folder of reference sites with no annotation is almost useless. A folder of reference sites where each one is labelled "I like the way this page handles the scroll transition" or "this hierarchy makes it immediately clear what the company does" is extremely useful.

Be precise about what you are responding to. Is it the overall art direction? The structure? The speed? The tone of the copy? Good design teams are not looking for sites to copy — they are looking to understand what you respond to and why.

Think about content ownership from the start

One of the most common project delays is content. Pages get designed around copy that does not exist yet. Photography sessions get pushed back. Approval chains are longer than anyone anticipated.

Before you start working with an agency, map out who owns each piece of content, who needs to approve it, and what the realistic timeline is. If you know content is going to be a bottleneck, say so early. Most agencies can plan around it — they cannot plan around surprises.

What a good brief looks like in practice

A working brief does not need to be a fifty-page document. It needs to answer:

1. 01What is wrong with the current situation, and what does fixed look like?
2. 02Who are we building this for, specifically?
3. 03What do we have, and what still needs to be created?
4. 04What is our budget and timeline?
5. 05What reference points do we like, and why?

If you can answer those five questions clearly before the first conversation, you will save weeks of back-and-forth and almost certainly end up with a better result.

For more thinking on how websites are built and what separates work that performs from work that just looks good, the Threnly articles hub is a good place to start.

If you are ready to brief a project and want a direct conversation about scope and approach, get in touch.