Describe the customer the website needs to help
A small business website design brief begins with the work you want to win. Name the service, customer and area involved. A company that wants more scheduled renovation projects needs different page content from a company mainly handling urgent repairs. Put that distinction into ordinary words before collecting design references.
Note what customers ask before they get in touch
Describe what the customer needs to know before getting in touch. They may need to confirm you handle their property type, work with existing equipment or cover their town. Ask the person who answers inquiries which details create repeated confusion. Those answers can guide the website structure.
Define the inquiry you want
Describe the action in words a customer understands. If the site invites an estimate request, explain what that request starts. Tell the designer whether the customer should expect a call, an inspection or a written response.
List the information staff need
Ask the team which details let them respond usefully. Separate information needed for the first reply from details gathered later. This keeps the brief grounded in a real customer process and gives the form a manageable scope.
Prepare a bathroom-project request
For a hypothetical bathroom project, the first request might need a contact method, a location and a short description. Label that as a proposed workflow, then have the staff responsible confirm what they will actually use.
List the pages and functions the site needs
Write a short list of pages and explain the purpose of each. A service page might help someone decide whether the work is relevant; a project page might show a completed example. Avoid listing pages because another business has them. Give each page a job that serves your own customer.
Specify the essential website functions
List the functions separately from the page names. Estimate requests, booking, downloads and CRM delivery all require decisions beyond visual design. Describe what a customer should be able to do and what the business receives afterwards. Mark features that are essential for the first release and those that can wait.
Describe the form handoff
Describe each function as a task someone can complete. For the inquiry form, include how the visitor recognizes success and how the message reaches the business. A page name alone does not capture these requirements.
Choose the receiving record
Name the destination inbox or CRM record and the staff owner. Note what happens when a required detail is missing. Keep account ownership and connection requirements in the brief while sharing access through normal account controls.
Write the acceptance check
A useful acceptance check is specific: send a marked test request, verify the confirmation and inspect the delivered record. Record who will perform the check so a visual approval is not mistaken for a tested integration.
Explain the existing setup without sharing passwords
Record where the domain, hosting and important business accounts are managed, and who owns access. Include the CRM or booking tool the website needs to work with. Share access through each service’s normal account controls rather than adding credentials to a project brief.
List the current website address, forms and connected tools, and note which parts the new site must retain. Identify any data or content that needs to be moved. This helps the designer plan the transition without relying on a screenshot to explain how the existing system works.
Gather content and identify who can approve it
Collect the service facts, photographs and project details you can accurately use. Keep customer permissions with the material rather than asking the designer to guess what is cleared. If an image is only a reference for style, label it that way so it is not accidentally treated as a usable site asset.
Assign the content decisions
Name the person responsible for each missing piece and the person who gives final approval. A designer can plan around an unfinished section when its owner and expected delivery are clear. Unassigned copy tends to remain an empty box until the deadline is close.
Build an approved evidence list
Make a short list of project photographs, captions and service facts cleared for the site. Mark what is missing and who will supply it. The designer can then use the available evidence without treating an inspiration image as a real project.
Check one project example against the work
Pick one item from that list and compare its caption with the completed work. A colleague who knows the project can confirm what the image shows and whether the explanation needs a limit or condition. Keep that confirmation with the selected item.
Record permission and scope
Store the relevant permission and scope notes alongside the selected material inside the business. The public page needs the useful project explanation; it does not need customer account details or private correspondence included in the design brief.
Agree on how you will review the finished site
Set a realistic budget boundary, target dates and review points. Tell the designer who will collect feedback so the project does not receive conflicting requests from several inboxes. Mark genuine constraints, such as a required launch event or a tool that must remain connected.
Finish with acceptance checks: review the page on a phone, follow important links, test the inquiry route and confirm the delivered record. W3C guidance recommends labels that identify form controls and explain their purpose. Ask for clear labels and understandable feedback in the actual form, then test it with someone unfamiliar with the site.
If you’d like a second pair of eyes on your brief before it goes to a designer, our website design support can help.


