Blog
 » 

Webflow

 » 
Creative Brief for a Website Redesign

Creative Brief for a Website Redesign

How to write a clear creative brief for a website redesign — what to include, what agencies need, and how to align teams from day one.

Daniel Moreno

By 

Daniel Moreno

Updated on

Jul 10, 2026

.

Jesus Vargas

Reviewed by 

Jesus Vargas

Founder

Why Trust Our Content

Creative Brief for a Website Redesign

A creative brief for a website redesign is the document that determines the quality of every proposal it generates. A specific, well-structured brief produces a specific, accurate, and comparable proposal.

A vague one produces a range of guesses from different agencies, making it impossible to evaluate them against each other or against your actual requirements.

The brief is the agency's instruction set for every design, content, and technical decision they will make on your behalf.

Every gap in the brief becomes a decision the agency makes without your input. The more complete the brief, the fewer surprises you will encounter in the proposals and in the work.

 

Key Takeaways

  • The Brief Is the Agency's Instruction Set: Every design, content, and technical decision an agency makes will reference the brief; gaps become gaps in the final output.
  • A Brief Is Not a Scope of Work: The brief defines what you need; the scope of work is the agency's translation of that into priced deliverables. They are different documents.
  • Specificity Reduces Proposal Risk: The more specific the brief, the more accurate and comparable the proposals; vague briefs invite agencies to scope very different projects.
  • Brand and Audience Sections Are Non-Optional: Agencies that don't understand who the site is for and what the brand stands for cannot make defensible creative decisions.
  • A Brief Is a Living Document: The first version captures current thinking; it is updated through discovery as research adds clarity and challenges initial assumptions.

 

Webflow Development Services

Webflow Experts On-Demand

Whether you're starting fresh or need a full revamp—we create fast, modern Webflow sites built for growth.

 

What a Creative Brief Contains and Why

How the brief connects to planning is the first question to answer before writing a single section. The brief is not the project plan.

It is the document that makes the project plan possible by defining what success looks like before any design work begins.

A brief that is written after planning has begun is too late. The brief should precede the agency engagement, not follow it.

 

The Brief Is Different From the Requirements Document

Confusing the brief with the requirements document is one of the most common and most damaging planning mistakes in website redesign projects.

  • Requirements Document Lists What Must Exist: The requirements document covers functional specifications: page types, integrations, features, accessibility standards, and technical constraints.
  • The Brief Provides Strategic Context: The brief answers why the site is being redesigned, for whom it is being built, with what brand voice, and toward what measurable goals.
  • Design Decisions Reference the Brief, Not Requirements: When a designer chooses a typography hierarchy, a color approach, or a navigation model, they are referencing the brief's audience and brand direction, not the requirements list.
  • Both Documents Are Required: Neither substitutes for the other; a project with only requirements and no brief produces technically correct work without strategic direction.

 

The Six Core Sections of a Redesign Brief

Every redesign brief requires six sections. Each is necessary; none is optional.

  • Business Context and Goals: What the company does, where it currently stands, and what the redesign must achieve, expressed in measurable terms.
  • Target Audience: Who uses the site, what they need, and what objections or concerns they bring to the evaluation.
  • Competitive Landscape and Differentiation: Who the competitors are, what they do well digitally, and what the new site must communicate that competitors don't.
  • Brand and Visual Direction: Current brand guidelines status, visual references with reasoning, and firm visual constraints.
  • Content and Messaging Direction: Tone of voice, core messages, and content production responsibilities with timelines.
  • Scope, Budget, and Timeline: The parameters within which the agency must design their proposal, with enough specificity to produce comparable estimates.

 

Who Should Contribute to the Brief

A brief written by one person is almost always incomplete. The brief benefits from input across the organization.

  • Leadership Provides Business Goals: Company leadership articulates the strategic objectives the redesign must serve; without this input, the brief may optimize for marketing goals at the expense of revenue goals.
  • Sales Contributes Audience Intelligence: Sales teams understand the objections prospects raise, the questions they ask, and the trust signals that matter most in the buying process.
  • Support Identifies User Problems: Customer support logs contain a record of where the current site fails users; this intelligence shapes both the information architecture and the content priorities.
  • IT Documents Technical Constraints: Technical requirements, integration dependencies, hosting constraints, and security requirements must be documented before an agency can accurately scope the technical work.

 

