Resource · Template
Website project brief template
Fill this in before contacting a studio or signing a proposal. A line or two per question is enough.
Free, no sign-up. Updated .
Write “unknown” where you have no answer yet: it shows where discovery is needed.
Who decides
- Who decides on design, budget and the launch date? Name each person if they differ.
- Who is the day-to-day contact, and how many hours a week can they give?
- Who else sees the work before it ships, and at which stage?
Why this year
- Why is this a project for this year, not next?
- Is any date fixed? What depends on it: a launch, an event, a contract ending?
What the site has to do
- What one thing should the new site do better?
- List up to three goals in order. When two conflict, which wins?
- Three months after launch, which number shows each goal was met? A target can come later.
- What does the current site do well that must not break?
- Which pages or tasks draw the most complaints, from visitors or staff?
Who it is for
- Which two or three visitor types matter most? What does each want to know, and do next?
- When their needs conflict, whose come first?
- What do your analytics say about visitors' devices and countries, if you have any?
- Any accessibility obligations beyond WCAG 2.2 AA, or legal ones in specific markets?
Pages and content
- Which pages exist now, and which at launch? A rough list is fine.
- Which pages must rank in search, and which only serve campaigns or direct links? (See SEO pages and paid landing pages are different products.)
- Who writes the copy, and when will final text reach us?
- Is content moving from the current site? Roughly how many pages?
- Who supplies photography, video, illustration or 3D assets, and do you hold the licences?
- Which languages do you need at launch, and which later?
Look and motion
- Send two or three sites you admire, saying exactly what you like in each. A bare link tells us little.
- Should motion stay quiet, support the content, or carry part of the story?
- Is there a product, data set or process people would grasp faster by using than reading about?
- If you want 3D or real-time graphics, what should older phones show instead?
Technical setup
- Who controls the domain and hosting, and can they grant us access?
- Who edits the site after launch, and how often? That decides whether you need a CMS.
- Which tools must the site connect to: CRM, analytics, consent manager, email platform, booking or a shop?
- Any IT, legal or procurement requirements before work starts?
- Which current URLs bring traffic or appear on packaging, ads or partner sites? They need redirects.
Budget and dates
- What budget range have you set aside? A range lets a studio fit scope instead of guessing.
- Is there money for support and new content after launch?
- When can work start, and when must the site be live?
- Which weeks can your team not review?
Before you send it
- Goals are in priority order, each with its number.
- A decision-maker and a day-to-day contact are named.
- Brand guidelines and technical documents attached or linked.
- A budget range and any fixed dates written down.
- Gaps say “unknown”, not blank.
When ready, send it via the contact page, or read how we run projects first.
Want a second pair of eyes on it?
Start a project and we will tell you plainly where the risks are.


