Small Business Website Brief: A Filled-In Example and Copyable Template

A small business website brief explains what the website must help customers do, what the project includes and who will supply the information. It gives a designer enough context to recommend a solution without guessing how your business operates.

You do not need a long strategy document to begin. You do need specific answers about customers, services, pages, content and approval. The example below uses a fictional local business, Cedar Home Repairs, to demonstrate the level of detail. Its requirements are illustrative, not results from a real client project.

A filled-in website brief example

Business: Cedar Home Repairs provides scheduled minor repairs for homeowners in a defined service area. It does not provide emergency call-outs or major structural work. The website should explain those boundaries before someone sends an enquiry.

Primary audience: Homeowners who have several small repair jobs and want to understand whether the company can help. A secondary audience is landlords arranging non-emergency maintenance. The homepage should prioritize the homeowner journey while making landlord enquiries possible.

Primary goal: Help an eligible customer submit a useful quote request. A useful request includes the location, type of work and preferred contact details. The project should not be judged only on whether the visual style looks newer than the old site.

Current problem: Customers regularly ask whether the business covers their area and whether small jobs are accepted. The new site should answer both questions before the enquiry form. These are business observations supplied by the fictional owner, not assumptions the designer should invent.

Define the pages and what each one must do

The proposed homepage introduces the service, states the coverage area and directs visitors to request a quote. A services page explains accepted work and exclusions. An about page introduces the team using approved information. A contact page explains the enquiry process and contains the request form.

Each page needs an owner for factual content. In this example, the business owner confirms service descriptions and coverage. An office coordinator supplies the public contact details. The designer organizes and presents the material but is not responsible for inventing operational promises.

The brief also records what is excluded: online payments, customer accounts, live scheduling and emergency support. If any of those become necessary, the team will assess the additional work before changing the scope. This is more useful than a vague requirement to make the site “future proof.”

Describe the content and assets honestly

The company has an existing logo and permission to use six project photographs. Two team photographs are still needed. The service descriptions exist as rough notes and require editing. The brief identifies these as separate tasks with named owners rather than marking all content as ready.

Any testimonials require permission and accurate attribution before publication. Stock photographs, if used, should not imply that they depict completed company work. If prices are not confirmed, the designer should not add illustrative prices that might accidentally reach the live site.

For each image, record where it will be used and whether the business has the necessary rights. Keep original files accessible to the person preparing the site. A screenshot of a logo from an old brochure is a warning to obtain a better source, not a complete brand asset pack.

Write requirements that can be checked

Replace “easy to contact us” with “the main service pages show a clear route to the quote form and the public telephone number.” Replace “works on mobile” with the tasks that need checking: read service coverage, navigate between pages and submit the form on a phone.

For Cedar Home Repairs, the review conditions are: the coverage area is visible; excluded jobs are explained; required form fields are agreed; and the person handling enquiries has tested receipt of a submission on the built site. A mockup can confirm the presentation, but the final submission test requires a functioning website.

Avoid using the brief to promise an exact search ranking or sales increase. Define the intended outcome, then decide how performance will be measured after launch. A goal and a guaranteed result are different commitments.

Copyable small-business brief template

Business and offer: We provide [services or products] for [audience] in [area or market]. We do not provide [important exclusions].

Website purpose: The primary visitor action is [action]. The current obstacle is [known problem]. We know this because [customer questions, enquiries or other evidence].

Pages and functions: The project includes [pages] and [functions]. The project excludes [items]. External services involved are [providers], owned by [person].

Content and assets: Ready materials are [list]. Missing materials are [list]. The person supplying each missing item is [owner], with an agreed date of [date].

Review and approval: The decision owner is [name or role]. Other reviewers check [areas]. Feedback will be consolidated in [place]. Design approval covers [scope], and launch checks cover [scope].

Practical constraints: The target launch window is [date or range], the budget range is [range], and dependencies are [items]. The team must confirm [open questions] before finalizing the proposal.

Handle unknown answers without delaying everything

Mark uncertain details as open decisions and explain their impact. If you do not know whether online booking is required, identify who will decide and when. The designer can explore an enquiry-first layout while making clear that booking functionality could change the work.

Separate decisions that block design from details that can be supplied later. The primary audience and conversion action often affect the whole page structure. A final staff photograph may not, provided the team agrees on a placeholder and replacement deadline.

Review the brief together before treating it as the project baseline. A written answer can still mean different things to different people. Ask the designer to explain the proposed customer journey back to you and resolve mismatches before producing detailed pages.

Turn the brief into a design review

When the mockup is ready, review it against the brief instead of starting again with personal preferences. For the example business, ask whether a homeowner can identify accepted jobs, understand coverage and find the enquiry route.

A Swelik preview link can present the exported design for this conversation. Include the brief and the questions you want answered in the accompanying message. Keep technical launch checks separate because an image preview does not demonstrate working forms or integrations.

Use the broader web design brief template for a general project structure and the website checklist for clients to track your responsibilities after the brief is agreed.

Frequently asked questions

How long should a small-business website brief be?

Long enough to explain the goal, scope, responsibilities and unresolved decisions. A concise brief with concrete answers is more useful than many pages of adjectives. Add supporting material separately when it helps explain the business.

Do I need to choose the layout before writing the brief?

No. Describe the customer need and practical constraints first. You can share visual references and explain what you like about them, but allow the designer to recommend a layout that fits your content.

Can this brief replace a proposal or contract?

Use it as an input to those documents. Commercial terms, responsibilities and formal commitments need to be agreed separately by the people involved.