How to Brief a Design Agency (And Why Most Companies Get It Wrong)

The brief is the most underestimated part of any design engagement. It determines the quality of the output more than the agency's skill level, more than the budget, more than the timeline. A strong agency given a weak brief produces mediocre work. A strong agency given a strong brief produces something that looks like the agency is significantly better than they are.

After 350+ projects at DesignMe, the pattern is consistent: the engagements that produce great work and smooth processes almost always started with a clear brief. The ones that produce frustration, revisions, and cost overruns almost always started with a vague one. The brief isn't admin. It's the most leveraged thing you'll do before the project starts.

Here's how to write one that actually works.

Why Most Briefs Fail

Most briefs fail for one of three reasons.

They describe the output instead of the problem. "We need a new website" is not a brief. It tells the agency what to make but nothing about why, for whom, or what success looks like. An agency working from this kind of brief is making assumptions at every decision point - assumptions that may or may not match what you actually need.

They're written by someone who isn't the decision-maker. A brief assembled by a marketing coordinator and approved without scrutiny by a VP who hasn't read it carefully creates a gap between what the brief says and what the stakeholder actually wants. That gap surfaces during reviews, costs revision rounds, and extends timelines.

They're too vague about constraints. Budget, timeline, technical requirements, approval process, existing brand guidelines - leaving these out of the brief doesn't make the project more flexible. It makes the scoping conversation longer and more painful, and it means the agency is pricing based on assumptions rather than specifics.

What a Good Brief Contains

1. The Problem You're Solving

Start here, not with the solution. What is happening now that isn't working, and why does it matter?

"Our current website was built two years ago when we were a different company with a different product and a different ICP. It doesn't reflect who we are now, and we're losing deals because prospects visit it before demos and arrive confused about what we do."

That's a brief. It tells the agency what the problem is, why it exists, and what the consequences are. Everything that follows can be oriented around solving it.

2. Who You're Designing For

Be specific. "B2B buyers" is not specific. "VP of Engineering at a Series B fintech company who's been burned by a previous agency engagement and is skeptical of design vendors" is specific. The more precisely you can describe the person the design needs to work on, the better the design decisions will be.

Include what they know, what they're skeptical of, what they're trying to accomplish, and what would make them trust you. This is the information that separates design that looks good from design that converts.

3. What You Want Them to Do

Every piece of design has a primary action it's trying to drive. Be explicit about it. For a marketing site it might be booking a demo. For a product onboarding flow it might be completing a first meaningful action. For a pitch deck it might be getting a second meeting.

Secondary goals are fine to include, but rank them. When a design decision has to trade off between two goals, the agency needs to know which one wins.

4. What Success Looks Like

Define it in terms you can measure. "The website should look better" is not measurable. "Demo conversion from the homepage should increase" is measurable. "Prospects should be able to understand what we do within 10 seconds of arriving on the homepage" is testable.

You won't always have a specific number. That's fine. But naming the metric you care about - even if you don't know the target yet - tells the agency what the design is optimising for.

5. What Exists Already

Share everything relevant: existing brand guidelines, previous design files, competitor sites you've bookmarked, design directions you've tried that didn't work, and visual references that point toward what you're aiming for.

The references piece is particularly valuable. Most people find it easier to react to examples than to describe preferences in the abstract. "Something between these two references" is more useful direction than two paragraphs of adjectives.

Equally useful: things you've rejected and why. Knowing that a certain visual direction was tried and shot down by the CEO saves everyone time.

6. The Constraints

Budget. Share it. I know the instinct is to withhold budget to avoid being charged up to it. The reality is that an agency scoping blind will either overscope (and the proposal comes in too high), underscope (and you get a cheaper version of what you needed), or spend time producing a proposal that doesn't match your budget and wastes everyone's time.

Sharing a budget allows the agency to tell you honestly what's achievable within it, suggest where to invest and where to compromise, and scope a proposal that's actually useful.

Timeline. If there's a hard deadline - a fundraise, a launch event, a sales conference - say so upfront. Agencies plan capacity ahead. A hard deadline that appears mid-project creates problems that a hard deadline communicated in the brief allows the agency to plan around.

