Skip to content
ReqBrief

Free tool

Website brief generator

Pick the kind of website you are building. You get the questions to send your client and a brief template to fill in from their answers, ready to copy or download. No sign-up.

1. What are you building?
2. Add names (optional)

They only fill in the document headings. Nothing you type is sent anywhere.

3. Copy or download

Downloads are Markdown (.md) text files, so they open in any editor and paste cleanly into a doc or an email.

Client questionnaire

Send this to your client before the first call.

# Website project questionnaire

Project type: Brochure site

Please answer in your own words. A sentence or two per question is plenty. "Not sure yet" is a useful answer too: it shows what still needs deciding.

## The project

1. In a sentence or two, what are we building, and why now?
2. What happens if this project does not happen this year?

## Audience

3. Who is the main visitor? Describe one real person rather than a demographic.
4. What does that person need to find or do on the site?

## Goals

5. What is the one result this site must deliver for the business?
6. Six months after launch, how will you judge whether it worked?

## Pages and enquiries

7. Which pages do you expect the site to have? A rough list is fine.
8. What is the one thing you most want a visitor to do: call, book, send an enquiry or visit you?
9. Where should enquiries from the site go, and who replies to them?
10. Do you want a blog or news section? If so, who will write for it after launch, and how often?
11. Do most of your customers come from a particular town or region? List the areas you serve.

## Content and assets

12. Who is writing the copy, and when will it be ready?
13. Which photos, videos, logos or brand guidelines already exist?

## Design

14. Share two or three websites you like, with a line on what you like about each.
15. Is there anything you definitely do not want, or a competitor you do not want to look like?

## Technical and access

16. Who owns the domain, and who can log in to its DNS settings?
17. What must the site connect to: a CRM, email marketing, booking, payments, analytics?

## Budget, timeline and approval

18. Is there a date the site must be live by, and what is driving it?
19. What budget range are we working within for this phase?
20. Who gives final approval, and who else needs to see the work before then?

---
Made with the free website brief generator from ReqBrief: https://reqbrief.com/tools/website-brief-generator

Website brief template

Fill this in from their answers, then get it approved.

# Website brief

Project: [Project name]
Client: [Client name]
Project type: Brochure site
Prepared by: [Your name]
Date: [Date]

## 1. Summary

[What is being built, for whom, and why now. Two or three sentences.]

## 2. Goal and success measure

[The one result the site must deliver, and how you will judge it six months after launch.]

## 3. Audience

[The main visitor, described as a real person, and what they come to the site to do.]

## 4. Scope

In scope: [What this project includes.]
Out of scope: [What it does not include, so a later request is a change, not a misunderstanding.]

## 5. Deliverables

[The things you hand over, for example a six-page site with a contact form, basic SEO setup and a handover session.]

## 6. Pages and calls to action

[Each page, with the one action it should lead the visitor to.]

## 7. Enquiry handling

[Where form submissions go, who replies, and any booking or call tool the site links to.]

## 8. Content and assets

[Copy, images, video and brand files. For each one: who supplies it and by when.]

## 9. Design direction

[Sites the client likes and why, anything to avoid, and any existing brand rules.]

## 10. Technical notes

[Platform, hosting, who holds the domain and DNS logins, and every tool the site must connect to.]

## 11. Timeline and milestones

[The launch date, what is driving it, and the review points before it.]

## 12. Budget

[The agreed range or figure, and what it does and does not cover.]

## 13. Stakeholders and approval

[The day-to-day contact, who else reviews, and the one person who gives final approval.]

## 14. Open questions

[Anything not answered yet, who will answer it, and by when. An honest list here prevents surprises later.]

---
Made with the free website brief generator from ReqBrief: https://reqbrief.com/tools/website-brief-generator

Rather not chase the answers?

Skip the document and send a ReqBrief interview instead. Your client opens a link and answers one question at a time, vague answers get a follow-up, and you get a structured brief back instead of a reply to decode. Start free with 3 briefs included.

