How to Brief a Design Agency (And Get Better Results Faster)

The most expensive design projects we've seen weren't expensive because of agency rates. They were expensive because of wasted cycles — rounds of revisions chasing a direction that was never clearly defined in the first place. A great brief doesn't guarantee great design, but a poor brief almost guarantees poor results.

What Most Briefs Get Wrong

Most founders write briefs that describe what they want (a redesigned homepage, a new app) rather than why they need it (conversions are dropping, users can't complete signup). The difference matters enormously. When a design team understands the underlying problem, they can solve it. When they only know the requested deliverable, they can only execute it.

The Eight Things Every Good Brief Covers

1. The Business Context

Who are you, what do you do, and what stage are you at? Pre-product, pre-revenue, post-launch, scaling? The right design decisions for a seed-stage startup are completely different from those for a Series B company.

2. The Problem You're Solving

Not the design problem — the business or user problem. What is happening right now that shouldn't be? What data or signal is telling you this is a problem? If you have session recordings, NPS comments, or churn interviews, share them.

3. Your Users

Who uses your product, and what do they care about? Age, geography, technical literacy, primary device, key jobs-to-be-done. Even two sentences of real user description is more useful than a 10-page persona document.

4. Success Metrics

How will you know the design worked? A specific metric is far more useful than 'we want it to look better.' Conversion rate, activation rate, time-to-first-value, NPS — pick something measurable.

5. Constraints

• Technical: what can and cannot change in the codebase?
• Brand: do you have existing brand guidelines that must be respected?
• Timeline: when does this need to be live and why?
• Budget: what is the total budget and how flexible is it?

6. The Competitive Landscape

Who are your top 2–3 competitors and what do you think they do well or poorly? What products (in any category) do you admire, and what specifically do you admire about them?

7. What You've Already Tried

If you've made design changes before, what happened? What worked, what didn't? This saves the design team enormous time and prevents repeating failed experiments.

8. Stakeholders and Decision-Making

Who will review the work? Who has final approval? How many rounds of feedback are expected? Knowing the decision-making structure upfront prevents late-stage surprises.

The quality of the output is determined by the quality of the input. Give us context, not just requirements.

A Template You Can Use Right Now

Here's a minimal brief structure that works for most design engagements:

• Company: [one sentence on what you do and who you serve]
• Problem: [what specific thing is broken or underperforming, with data if available]
• Users: [who they are and what they need most]
• Goal: [what success looks like in measurable terms]
• Deliverables: [what you need designed and in what format]
• Timeline: [when you need it and any hard deadlines]
• Budget: [range or fixed amount]
• Must-haves: [non-negotiables — technical, brand, legal]
• Nice-to-haves: [things you'd like but would sacrifice if needed]
• References: [links to 2–3 products whose UX you admire]

If you fill this out honestly before our first call, we'll walk in with better questions — and you'll get better work, faster.