Skip to content
Process · 18 November 2026 · 7 min read

Use a practical creative project brief template to explain goals, scope, budget, timing and success measures before requesting a quote from a studio.

To get a useful, accurate quote, explain what you want to achieve, who it is for, what work you expect the studio to do, and what constraints matter. A good brief does not need polished language or a finished strategy. It needs enough detail for a studio to understand the project, identify open questions and recommend a realistic approach.

Use the template below for a design, website, video or software project. Be specific where you can, mark unknowns honestly, and share examples of work you like and dislike. A clear brief helps you compare proposals on the same basis—and makes it easier to spot when a studio has misunderstood your needs.

What a project brief should help you decide

A brief is a working document, not a contract or a full specification. Its job is to give a prospective studio enough context to suggest a scope, explain its assumptions and quote for the work. For example, “We need a new website” leaves many important questions unanswered: what should the site do, how many pages are involved, and who is providing the content?

You do not have to know the solution before you ask for help. You might know that customers struggle to find a service, but not whether the answer is a redesigned navigation, new page content or a different site structure. Describe the problem and invite the studio to recommend a way forward.

The more important a detail is to your decision, the more clearly it belongs in the brief. Separate firm requirements from preferences, and identify assumptions the studio should check before it prices the project.

Start with the goal and audience

Lead with the reason for the project. What is happening now, what would you like to change, and why is this the right time to address it? A design project might aim to make a service easier to understand. A video might introduce a new product. A software tool might reduce a repetitive internal task.

Then explain who the work is for. Include what you know about their needs, questions or behavior—not just a broad label such as “small businesses.” If you serve more than one audience, say which one matters most for this project and whether others need to be considered.

Describe success in terms that can be observed. That could mean customers can complete a task more easily, a team can publish updates without developer help, or a video is ready for a specific sales presentation. If you already track a relevant measure, share it; if you do not, say what you would like to learn. Avoid promising an outcome that depends on factors outside the project, such as a specific number of sales.

Define the scope, including what is out

List the work you believe is needed, then distinguish essentials from optional ideas. For a website, the scope might include planning, visual design, development, migration and staff training. For a video, it might include concept, script, filming, editing, captions and versions for different channels. For software, describe the main user tasks and any systems it needs to work with.

Include a rough sense of size where possible: number of pages, screens, deliverables, locations or audiences. You do not need a perfect inventory. Even an estimate helps the studio understand whether you are describing a small update or a broader project.

Just as useful is a short list of what is not included. You may need a new website but not a new logo; a product video but not a full campaign; or a prototype but not a production-ready application. Naming exclusions helps prevent both sides from assuming that adjacent work is part of the quote.

Flag technical, brand or operational requirements, too. Examples include a platform that must stay in place, accessibility needs, existing brand guidelines, required integrations or approval rules. If something is a strict requirement, label it as such rather than leaving the studio to infer it.

Share examples and explain your content status

References make abstract preferences easier to discuss. Link or attach examples you like and point to the specific qualities that work for you: a clear layout, a calm tone, a certain pace or an accessible way of explaining a complex topic. Also share examples you dislike, with a brief note about what you want to avoid.

An example is a reference, not necessarily a request to copy it. Say whether you are pointing to the overall style, a particular feature or simply the feeling it creates. If you have a brand guide, existing site, product screenshots or earlier campaign materials, include those when they help explain the context.

Be direct about content and assets. Say whether copy, photography, video footage, product details, translations or data are ready, in progress or still need to be created. If you expect your team to provide them, name the owner and likely timing. Missing content can affect the project plan, so it is better to disclose the gap than to imply everything is ready.

Be open about budget, timing and decisions

Sharing a budget range helps a studio recommend a scope that fits your resources. Without it, the studio has to guess whether to propose a lean first phase, a fuller engagement or several options. A range also helps surface a mismatch early, before either side spends time refining an approach that cannot work for you.

