How to write a website brief before requesting proposals

A website brief is useful long before a designer opens a layout file. It gives everyone a shared description of the problem and prevents a proposal from becoming a collection of assumptions. For a small business planning a new site, the brief does not need to be a large technical document. It needs to make the important decisions visible enough that different agencies can respond to the same assignment.

Start with the reason for the project. Saying that the website feels dated is understandable, but it is not yet a business objective. Explain what is happening because of that condition. Perhaps prospects misunderstand the services, staff cannot publish updates, or mobile visitors struggle to request an appointment. These are different problems, and each suggests a different way to judge whether the investment was worthwhile.

Describe the audience and their decisions

Identify the main people the website must serve. A commercial contractor might need to help property managers assess capabilities while also helping prospective employees find openings. Those audiences can share a site without sharing the same journey. Write down the questions each group needs answered, the evidence they expect, and the action they should be able to take.

Avoid describing the audience only through broad labels such as professionals or homeowners. Include the situation that brings them to the website. A homeowner comparing providers before a planned renovation has different information needs from someone seeking urgent repairs. The brief should help a team choose an appropriate structure rather than leaving every page to compete for equal attention.

Separate requirements from preferences

List the functions the business genuinely needs: an inquiry form, a searchable project library, a booking connection, or a content management system. For each function, name the person who will use it and the task it supports. This makes it easier to distinguish an operational requirement from an attractive feature that nobody has agreed to maintain.

Visual references can help, but explain what you like about them. You might appreciate a clear navigation system, large project photography, or restrained use of motion. Copying another site wholesale is neither a strategy nor a reliable scope. References work best when they communicate qualities and constraints, including the existing logo, colors, and other brand elements that must remain unchanged.

Make content ownership explicit

State who will write the copy, supply photography, approve claims, and enter existing content. Content work is often underestimated because it does not look as tangible as development. A twenty-page site with approved copy is a different assignment from a twenty-page site that requires interviews, research, image selection, and several rounds of review.

Include a preliminary inventory of pages and files. Mark what should be retained, rewritten, combined, or retired. If the old site receives relevant search traffic, say that preserving valuable URLs and planning redirects is part of the project. Also identify integrations and account owners so access problems can be resolved before they threaten the launch schedule.

Ask for comparable answers

Share a budget range, a desired launch window, and any fixed event driving that deadline. Ask each agency to describe deliverables, exclusions, review rounds, training, and ongoing support. The cheapest proposal is difficult to evaluate when it quietly leaves content preparation or migration to the client.

Before sending the brief, have the internal decision maker approve it. Then use it as a working reference throughout the project. Changes are normal, but they should be visible choices with consequences for timing and cost. A clear brief does not eliminate collaboration. It gives collaboration a useful starting point and makes the final website easier to evaluate against the problem it was meant to solve.