Refspan project guide
How to write a website brief for a developer
A website brief explains what you need the website to achieve, who it serves, and what work is included. You do not need a technical specification to start. A clear description of the business problem gives a developer enough context to ask useful questions and prepare a scope.
Start with the customer and the action
Describe your business, your main customers, and the action you want them to take. A local service business might need enquiries. An agency portfolio might need visitors to review work and request a proposal. Choose the main action before listing features.
Explain what is wrong with the current website, if you have one. “Customers cannot find our service areas” is more useful than “make it modern”. Include the current URL and any pages that need to stay available.
List pages, content, and functionality separately
A page list helps define the size of the website. A functionality list explains what it must do. Keep these separate so a five-page site with a booking system is not mistaken for a simple brochure website.
- Pages: Home, services, About, contact, and any essential supporting pages.
- Content: who supplies the text, images, logo, and brand guidelines.
- Functionality: forms, booking, payments, account access, or integrations.
- Editing: which content your team needs to update after launch.
Give a budget range and explain your deadline
A budget range helps the developer recommend an appropriate scope. If you have a fixed launch date, explain why it matters and when you can supply content and feedback. Ask which dependencies might affect the schedule.
Separate essential launch features from later ideas. This makes it easier to agree a first release and quote optional work separately.
Agree what happens at handover
Ask what access, documentation, and editing guidance will be supplied. Confirm who handles hosting, domain access, backups, software updates, and post-launch changes. These responsibilities should appear in the scope rather than being assumed.
Before approving a quote, check the deliverables, exclusions, review stages, and process for changes. Refspan uses the brief to agree scope before development begins.