How to Brief a Web Agency (And Actually Get a Proposal Worth Reading)

We receive a lot of briefs. Some are two paragraphs and a wish. Others are forty-page documents that still somehow leave out the one thing we needed to know. Here's what actually helps — written from the agency side.

Why Most Briefs Fail

A poor brief doesn't just make it harder for an agency to quote accurately — it sets the entire project up to go wrong. When the scope isn't clearly defined at the start, every ambiguity becomes a renegotiation later.

The briefs that generate useful proposals share a common trait: they describe the problem clearly, not just the solution they've already imagined. The briefs that don't work usually open with "we want a website that looks like [competitor]" and end with "budget: flexible."

Here's what to actually include — and why each part matters.

1. The Business Context (Not Just 'About Us')

Every agency will ask about your business, but most briefs give the version that's already on your website. That's not the information we need.

What actually helps:

What's changed that triggered this project. Are you rebranding? Entering a new market? Is the current site technically broken, or just underperforming?
What you sell and to whom. Not the marketing version — the actual customer, the actual product, the actual price point.
What's working right now and what isn't. Agencies who inherit your existing setup need to understand the baseline.

A sentence that says "we've been running for 12 years and have outgrown our current site" tells us more than three paragraphs of company history.

2. The Actual Goal (Not 'A Better Website')

"We want a modern website that better represents our brand" is what almost every brief says. It's also almost useless, because it doesn't tell us what success looks like.

What useful goals look like:

"We generate 15 inbound leads a month from the website. We want 40."
"Our e-commerce conversion rate is 0.8%. Industry average is 2.5%. We want to close that gap."
"We're launching in three new markets and need the site to work in two additional languages within six months."
"We're raising a Series A and need a site that doesn't embarrass us in front of investors."

Even if the goal is partly qualitative — credibility, confidence, positioning — say so explicitly. "We want to stop losing proposals to competitors who look more established online" is a legitimate brief. We can design to that.

3. Budget: Say a Number

This is the one thing most clients resist, and the one thing that makes the most difference.

We understand the instinct to withhold budget — it feels like showing your cards. But it doesn't work the way you think. Agencies don't price up to your maximum and pocket the difference. What they actually do without a budget is guess at the scope, which leads to proposals that are either over-engineered (expensive and slow) or under-specified (cheap but inadequate).

A stated budget does two things: it filters out agencies who work at a different level, and it lets the right agency design the best solution for what you're actually investing. A £20,000 brief and a £100,000 brief for "a new website" are completely different projects.

If you genuinely don't know what it should cost, say that — and ask for a ballpark during the conversation. A good agency will tell you honestly.

4. Scope: What's In and What's Out

Be specific about what the project includes. The scope section of a brief is where vague ambitions collide with finite budgets, and getting it wrong is expensive.

Things to define clearly

Number of pages. Roughly how many distinct page types? (Home, About, Services, Blog, Contact is five; a 200-product e-commerce catalogue is not.)
Content. Are you supplying copy and images, or is that part of the scope? This is one of the most common sources of project delay.
Integrations. Does it need to connect to a CRM, booking system, payment processor, inventory management, or third-party API?
Languages. One language or multiple? If multilingual, is translation included?
CMS requirements. Do you need to edit content yourself? How often and who will be doing it?
Ongoing support. Is post-launch maintenance in scope, or is this build-and-handover?

5. Timeline: The Real One

"As soon as possible" is not a timeline. Neither is "ideally before summer."

If you have a hard deadline — a product launch, a conference, a fundraise close — say so. Agencies can work backwards from that and tell you honestly whether it's achievable.

If the timeline is flexible, say that too. It allows the agency to propose a realistic schedule rather than an optimistic one designed to win the work.

One thing that consistently delays projects: client-side feedback cycles. If your sign-off process involves five stakeholders across three time zones, that's relevant information. Build it into the brief so the timeline reflects reality, not the ideal.

6. Decision-Making: Who's Actually Involved

Agency proposals get approved and then stall because the person who commissioned the brief wasn't the person who signs off the budget. Or the CEO has opinions that weren't in the brief. Or legal needs to review any vendor contract before it's signed.

Being transparent about the decision-making process isn't a weakness — it helps agencies scope their response appropriately and manage expectations on both sides. A "we need board approval for anything over £15,000" upfront is far better than finding out three weeks into scoping.

7. What You've Tried Before (And What Happened)

If this isn't your first website, what happened with the last one? This isn't about fault — it's about patterns. If the last agency went quiet after month two, that tells us something about what communication looks like for you. If the site was built but never handed over properly, that's a scope problem to solve this time.

Past projects, good or bad, contain the most useful information about how to structure the current one.

The Brief Checklist

Before sending a brief to an agency, run through this:

✓ Business context — what changed, what you sell, what's working
✓ Specific, measurable goal — not "better website," but what better actually means
✓ A real budget figure, or a genuine "help me understand what this should cost"
✓ Scope — pages, content ownership, integrations, languages, CMS, support
✓ Timeline — hard deadlines, flexible dates, and internal review cycles
✓ Decision-making — who's involved, who signs off, any procurement constraints
✓ History — previous vendors, past attempts, lessons learned

A brief that covers these points will get you proposals that are comparable, accurate, and worth your time to evaluate. Anything less, and you're comparing guesses.

One More Thing

The agencies worth working with will push back on your brief — not to be difficult, but because they're already thinking about your project. If you send a brief and receive a proposal within 24 hours with no questions asked, that's not efficiency. It's a template with your name dropped in.

The best agency relationships start with a conversation, not a quote. A brief is the starting point — not a spec to be executed blindly.

The agencies worth working with will push back on your brief. That's not friction — it's the first sign they're actually thinking about your problem.