How to Brief a Design Agency (and Why Companies Often Get It Wrong)

The brief is the most underrated part of any design project. It shapes the result more than the studio’s talent, the budget or the timeline. A strong studio with a weak brief ships average work. A strong studio with a strong brief ships work that makes it look even better than it is.

After 500+ projects at GG Studio, the pattern is consistent. The projects that ran smoothly and produced great work almost always started with a clear brief. The ones full of revisions and overruns almost always started with a vague one. The brief isn’t paperwork. It’s the highest-leverage thing you do before the project starts.

Here’s how to write one that works.

Why Most Briefs Fail

Most briefs fail for one of three reasons.

They describe the output, not the problem. “We need a new website” is not a brief. It says what to make and nothing about why, for whom, or what success looks like. A studio working from that is guessing at every decision.

They’re written by someone who doesn’t decide. A brief put together by a coordinator and signed off by a VP who skimmed it creates a gap between what the document says and what the decision-maker wants. That gap shows up in reviews, costs revision rounds and pushes the timeline.

They’re vague about constraints. Budget, timeline, technical requirements, approval process, brand guidelines. Leaving them out doesn’t make the project flexible. It makes scoping longer, and it means the studio prices on assumptions.

What a Good Brief Contains

1. The Problem You’re Solving

Start here, not with the solution. What isn’t working right now, and why does it matter?

“Our site was built two years ago for a different product and a different buyer. It doesn’t reflect who we are now, and prospects arrive at demos confused about what we do.”

That’s a brief. It names the problem, where it came from and what it costs. Everything else can be built around solving it.

2. Who You’re Designing For

Be specific. “B2B buyers” isn’t specific. “A VP of Engineering at a Series B fintech who got burned by their last agency and doesn’t trust design vendors” is. The sharper the picture of the person, the better every design decision gets.

Include what they know, what they doubt, what they’re trying to get done and what would make them trust you. That’s what separates a page that looks good from a page that converts.

When Montag School came to us, the buyer was the whole story: creative directors and art directors who judge craft for a living and spot a template in seconds. Knowing that changed every decision on the page.

3. What You Want Them to Do

Every page has one main action it exists to drive. Name it. For a marketing site it might be booking a demo. For onboarding, completing a first meaningful action. For a course launch, enrolling.

Secondary goals are fine, but rank them. When a design decision forces a trade-off, the studio needs to know which goal wins.

4. What Success Looks Like

Make it measurable. “The site should look better” isn’t. “Demo conversion from the homepage should go up” is. “A prospect should understand what we do within 10 seconds” is testable.

You won’t always have a target number, and that’s fine. Naming the metric you care about still tells the studio what the design is optimizing for.

5. What Exists Already

Share everything: brand guidelines, old design files, competitor sites you’ve bookmarked, directions you tried that didn’t work, references that point where you want to go.

References are especially useful. Most people react to examples more easily than they describe taste. “Something between these two” beats two paragraphs of adjectives.

Just as useful: what you’ve rejected and why. Knowing the CEO killed a certain direction saves everyone a round.

6. The Constraints

Budget. Share it. I know the instinct is to hold it back so you don’t get charged up to it. In practice, a studio scoping blind either overscopes (proposal too high), underscopes (you get a cheaper version of what you need) or writes a proposal that doesn’t fit and wastes everyone’s week.

A shared budget lets the studio tell you what’s realistic, where to invest and where to save. If you don’t know what a realistic range looks like, our SaaS website design cost breakdown shows what different budgets buy.

Timeline. If there’s a hard date (a raise, a launch, a live event), say it up front. Studios plan capacity ahead. A deadline in the brief can be planned around. A deadline that appears mid-project creates problems. When Human AI Academy briefed us on the ChatGPT Pro launch, the live date was fixed from day one, so we built a 7-day plan around it and the page went live on schedule.

Technical requirements. Platform, current stack, integrations that must work, accessibility and performance targets. These constrain design from the start. If you’re still choosing a platform, our Webflow vs Framer comparison is a good place to begin.

Approval process. Who signs off? How many feedback rounds? Is there a committee? Does the founder review everything? This shapes how the studio sets up the timeline and how much buffer it builds in.

Common Mistakes and What They Cost

Describing the solution instead of the problem. When a client asks for a “modern, clean, minimal website”, we have to dig in discovery to find the problem behind it. Sometimes minimal is right. Sometimes the problem needs something bolder. Jumping to the solution closes doors that might serve you better.

Too many references, no direction. Twenty reference sites with no notes create more confusion than they solve. Pick three to five and say exactly what you like in each: the layout, the color, the type, the tone, the motion. Annotated references are worth ten times the bare ones.

Vague copy guidance. “Professional but approachable” describes almost every SaaS company’s wish. What does your voice actually sound like? What would it never say? Is there copy you already love? Copy direction belongs in the brief even if copywriting isn’t in scope.

Leaving out the history. We’ve inherited projects where key context (what was tried, who prefers what, constraints invisible from outside) never made it into the brief. Sharing that history saves time and avoids solving problems that already have answers.

Approval by committee with no decider. The most expensive revision pattern is feedback from several people with equal weight and nobody to settle conflicts. One round from five people who disagree costs more than three rounds from one clear decider. Set the approval chain before the project starts. With Hubla, we ran a Discovery Workshop with the whole marketing team before any design, to align everyone on one conversion thesis, one target buyer and one visual standard. That alignment is what kept the project moving.

What a Strong Brief Actually Looks Like

Here’s the same project, briefed two ways.

Weak: “We need to redesign our website. It’s outdated and doesn’t represent our brand. We’d like something modern and clean that explains what we do clearly.”

Strong: “We’re a Series A B2B SaaS company selling compliance software to legal teams at mid-market financial services firms. Our site was built eighteen months ago for a slightly different product and a broader audience. Since then we’ve narrowed our focus and sharpened our positioning. The site doesn’t show that.

The main goal is more demo bookings from the homepage, which converts at about 1.2% today. The second goal is fewer prospects showing up to demos unsure whether the product fits them. Our sales team flags this every week.

Our buyer is a General Counsel or Chief Compliance Officer at a 200 to 500 person financial services firm. They’re conservative, skeptical of vendor claims and respond to proof over promises. They’re busy and leave within 30 seconds if they can’t see themselves in the use case.

Budget: [our approved number] for design and build in Framer. Timeline: live within eight weeks, before a major industry conference at the end of the quarter.

Three sites we think do this well: [links, with a note on each]. One direction we tried and rejected, and why: [reason].”

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

How to Use This to Evaluate Agencies

A good studio pushes back on a weak brief. It asks about the problem, the buyer, the constraints and the success metric before accepting a vague request. If a studio takes “we need a modern website” and sends a proposal without a single question, that tells you something.

At GG Studio, the first call exists to get these answers before we scope anything. If we can’t get clear enough answers to brief ourselves, we say so up front, because shipping good work without a clear brief is hard, and we’d rather be honest about it than deliver something that misses.

The brief is a collaboration. A good studio helps you build it. You bring the foundation: the problem, the buyer, the constraints and what success looks like. The rest gets worked out together.

And before you brief anyone, be honest about whether an agency is even the right model for your stage. We cover that in when to hire a design agency vs. an in-house designer.

GG Studio works with funded B2B SaaS and AI startups on websites, product design and ongoing growth retainers. On the first call we’ll tell you honestly whether we’re the right fit before either side commits to anything:

ggstudio.agency/contact