How to Write a Design Project Brief Agencies Can Quote From

A vague brief gets you vague quotes. A specific design project brief with clear deliverables, timelines, and success metrics gets you actionable proposals you can actually compare. Here's what to include so agencies can give you real numbers instead of ballpark ranges.

What Makes a Design Project Brief Quotable?

Agencies need four things to quote accurately: scope, timeline, budget range, and success criteria. Without these, they either pad their estimates or decline to quote at all. According to Nielsen Norman Group, unclear project requirements are responsible for 60% of project delays and budget overruns in UX projects.

Your design project brief should fit on 2-3 pages maximum. Include your company background (2-3 sentences), the problem you're solving, what you need designed, who will use it, when you need it, and how much you can spend. If you're writing this for the first time, start with a design brief template and customize it—don't start from scratch.

What to Include in Your Project Scope

Be specific about deliverables. "We need a mobile app" isn't quotable. "We need iOS and Android apps with 8 core screens, user authentication, and integration with our existing REST API" is.

Break down exactly what you need:

• Platform(s): Web responsive, iOS native, Android native, or all three
• Number of unique screens or page templates
• Key features and user flows (login, checkout, dashboard, etc.)
• Design system components (if you need a scalable component library)
• File formats you need delivered (Figma, Sketch, Adobe XD, developer handoff specs)

If you have existing brand guidelines, design systems, or technical constraints, mention them upfront. Agencies price differently when they're working within established systems versus creating from scratch.

How to Communicate Timeline and Budget

Give a realistic timeline and budget range. "As soon as possible" and "open budget" both signal that you haven't thought this through, which makes agencies wary.

For timelines, specify your ideal launch date and any hard deadlines (investor demos, conference launches, seasonal campaigns). Most design projects take 6-12 weeks depending on complexity. According to a 2023 Forrester study, design projects with clearly defined timelines are 40% more likely to stay on budget than those with flexible deadlines.

For budget, give a range. Here's what different project types typically cost:

If your budget is below these ranges, say so. Some agencies work with smaller budgets or offer phased approaches. But hiding your budget wastes everyone's time.

Define Success Metrics and Target Users

Agencies need to know what success looks like and who they're designing for. This isn't theoretical—it affects their approach and pricing.

For target users, provide:

• Primary user persona (role, technical proficiency, main goals)
• Key use cases or jobs-to-be-done
• Device and browser requirements
• Accessibility requirements (WCAG 2.1 AA compliance, screen reader support, etc.)

For success metrics, be specific:

• "Reduce checkout abandonment from 68% to under 40%"
• "Increase feature discoverability—70% of users should find Settings without help"
• "Match or exceed our NPS benchmark of 42"

When you know how to write a design brief with clear metrics, agencies can propose research methods, testing plans, and iteration cycles that actually move those numbers.

What to Avoid in Your Brief

Don't include:

• Subjective descriptors ("modern", "clean", "intuitive"—everyone interprets these differently)
• Solution prescriptions ("use a hamburger menu", "make it like Airbnb")—describe the problem instead
• Organizational politics or internal debates
• Requests for free spec work or unpaid design concepts

Don't ask agencies to sign NDAs before seeing your brief. If your idea requires an NDA to be valuable, you have a strategy problem, not a design problem. Share enough context for agencies to quote accurately, then handle confidential details after you've selected a partner.