Technical requirements. Platform preferences, existing tech stack, integrations that need to work, accessibility requirements, performance targets. These constrain design decisions in ways that matter from the start.

Approval process. Who has final sign-off? How many rounds of feedback are expected? Is there a committee? Does the founder review everything? This shapes how the agency structures the engagement timeline and how much buffer to build into revision rounds.

Common Mistakes and What They Cost

Describing the solution instead of the problem. When a client tells us they need a "modern, clean, minimal website," we have to do extra work in discovery to understand what problem that's meant to solve. Sometimes "modern, clean, minimal" is right. Sometimes the problem actually requires something bolder. Skipping to the solution forecloses design options that might serve you better.

Providing too many references with no direction. A brief with twenty reference sites and no explanation of what you like about each one creates ambiguity rather than resolving it. Pick three to five and explain specifically what you're pointing at - the layout, the colour approach, the typography, the tone, the interaction style. References with annotation are worth ten times the references without.

Vague copy guidance. "We want the tone to be professional but approachable" describes almost every SaaS company's aspiration. What does your voice actually sound like? What would it never say? Is there existing copy that represents the brand well that the agency can use as a reference point? Copy direction is part of the brief even if copywriting isn't in scope.

Leaving out the history. We've inherited projects from previous agencies or in-house teams where important context - decisions that were tried, stakeholder preferences that shaped previous work, constraints that weren't obvious from the outside - wasn't shared in the brief. Starting with that history saves time and avoids rediscovering problems that already have answers.

Approving by committee without a decision-maker. The most expensive revision dynamic we see is feedback from multiple stakeholders with equal weight and no single decision-maker to resolve conflicts. One round of feedback from five people with different opinions is more expensive than three rounds of feedback from one clear decision-maker. Establish the approval chain before the project starts, not during the first review.

What a Strong Brief Actually Looks Like

To make this concrete, here's the difference between a weak and a strong brief for the same project.

Weak: "We need to redesign our website. It's outdated and doesn't represent our brand well. We'd like something modern and clean that communicates what we do clearly."

Strong: "We're a Series A B2B SaaS company selling compliance tooling to legal teams at mid-market financial services companies. Our current website was built eighteen months ago for a slightly different product and a broader audience. Since then we've niched down significantly and our positioning has sharpened. The site doesn't reflect that.

The primary goal is to increase demo bookings from the homepage, which currently converts at around 1.2%. Secondary goal is to reduce the number of prospects who arrive at demos confused about whether our product is relevant to them - this is a persistent issue our sales team flags.

Our ICP is a General Counsel or Chief Compliance Officer at a 200-500 person financial services firm. They're conservative, skeptical of vendor claims, and respond to proof over promises. They're also time-poor and will leave the site within 30 seconds if they can't immediately see themselves in the use case.

Budget is $18,000 to $22,000 for design and Webflow development. Timeline: we'd like to be live within eight weeks as we have a major industry conference at the end of the quarter.

Here are three sites we think are doing this well: [links with specific notes on each]. Here's one we tried a direction like and rejected because [reason]."

The second brief produces a better scope, a better proposal, fewer revision rounds, and almost certainly a better outcome. It takes an extra two hours to write. Those two hours save weeks.

How to Use This to Evaluate Agencies

A good agency will push back on a weak brief. They'll ask about the problem, the audience, the constraints, and the success metrics before accepting a vague directive. If an agency takes a brief like "we need a modern website" and immediately returns a proposal without asking clarifying questions, that's a signal.

At DesignMe, our intro call is designed to surface these questions before we scope anything. We've turned down projects where we couldn't get clear enough answers to brief ourselves confidently - not because the client was difficult, but because producing good work without a clear brief is genuinely hard, and we'd rather say that upfront than deliver something that misses.

The brief is a collaboration. A good agency will help you build it. But you need to come with the foundation: the problem, the audience, the constraints, and what success looks like. Everything else can be figured out together.

DesignMe works with funded B2B SaaS and AI companies on design and development projects and retainers. Our intro call is 30 minutes and we'll tell you honestly whether we're the right fit before either of us commits to anything:

designme.agency/intro