The first month of an agency project often disappears before any real work begins. The kick-off happens, the agency asks a few questions, everyone agrees it was productive, and then a week passes waiting for brand assets. Another week goes to a deck that explores the wrong direction. By the time the first concept arrives, the deadline is already tight.
Most of that waste is preventable. A brief is not a decoration attached to a contract. It is the document that records what success looks like, who decides and what the team is not doing.
Start with the problem, not the deliverable
"We need a new website" is a deliverable. "Our trial sign-up rate is half the industry benchmark and the current site cannot explain the product in one screen" is a problem. The second version gives the agency something to solve and a way to judge the work.
Include the evidence you already have: analytics, customer interviews, sales objections, support tickets. Even a small amount of real data is more useful than a page of adjectives about being bold and disruptive.
Six sections every brief needs
One: the business problem and the measurable outcome. Two: the audience, including what they currently believe and what would change their mind. Three: the scope, with named deliverables and explicit exclusions. Four: constraints on budget, timing, technology and brand. Five: the decision-maker, the reviewers and the review process. Six: the definition of done.
The order matters. Agencies can work with an ambitious goal; they struggle with a vague one. They can work with a small budget; they struggle with a budget revealed at the end of the pitch.
Most projects do not fail at the design stage. They fail because nobody agreed who gets to say yes.
Name the decision-maker
A project with six reviewers and no owner will produce six directions and no decision. Name one person who can approve the work and one backup who can act when that person is unavailable. Everyone else can comment; only the owner can approve.
Agree how feedback is collected. Written comments in one place beat a meeting where the loudest voice sets the direction. Consolidate feedback before it reaches the agency so the team is not asked to reconcile contradictory notes.
Key facts
- Name one decision-maker and one backup.
- State the business problem before the deliverable.
- Include budget range and timing constraints up front.
- List what is out of scope in writing.
- Agree the review process and the number of rounds.
Budget and timing are creative inputs
A budget range is not a negotiating tactic; it is a design constraint. It tells the agency whether to propose a focused landing page or a full campaign system. Hiding it usually produces a proposal that is either unaffordable or underwhelming, and both waste a month.
Timing works the same way. State hard deadlines, such as a trade show or a funding round, and separate them from preferences. If everything is urgent, nothing is.
Write down what is out of scope
Out-of-scope does not mean unwelcome. It means the project will not deliver it in this phase. List the pages, languages, integrations and campaigns that are excluded, and note where they might sit in a later phase. This single section prevents most scope disputes.
Include the operational details too: who supplies photography, who writes copy, who hosts the site and who owns the accounts. The answers decide how quickly the project can start.
The bottom line
A useful brief is short enough to read and specific enough to argue with. It names the problem, the audience, the scope, the constraints and the person who says yes. Get those right and the first month produces work instead of meetings.
More agency guidance is on the Creative & Digital Agency desk. For the marketing side of the same project, read Digital Marketing.
