You can write a website brief without a single technical word, and it will still do its job. Here is what it should contain, how to describe features from the visitor’s point of view, and a short template you can fill in over an evening.
Why write a brief if the developer will ask anyway
A brief, or a statement of requirements at the early stage, does three things.
First, every developer estimates the same job. If you tell three candidates “we need a company website”, one will price a page that takes a day, another a three-month online store. You cannot compare those numbers.
Second, the brief becomes part of the contract. When a dispute comes up at the end of the project about whether a booking form was included, the answer is in the attached document, not in a chat from six months ago.
Third, writing it helps you understand what you actually need. This is often the moment you find out that half of the planned pages are unnecessary and one important feature was missing.
How to write a website brief if you are not a programmer
Write about the business, not the technology. The most common mistake of a non-technical client is trying to write like a programmer: choosing a platform, naming databases, listing languages. That is not your job, and a wrong choice there costs more than making none.
Your job is to explain what happens in your business and what should happen on the website. How to build it is the developer’s decision, and you check the result. A good developer will ask the technical questions and offer options.
What goes into a website brief
About the business
Two or three paragraphs: what you do, who your customers are and how you differ from competitors. Say you run a bakery that makes custom cakes. It matters that most orders come before holidays, that customers choose fillings and decorations, and that half of the orders currently arrive through Instagram and WhatsApp.
The goal
One main goal, stated as an outcome. Not “a beautiful modern website”, but “a customer picks a cake and a date and pays a deposit, and we get the order without back-and-forth messages”. If there are several goals, rank them.
The audience
Who visits and in what situation. Phone or computer, first visit or returning, what they need to see in the first few seconds. For the bakery, that might be “a parent looking for a birthday cake a week ahead, coming from Instagram on a phone”.
Pages
A simple list of sections: home, catalog, product page, delivery and payment, about, contacts. No need to sketch them. One line about what each page should contain is enough.
Features from the user’s side
This is the most useful part. Describe features as “the visitor wants to…” or “the admin wants to…”. For example:
- the visitor wants to filter cakes by occasion and price;
- the visitor wants to pick a date and see whether it is available;
- the visitor wants to pay a deposit by card online;
- the admin wants to get a Telegram notification for each order;
- the admin wants to change prices and add new cakes without help.
Both you and the developer understand sentences like these. They make it easy to estimate the work and later to check that everything was done.
Examples you like
Two to five websites, each with a comment. Not “this one is nice”, but “I like how large the photos are” or “it is handy that prices show right in the catalog”. Examples of what you dislike help too.
Who prepares the content
Texts, photos, product descriptions, prices. Be honest about what you already have and what you do not. If there are no photos, the developer needs to know before estimating: either the shoot goes into the quote, or you find a photographer separately.
Integrations
What the website should connect to: card payments, accounting software, Telegram, WhatsApp, a delivery service. If you do not know the right term, describe it in words: “we log orders in a spreadsheet now and want them to land there automatically”.
Budget and deadline
Many people avoid naming a budget so the developer will not fit the price to it. In practice, without a range you get quotes you cannot compare: some for the bare minimum, others for everything at once. Give a range and let the developer say what is realistic within it. What drives the price is covered in How much a website costs.
The same goes for the deadline: say when you need the site and why. “Before our new location opens on March 1” is clearer than “as soon as possible”.
Who makes decisions
Name one person who answers questions and approves work. If two people decide, agree between yourselves whose word is final.
Describe not how the website should look, but what a visitor should be able to do on it. A good developer will suggest the rest.
Website brief template and example
Copy it and fill it in. Where you do not know the answer, write “not sure”: that is useful information too.
- Company. What we do, who our customers are, how we differ.
- Goal. What should happen because the website exists.
- Audience. Who visits, from where, on which device, looking for what.
- Pages. A list of sections with one line each.
- Features. A list of “the visitor wants to…” and “the admin wants to…”.
- Examples. Links to websites and what you like or dislike about them.
- Content. What you already have (texts, photos, logo) and what needs making.
- Integrations. Payments, messengers, accounting, delivery, spreadsheets.
- Languages. One or several.
- Budget. A range in dollars.
- Deadline. The target launch date and the reason.
- Contact person. Who answers questions and approves work.
One or two pages are enough. A thirty-page document usually gets in the way: nobody reads it in full, and the important parts get lost among the minor ones.
What happens next
Send the brief to several developers and see how they respond. It is a good sign when they ask follow-up questions: about seasonality, how orders are handled today, what matters most if the budget does not cover everything. It is a bad sign when someone names a price five minutes later without asking anything. Which questions to ask them in return is covered in 15 questions to ask a developer.
After the discussion, the brief usually turns into a more detailed document or straight into a prototype of the main screens. At NOVO, for example, the brief is followed by a clickable prototype, so everyone can see whether the task was understood correctly before development starts. Why that matters is explained in Prototype and first version.
Attach the final, agreed brief to the contract. That fixes the scope, and any new wishes have a clear path: discussed separately, with their own estimate of time and money.
In short
- A brief lets you compare developers on the same task and fixes the scope in the contract.
- Write about the business, the goal and the visitors; leave technical decisions to the developer.
- Describe features as “the visitor wants to…” and “the admin wants to…”.
- Give a budget range and the real reason behind the deadline.
- One or two pages from a template beat a long document nobody reads.