A branding brief brings together the information needed to make decisions about a brand. It does not need to predict the final design. It should explain the business, what is changing and what the engagement needs to help resolve.
A page of adjectives can still leave the task unclear. “Modern, bold and premium” has many interpretations. “We sell a technical product, but our sales materials make it look like a generic service” gives the team a specific communication problem to investigate.
Explain the business and the offer
Describe what the company does, who buys and how a purchase happens. Use plain language rather than internal terminology. Include common questions from sales conversations and identify which product or service is the priority.
Separate evidence from assumptions. A team’s belief about customers is not the same as feedback collected from customers. Naming uncertainty helps the studio plan discovery instead of building decisions on an untested claim.
State the reason for the project
Describe the current situation and the intended change. Are you entering a new market, connecting several products or struggling to explain the offer? Several issues can coexist, but the brief should make the primary one clear.
Give observable examples: sales decks that are rebuilt for every meeting, inconsistent product materials or confusion between a company and product name. Design can address communication; it cannot independently fix product quality, sales operations or fulfilment.
Describe audiences through real decisions
- Who buys, who uses and who approves the purchase?
- What must each person understand before moving forward?
- Which questions or objections recur in actual conversations?
- Where do people encounter the business?
- Which observations are supported by evidence, and which need research?
In a B2B business, the buyer, user and financial approver may be different people. For a global business, add markets and languages. Avoid assuming that one customer profile explains every country or every decision maker.
Give references a purpose
Share examples and explain what interests you: information hierarchy, typography, contrast, photography or clarity. Include references that feel wrong for the business, with reasons. A link without a comment leaves the design team guessing.
References should inform a discussion rather than prescribe imitation. A visual choice that works for another business may communicate something different in your category or market.
Define applications and collaboration
List the first touchpoints that need the identity: website, sales deck, packaging, product interface or social templates. Share current files and constraints, such as retaining a recognised symbol or using an existing website platform.
For teams across time zones, agree on a feedback owner, review windows and the working language. Identify the final decision maker and consolidate feedback before each review. Specify the desired launch, dependencies and available budget range when possible.
A launch also depends on copy, production and implementation. The design schedule should connect to those activities rather than treat the launch date as a standalone deadline.
A practical briefing checklist
- The offer makes sense to someone outside the company.
- The main problem has concrete examples.
- Audiences and recurring questions are identified.
- References include explanations.
- Deliverables and constraints are listed.
- Approval owners, timing and dependencies are clear.
Do you need every answer before starting?
No. Identify unresolved questions rather than invent certainty. The brief starts the conversation; discovery develops the direction. Disagreement within the team about the audience or offer is useful information to surface early.
Explore Wyra’s Branding approach and complete our project brief to organise your context. If you would rather start with a shorter conversation, contact the studio.