How to Brief a B2B Design Agency So the First Draft Isn't a Waste of Time
Creative brief templates usually ask for audience, objectives, timeline, budget, and deliverables. But even when that's all filled in accurately, a first draft can still miss, because the fields only capture what a client already knows. For many B2B tech companies, the answers going into those fields haven't actually been tested yet.
A design brief that produces a strong first draft answers three questions with real specificity: who exactly the work is for, what makes the company different from the alternative that the buyer is already considering, and what the work needs to accomplish. Every standard brief template already has fields for these, but filling in a field is different from having a validated answer. An untested assumption gets designed around instead of getting caught at the brief stage. The first draft ends up polished, expensive, and still wrong in the same place the brief was.
Why a filled-out brief can still produce a wasted first draft
Audience, objectives, competition, deliverables, timeline, and budget are the right categories of information. The issue is what goes into the template.
A founder or marketing lead filling out a brief usually answers who this is for with something like security teams at mid-market companies, which sounds specific and isn't. It doesn't say what that buyer already believes, what alternative they're comparing the company against, or what would make them stop and pay attention. The brief looks complete, but the agency is starting from an answer that's still a guess, and the first draft inherits that guess.
The three questions worth answering before writing the brief
Who exactly is this for, described specifically enough to picture one real buyer, the company size, and the moment they're in when they encounter the work. "A VP of Engineering at a 200-person company evaluating three vendors after a failed audit" gives a designer something to build toward. Generic "technical decision-makers" doesn't.
What does this company do differently than the alternative that buyer already has in mind? Every B2B buyer is comparing something to something else: a competitor, an internal build, or doing nothing. If the brief doesn't name what the company is being compared against and why it wins that comparison, the first draft will default to generic category language, because there's nothing more specific to work from.
What does success look like for this specific piece of work? Not a general company goal, but what this particular deliverable needs to do: get a buyer to book a call, help sales close a specific type of deal faster, make a technical concept legible to a non-technical stakeholder in a buying committee. A brief that states a goal this specific gives the agency something to design against.
What happens when these go unanswered
The brief still gets filled out completely, so the document looks thorough. Nothing about a completed brief signals that the audience description is vague or the competitive framing is missing, which is why it's easy to hand off a brief that feels done but isn't.
The first draft reflects the ambiguity back, just with better production value. A designer working from security teams at mid-market companies produces something that technically matches the brief and still feels wrong to everyone who sees it, without anyone being able to say exactly why. That's usually the moment a first draft gets labeled a miss, when the real issue is upstream of the design work entirely.
The revision cycle that follows often doesn't fix the real gap. Feedback like "make it feel more premium" or "this doesn't feel like us" is a symptom of the same missing specificity, not a new problem. Without going back to answer who the work is for and what it's competing against, a second and third draft can miss for the same underlying reason the first one did.
What this means for the brief itself
Answer the three questions above honestly, including admitting when the answer is still a guess. A brief that says "we believe our audience is X, but we haven't validated this" is more useful to an agency than one that states an unvalidated assumption with false confidence, because it tells the agency where to push back.
Treat the kickoff conversation as part of the brief, not a formality after it's submitted. The written document rarely captures everything, and the first real test of a brief is whether the audience and positioning hold up when a designer asks a direct follow-up question about them. A brief that survives that conversation intact was probably specific enough to begin with.
Expect the agency to push on the answers. Once you've settled on which agency to brief, the ones worth working with will ask harder questions about audience and differentiation before starting.
Ready to brief a project that gets the first draft right?
At BRIGHTSCOUT, our branding team starts every engagement by pressure-testing audience and positioning before any design work begins.
FAQs
What should a design brief for a B2B company include?
A strong design brief specifies exactly who the work is for, what makes the company different from the alternative that the buyer is comparing it against, and what the specific deliverable needs to accomplish. Standard fields like timeline, budget, and deliverables matter too, but they don't prevent a wasted first draft the way specificity in these three areas does.
Why does a completed brief still sometimes lead to a bad first draft?
Because filling in a field isn't the same as having a validated answer. A brief can have every section completed and still contain vague or untested assumptions about audience and positioning, and the first draft will reflect those same assumptions.
How specific should the audience section of a brief be?
Specific enough to picture one real buyer: their role, company size, and the situation they're in when they encounter the work. A description like "a VP of Engineering evaluating vendors after a failed audit" gives a designer something concrete to design toward, while a broad label like "technical decision-makers" doesn't.
What's the difference between a design brief and a kickoff conversation?
A design brief is the written document that captures audience, objectives, and deliverables before work begins. A kickoff conversation is where those answers actually get tested, since a designer's follow-up questions often surface gaps that a completed document didn't reveal on its own.
How do you know if a brief is specific enough before sending it to an agency?
Check whether it names one specific real buyer and what the work is competing against. If the brief could apply equally well to several different companies in the same space, it isn't specific enough yet to produce a first draft that's close to right.