Business Context and Goals Section

Requirements that feed the brief from functional requirements to strategic goals requires a section of the brief dedicated to grounding every design decision in measurable business reality.

The business context section is the first section any agency reads and the one that most directly shapes how they interpret every other section.

 

Describing the Business and Its Current Position

The agency needs to understand the company before they can design for it. This section provides that context.

  • State What the Business Does in Plain Language: Describe the core business model, primary revenue source, and main customer type in two to three sentences that anyone outside the industry can understand.
  • Define the Competitive Position: Explain where the business sits in its market: category leader, challenger, niche specialist, or emerging competitor. This shapes the design's competitive posture.
  • Name the Primary Target Market: Describe the geographic scope, industry focus, company size range, and buyer persona of the primary customer the site must serve.
  • Acknowledge Current Digital Weaknesses: Describe honestly where the current site is failing: low conversion rates, poor mobile performance, weak SEO, or confusing navigation. This focuses agency energy on real problems.

 

Documenting Current Site Performance

Baseline data transforms the brief from an aspirational document into an accountability framework.

  • Current Conversion Rate Is the Primary Baseline: The number of qualified leads or purchases generated per 100 visitors is the metric the redesign must move; document it precisely.
  • Monthly Organic Traffic Volume Matters: The current organic search traffic volume sets the baseline that SEO preservation efforts must protect and that growth strategies must exceed.
  • Top Five Pages by Traffic Identify What Works: Understanding which current pages drive the most traffic informs what must be preserved and what design patterns are already working.
  • Where the Site Fails Is As Important As Where It Works: Document specific pages with high exit rates, form abandonment, or low conversion; these are the problems the redesign must solve.

 

Stating Business Goals in Measurable Terms

Vague goals produce vague designs. Specific, measurable goals produce designs with clear purpose.

  • Use Current Baseline and Target Format: A goal stated as "increase qualified form submissions from 45 per month to 80 within 90 days of launch" is actionable; "increase leads" is not.
  • Three to Five Goals Is the Right Range: Fewer than three risks missing important objectives; more than five risks diluting focus across too many competing priorities.
  • Connect Each Goal to a Business Outcome: A goal should connect to revenue, cost reduction, or strategic advantage; goals that don't connect to business outcomes rarely receive appropriate design investment.
  • Assign a Priority Order to the Goals: When design tradeoffs arise during the project, the priority order of goals provides the decision framework; without it, every decision becomes a negotiation.

 

Audience and Competitive Context Section

The audience and competitive sections are the sections most briefs treat superficially. They are also the sections that most directly determine whether the design is differentiated or generic.

Stakeholder input for brief accuracy is most important in this section because audience understanding requires input from people who talk to customers and prospects regularly, not just those who manage the website.

 

Writing Audience Personas for the Brief

Personas written from real customer data produce design decisions that resonate with actual buyers. Personas written from internal assumptions produce design decisions that miss the mark.

  • Base Personas on Real Data, Not Guesses: Combine CRM data, sales team interviews, customer support logs, and user research to ground each persona in observed behavior rather than internal assumptions.
  • Include Role, Goal, Objection, and Trust Signal: Each persona should describe the person's job context, primary goal on the site, key concern or objection, and the trust signals that most effectively address that concern.
  • Describe Primary Content Needs per Persona: Identify the two or three pieces of content each persona most needs to find; these become the high-priority content items in the information architecture.
  • Keep Personas Focused to Two or Three: More than three personas indicates either genuine audience complexity that warrants separate site sections, or over-segmentation that will dilute design focus.

 

Describing the Competitive Landscape

A competitive landscape section that lists company names without analyzis forces agencies to conduct their own research and arrive at their own conclusions, which may not match yours.

  • List Three to Five Direct Competitors With URLs: Identify the sites that your prospects compare you against in their evaluation process; include the specific URL of their main site and any pages worth examining.
  • Describe What Each Does Well Digitally: Note specific digital strengths: clear value proposition, strong case study library, excellent mobile performance, or effective use of social proof.
  • Identify Specific Weaknesses to Exploit: Where competitor sites fail to serve the shared audience, note those gaps explicitly; the brief should mandate that the new site fills them.
  • Include One Benchmark Example per Competitor: A specific URL that demonstrates a feature or design approach worth matching or beating turns the competitive analyzis from abstract to actionable.

 

