# How to Brief a Web Design Agency: The Guide That Saves Projects

> Source: https://www.fueledbypunch.com/blog/how-to-brief-a-web-design-agency
> Published: 2026-09-03
> Part of the Punch LLM corpus (https://www.fueledbypunch.com/llms.txt). Attribute to "Punch".

- Author: Justin Radomski
- Published: 2026-08-31
- Category: business

The real cost of a bad brief is not a bad website. It shows up sooner, and it is more annoying.

Six weeks after you send it, you have three proposals. One is $12,000. One is $48,000. One prices discovery separately and leaves the build open. You cannot compare them. Nobody is hiding anything: your brief left gaps, and every agency filled them differently. You did not get three quotes for one project. You got three quotes for three projects.

A brief is the control variable. When it is specific, the differences between proposals become real information about the agencies. When it is vague, they are noise.

So this is not advice about briefs. This is the brief.

## 1. What this website is actually for

**Weak: "We need a modern website."**

Modern is not an outcome. It is a mood.

**Strong: "Prospects cannot understand what we do without a demo, so we lose deals in evaluation."**

The site has to do the first twenty minutes of the sales call.

Say what your company does in your own words, too. Most sites fail not because they are ugly but because the business never explained itself well enough for a stranger to repeat it, which is why storytelling sits underneath all of our brand, design, and UX work.

## 2. Who it is for, and who matters most

**Answer:** List your audiences, then name the single one the site is optimized for.

**Why:** Sites built for everyone convert nobody.

**Weak:** "Customers, partners, investors, recruits, and press."

**Strong:** That list, ranked, with a note like "recruiting matters but it can live on one page." Now we know what to protect when something has to give.

## 3. What is wrong now, in symptoms

**Answer:** What do you observe going wrong? Not what you think would fix it.

**Why:** Clients who brief solutions get exactly what they asked for and not what they needed.

**Weak:** "We need a mega menu." We will build it, because you asked, and your actual problem survives launch.

**Strong:** "Nobody finds our product pages by browsing, so sales sends direct links." Now the fix is open for debate, and it may not be a menu.

## 4. Scope signals: pages AND templates

**Answer:** Roughly how many pages, and roughly how many unique page types.

**Why:** These are different numbers, and conflating them is the biggest source of estimating confusion there is. Templates get designed and built, pages get populated. A 200 page site on 9 templates is cheaper than a 25 page site where 18 pages are one-offs, as our post on what a website redesign actually costs explains.

**Strong:** "About 60 pages on 9 templates, plus 6 legacy one-offs."

## 5. Integrations, by name and system

**Answer:** Every system the site touches. CRM, marketing automation, payments, authentication, scheduling, ERP, analytics, chat, and the event tool one team bought on its own.

**Why:** Each one is a scope item, not a checkbox. The integration that feels too small to mention is the one that eats a week. It is almost always the newsletter signup.

**Strong:** Named systems, plus who administers each and whether they still work there.

## 6. Content, honestly

**Answer:** Does the content exist, who writes what does not, and how much is migrating?

**Why:** Migration cost scales with inconsistency, not volume. Four hundred pages built the same way is a scripted job. Ninety pages made by a dozen people over six years is manual work, page by page. The question is not how many pages, it is how many different ways they were made.

**Strong:** "About 300 posts, built three different ways across two CMS migrations. Anything older than 2022 can go."

## 7. Technical constraints

**Answer:** Current platform and hosting, anything you are contractually stuck with, and who maintains it today.

**Why:** Constraints are the difference between a proposal and a guess. If you are unsure what counts as a design decision versus an engineering one, our breakdown of web design versus web development sorts it out fast.

## 8. Budget range

**Answer:** A range. An actual one.

**Why:** The fear, said plainly: name a number and you will be quoted that number. What withholding it reliably causes is weeks of proposals that were never viable, either well above your ceiling or well below it.

Language that gives a range without giving up position: "Our working range is $X to $Y. Show us what fits, and tell us separately what you would add if it moved."

Clutch's pricing data, covering 79,000 plus agencies as of August 2026, puts the mean project at $38,105 and the median under $10,000. A custom marketing site from Punch typically runs $15,000 to $25,000.

## 9. Timeline, and what is driving the date

**Answer:** Target launch, and why that date.

**Why:** A date tied to a real event is a constraint everyone can plan around. A date pulled from the air is a preference, and preferences get renegotiated in week nine.

**Strong:** "Trade show on March 3, and the booth graphics point at the new site." Most builds run 12 to 16 weeks from kickoff, so that line tells everyone whether scope has to shrink.

## 10. Decision makers and the approval process

**Answer:** Who approves design, who can overrule that, how feedback is collected, and how long a review round takes on your side.

**Why:** Almost nobody includes this, and it is one of the most valuable sections here. Approval structure is a hidden cost driver. If five stakeholders each get an independent review round, you did not buy one design phase, you bought five. Sequential feedback is how a clean 12 week schedule becomes 20.

**Strong:** "One owner consolidates feedback into a single document within five business days."

## 11. How you will judge success

**Answer:** What has to be true six months after launch, and how will you measure it?

**Why:** It sets the definition of done, and keeps launch day from becoming a referendum on the hero image.

## What agencies actually think when they read your brief

**No budget produces one of two bad outcomes**

A padded proposal, because we are covering unknowns you refused to name, or a lowball built to win the meeting, with the real number arriving as change orders in month three.

**Forty features and no priorities tells us nothing**

Tradeoffs are the entire job, and an unranked wish list means we have to guess which of your forty items you would trade for the other thirty nine. The next agency guesses differently, and that is how you get proposals you cannot compare.

**The most useful sentence you can write is what you will NOT do**

"No e-commerce this year." "We are keeping the current CRM." Constraints make proposals comparable, because they shrink the space where assumptions hide.

**Briefs written by committee have no point of view**

Every stakeholder edit softens a sentence until the brief says everything and asks for nothing, and a document with no point of view produces proposals with none either. Have one person write it and circulate it only for corrections of fact.

## How to run the process after the brief goes out

**Same document to everyone**

With the same deadline, stated up front.

**One written question round**

With every question and answer shared with all bidders. That removes the advantage of whoever emailed you most.

**Compare interpretations, not totals**

Read for how each agency understood the problem, and what they added, cut, and refused.

The honest one: the most useful signal in a proposal is which agency pushed back on your brief. An agency that tells you your page count and your date cannot both be true, or that your real problem is positioning rather than design, is doing the job before you have paid for it. Agreement is easy. There is more on that in our guide to how to choose a web design agency, and our web development team can usually tell you in one call whether a scope and a date fit.

## One last thing

A good brief is not about being impressive. It is about being legible. Half of what makes one work is writing down what your team already knows and has never said out loud in the same room.

One caveat worth naming: if the brief you are drafting keeps circling back to who you are rather than what the site should do, the project in front of you may be a brand problem instead, and rebrand versus refresh is the better place to start.

Do that and every conversation gets better, including the ones that do not end with hiring us. If you want a second set of eyes on yours before it goes out, tell us what you are working on. We will be straight about scope, range, and timing, even if the answer is that someone else is the better fit.