A useful website project brief states who the business helps, what visitors need to do, the pages and features required, available proof and content, ownership expectations and the budget or decision constraints. It gives providers enough context to scope work around the business goals and constraints.
Before requesting a website quote, explain the business problem the site needs to solve and the information a provider needs to scope it. A short, factual brief gives each provider the same starting point and exposes assumptions before work starts.
Write the brief in plain language. Replace a request like “a modern five-page website” with concrete facts about your customers, scope and constraints.
What a provider needs to understand before quoting
A useful brief lets a provider answer five questions:
- Who is the website trying to help?
- What should that visitor understand or do?
- What information, proof and material already exist?
- What must the site include or preserve?
- What does success look like for the business?
When key answers are missing, providers may assume different requirements and price different work.
A copy-and-paste website project brief
Use the template below. Short answers are fine. Leave a field blank when it does not apply.
1. Business and audience
- Business name and website (if one exists):
- What do you sell or provide?:
- Who is the main customer?:
- Where do you work or deliver?:
- What do customers usually need to understand before they enquire?:
- What makes your offer meaningfully different?:
These answers help a provider plan the first screen, select proof that addresses customer questions and use language your audience understands.
2. The project goal
- Is this a new website, redesign or targeted improvement?:
- What is not working now?:
- What should a visitor be able to do after the project?:
- What would make this project successful after launch?:
Be specific. “More enquiries” is a useful goal, but it becomes more actionable when paired with the desired action: call, WhatsApp message, form submission, booking, quote request or visit to a physical location.
For help deciding whether the site needs a rebuild, read redesign versus targeted improvements.
3. Pages, functions and content
- Pages you believe are needed:
- Services or products that must be explained:
- Features required: contact form, booking, catalogue, online payments, client login, map, newsletter or something else
- Content already available: logo, brand guide, copy, photos, testimonials, case studies, reviews, product details
- Content that still needs help:
- Competitor or reference websites: what do you like or dislike about each?
Describe what you want to borrow from each reference, such as calm typography or a simple quote form, and ask the provider to adapt those ideas to your business.
For a more detailed list of inputs, read what content a web designer needs from you.
4. Enquiry path and operations
- How should a visitor contact you?:
- Who receives enquiries?:
- Which email address, phone number or WhatsApp number must be used?:
- Do you have an existing domain, hosting, email or analytics account?:
- What must be retained from the existing site?:
- Who will approve content and design decisions?:
This section catches practical problems early. For example, a form design cannot be finalised without knowing who must receive it, and a migration cannot be scoped safely without knowing what must move.
5. Budget, timing and decision process
- Budget range or package you are considering:
- Important deadline and the reason for it:
- Who makes the final decision?:
- What are the non-negotiables?:
- What can be phased into a later project?:
Share a budget range or priority list when you are comfortable doing so. This helps a provider recommend a sensible first phase and avoid pricing every possible feature at once.
Make the proof easy to verify
Many small-business briefs list services but leave out the material that would help a visitor trust those services. Include anything real and verifiable that shows how the business works:
- Before-and-after examples where appropriate.
- Project photographs you own or have permission to use.
- Testimonials and reviews with permission to publish.
- Measurable project outcomes that can be supported.
- Certifications, registrations or team experience.
- Common customer questions and objections.
Use only claims you can verify, and make real evidence easy to find and understand. Read our guide to case studies for more on presenting project evidence.
Tell providers what needs to be preserved
For a redesign, a brief should name the assets and functions that cannot be lost. Examples include the current domain, high-performing pages, email addresses, form routes, Google Business Profile links, analytics access, legal pages, product information and old URLs with search traffic.
If you cannot identify which URLs matter, mark them as unknown and ask the provider to review the current URLs before migration.
A redesign also affects which pages and information users and search engines can reach. If the old site has indexed pages, a provider may need to plan redirects and content migration.
Brief for inclusion and everyday use
Mention anything that affects the practical use of the site: visitors primarily on mobile, a team that must update information itself, language needs, older customers, low-bandwidth conditions, keyboard use or sensitivity to motion.
These details affect the site’s layout, text, navigation and interaction requirements. Ask the provider to explain how the design will support mobile visitors, keyboard use, language needs and motion preferences. W3C explains that accessibility depends on how sites are designed and developed; raising it before work starts can prevent avoidable rework.
Send the same brief to every provider
If you are collecting more than one proposal, send the same base brief to each provider. Then ask them to state:
- What they understand the project to include.
- What they need from you.
- What timeline and key phases they propose, which client inputs or approvals each phase needs, and what assumptions could affect timing.
- What assumptions they have made.
- What is excluded or optional.
- What the first-year operating costs are.
- Who owns the domain, hosting and accounts after launch.
This gives you a consistent basis for comparing proposals with the website quote comparison checklist. It also lets providers flag a gap before pricing so assumptions stay visible.
Keep the brief focused
Leave technology, design-system and search-strategy decisions for the provider to recommend. Give them the business context, customer need, known constraints and available evidence so they can propose an approach.
When you are ready, tell IDJoy about your project. A clear first message can be short; the template gives you a place to record the important decisions.