A website brief checklist for small business owners should cover the customer, the action the site needs to support, the pages and features required, and who supplies the content. Add budget, timing and acceptance checks. You do not need design expertise to explain what your business needs the website to do.
Describe the customer before listing design preferences
Describe your main services or products, the customers you serve and the decision that brings someone to the website. Be specific about the action you want: requesting an estimate, booking a consultation, applying for a role or making a purchase.
Separate primary and secondary audiences. A prospective customer and an existing client looking for support need different information. The brief should say which journey is most important without making the other journey difficult to find.
List pages and tasks separately
A page list defines the content structure. A task list defines functionality. “Contact page” does not explain whether the form needs file uploads, location selection, a confirmation email or routing to different staff members.
- Content: home, services, individual service pages, about, articles and contact.
- Tasks: send an enquiry, book a meeting or request a document.
- Management: edit service details, add articles and review submissions.
- Connections: the existing email, payment, booking or customer management systems involved.
For each connection, name the system and explain the required result. Access and integration constraints can affect scope even when the visible page looks simple.
Identify the content owner
Specify who writes, approves and uploads the content. Include photography, logos, staff details and any evidence used to support claims. If the website is replacing an older one, decide which pages need rewriting and which should be retained.
A practical content inventory has one row per page with its owner, source material, approval status and deadline. This exposes a common scheduling problem: development is ready, but the business has not decided what the site should say.
Describe success and constraints
State the budget range, preferred launch window and any event that makes the date important. Distinguish a genuine deadline from a preference. Document accessibility needs, languages, mobile requirements and the devices your customers use, where known.
Include acceptance checks that can be demonstrated. For example: a visitor can complete the enquiry form on a phone, the correct team receives the submission, and the confirmation accurately explains the next step. “Modern and fast” needs this kind of practical definition.
Compare proposals against the same brief
Ask each provider to identify assumptions, exclusions, review rounds and post-launch responsibilities. A lower estimate may cover fewer page types or leave writing and migration to your team. Compare the actual work before comparing the total.
A short brief you can complete before asking for quotes
Complete these prompts in plain language:
- Customer and task: our main visitor needs to understand this service and request this next step.
- Scope: these pages and functions are required at launch; these can wait.
- Content: this person supplies copy, images and approved evidence by this date.
- Connections: the enquiry must reach this inbox or customer system.
- Constraints: our budget range, launch reason and approver are recorded here.
- Acceptance: we will test the enquiry journey on a phone and confirm receipt.
Ask providers to mark assumptions against these prompts. That makes differences in writing, migration, training and maintenance easier to spot before comparing prices.
Common questions
How detailed should a small business website brief be?
Detailed enough to explain the customer journey, required functionality, content responsibilities and constraints. A short brief with a page inventory and clear acceptance checks can be useful. Add detail where it changes scope, cost or launch readiness, rather than prescribing every visual choice.
What should I ask an agency to include in its website proposal?
Ask for included pages and functions, content responsibilities, migration work, review rounds, training and ongoing support. Request a list of assumptions and exclusions. Compare each proposal with the same brief so an omitted task does not look like a saving.
ReachCrowds website design and development begins with these decisions. A clear brief does not need to prescribe every design detail. It needs to make the business goal, project boundaries and working responsibilities understandable enough for useful design decisions to follow.
Further reading: What Makes a Business Website Convert?.