Send it as an interview →See how the interview works

How to use it

  1. 1

    Send the questionnaire before the first call

    Facts like the page list, the domain login and the launch date belong in writing, where the client can go and check them. That leaves the call for what a form cannot reach: stakes, people and money. The client discovery call agenda shows how to spend it.

  2. 2

    Fill in the brief from the answers

    Move each answer into the matching section and put it in your own words. Anything the client could not answer goes under Open questions, not into a guess. If a section is new to you, the project brief template guide explains what each field is really asking.

  3. 3

    Get the brief approved before you quote

    Send the finished brief back and ask the client to approve the scope, including the out of scope list. A later request that is not in the brief is then a change, not a misunderstanding. For the reasoning behind the core questions, the web design questionnaire template walks through fourteen of them with a filled-in example.

What changes by project type

Every version asks about the project, the audience, goals, content, design, technical access, budget, timeline and approval. Each project type then adds its own questions and brief sections.

Brochure site

Adds questions on the page list, the one action each page leads to, where enquiries go, and the areas the business serves. 20 questions in total.

E-commerce shop

Adds questions on the catalogue, checkout and payments, delivery and tax, and what happens after an order. 25 questions in total.

Webflow build

Adds questions on who owns the workspace, the CMS collections, what the client edits after launch, and where forms go. 22 questions in total.

WordPress redesign

Adds questions on what is broken today, hosting, theme and plugins, the content to carry over, and the URLs that must keep working. 24 questions in total.

SaaS marketing site

Adds questions on positioning, the path from the call to action into the product, the launch pages, and tracking. 23 questions in total.

What a template cannot do

A form, however polished, is still a fixed list of questions. It cannot tell that “something modern” is not a design direction, or notice that “we’ll send the copy later” came without a date. Those are the answers that turn into rework. None of this gets decided in week three. It gets decided before the project starts.

So read every answer before you fill in the brief, and follow up on anything vague. If you would rather not do that by email, a ReqBrief interview asks the follow-up for you. The comparison of a PDF questionnaire and an interview sets out the trade-offs, including where a document is the better choice.

FAQ

What should a website brief include?

What is being built and why, the goal and how success will be judged, the audience, what is in and out of scope, the deliverables, the content and who supplies it, the design direction, technical notes, the timeline, the budget, who gives approval, and the questions still open. The generator adds the sections a project type needs on top of that, such as the catalogue and checkout for an e-commerce shop or redirects for a WordPress redesign.

Should I send the questionnaire before or after the discovery call?

Before. Facts such as the page list, the domain login and the launch date are better answered in writing, where the client can go and check them. That leaves the call for what a questionnaire cannot get at: why the project matters now, who really decides, and how the budget was set.

Is the website brief generator free?

Yes. There is no sign-up and nothing to install. Both documents are built in your browser from fixed templates, and the names you type are not sent anywhere.

How is this different from sending a ReqBrief interview?

The generator gives you a fixed list of questions to send as a document. A ReqBrief interview asks your client one question at a time from a link, follows up when an answer is vague, and writes the brief for you at the end. The free plan includes 3 briefs.

Keep exploring

Guides that go deeper

Web Design Questionnaire Template: 14 Questions

A free web design questionnaire template: 14 client questions on goals, audience, design and budget, a filled-in example, and how to adapt it for a redesign.

Project Brief Template + How to Write One

A free, copy-paste project brief template, a filled-in example, and how to write one: what each field is really asking, and how to get clients to answer it.

Client Discovery Call: The 45-Minute Agenda

How to run a client discovery call that wins the project and scopes it properly: a copy-paste 45-minute agenda and the ten questions worth asking live.

7 Questions to Ask Clients Before a Project

Seven questions to ask clients before starting a project, covering hidden stakeholders, sign-off, integrations, and what done actually looks like to them.