How to Write a Website Brief That Actually Gets You Accurate Quotes
If you've ever asked two or three web agencies for a quote on the same project and had the numbers come back wildly different, from a few thousand pounds to five figures for what felt like the same brief, you're not alone, and it's rarely the agencies being dishonest. Most of the time it means the brief left too much open to interpretation, and each agency quietly filled the gaps with their own assumptions.
A good brief doesn't need to be a technical document. It just needs to answer the questions an agency will otherwise have to guess at. Get that right and you'll get quotes back that are accurate, comparable, and far less likely to change once the project starts.
Why a vague brief costs you money, not just time
When a brief is thin, an agency has two options: ask you a long list of follow-up questions before they can quote at all, or make reasonable assumptions and price accordingly. Most will do a mix of both, and the assumptions are where the trouble starts.
One agency might assume you need five pages and a simple contact form. Another might assume you want a blog, a booking system, and multilingual support because you mentioned "growing internationally" in passing. Neither has done anything wrong, they've just interpreted an open brief differently, which is exactly why the quotes don't line up. Worse, if you pick the cheapest quote because it looks like the best deal, you often find out three weeks into the project that it didn't include something you assumed was obvious, and now you're paying for a change request on top.
Scope creep, where a project's requirements expand after work has already started, is one of the most common reasons web projects run over budget and over time. A clear brief doesn't eliminate scope creep entirely, new ideas come up during any project, but it draws a line everyone agreed to at the start, so anything beyond that line is a visible, deliberate decision rather than something that quietly crept in.
What to actually put in your brief
You don't need jargon or technical specification. You need honest answers to the following, written in plain English.
The problem you're trying to solve. Not "we need a new website" but what's actually wrong with the current one, or what gap you're trying to fill. "Our site looks dated and we're losing enquiries to competitors" tells an agency something very different from "we're launching a new service and need a page to sell it."
Who the website is for. A quick description of your typical customer and what they're trying to do when they land on your site. This shapes everything from the tone of the copy to which features actually matter.
The must-have features, separated from the nice-to-haves. A booking calendar, an online shop, a members' login, multi-language support, each of these adds real cost and time. List what you genuinely need versus what would be nice eventually, and say so explicitly. An honest "we don't need this yet, but might in a year" helps an agency build something that can grow into it later without paying for it now.
Examples of sites you like and dislike, with reasons. Three sites you like (not necessarily competitors) and a sentence on what you like about each, tone, layout, speed, how easy they are to use. This does more to align expectations than almost anything else in the brief.
Whether your content is ready. Photography, copy, logos, testimonials, product information. If none of it exists yet, say so. Content production is one of the most underestimated parts of a website project and one of the most common causes of delay, so flagging it upfront lets an agency quote for it properly or plan around it rather than assuming you'll have it ready in a week.
A realistic budget range. This is the one business owners are most reluctant to share, usually out of a fear of being quoted "up to" whatever figure they give. In practice, the opposite tends to happen. Without a budget range, an agency has to guess what kind of build you're expecting, and that guess is often wrong in both directions. A range, even a wide one, lets them propose something that actually fits rather than something generic that may be well above or below what you intended.
Your timeline and why it matters. "As soon as possible" tells an agency nothing useful. A specific date tied to a reason, a trade show, a product launch, the end of a lease on an old site, helps them tell you honestly whether it's realistic and what might need to be prioritised to hit it.
Any existing systems it needs to work with. Your CRM, accounting software, booking system, payment provider, or stock management tool. Integrations are one of the biggest hidden sources of extra cost on a website project, so flagging them early means they're priced in from the start rather than discovered halfway through.
How you'll know it worked. More enquiries, more online sales, fewer phone calls asking questions the website should answer, a better first impression for new leads. This isn't essential for a quote, but it helps an agency make decisions that actually serve the outcome you care about, rather than just ticking off a feature list.
A simple structure you can copy
You don't need a polished document. A page or two covering the sections above, even in bullet points, is enough. If it helps, structure it as:
Background and the problem you're solving
Who it's for
Must-have features and nice-to-haves
Examples you like, with reasons
Content readiness
Budget range
Timeline and the reason behind it
Existing systems and integrations
How you'll measure success
Send the same brief to every agency you're getting quotes from. That consistency is what makes the quotes genuinely comparable rather than just similarly priced.
What to do once the quotes come in
A detailed brief tends to produce detailed quotes, and that's useful in itself. If one agency's quote is dramatically lower than the others for the same brief, it's worth asking directly what's excluded, rather than assuming it's simply the best deal. The gap is usually explained by what's left out: ongoing support, content migration, a certain number of revision rounds, or hosting and maintenance after launch.
Getting an accurate quote is really about giving an agency enough honest information to price your actual project, not a guess at it. A good one will often come back with clarifying questions anyway, and that's a healthy sign, it means they're reading the brief properly rather than pricing on autopilot.
If you're at the stage of putting a brief together and want a second pair of eyes on it before it goes out to anyone, that's a conversation we're always happy to have at Digital Hand, free of charge and with no obligation to work with us afterwards. You can book a free 15-minute consultation and we'll help you work out what actually needs to be in it.