Articulating Differentiation Requirements

The differentiation mandate is the most strategic content in the entire brief. It defines what the design must communicate that competitors do not.

  • State the Differentiation in One Clear Sentence: The brief should articulate in one sentence what makes this company the right choice for its ideal client in a way that competitors cannot legitimately claim.
  • Design Must Express Differentiation Visually: Ask specifically how the visual design should communicate the stated differentiator; this connects the brand section to the competitive section through design direction.
  • Proof Points Must Support Differentiation Claims: Every differentiator needs a corresponding proof point; claims without evidence are claims competitors can also make, which eliminates the differentiation value.
  • Test Differentiation Against Real Prospects: Before finalizing the differentiation statement in the brief, validate it with two or three actual clients or prospects to confirm it resonates outside the building.

 

Brand and Visual Direction Section

Brand context for redesign brief must be captured in the brief before agencies begin interpreting the design opportunity. Without clear brand guidance, agencies make aesthetic assumptions that often require expensive revision rounds to correct.

The brand and visual direction section is where the brief most directly enables confident creative decisions. Agencies given clear visual direction produce stronger first concepts.

 

Brand Guidelines and Asset Status

The brand guidelines section must be honest about the state of existing brand assets, including acknowledging when they don't exist or are not current.

  • Attach Current Guidelines and Note Their Status: Whether the guidelines are current and approved, partially outdated, or undergoing revision, state this clearly so agencies can factor it into their process and timeline.
  • Flag Simultaneous Rebrand Activities: If a brand refresh is happening at the same time as the redesign, this is a significant scope item; agencies need to know whether they are designing against final brand assets or provisional ones.
  • Document What Guidelines Don't Cover: Most brand guidelines are incomplete; noting what they don't address, such as motion, interactive patterns, or digital-specific typography, helps agencies identify where they need creative latitude.
  • Provide Logo Files in Multiple Formats: Include vector logo files in all standard formats; agencies cannot design or prototype effectively without high-quality asset files from the project start.

 

Visual Reference Examples With Reasoning

Visual references with reasoning are the most useful single input in the brief's brand section. References without reasoning produce guesswork.

  • Provide Five to Eight External Website References: Identify websites that the brand admires from outside the industry; within-industry references risk producing work that resembles competitors rather than differentiating from them.
  • Explain Specifically What You Admire: "We like the whitespace density and typographic hierarchy" is useful direction; "we like this website" is not. Specific observations translate directly into design decisions.
  • Include Examples of What You Do Not Want: Negative visual references are as useful as positive ones; a site that represents the exact wrong aesthetic provides a clear boundary the design must not cross.
  • Reference Functional as Well as Aesthetic Elements: Include references for navigation patterns, hover interactions, content hierarchy, and page structure, not only for visual aesthetic and color palette.

 

Visual Constraints and Non-Negotiables

Hard constraints prevent wasted creative effort on directions that will be rejected regardless of their design merit.

  • State Competitor Color Exclusions Explicitly: If the brand cannot use a particular color because a competitor owns it in the category, state this clearly; discovering it during design review rounds is expensive.
  • Define the Brand's Tone Range: Corporate-to-warm, formal-to-conversational, exclusive-to-accessible are axes on which the brand's visual tone can be calibrated; position each one explicitly.
  • Name Any Mandatory Visual Elements: If the brand has an icon, a pattern, a photographic style, or a graphic element that must appear on the site, state that requirement in the brief with examples.
  • Describe What the Site Must Not Look Like: "Must not look like a government agency," "must not feel like a startup," and "must not feel clinical or cold" are constraints that save significant revision time.

 

Content Direction Section

Content strategy in the brief is the section that most agencies treat as an afterthought and most clients fail to complete.

This section determines whether the site launches with content that serves the audience or with placeholder copy that never gets replaced.

Content direction in the brief is not a full content strategy. It is the parameters within which the content strategy will be developed.

 

Tone of Voice and Messaging Principles