A budget is not a demand that the studio spend every dollar. Explain whether the range is a firm limit, an initial phase budget or a planning estimate. If you do not have a number yet, say so and ask what information the studio needs to provide a useful estimate. Avoid asking for the most comprehensive proposal possible without sharing any constraints.

Give the deadline and the reason behind it. A date tied to a conference, launch or internal commitment is more useful than a date without context. Include important intermediate milestones, and say whether the date is fixed or flexible. A studio can then discuss what is feasible and what trade-offs might be needed.

Name the people who will provide input and approve the work. Identify one person who can consolidate feedback if possible, and explain any review or procurement steps that affect timing. If several decision makers have different priorities, mention them early rather than waiting until a proposal or design is underway.

Copy-and-paste creative project brief template

Paste this outline into a document and answer in plain language. If you do not know an answer, write “unknown” and add what you need to find out. The goal is to start a clear conversation, not to fill every blank perfectly.

  • Project name and contact: What should we call the project, and who is coordinating it?
  • Background: What is happening now, and why are you considering this project?
  • Goal: What should change or become possible when the project is complete?
  • Audience: Who is the work for, and whose needs matter most?
  • Scope: What work and deliverables do you expect? Include rough quantities if known.
  • Must-haves: What requirements, platforms, integrations or constraints cannot be changed?
  • Out of scope: What related work should not be included in this project?
  • Examples: What do you like or dislike, and what qualities should the studio notice?
  • Content and assets: What is ready, what is in progress, and what still needs to be made?
  • Budget: What range should the proposal work within? Is it a cap, a first phase or an estimate?
  • Timing: What is the target deadline, why does it matter, and which milestones are fixed?
  • Decision makers: Who will give feedback, approve the work and manage internal reviews?
  • Success measures: How will you judge whether the project has done its job?
  • Open questions: What do you need the studio to investigate or recommend?

Check the brief before you send it

Read the document as if you were the person receiving it. Could someone understand the problem and intended result without knowing your organization already? Are your must-haves separated from nice-to-haves? A brief can be short and still be useful if it answers the questions that affect scope, effort and decisions.

Before you share it, check that you have:

  • Described the business or customer problem, not only the deliverable you have in mind.
  • Identified the primary audience and a practical way to recognize success.
  • Separated essential requirements from preferences and optional work.
  • Included examples with notes about what you want to borrow or avoid.
  • Been clear about the state of content, assets and internal resources.
  • Shared a budget range or said plainly that you need help establishing one.
  • Named the deadline, decision makers and any approval steps that could affect timing.

Once you receive a proposal, check that it reflects your brief. Look for a clear description of the work, deliverables, assumptions, exclusions, client responsibilities and timing. Ask about anything that seems missing or unclear before comparing options. A lower quote may cover a narrower scope, while a broader proposal may include work you do not need.

Where to start

If you are not sure how much detail to include, start with the problem, audience, deadline and budget range. Those answers are enough to begin a conversation; the studio can help clarify the scope and identify what still needs a decision. ASAYA's eight-question project assessment is one way to organize the basics before you reach out.

ASAYA's first call is 30 minutes and free. You can book a call to discuss the project, or review our process to understand how scoping works. Every ASAYA quote is fixed after scoping, so the goal is to agree on the work and its assumptions before a quote is finalized.

Frequently asked questions

Long enough to explain the goal, audience, scope, constraints and decision process. A concise document is useful if it covers those points; mark unknowns rather than guessing.

Yes, if you can. A budget range helps a studio recommend a scope that fits your resources and explain trade-offs. If you do not know the range, say so.

Describe the problem, desired result and constraints, then identify what you want the studio to help determine. You do not need to have the solution fully specified before asking for a proposal.

Daniel Lamberth, founder of ASAYA Media, playing a red cello

Written by

Daniel Lamberth

Founder & Creative Director at ASAYA Media. 15+ years across visual effects, motion, illustration, and software; author of Mastering FLUX.

From first spark to full-scale launch. Creative power, technical precision, and a studio that treats your goals as seriously as you do.