Most web design briefs fail for the same reason: they answer questions nobody asked and skip the ones that actually matter. A five-page brief full of adjectives — “modern,” “clean,” “premium” — tells an agency almost nothing, because every agency already believes it can deliver those. What actually moves a project forward is specificity.
Start with the decision, not the design.
Before anyone talks about colors or layout, write down the one thing you want a visitor to do on the site, and what's currently stopping them from doing it. “We want more enquiries” is a start. “We get traffic from Instagram but our enquiry form has an 80% drop-off because it asks for information people don't have on their phone” is a brief.
Show examples, but explain the “why.”
Sending five competitor screenshots with no comment is not a brief — it's homework you're handing back. Instead, pick two or three sites and say exactly what you're reacting to: “the way this pricing page handles objections before the price is even shown” is useful. “I like this vibe” is not.
Separate non-negotiables from nice-to-haves, honestly.
Every brief we've seen mixes “we must accept UPI payments” with “it would be nice to have a blog” in the same list, with the same emphasis. Rank them. A good agency will still ask, but ranking saves a round of back-and-forth.
Say what's actually broken today.
If you have a current site or product, the single most useful thing you can hand over is not a wishlist — it's the truth about what isn't working: slow load times, a form nobody checks, an admin panel your own team avoids using. That context shapes decisions a wishlist never will.
Give a real timeline and a real budget range.
Vague timelines (“soon”) and withheld budgets don't protect you — they just mean the first draft of any proposal has to guess, and guesses are rarely generous to you.
Name who actually approves.
Projects slow down most often not during design or development, but waiting on a decision-maker who wasn't in the loop from the start. Name that person in the brief, and get them into the first conversation.
A brief doesn't need to be long. It needs to answer what's actually broken, what is non-negotiable, what the real timeline is, and who signs off.
Everything else — the fonts, the exact page count, the specific plugin — is a conversation a good agency should be having with you, not one you need to have finished alone before you reach out.
If you're not sure how to answer some of these yet, that's fine — tell us what you do know, and start a project conversation with the rest.