Published 2026-08-13 · Updated 2026-08-13 · Adrieluxe Team
What a Good Client Brief Looks Like (Annotated Example)
A good client brief is checkable, not just detailed: it states the problem in numbers, draws an explicit boundary around what's in and out of scope, gives a real deadline with room to push back on it, names a specific budget grounded in something, and says outright who actually approves the spend. Those are the same four vectors — Scope Clarity, Budget Alignment, Timeline Pressure, Stakeholder Position — the free Bid/No-Bid Matrix scores. Below is a realistic brief that scores well on all four, annotated line by line, plus what each line would look like instead if it were a red flag.
TL;DR
A strong brief hits four things: a quantified problem (not adjectives), an explicit scope boundary (what's excluded, not just included), a real deadline that invites pushback if it's unrealistic, and a named decision-maker with a stated sign-off threshold. Most real briefs nail two or three of these, not all four — the gaps are exactly what to ask about before you quote.
Why it's worth learning the good pattern, not just the bad ones
Most advice on client briefs teaches assembly — the sections a template should have — not diagnosis: what a strong answer in each section actually sounds like versus a weak one. That gap matters because the cost of getting it wrong is well documented. PMI's Pulse of the Profession found that 47% of unsuccessful projects fail specifically due to poor requirements management, and for every $1 billion spent, organizations waste $51 million (5.1%) on projects hurt by poor requirements. Separately, PMI's 2018 Pulse of the Profession found 52% of projects experienced scope creep in the prior 12 months, up from 43% five years earlier— a trend running in the wrong direction, and one an explicit scope boundary in the brief is one of the few things that actually stops.
A template tells you what sections to include. It doesn't tell you what a strong answer in each one actually sounds like.
The example: a real-looking brief, annotated line by line
This is a realistic first message from a prospective client — closer to the 90th percentile than the median, since most real briefs get two or three of the four vectors right, not all four. Each paragraph is followed by what makes it strong and which vector it covers.
“I'm Priya, ops lead at Solborne Outfitters (a 12-person outdoor-gear retailer). We're looking to redesign our e-commerce site because our mobile conversion rate has been flat at 1.1% for the past two quarters — well below the 2.8% we're benchmarking against — and about a third of our support tickets last month were people unable to complete checkout on mobile.”
Scope ClarityThe problem is stated with numbers, not adjectives. "Conversion is flat at 1.1% vs. a 2.8% benchmark" and "a third of tickets are checkout failures" are both checkable and give you a real target to design against — compare this to a brief that just says the site "needs a refresh."
“Scope we're expecting: a mobile-first redesign of the product listing, product detail, and checkout flow — not a full rebuild of the brand or the CMS underneath (we're staying on Shopify). We'd want the current 340-SKU catalog migrated as-is, not restructured.”
Scope ClarityThis is the single most valuable sentence in the whole brief: it names what's explicitly out of scope, not just what's in it. "Not a full rebuild," "staying on Shopify," "migrated as-is" each close off a specific, common way this project could quietly grow after you've quoted it.
“Timeline: we'd like a working v1 live before our fall sale starts October 12 — about 9 weeks from a signed agreement. If that's not realistic given the scope, tell us now rather than partway through; we can push the sale a couple of weeks if we have to, but not more.”
Timeline PressureThe deadline is external and real (a sale date, not an arbitrary "ASAP"), it's quantified in weeks from signature rather than a calendar date that erodes while you're still in discussions, and it explicitly invites pushback if the scope doesn't fit the window — the opposite of a client who'll only discover the timeline is unrealistic once it's too late to renegotiate.
“Budget: we've set aside $18,000–$24,000 for this phase, based on two other quotes we've already gotten in that range. If your estimate lands meaningfully outside that, we'd rather know upfront and either adjust scope or pass, than negotiate at the end.”
Budget AlignmentA real range, grounded in actual comparable quotes rather than a guess, offered before you've asked for it. This is the genuine-market-awareness case, not the two riskier budget patterns — a number fixed by someone else that can't move, or a lowball anchored to a much cheaper, different offer.
“Decision-making: I run point on this and can sign off up to $25,000 without going back to our owner, Deepa — she'll want a one-page summary before kickoff but won't need to be in working sessions.”
Stakeholder PositionThis answers, unprompted, the exact question that otherwise takes a full call to extract: who actually approves the spend, and does the person you're talking to have that authority. Naming the real owner and the exact sign-off threshold rules out a late-stage "let me check with my partner" surprise.
“Happy to hop on a call this week if useful. Portfolio examples from other DTC/e-commerce clients would help us gauge fit.”
A specific, relevant ask (portfolio work in the same category) rather than a generic "send me your rates" — this reads as someone evaluating fit, not mass-messaging ten freelancers with the same unedited paragraph.
What changes if it's not good
Three of the lines above, swapped for their weaker, more common equivalent:
Scope Clarity
Good: "We'd want the current 340-SKU catalog migrated as-is, not restructured."
Weaker: "Redesign our whole site, make it look modern, and while you're in there maybe help with our email marketing too."
Why it matters: No boundary on what's included means the project can grow indefinitely without ever technically going outside what was "asked for."
Budget Alignment
Good: "We've set aside $18,000–$24,000, based on two other quotes we've already gotten in that range."
Weaker: "What's your rate?" — asked before any project detail.
Why it matters: Rate-shopping ahead of scope treats the number as the whole conversation, not a figure sized to the actual work.
Stakeholder Position
Good: "I can sign off up to $25,000 without going back to our owner."
Weaker: "I'll need to check with my partner on budget" — with no name or authority given.
Why it matters: You can't tell whether you're negotiating with the person who actually decides, or restarting the conversation with someone else later.
None of the weaker versions are automatically disqualifying on their own — see 12 red flags in a client brief for the fuller list and what to do once you spot one.
Scoring a real brief against the same four vectors
The example above would score well across all four criteria in the bid/no-bid decision matrix: Scope Clarity and Budget Alignment both land near the top of their range, and Timeline Pressure and Stakeholder Position are both handled rather than just present. That's not a coincidence — the matrix was built from the same four gaps that actually predict trouble, so a brief that closes all four reads as low-risk on the same scale that flags a vague or unbounded one.
Related reading
For the fuller range of warning signs when a brief goes the other way, see 12 red flags in a client brief. If the scope specifically reads unclear rather than flagged, run it through the 5-criteria scope-clarity scoring method. For the weighted go/no-go score across all four vectors at once, see bid or no-bid for freelancers: the decision matrix agencies use. For the full scored workflow this all feeds into, see client qualification: the complete guide.
Frequently asked questions
It's closer to the 90th percentile than the median — most real briefs get two or three of the four vectors right, not all four. That's the point of showing a strong one in full: without a clean reference, it's hard to notice that a real brief is missing the budget range, or never names who signs off, because the rest of it reads fine.
That's the normal case, not a failure state — treat the missing vector as the one thing to ask about, not a reason to write the client off. A brief with clear scope, budget, and timeline but no named decision-maker just needs one direct question ("who signs off on this?") before you quote, not a full requirements-gathering call.
No — that reads as homework and will cost you the reply. Use it the other way: read the client's actual brief against the four vectors yourself, silently, then ask only the specific questions that fill the gaps it's missing instead of the ones it already answered.
A template tells you what sections to include; it doesn't tell you what a strong answer in each section actually sounds like versus a weak one. This page shows a filled-in example annotated against what makes each line good — templates are about assembly, this is about diagnosis.
No — a well-written brief lowers risk on the axes it covers (scope, budget, timeline, stakeholder authority), but it doesn't rule out unrelated problems like a difficult personality or a habit of scope-creeping after the contract's signed. Treat it as a strong first signal, not a final verdict.
See how your next brief actually scores.
The free Bid/No-Bid Matrix scores a real brief against the same four vectors used above — Scope Clarity, Budget Alignment, Timeline Pressure, Stakeholder Position — and returns a Bid / Bid Carefully / No Bid recommendation instead of a gut call.
Score your next brief