To brief a design agency well, explain the business situation, the goal and how you’ll measure it, who the work is for, what problem it needs to solve, what you’ve already tried, and your constraints on scope, time, budget and decision making. Add a few references with notes on why you chose them. A brief built on business context gets better work than a list of deliverables, because it lets the agency solve the real problem instead of just producing the assets you guessed you needed.
Why do most design briefs lead to disappointing work?
You sent the agency a clear list: new homepage, five inner pages, refreshed logo, a pitch deck template. The work came back on time and looked fine. It just didn’t do anything. Sales still struggles to explain the product. Investors still ask the same questions. The new site looks better and converts the same.
That’s what a deliverables-only brief produces. You told the agency what to make, not why. So they made exactly that.
Why does business context beat a list of deliverables?
A deliverables list is your guess at the solution. Sometimes the guess is right. Often it isn’t:
- You ask for a new homepage when the real problem is positioning, and no layout fixes unclear positioning.
- You ask for a logo refresh when the bigger issue is that the product UI and the website look like two different companies.
- You ask for a launch video when what the launch needs is a clear story across site, video and social.
When you share the business context, the agency can push back, suggest a better scope or tell you something isn’t worth doing. That conversation is worth more than any single deliverable. It’s also how you find out whether an agency thinks strategically or just executes.
What should a design brief include?
Every good brief answers the same set of questions:
| Section | What it answers | Why it matters |
|---|---|---|
| Business context | Who you’re, stage, funding, what is changing | Sets the stakes and the level of polish needed |
| Goal and metric | What success looks like and how you’ll know | Lets the agency design for an outcome |
| Audience | Who must be convinced and what they care about | Shapes message, tone and structure |
| Problem | What isn’t working today | Separates symptoms from causes |
| What you’ve tried | Past attempts and what happened | Avoids repeating mistakes |
| Scope | What you think you need, open to challenge | A starting point, not a contract |
| Constraints | Platform, brand rules, legal, technical limits | Prevents work that can’t ship |
| Timeline | Key dates and what drives them | Allows planning backwards from launch |
| Budget range | The range you’re comfortable with | Lets the agency propose the best value scope |
| Decision makers | Who approves and who gives input | Prevents late surprises and rework |
| References | Examples you like, with reasons | Makes taste discussable |
What is a design brief template I can copy?
Copy this, fill it in and send it. Short, honest answers beat polished ones.
DESIGN BRIEF: [Company name] / [Project name]
Date: [date] Contact: [name, role, email]
1. BUSINESS CONTEXT
- What we do (one or two sentences):
- Stage and funding:
- What has changed recently (raise, pivot, new market, launch):
- Why this project, why now:
2. GOAL AND METRIC
- The outcome we need from this work:
- How we'll measure it (e.g. demo requests, sign-up rate, investor feedback):
- What happens if we do nothing:
3. AUDIENCE
- Primary audience (role, company type, what they care about):
- Secondary audiences (investors, candidates, partners):
- What they believe about us today:
- What we need them to believe after:
4. PROBLEM
- What isn't working today:
- Where we see it (sales calls, analytics, feedback):
5. WHAT WE HAVE TRIED
- Previous attempts and results:
- What we learned:
6. SCOPE (OPEN TO CHALLENGE)
- What we think we need:
- What is out of scope:
- Existing assets we can reuse:
7. CONSTRAINTS
- Platform or tech requirements:
- Brand elements we must keep:
- Legal, compliance or accessibility needs:
- Ownership and licensing (source files, fonts, stock, music):
8. TIMELINE
- Hard deadline and what drives it:
- Key milestones (raise, launch, event):
9. BUDGET RANGE
- Range we are comfortable with:
- One-off project or ongoing support:
10. DECISION MAKERS
- Final approver:
- People giving input:
- How fast we can give feedback:
11. REFERENCES
- [Link] - what we like about it:
- [Link] - what we like about it:
- [Link] - what we want to avoid and why:
What mistakes should you avoid when briefing an agency?
- Writing a brief for consensus. If the brief tries to please every stakeholder, it says nothing. Pick the goal.
- Hiding the budget. You get proposals that are either too thin to work or too big to approve. Share a range. Clutch’s pricing guidance says the same: tell providers what you expect to spend so they can point you to the right scope.
- Leaving ownership to the contract. Under US copyright law, commissioned work from an outside contractor only counts as work made for hire in nine specific categories and with a signed written agreement. Say in the brief that you expect full ownership of final files and source, so it’s priced in. AIGA’s Standard Form of Agreement for Design Services is a useful reference for what a design contract covers.
- Sending references without reasons. “We like Stripe” tells an agency very little. “We like how Stripe makes a complex product feel simple” tells them a lot.
- Leaving out the decision maker. If the CEO sees the work for the first time in round three, expect a restart.
- Over-specifying the solution. Say what you think you need, and invite the agency to challenge it.
- Skipping the “why now.” Urgency and stakes shape every decision, from scope to polish to timeline.
What happens after you send the brief?
A good agency should come back with questions, not just a price. Expect a discovery call where they test your assumptions, ask about buyers and sales conversations, and check the goal against the scope. If an agency quotes without asking anything, that tells you how they will run the project.
If you’re still deciding what kind of partner to brief, read design agency vs freelancer vs in-house. When the proposals come back, how to choose a design agency has a checklist for comparing them. If budget is the open question, how much a startup website costs gives typical market ranges.
How does Alterra Studio use your brief?
We read the brief before a 30-minute discovery call, then use the call to pressure-test the goal, the audience and the scope. Sometimes the scope gets smaller. Sometimes we recommend doing brand work before the website, or the reverse. The proposal that follows is built around the outcome you described.
Our designers cover brand identity, websites, product design and motion and 3D. For companies with ongoing needs, a design partnership means you brief us once and the context keeps building, instead of starting from zero every project. Our starting prices are on our pricing page, we show how we work with AI companies, and our glossary defines the terms agencies use in proposals.
The short version
- Brief the business situation and the goal, not just a list of deliverables.
- Include audience, problem, past attempts, constraints, timeline, budget range and decision makers.
- Share references with reasons, including what you want to avoid.
- Invite the agency to challenge your scope. Their questions tell you how they think.
- Use the template above and keep it to one to three pages.
Want a head start on your brief? The free 12-question Brand & Website Scorecard highlights where your brand and site need the most work. Or book a 30-minute call and bring your brief, finished or not.
Sources
Checked October 2, 2026.
- Clutch, Web Design Company Pricing Guide 2026 (published January 30, 2025).
- US Copyright Office, Circular 30: Works Made for Hire (revised August 2024).
- AIGA, Standard Form of Agreement for Design Services (updated 2020).
Frequently asked questions
How long should a design brief be?
One to three pages is usually enough. Long enough to give real context, short enough that every person on the agency team will actually read it. Link to supporting material rather than pasting it in.
Should I share my budget in the brief?
Yes, as a range. It lets the agency propose the scope that gives you the most value for that budget instead of guessing. Hiding the budget usually leads to proposals that are either too small to work or too big to approve.
What if I don't know what I need yet?
Brief the problem and the goal, and say clearly that you want the agency's recommendation on scope. A good agency will ask questions on a discovery call and propose the right deliverables.
Should I send the brief to several agencies?
Sending the same brief to two or three shortlisted agencies is reasonable and makes proposals easier to compare. Sending it to ten wastes your time on calls and rarely improves the outcome.
Want a straight answer for your company?
Book a 30-minute call. We'll look at your situation and tell you what we'd do, even if we're not the right fit.
Book a call, get a price range