A brief is a short document telling the developer what you want and why. If it is vague, the quote is approximate, and the real costs appear mid-project, when changes are already hard.
We do not claim that a brief saves a specific percentage of budget; no such number can be justified. But we can show which misunderstandings usually arise and how to prevent them at the start.
Why a brief matters
Without one, the two sides make different assumptions: does “website” include translations, does “shop” include syncing with accounting, who writes the texts. Each assumption later becomes extra work or a dispute.
A brief is not a legal document and need not be perfect. It is the basis for a conversation. Even one page answering the questions below makes a quote easier to prepare. On choosing a partner see how to choose a web agency.
1. Why you need this project
Start with the problem, not the solution. “We need a new website” is a solution. The problem may be “the site brings no enquiries”, “the team cannot change content” or “we need to sell online”. Write down what you want to change in the business, how you will know it worked (enquiries, orders, time saved) and why now.
2. Who it is for
Describe two or three main users (the buyer, a partner, your team) and what each wants to do: find a price, order, send an enquiry, open an invoice. If you have no statistics yet, say so.
3. What is to be built
List the pages or sections you think you need, even roughly. Note:
- languages (LV, EN);
- how many pages come from the current site and how many are new;
- who prepares texts and images;
- whether an online shop is needed, and how many products at the start;
- constraints: brand guidelines, mandatory tools, platform.
If you are rebuilding an existing site, add the URLs that must not be lost; losing them often drops search rankings, as we explain in redesign and SEO.
4. What it must connect to
This is the most important and most often skipped part. List the systems the data must match:
- accounting and ERP (Moneo, 1C, Jumis, Visma or another);
- CRM and enquiry handling;
- payments and delivery;
- email tools, analytics, ad accounts.
Even if an integration is not in version one, write it down. It is cheaper to plan the architecture with integration in mind than to adapt it later. See our article on automating form enquiries.
5. Who decides, and how
Write who approves the design, texts and budget, and who accepts the result. If there are several decision makers, say who has the last word. Projects are often late not for technical reasons but because approvals come from different sides with conflicting demands. Name your contact person and how fast they can answer.
6. Deadline, budget limit and maintenance
If there is a fixed date, such as a campaign or a trade fair, state it and the reason. If the budget is limited, name the limit: it lets us propose options rather than a quote you cannot afford. To compare quotes see why web development prices differ.
Also write what happens after launch: who updates content, fixes bugs and maintains the system. Code, domain and data should belong to you; make sure the quote says so.
A vague wish versus a clear one
Vague: “We need a modern website with a shop.”
Clear: “Orders reach us by email and phone; we want regular customers to order themselves. Buyers are companies with their own prices. Products and prices are in the accounting system and the shop must read them from there. The goal is for half of repeat orders to happen online. Two people decide.”
The second does not choose a platform, but it gives the developer what is needed: the goal, the buyer type, the integration and the decision makers.
Decision rule
- You know the problem but not the solution: write the brief about the problem and let the studio propose options.
- You already have a specific solution in mind: give the reason, not just the technology.
- Unsure what to include: answer the six questions, send an incomplete brief, and let the first conversation fill it in. “Don’t know” is a valid answer.
We also take on small tasks, not only large projects. If you have an idea but no brief, see our services and write to us. Start with a short brief.
Sources
This article draws on the studio’s experience and uses no external figures.
