Planning & Ownership · 5 min read
How to Write a Business Website Brief That Gets a Useful Quote
A practical website brief covering goals, customers, pages, content, payments, responsibilities and acceptance checks, with a worked service-business example.
The practical answer
A useful brief explains the business problem, the visitor's next action and what must be delivered. Add real content, operational needs, a budget range, a deadline and acceptance checks so a builder can quote a clear scope.
In this guide
- Describe the job the website must do
- Name the audience and the main action
- List pages by the questions they answer
- Collect content and define who supplies it
- Explain the workflow behind each feature
- Set quality and acceptance checks early
- Add budget, timing and a compact example
- Use the brief as a shared project record
Describe the job the website must do
A useful website brief can begin as a short document. It should explain what is happening now, what needs to improve and what a visitor should do after arriving. Technical terms are optional. Clear business decisions are more valuable than a long list of visual effects copied from unrelated websites.
Replace a broad goal such as having a modern website with a concrete purpose. For a hypothetical catering company, that could be helping office managers understand corporate lunch options and send an enquiry with the date, guest count and location. That statement gives the copy, form and page structure something specific to support.
Name the audience and the main action
Describe the people most likely to use the site, what they already know and what they need before contacting the business. Include practical context such as whether customers usually browse on phones, compare several providers or need approval from a manager. Use evidence from actual enquiries where it exists and label assumptions that need checking.
Choose a primary action: request a quote, book a consultation, buy a product or submit an application. Secondary actions can help, but they should have a purpose. A catering site might make quote requests primary and menu downloads secondary, with both leading toward the same sales conversation.
List pages by the questions they answer
For each proposed page, write the visitor question, the information needed to answer it and the next step. A service page can explain suitability, inclusions, process and how pricing is established. A projects page can show approved work and explain the relevant problem and build without inventing performance figures.
Google's SEO Starter Guide emphasizes useful, understandable content and clear organization. The brief can support that by naming services accurately and supplying specific information. A menu full of vague labels leaves both the writer and the visitor guessing about what the business actually offers.
Collect content and define who supplies it
Create an inventory of the logo, brand colours, service descriptions, product details, prices, photographs, team information and business contact details. Mark each item as ready, needing revision or missing. State which photographs and testimonials have permission for publication and which facts still require approval.
Assign an owner and due date to missing material. If the developer is writing copy or creating basic brand styling, name that work in the scope. If the business must provide product photographs or legal wording, record that responsibility too. A launch date is more believable when the necessary inputs have a delivery plan.
Explain the workflow behind each feature
A feature label such as booking or payments is too broad to quote accurately on its own. Describe the steps. Does the visitor choose an available time, pay a deposit and receive a confirmation? Can staff cancel or reschedule? What should happen when payment fails or an enquiry arrives outside working hours?
List existing tools that must connect, such as business email, a payment provider, a spreadsheet or an approved messaging platform. State whether staff need to edit text, prices and images themselves. Include the number of admin roles and any information that should be visible only to certain people.
Set quality and acceptance checks early
Describe a few things the finished website must demonstrate. A visitor should be able to find the main offer on a phone, submit the required details and receive a clear confirmation. The business should receive that enquiry in the agreed place. Payment-related features need agreed checks for success, failure and an interrupted attempt.
Include accessibility in the conversation from the start. web.dev's accessibility course covers areas such as content structure, keyboard focus, contrast and forms. Agree appropriate checks for the site instead of assuming that a polished screenshot proves the experience works for everyone. Record who reviews these checks and signs off the launch.
Add budget, timing and a compact example
Share a budget range, the required launch date, the reason for that date and who makes final decisions. Separate essential launch features from later ideas. Reference sites are helpful when accompanied by a reason: readable service explanations, an understandable product filter or a simple enquiry path. A reference is direction, not permission to copy another business's work.
A short example could read: Corporate catering for office managers in Lagos. Main action: request a quote. Launch pages: home, catering services and contact. Form: date, location, guest count and contact details. Existing assets: logo and approved food photos. Staff need to edit menus. Online payment can wait until the quote process is clear.
Use the brief as a shared project record
Finish with a list of open questions and the assumptions behind the proposed scope. Ask the builder to confirm deliverables, exclusions, revision rounds, recurring costs, handover and support. When the brief changes, record the effect on cost or timing before the new work begins.
My website packages provide a starting point for that discussion. The website cost guide explains how to compare proposals, while the handover checklist covers what the business needs at delivery. A clear brief helps turn a package heading into an agreed website that the business can review, launch and operate.
Sources & further reading
Official references behind the technical guidance.