A useful website brief lets a developer estimate the work and lets you compare quotes on the same basis. It does not need to be a long document. It needs to explain who the site serves, what people should do there and what the business can provide.
Start with the customer task. A guest house needs visitors to check rooms and enquire about availability. A recruitment business needs employers and candidates to reach different forms. An online shop needs a dependable path from product selection to payment. Each task leads to a different scope.
Describe the job in one paragraph
Write down what the business does, where it operates and who buys from it. Add the action you want a visitor to take. Include what currently gets in the way, such as unanswered enquiries, difficult product updates or a booking process that relies on repeated phone calls.
Choose a result you can measure. That might be completed quote requests, confirmed bookings or fewer calls asking for opening hours. Record the current position if you have the information. This gives the project a reference point after launch.
List pages and the work behind them
A page list is helpful, but it can hide the difficult work. “Products” could mean five items entered by the developer or a catalogue with hundreds of variants, stock updates and trade pricing. Explain which one you need.
For each main task, describe who starts it, what information they supply and what happens next. If a quote request should reach a particular branch, say how the branch is chosen. If customers need accounts, explain what they can see and change.
Include the systems involved: accounting, bookings, stock, payments, email and customer records. Share the product names and the account owner. The developer can then assess the integration before committing to a price.
Prepare the content you already have
Gather your logo files, service descriptions, product information, photographs and contact details. Label material that needs rewriting or replacing. Confirm who has permission to approve each piece.
Use the details customers need locally: service areas, South African telephone numbers, trading hours in SAST and prices in rands. State delivery areas and collection arrangements where relevant. If a price excludes anything, have the responsible person confirm how that should be presented.
You can include two or three reference websites, with a sentence explaining what you find useful about each. “The product filters are easy to use” gives a designer more direction than “make it modern”.
Name the owners and constraints
Identify who controls the domain, hosting, email and existing site. Check that those accounts are accessible before planning a move. Record any renewals or contract dates that affect the project.
Give a budget range and a preferred launch date, plus the reason for that date. Separate a fixed event from a preference. Name one person who can consolidate feedback and approve work, and allow time for them to do so.
Agree whether the project includes writing, photography, data entry, staff training, hosting and maintenance. Those items often explain the difference between two apparently similar quotes.
Ask for a quote you can check
Ask each supplier to show the scope, assumptions, exclusions, milestones and ongoing costs. Request an explanation of what you will own and how you can update the site. Keep the brief and the accepted quote together.
For a starting point, send webrack your customer task, the pages you expect and the systems the site needs to connect to. We can use that to identify the questions that affect the estimate.