Before you redesign your website, rewrite the brief

When a website feels dated, the natural first conversation is about its appearance. The colours need refreshing. The homepage needs more movement. The layout needs to feel more professional. Those observations can be useful, but they are only the beginning of a good brief.

Before choosing a new visual direction, step back and ask what the website needs to help your business do. That answer should guide the design, the structure, and the technology behind it.

Start with the visitor’s decision

Your visitors arrive with questions. Can you solve their problem? Have you worked on something similar? What does working with you involve? What should they do next?

List the questions your ideal customer asks before making an enquiry. Then match each question to a page or section. This often reveals a more useful structure than copying the navigation from the existing site.

• Use service pages to explain the problems you solve and the scope of your work.
• Use project stories to show your thinking, your contribution, and what you can share with permission.
• Use FAQs to answer practical questions about timing, ownership, and support.
• Give each page a clear next step that fits the visitor’s level of interest.

Audit the content before adding more

A redesign is a good opportunity to remove duplicated descriptions, outdated offers, and generic stock copy. Keep the material that helps a customer understand your business. Rewrite the parts that require too much interpretation.

If much of your work is confidential, explain your approach through clearly labelled concept examples and anonymised descriptions you are authorised to share. You do not need to invent client results to demonstrate sound judgement.

Define what a better website means

Choose a small set of outcomes you can evaluate. That might mean clearer service navigation, a simpler enquiry form, easier content editing, or faster loading on the devices your audience uses. Agree how you will check those outcomes before development begins.

Visual quality still matters. Strong typography, a consistent visual language, and considered interactions help the experience feel intentional. They work best when they support a clear message.

Turn the brief into a practical scope

Write down the pages, content responsibilities, integrations, and launch requirements. Decide what belongs in the first release and what can follow. A short, specific brief gives design and development a useful direction—and gives you a clearer basis for reviewing the result.

Planning a redesign? Talk to AgileGist about your website, or explore our website and development services.