How to write a useful website redesign brief
You do not need to arrive with the design solution. You do need to explain what changed, who the site is for, what is getting in the way and how the project will make decisions.
Replace “make it modern” with an observable problem
Perhaps prospects misunderstand the service, a new offer is missing, qualified visitors cannot find proof or enquiries reach the wrong team. Include examples and customer feedback. Separate what you know from what the project still needs to test.
Name the person and the decision
Who is evaluating the business, and what must they understand before contacting you? List the questions that repeatedly appear in sales calls. Those questions are usually more useful for content planning than a folder of competitor animations.
Count the evidence you actually have
List case studies, approved testimonials, biographies, photography and product material. Mark what is ready, what needs rewriting and who can approve it. Never build a launch schedule around proof that does not exist yet.
Make the constraints visible
Include the platform, pages, integrations, accessibility needs, budget range and intended launch window. Name who owns copy, design, development, analytics and maintenance. Ask the proposal to state exclusions as clearly as deliverables. “Website redesign” is not a scope.
Use this short brief
Our business has changed because __. We serve __. Visitors need to understand __ and then __. The current website makes that difficult because __. We can provide __. Our budget and timing are __. The decision-maker is __. Success will be assessed using __.
Measure the problem you started with
If the problem was understanding, test comprehension. If it was poor-fit enquiries, track enquiry quality. If it was a broken journey, measure completion. Record a baseline when possible. More traffic does not prove that the right person understood the page.