Tone of voice direction ensures that content written by multiple people across a long project feels consistent with the brand rather than random.

  • Define the Voice in Contrasting Pairs: "We are authoritative but not arrogant, expert but not inaccessible, direct but not blunt" is actionable voice guidance that writers can apply to every page.
  • Include Copy Examples That Are On-Brand: Pull two or three excerpts from current materials that represent the brand voice well; these become the calibration reference for every content decision.
  • Include Copy Examples That Are Off-Brand: Showing what the brand does not sound like is equally instructive; include one or two examples of copy that misrepresents the tone or voice.
  • Describe the Reading Level Target: Whether the site should be written at a professional, technical, or general consumer reading level shapes every vocabulary and sentence structure decision across the project.

 

Core Messages That Must Come Through

Core messages are the non-negotiable communications that every visitor must receive, regardless of which pages they visit.

  • Primary Value Proposition in One Sentence: The value proposition is the core message that explains what the site does, for whom, and why it matters; every page should reinforce it.
  • Primary Trust Signal Must Be Visible: The one credential, proof point, or customer outcome that most effectively converts skeptical prospects should appear on the homepage and on high-conversion pages.
  • Primary Differentiator Must Be Explicit: The brief must state clearly what the new site must communicate that competitors cannot match; content writers need this as a mandate, not a suggestion.
  • Primary Call to Action Must Be Consistent: If the primary conversion goal is a demo request, a free consultation, or a trial signup, every page should funnel toward it with consistent language and placement.

 

Content Responsibilities and Timelines

Undefined content responsibility is the most common cause of website redesign delays. Agencies cannot design around content they don't have; clients cannot contribute content they haven't planned for.

  • Assign Each Content Type to a Named Owner: Homepage copy, service page content, blog articles, and case studies each need a single named person responsible for delivery on a committed date.
  • State Content Readiness Dates in the Brief: If content will be delivered in phases, the brief should say so with specific dates; agencies design timelines around content availability, and surprises here delay launch.
  • Scope Agency Content Responsibilities Explicitly: If the agency is responsible for writing any content, state that in the brief as a scoped workstream with deliverables, not as a general expectation that someone will figure out.
  • Identify Content That Must Be Migrated: Existing content being carried over to the new site should be listed and its readiness status noted; migration content that requires rewriting is a scoped task, not a default inclusion.

 

How the Brief Is Used in Discovery

Brief use during discovery phase is the topic most clients don't grasp until they are inside the process. Knowing how the brief will be used helps clients write it more strategically and participate more effectively.

Discovery does not start from scratch. It starts from the brief and advances from there based on research findings, stakeholder interviews, and competitive analyzis.

 

The Brief Is a Starting Point, Not a Final Answer

The brief captures the best current thinking before research begins. Discovery is the process of testing that thinking against evidence.

  • Discovery Challenges Brief Assumptions: Stakeholder interviews frequently reveal audience insights that contradict the brief's persona descriptions; this is productive, not problematic.
  • Competitive Research May Shift Differentiation: What seems like a unique differentiator in the brief may prove to be a category hygiene claim once competitors are analyzed in depth; the brief must accommodate this revision.
  • User Research Updates Audience Understanding: Actual user interviews and usability testing of the current site often reveal task priorities that differ significantly from what internal stakeholders assumed.
  • Treat Brief Revisions as Progress: Sections of the brief that are updated through discovery represent clarity gained; teams that treat the brief as immovable miss the value of the discovery process entirely.

 

Gaps in the Brief Become Discovery Priorities

Agencies who read a brief carefully can tell where the client team is confident and where they are uncertain. Uncertainty in the brief becomes a structured research question in discovery.

  • Weak Persona Sections Trigger User Research: A brief that describes audiences vaguely will prompt the agency to propose user interviews or survey research as a discovery deliverable to fill the gap.
  • Missing Performance Baselines Generate Analytics Work: When the brief doesn't include current site performance data, the agency's discovery phase includes an analytics audit to establish the missing baselines.
  • Vague Differentiation Triggers Positioning Workshops: A brief that can't articulate differentiation clearly will trigger a competitive analyzis and positioning workshop as a discovery output before design begins.
  • Undefined Content Responsibilities Become Discovery Risks: If content responsibilities are unclear in the brief, they become a discovery conversation that must be resolved before the project scope can be confirmed.

 

