The Website Brief
Get a downloadable brief you can send to any studio.
Overview
Company name and current website.
If there's no website yet, leave the second field blank.
What does the company do?
A few sentences in your own words, including what stage you're at.
Describe the project in your own words.
A few paragraphs on what you're building, what has changed, and what you need the new website to do. Write it the way you'd explain it to a studio on a call.
Why now?
The trigger changes the project. A raise, a repositioning and a website that stopped matching the company lead to different work.
What's wrong with the current website?
Be specific where you can. This gives a studio something to investigate rather than a redesign request.
Objective
What does a successful project look like?
Something you could check a few months after launch and get a clear answer on.
Prospects stop asking what we do on the first sales call.
Pricing is clear enough that unqualified leads stop booking demos.
Our team can publish a new page without asking engineering.
The website holds up when an investor sends it to their partners.
What's the main job of the new website?
Pick the primary one. Most websites do several things, but the order matters when decisions conflict.
Audience
Who is the website primarily for?
Job title and the context they're in when they land. In B2B the person using the product and the person approving the purchase are often different, so name whichever one the website has to convince.
What should they understand, believe or do after visiting?
One or two sentences. This is what the page structure gets built around.
Who else reads it?
If the website is doing recruiting or diligence work, those pages need to be in scope rather than assumed.
Scope
What needs to be included?
Select the page types, then note counts where there are several of the same kind.
What is explicitly not included?
These get assumed into scope on most projects. Marking them now means a later request becomes a scope conversation.
Who updates the website after handoff?
This decides the platform. If your team needs to publish changes without engineering, that rules some options out.
Content
Who writes the copy?
The most common reason projects stall. Design work waits on finished copy, so this needs a name and a date attached.
What do you already have?
What exists affects the scope and the price more than most things on this page.
Technical
Anything that has to stay connected or stay where it is?
Systems, platforms and requirements the new website has to work around.
Direction
Three to five websites you like, and what you like about each.
Be specific about what you’re pointing at. "The way they handle the pricing comparison" is usable. "It’s clean" isn’t.
Any website you don't want to resemble?
Negative references narrow the work faster than positive ones.
Timeline & budget
How long do you expect the project to take?
A rough sense of the window you have in mind.
What's the budget range?
Studios scope the depth of the work around the budget, so a range gets you a realistic proposal instead of a guess.
Decisions
Who approves the work?
The person with final sign-off, plus anyone else who will give feedback.
Open questions
What are you least certain about?
Anything you'd want a studio to help you work out rather than decide for you. This is usually the most useful answer on the page.
Additional comments
Anything else the studio should know?
Context that didn't fit the questions above: constraints, history, people, or anything you'd mention in a first call.
Generate your brief
Download it as a PDF you can forward to any studio.