Write a website brief a builder can price

Define the work before you compare quotes.

Begin with one visitor task

Write down what a visitor needs to accomplish: request a service estimate, book an appointment, or find opening hours. Then identify the information they need before taking that step. A brief that only asks for a modern website leaves the builder guessing about content, integrations and review work.

Make a page-and-evidence inventory

List each proposed page, its intended reader, the question it answers, and who supplies the content. For a service page, collect the service scope, exclusions, service area and a real example you have permission to show. For contact, verify the mailbox and response process. Do not invent testimonials to fill a layout.

Separate a deliverable from an assumption

State who writes copy, supplies photography, purchases licenses, connects forms, migrates existing URLs and checks mobile layouts. Specify the number of review rounds and the handover format. Ask whether recurring fees include changes or only hosting. These details explain price differences more usefully than comparing page counts alone.

Define acceptance with a small test

An example acceptance test is: a visitor on a narrow mobile screen can find the service, understand its limits, submit an enquiry, receive a clear confirmation, and have that enquiry reach the intended inbox. Test failure and validation states too. Record the test date and who checked the receiving inbox.

A brief you can copy

Project purpose: __. Main visitor task: __. Required pages: __. Content owner: __. Integrations: __. Existing URLs to preserve: __. Accessibility checks: __. Launch acceptance test: __. Monthly owner and budget: __. This is a starting worksheet; add the constraints specific to your project.