Sign-Off on the Refined Brief Before Design Begins

The most common error in the brief-to-design transition is allowing design to begin before the brief has been updated to reflect discovery findings.

  • Discovery Produces a Refined Strategy Document: At the end of discovery, the agency should produce an updated brief or strategy document that reflects research findings and revised audience and differentiation thinking.
  • Client Approval on the Refined Brief Is a Gate: Design should not begin until the client has approved the updated strategy document; beginning design against an unresolved brief produces work that fails review.
  • The Refined Brief Governs All Design Decisions: From this point, when creative decisions are challenged in review, they should be evaluated against the refined brief, not against personal preference or late-changing requirements.
  • All Stakeholders Must Review the Refined Brief: If a stakeholder who was not involved in discovery can veto design decisions in review, they must read and approve the refined brief before design begins.

 

Conclusion

A strong creative brief for a website redesign reduces proposal risk, accelerates discovery, and produces better design because every creative decision has a clear rationale rooted in real goals and real audience understanding.

The brief is not overhead; it is the investment that makes everything downstream faster, cheaper, and more likely to succeed.

The most productive first step is writing the business context and goals section this week, before any other section.

That one section often reveals more strategic gaps in the project thinking, and in the project strategy, than any other exercise in the entire redesign process.

 

Webflow Development Services

Webflow Experts On-Demand

Whether you're starting fresh or need a full revamp—we create fast, modern Webflow sites built for growth.

 

LOW/CODE Agency Helps You Build the Brief Before the Proposal Stage

LOW/CODE Agency offers pre-engagement briefing workshops that produce a clear, agency-ready brief before proposals are requested. We have seen too many projects derailed by vague briefs to skip this step.

We are a strategic product team, not a dev shop. Our briefing process begins with stakeholder interviews, competitive analyzis, and audience research, producing a brief that is grounded in evidence rather than internal assumptions.

  • Stakeholder Discovery Workshops: We facilitate structured sessions with leadership, sales, marketing, and support teams to surface the business goals, audience insights, and competitive context the brief requires.
  • Audience Research and Persona Development: We develop brief-ready audience personas from real customer data, sales team intelligence, and user research rather than from internal assumptions.
  • Competitive Analyzis and Differentiation Definition: We analyze competitor digital presence and help teams articulate a differentiation mandate that is specific, defensible, and reflected in every design decision.
  • Brand Voice and Messaging Framework: We develop the tone of voice and core messaging hierarchy that gives content writers a consistent framework across every page of the redesigned site.
  • Visual Direction Development: We help teams identify and articulate visual references with reasoning, brand constraints, and design direction that gives designers confident creative parameters.
  • Requirements Documentation: We translate business goals and audience needs into a formal requirements document that complements the brief and enables accurate technical scoping.
  • Discovery Phase Management: We run the post-brief discovery process that tests assumptions, fills gaps, and produces the refined strategy document that governs all design decisions.

With over 350 products delivered for clients including Coca-Cola, American Express, Sotheby's, Medtronic, Zapier, and Dataiku, LOW/CODE Agency brings the briefing rigor that produces better proposals and better outcomes.

Our redesign agency brief and discovery process is designed for teams that want to invest in getting the foundation right before the design work begins.

Start with a scoping call

Last updated on 

July 10, 2026

.

Daniel Moreno

Daniel Moreno

 - 

Web Developer

Daniel is a Web Developer at LOW/CODE Agency who has been building websites in Webflow since 2022. With a background in graphic design, he turns the design team's concepts into fast, responsive sites

Custom Automation Solutions

Save Hours Every Week

We automate your daily operations, save you 100+ hours a month, and position your business to scale effortlessly.

FAQs

Watch the full conversation between Jesus Vargas and Kristin Kenzie

Honest talk on no-code myths, AI realities, pricing mistakes, and what 330+ apps taught us.
We’re making this video available to our close network first! Drop your email and see it instantly.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Why customers trust us for no-code development

Expertise
We’ve built 330+ amazing projects with no-code.
Process
Our process-oriented approach ensures a stress-free experience.
Support
With a 30+ strong team, we’ll support your business growth.