Every web design project that runs over budget, delivers a website that misses the mark, or requires three complete redesigns shares a common cause: an unclear brief.
The brief is the most important document in a web design project. It defines what success looks like before a single pixel is placed. A vague brief gives the designer permission to make assumptions — and their assumptions about your business, your audience, and your goals are almost never perfectly aligned with yours.
This guide covers every component of a strong web design brief, in the order you should address them.
1. Business Context: Why Are You Building This Website?
Start with the business reason for the project. This is not "we need a new website" — that is a description of the output, not the goal. The goal might be:
- We are launching a new company and need our first proper web presence
- We have outgrown our current website and it no longer reflects our positioning
- Our current site is not converting visitors into leads and we are losing business to competitors
- We have rebranded and need the website to reflect the new brand identity
- We are raising a Series A and the website needs to work alongside the pitch deck
The business context tells the designer what the website is supposed to accomplish in commercial terms. A website built to establish a new company's credibility looks different from a website built to improve lead conversion from existing traffic.
2. Target Audience: Who Uses This Website?
Describe your primary audience with specificity:
Bad: "Our customers are businesses of all sizes."
Better: "Our primary buyer is a finance director at a company with 50–500 employees. They are typically 35–55, evaluate software with their IT and security team, and take six to twelve weeks to make a purchase decision. They care about security, integration with existing tools, and ROI clarity."
A designer who understands your buyer designs for that buyer. Navigation decisions, information hierarchy, visual tone, and CTA placement all change depending on who needs to be convinced and what they need to see.
List multiple audiences if relevant, and rank them by priority. A PropTech platform might serve both urban planners and real estate investors — the website should serve both, but one is primary.
3. Brand Identity Assets: What Do You Already Have?
List every brand asset that exists and must be used in the project:
Logo: File formats available (SVG, AI, EPS, PNG). Whether there is a horizontal version and an icon version.
Colors: Primary and secondary brand colors as hex codes. Ideally also as RGB, CMYK, and Pantone references if print use is involved.
Typography: Primary and secondary typefaces, and whether you have licensed versions or rely on Google Fonts / Adobe Fonts.
Brand guidelines: If these exist, share them. If they don't, that is important information — the designer will need to make brand decisions as they go unless you clarify the constraints.
Photography and imagery: Existing photo library, stock subscription, or a photography brief for new assets.
If your brand identity is incomplete or inconsistent — different logos used in different places, colors that have drifted from the original spec — address this before the web design project starts. Our brand identity checklist covers what a complete brand system needs to include.
4. Pages and Content: What Goes on the Site?
List every page the website needs:
- Homepage
- About / Company
- Services or Products (list each)
- Blog / Resources (if applicable)
- Case Studies or Portfolio (if applicable)
- Contact
- Legal (Privacy Policy, Terms)
- Any additional pages specific to your business
For each page, state: who writes the content (you, a copywriter, or the designer/developer), whether existing content exists or needs to be created from scratch, and any functional requirements (forms, calculators, embedded tools).
Be explicit about copywriting. Most web design quotes do not include copywriting. If you expect the designer to write the page content, state this and expect to pay for it separately. If you are writing the content, state when it will be delivered — delayed content delivery is the single most common cause of project delays.
5. Technical Requirements: What Does the Site Need to Do?
Answer these questions explicitly:
Hosting: Do you have a hosting preference or requirement? (Vercel, AWS, your existing server)
CMS: Do you need non-developers to update content? If so, which CMS? (Webflow CMS, Contentful, Sanity, WordPress)
Integrations: What tools need to connect to the website? (CRM, email marketing, analytics, payment processing, live chat, calendar booking)
Performance requirements: Are there specific load time or Core Web Vitals targets?
Accessibility requirements: WCAG 2.1 AA compliance for public sector or enterprise clients
Existing infrastructure to preserve: Domain registrar, existing DNS configuration, email server
Analytics: Which analytics tools need to be installed and configured?
6. Examples: What You Like and What You Don't
Provide three to five website examples you find compelling — not necessarily in your industry, but that achieve an aesthetic or structural goal you want. Alongside each, note what you like about it.
Also provide examples of websites you actively dislike or want to avoid. Common negative examples: "we don't want it to feel like a generic SaaS landing page" or "we don't want it to feel corporate and cold."
This is not about copying — it is about aligning aesthetic vocabulary before the project starts. Without examples, the designer's interpretation of "clean and modern" may be very different from yours.
7. Success Metrics: How Will You Measure Whether the Website Is Working?
Define what success looks like in measurable terms:
- Lead form submissions increase by X%
- Bounce rate decreases from current baseline
- Average session duration increases
- A specific conversion action (demo request, download, purchase) increases
A designer who knows the success metric optimizes for it. Without a defined metric, "success" is subjective and unmeasurable.
8. Budget and Timeline
State both clearly. Withholding budget information to negotiate a lower quote does not work — it produces either an underscoped quote that expands during the project or an overscoped quote that does not match your actual investment level.
Budget honesty produces: a proposal scoped to what you can actually afford, no surprises during the project, and a designer who has realistic expectations about the time they can invest.
Timeline should include: when the site needs to be live, any fixed deadlines (product launch, fundraise, conference), and when you can deliver content if you are writing it.
Ready to brief a web design project properly?
Evoke Studio takes a structured brief before every project — we help you clarify what you need before we quote. Fill out our contact form and we will get back to you with a structured brief template.
Eight components: business context (why you need the site and what it should accomplish), target audience (who uses it and what they need), brand identity assets (logo, colors, typography, guidelines), page list with content ownership, technical requirements (hosting, CMS, integrations), design examples (what you like and dislike), success metrics, and budget and timeline. A brief that covers all eight produces better results and fewer misalignments.
Long enough to cover the eight components above, short enough to be read in fifteen minutes. A one- to two-page brief with clear sections is ideal. Bullet points over prose for most sections. The brand identity section should include actual file links, not descriptions.
Yes. Withholding budget produces either an underscoped quote that grows during the project or an overscoped quote that cannot be delivered at cost. A designer who knows the budget can scope accordingly and tell you clearly whether your requirements are achievable within it — which is the information you need before committing.
Establish it first, or include it in the project scope with a clear design phase before web design begins. Starting a website without a brand identity means the designer makes brand decisions as they go — which is expensive to correct later and usually produces an incoherent result.
Start with the business problem, not the design solution. 'We are losing leads because visitors don't understand what we do' is a better brief starting point than 'we want a cleaner design.' A good designer will translate the business problem into a design direction. Your job is to describe the problem clearly — their job is to solve it.
Not all of it, but a content outline for every page before design begins, and final content before development begins. Design created before content exists often needs to be restructured when the actual content does not fit. Real content — even rough — produces better design than placeholder Lorem Ipsum.
Quick Answers
Describing the output ('we want a redesign') rather than the business goal ('we want to increase demo requests from enterprise buyers'). A brief focused on outcomes gives the designer a target to design toward. A brief focused on features gives them a checklist to execute without a clear success criterion.
The designer fills the gaps with their own assumptions. Their assumptions about your audience, your tone, and your priorities are rarely perfectly aligned with yours. The project takes longer (more rounds of revision to align on direction), costs more (revision rounds are billable), and often produces a result that is technically competent but not quite right.
You should write the business context, audience, content, and technical requirements — you know these. The designer should contribute to the brief review, asking clarifying questions and flagging missing information. Some designers provide a brief template; filling it in together in a kick-off call is often the fastest path to an aligned brief.
State clearly that no brand identity exists and include brand direction as a required deliverable before website design begins. Provide: company description, target audience, competitors you admire (and why), aesthetic references (from any industry), and the tone of voice you want to communicate. This gives the designer enough to build a brand foundation, then the website on top of it.