How to Brief a Web Agency: A Practical Template

A prospective client once sent us a one-line inquiry: "We need a new website, can you give us a price?" We asked a handful of follow-up questions before we could even attempt a number: how many pages, what the site needed to do, whether copy and photography existed, what platform they were on. Three email exchanges later, we had enough to scope it properly. That back-and-forth wasn't friction for its own sake. It was the difference between a quote that means something and a number pulled out of thin air.

This happens constantly, and it's not the client's fault: nobody teaches you how to brief a web agency. But it's worth learning, because the quality of your brief has a direct, measurable effect on the quality of the quote you get back, and on how smoothly the project runs afterward. This article is a practical template for writing one, section by section, so you can send something useful the first time.

Why a vague brief produces a vague quote

When an agency receives "we need a new website" with no other detail, they have two options, and both are bad for you. The first is to pad the estimate to cover the risk of unknown scope: more pages than expected, more revision rounds, a content-management need nobody mentioned, integrations that surface halfway through discovery. Padding protects the agency but inflates your price for no reason, because you end up paying for hypothetical scope that might never materialize.

The second option is worse: the agency quotes low, based on optimistic assumptions, and the gaps surface once the project is underway. That's when you start seeing change-order costs: extra line items for things that were never explicitly excluded, but were never explicitly included either. A booking system you assumed was standard. A multilingual setup you mentioned once in passing and the agency didn't price for. Neither party is acting in bad faith here; the estimate was built on missing information, and missing information has to be paid for by someone, eventually.

A good brief solves both problems at once. It lets the agency quote closer to the real scope instead of a padded guess, and it gives you a paper trail to point back to if scope creep starts happening later: "this wasn't in the brief" cuts both ways, and it's usually the client who benefits from that clarity more than the agency does.

If you haven't settled on an agency yet, it's worth reading How to Choose the Right Web Agency: 12 Questions to Ask First before you get to this stage: it covers how to shortlist and vet agencies. This article picks up from there: once you've got a shortlist and you're ready to actually reach out, here's what to send them.

The brief template

You don't need a polished document. A structured email or a shared doc with these sections filled in (even partially) is enough to start a real conversation. Here's what to include.

1. Business context

• What does the business do, in plain language? Don't assume the agency will infer it from your industry.
• Who are your customers: B2B or B2C, local or international, price-sensitive or premium?
• What's changing right now that's driving this project? A rebrand, a new product line, outgrowing the current site, a founder finally having time to deal with it. The "why now" shapes priorities more than people expect.

2. Goals, stated as outcomes

This is the section most briefs get wrong. "We want a new design" is a preference, not a goal: it tells the agency nothing about what success looks like. Instead, state the outcome you're after:

• "Increase qualified leads from the website" rather than "we want a new design."
• "Reduce the number of basic questions our sales team answers by phone" rather than "add an FAQ page."
• "Make it possible for customers to book directly instead of emailing us" rather than "add a calendar."

Outcomes let the agency propose the right mechanism to get there, sometimes it's not the mechanism you had in mind, and that's useful information to surface early rather than after the design is built.

3. Current situation

• Link to your existing website, if you have one.
• What's working about it? Don't throw everything out reflexively: some pages, copy, or structure might genuinely be worth keeping.
• What isn't working? Be specific: slow load times, hard to update, doesn't look credible on mobile, conversion is low, it's built on a platform nobody in-house understands anymore.
• If you have analytics access, even rough numbers help: monthly visitors, top traffic sources, bounce rate on key pages. You don't need a full report; approximate figures are still more useful than none.

4. Scope specifics

• A rough page count or list of main sections: home, about, services, case studies, blog, contact, and so on. It doesn't need to be final, just a working estimate.
• Key functionality required: online booking, ecommerce and payment processing, multiple languages, a members' area, a blog or resource library, integrations with existing systems (CRM, email marketing, inventory, accounting software).
• Anything explicitly out of scope, if you already know: for example, "we're not touching our existing checkout system, just the front-end pages around it."

5. Content readiness

This is one of the most commonly underestimated pieces of a website project, and it deserves its own line item rather than being lumped in with "scope." Be honest about where things stand:

• Who is writing the copy: you, someone on your team, or does the agency need to handle it?
• Do you have existing photography and brand assets, or does new photography need to be commissioned?
• Is any of this already written or shot, or does it all need to be created as part of the project?

Content creation is frequently the actual bottleneck on a website timeline, not development. An agency that knows upfront that copy doesn't exist yet can build a content-gathering step into the schedule and the price. An agency that assumes copy is ready, only to discover in week three that nothing has been written, ends up with a stalled project and a client wondering why the timeline slipped.

6. Technical constraints or preferences

• Any required platform: WordPress, a headless CMS, a specific ecommerce platform your team already knows.
• Hosting preferences, or an existing hosting arrangement that needs to be kept or migrated.
• Systems that must integrate: a CRM, a booking tool, an ERP, an email platform, analytics or tag manager setups already in place.
• Any accessibility, security, or compliance requirements specific to your industry.

If you genuinely have no preference on platform, say so, that's useful information too, and it gives the agency room to recommend what fits the goals rather than working around a constraint that doesn't actually exist.

7. Budget range

This is the section clients most often leave blank, usually out of an instinct to protect their negotiating position. In practice, withholding it almost always backfires on the client rather than the agency. Without a range, an agency has to guess whether you're expecting a five-page brochure site or a fully custom platform with ongoing development. If they guess wrong in either direction, you either get a proposal wildly outside what you can spend, or a scoped-down version that quietly cuts things you actually needed. An approximate range, even a wide one, lets the agency propose something that's actually reachable and shaped around what matters most within it.

8. Timeline and deadlines

• When do you need the site live?
• Is that a soft preference or a hard deadline: tied to an event, a campaign launch, a trade show, a contract renewal?
• Are there internal milestones the agency should know about, like a board review or a marketing push that depends on the new site?

Hard deadlines change how a project gets scoped and staffed. An agency that knows about a fixed launch date early can plan around it; one that finds out two weeks before can only tell you what has to be cut.

9. Decision-makers and stakeholders

• Who has final sign-off on design and copy?
• Who else needs to review or approve along the way: a marketing lead, a business partner, an external brand consultant?
• Is there one point of contact managing the project, or will the agency be coordinating with several people?

Unclear approval chains are one of the most common causes of delay on web projects, independent of how good the brief is otherwise. Naming the decision-makers upfront saves rounds of revisions caused by late-arriving feedback from someone who wasn't in the loop.

How much detail is actually enough

You don't need every field in this template answered with certainty before you send it. A working draft with your best guesses, clearly marked as such, is more useful to an agency than a perfect document you spend three weeks polishing before reaching out. Send what you have, flag the parts you're unsure about (for example, "rough budget, open to discussion," or "page count is a guess, could be more or less") and let the agency ask clarifying questions.

A competent agency will read your brief and come back with follow-up questions regardless of how thorough it is; that's a normal part of scoping, not a sign your brief was inadequate. What the brief actually does is set the starting point of that conversation much closer to reality, so the questions that follow are sharper and the quote that comes out the other end reflects the project you're actually building, not a guess at it.

If you're getting ready to reach out to agencies with a project like this, our custom web design team is happy to work through a brief with you, gaps and all, get in touch and we'll help you scope it properly.