Published
9 MIN READ
Website brief template: ready to copy
A website brief is the document that defines what the project needs to solve before a single screen exists. It covers business, audience, goal, scope, brand and deadline. Without it, the vendor guesses the quote and the client finds out halfway through that they agreed to something else.
The templates that circulate in Portuguese are five to eighteen years old, were written for developers rather than for the people hiring them, and none of them covers CMS, integrations or what to do when the copy doesn't exist yet. Below is the script we use in our discovery conversation, organized into four blocks, ready for you to copy and fill in before talking to any vendor.
What is a website brief?
It's the translation of a business problem into project requirements. It isn't a list of pages or a layout description. It's the document that answers why the website exists, who it speaks to, what needs to happen after the visit, and what the real constraints on content, timeline and budget are.
At Wama this doesn't start with a form; it starts with a discovery conversation. The difference matters: a form collects ready-made answers, a conversation uncovers what the company hasn't put into words yet. But the conversation has a script, and that script became the template published here. Showing up with it filled in shortens discovery and improves the proposal you get.
Why does the brief decide the quote?
Because the price of a project is the cost of making decisions, and the brief is where those decisions start. A vendor who gets a clear scope quotes what exists. A vendor who gets "I want a nice-looking website" quotes the risk, and risk is always more expensive than work.
There's a well-known technical reason for this. According to the Software Defect Reduction Top 10 List, by Barry Boehm and Victor Basili, published in IEEE Computer in January 2001, software projects spend 40% to 50% of their effort on avoidable rework. The authors also note that fixing a problem after delivery costs far more than fixing it at the requirements stage, by a factor of about five in small systems and up to a hundred in large ones.
A website isn't critical software, so the relevant number here is the smaller one. Even so, five times is the difference between adjusting a sentence in the brief and redoing three pages with approved design. That's exactly why turning the brief into a quote that doesn't change midway starts before the first sketch.
The template, block by block
Copy the table below and answer with whatever you have. An incomplete answer is useful; a made-up one isn't. Where you don't know, write that you don't know: that's information for whoever is quoting, too.
Block | Question | Your answer |
|---|---|---|
1. Business and audience | What the company does, in one sentence a stranger would understand | |
1. Business and audience | Who buys, and who makes the buying decision on the other side | |
1. Business and audience | Why a customer picks you and not the competitor | |
1. Business and audience | Two or three competitors, with each one's website | |
2. Website goal | What needs to happen after someone visits | |
2. Website goal | How you'll know the website worked | |
2. Website goal | What the current website gets wrong today, if there is one | |
2. Website goal | Which audiences show up besides the buyer | |
3. Scope | Pages you have in mind, even if you're not sure | |
3. Scope | Who writes the copy: you or the vendor | |
3. Scope | Do you need a blog or a content area you publish yourselves | |
3. Scope | Integrations: form, CRM, email, chat, payments | |
3. Scope | Do you need a logged-in area, a catalog or a store | |
4. Brand, timeline and budget | Brand assets: vector logo, colors, typography, photos | |
4. Brand, timeline and budget | Three reference websites, with the reason you like each one | |
4. Brand, timeline and budget | Deadline and what depends on it | |
4. Brand, timeline and budget | Budget range, even a rough one, and who approves it |
That's seventeen answers. A prepared client takes an hour to fill it in, and that hour usually saves weeks later. If you're asking more than one vendor for a quote, send this exact same document to all of them: the same brief sent to three vendors is the only way to compare proposals that mean the same thing.
Which question changes the project's direction the most?
One, and it's in block two: what needs to happen after someone visits the website. It's the question that defines the entire structure, because every page then exists to lead to that outcome, and whatever doesn't lead there comes out of scope.
When the answer is "the person gets in touch," the website is built for a conversation. When it's "the person understands we're bigger than we look," it's built for proof. When it's "the person applies for a job," everything changes again. They're different websites with the same number of pages, and that difference comes entirely from one sentence. On how that decision turns into structure, it's worth reading the question about what the website needs to make happen.
The second most revealing question is in block one: why a customer picks you and not the competitor. A company that can't answer that has a positioning problem, not a website problem, and no layout fixes it. Better to find out in the first week than on delivery day.
Who fills it in, and how long does it take?
The person who decides, with one other person at most. A brief filled in by committee becomes an average of opinions, and an average of opinions produces a generic website. If several departments have a stake, collect everything and let one person write the final version, owning the choices.
It takes an hour for someone who knows the business, and weeks for someone who has to align internally first. That second case is common and isn't a problem, as long as it happens before the project starts and not during it. A website's timeline depends on it: the timeline only starts counting once the content exists.
What shouldn't go in the brief?
Three things get in the way more than they help, and all of them look useful at first glance.
Layout descriptions. "Top menu with five items and a big banner" solves the screen, not the problem. Describe the goal and leave the solution to the people you hired.
A feature list copied from a competitor. Without knowing why the competitor did it that way, the list imports their mistakes along with it.
A hidden budget. Leaving out the range doesn't improve the proposal; it delays it. The vendor quotes whatever scope fits and you find out two weeks later that it doesn't add up.
There's one special case worth noting. Sometimes the brief reveals that the request isn't a website: a logged-in area, a data dashboard, business rules. Then when the brief reveals the request isn't a website, the whole conversation changes: scope, timeline and price range. Finding that out in the document is cheap; finding it out mid-project isn't.
Common brief mistakes
Answering what the website should have, not what it should solve. It's the most frequent mix-up and the one that most often produces a beautiful, useless website.
Leaving the content block blank. Who writes the copy is the decision that moves price and timeline the most, and the one most often put off.
References without a reason. Three loose links say nothing. What informs is the sentence explaining what you liked about each one.
Not saying who approves. A project without a defined owner piles up review rounds and blows the timeline without anyone noticing where.
Confusing a deadline with a campaign date. The date exists, but it needs to come with what depends on it, or it becomes pressure without criteria.
The brand block deserves special attention because it's the most underestimated. Inconsistent assets force visual rework nobody quoted, and the discussion about what the company expects to change after the new website usually starts right there.
What happens after you hand in the brief
A serious vendor sends back questions before sending back a price. If the first reply to your brief is a fixed quote, with no questions along the way, be suspicious: either the scope was perfect, which is rare, or nobody read it carefully.
After the questions comes the proposal, and it should mirror the brief item by item, including what was left out. According to the Pulse of the Profession 2026 report, from the Project Management Institute, 31% of complex projects don't deliver the originally intended scope of benefits. Scope written down on both sides is the cheapest defense against that.
Keep in mind that the brief changes with the company's moment. An established company and one that just raised funding answer block two very differently, and how the brief changes with the company's stage is a useful read before filling it in.
Frequently asked questions
Is there a ready-made website brief template?
The template in this article covers four blocks and seventeen questions, and it works for a corporate website, a landing page and a product website. Copy the table and answer with whatever you have. What matters isn't filling in everything; it's recording what you don't know yet.
Who should write the brief, the client or the agency?
The client writes the first version and the agency completes it with questions. A brief written only by the vendor becomes assumptions about someone else's business, because no outsider knows the operation. Written only by the client, it usually lacks the technical part (scope, integrations and content), which is exactly where the quote gets decided.
Do I need to know how much I want to spend before asking for a quote?
A rough range is enough and helps a lot. Without it, the vendor quotes whatever scope they imagine, and the conversation starts over when the number shows up. Stating the range doesn't push the price up; it brings the proposal closer to what you can actually hire.
Does the brief change for a landing page?
It changes in size, not in structure. A landing page has a single goal, so block two gets shorter and more precise. The business, brand and timeline blocks stay the same, because they decide just as much on one page as on twenty.
What if I don't have the copy ready?
Record that in the brief instead of leaving it blank. Who writes the content is the item that moves a website project's price and timeline the most. Stating that the vendor will write the copy changes the quote, but it prevents the most common delay of all.
If you've filled in the template and want a read on what it reveals about the project, it's worth bringing your brief to a conversation with Wama. Discovery starts with exactly these questions.
