Small business website brief: what to prepare and delegate?

You do not need finished copy, mock-ups or a chosen platform before talking to a designer. You need to explain what the website must help people do, what you already have and what you want to delegate.

A website brief sets out your needs, scope and constraints. For a small service business, begin with a short document and refine it with your provider. This guide concerns a website that presents services and encourages enquiries. Shops, customer portals and business applications need additional requirements. For a redesign, record what must be retained.

Go straight to the fill-in template.

1. Define the visitor and the next step

“A beautiful website” does not identify its audience or purpose. Write one sentence with a customer, a need and an action.

Fictional example: “We want local office managers to understand our cleaning service and request a quote with their premises size and preferred frequency.” This is a brief, not a client result or promise of more enquiries.

It suggests useful information: services, coverage, working arrangements and contact. For a first site, use questions from real conversations. For a redesign, add accurate existing content and observed difficulties. If you lack reliable traffic data, say so. “More suitable enquiries” can be an objective; “double enquiries in three months” is an unsupported forecast.

Identify who receives and answers enquiries. A booking form is useful only if availability is maintained and someone handles the appointment.

2. Choose the pages and functions needed at launch

A sitemap here means the planned list and organisation of pages. Do not impose five or ten pages before considering what each helps a customer decide.

This is a suggested structure, not a compulsory page count. Add the business and privacy information required for your organisation. A blog or second language needs a clear audience and someone able to maintain it.

Describe functions by their use: “A visitor requests a quote, it reaches this inbox and the page confirms submission.” Name existing calendars, customer-management tools and booking services. Integrations can affect cost and timing.

Mark each requirement essential at launch, quote separately or later. Ask the provider to confirm the classification.

3. Gather content without writing everything yourself

You can delegate writing and presentation. The writer still needs accurate information about what you do, for whom, where, how and with what limits. Notes or a conversation can be a starting point when the quote includes that work.

Use a shared folder and record the state, owner and next action for each item.

If you have no customer reviews or photography, say so. An honest explanation of your method is useful. Illustration should be labelled when readers might mistake it for completed client work.

Replace “client supplies content” with a clear agreement: who produces the first draft, from what material, who revises it and who approves it? Image selection, photography and licence purchases are different tasks.

4. Assign responsibilities and approvals

Delegating design does not require you to choose fonts or programming languages. Your role is to confirm that the proposed site represents your business and supports the agreed action.

Choose one person to collect feedback. Useful feedback describes a problem: “We do not serve that town” or “The visitor cannot find the quote request.” Let the professional propose the design solution.

A DIY tool can suit simple needs with an available owner. A one-off build can suit a business with ongoing support already arranged. A managed service may suit one that also wants to delegate maintenance and changes. Choose the responsibilities before the payment model.

5. Set the budget and milestones

Give a budget range and explain constraints. Ask what covers design, copy, imagery, integrations and testing. List recurring domain, hosting, maintenance, email, software and change costs. Use the subscription and upfront purchase comparison to compare the same scope over time.

Use milestones with entry conditions:

1. Scope confirmed: purpose, priorities and responsibilities agreed; unknowns listed.
2. Proposal ready for feedback: necessary information available; approver and response dates named.
3. Content and build approved: accurate copy, usable images and agreed functions in place.
4. Checks and launch: blocking defects handled, approval given and ongoing owner appointed.

These are suggested stages, not a standard delivery time. Missing copy, unavailable approvers or inaccessible accounts can delay launch. Separate your preferred date, an essential deadline and the date the provider accepts.

For a redesign, include existing notice periods, email, pages to preserve and available access. The brief does not replace a handover plan.

6. Plan the domain, privacy and visibility

The domain is your address; hosting makes the website accessible. Ask who is recorded as the domain holder, who renews it and how management can be recovered. ICANN’s transfer guidance covers generic domains such as .com; country-code extensions have their own rules.²

Record services and account owners in the brief, never passwords. Arrange delegated access separately. Preserve email services during a redesign.

Legal requirements depend on the organisation, jurisdiction and data uses. For a UK business, the ICO explains privacy notices and cookie information.³ A UK template is not a universal compliance checklist for the US, Canada or Australia. Have the applicable requirements checked for your business, customers and tools.

For a form, identify the necessary fields, recipients and retention arrangements. Check analytics, embedded videos and booking tools individually; adding a banner does not by itself settle all obligations.

For search visibility, ask for descriptive titles, understandable pages, mobile usability and crawlable public content. These SEO foundations help search engines discover and understand the website; they do not guarantee a ranking.¹ Describe your services and service area rather than demanding “first on Google”. An AI citation cannot be guaranteed either.

7. Check before approving launch

Acceptance checks establish whether delivery meets the agreed requirements. Write them before the build begins.

• On a phone, I can understand the service and reach the contact action.
• A test enquiry reaches the intended recipient; success and error messages are clear.
• Phone links and booking work, and someone handles the requests.
• Services, contact details, conditions and imagery have been approved.
• Required business and privacy information is accessible; added tools have been checked.
• The intended domain works; preserved URLs and email have been tested for a redesign.
• Responsibility for access, renewals, hosting and corrections is clear.

Add checks for specialist functions. This is a starting point, not a complete legal, security or accessibility audit. Record defects, owners and whether they block launch.

After launch, check that enquiries continue to arrive. Arrange a first review of outdated facts, reported issues and suitable enquiries. Use the monthly website review to choose the next improvement.

8. Your fill-in website brief

Select the relevant answers and add details only where needed. Everything is optional. You can create an initial brief after the first section, then complete content and responsibilities with your provider. An unanswered section remains “To clarify”, not “unnecessary” or “included in the price”. Your choices describe needs; they do not confirm a quotation’s scope.

Review, copy or download an editable text file. No account or email address is required. Answers are neither sent nor saved by this tool: download before leaving. Do not enter passwords or confidential customer data.

Send the same brief to the providers you consult. Ask for deliverables, exclusions, content work, included feedback, conditional milestones and recurring costs. Resolve unanswered sections together. The brief helps frame the discussion; it does not replace the agreed quote and contract.