Why the Brief Determines the Quote
Every quote is an estimate of uncertainty. When a studio cannot tell how much work is hidden behind a request, it does one of two things: pad the number, or quote low and manage the gap later through change requests. Neither serves you. A precise brief removes the uncertainty, and the price drops or the scope rises accordingly.
There is a second effect. Sending the same clear brief to three studios is the only way to get comparable proposals. Without it, you receive three quotes for three different projects and no basis for choosing between them beyond the number at the bottom.
The Brief, Section by Section
1. The business, in five sentences
What you sell, who buys it, what the sales cycle looks like, what makes people choose you over the alternative, and what stage the business is at. Studios that design well design for a specific commercial situation, and this is the section that supplies it.
2. What the site must achieve
Not "a modern website". A commercial outcome: generate qualified enquiries, sell directly, reduce support calls, help recruiting, establish credibility before a sales meeting. Then state how you will know it worked. If nobody can answer that, the project has no success criteria and the design has no target.
3. Who the site is for
Primary audience, secondary audience, and the difference between them. What do they already know when they arrive? What are they anxious about? What do they need to see before they will make contact? A brief that says "everyone" produces a site that persuades nobody.
4. Structure
A rough sitemap — bullet points are fine. Distinguish pages that need their own layout from pages that share one, because that distinction is the main driver of cost. If you are unsure, list the pages and let the studio advise; just do not leave the list out.
5. Content: who supplies what
The section most often omitted and most often responsible for delay. State plainly:
- Copy — do you have it, are you writing it, or should the studio?
- Photography — existing library, new shoot, or stock?
- Video or motion — required, and from where?
- Logo and brand assets — do you have usable source files?
- Product data, case studies, team bios, testimonials — who is collecting them, and by when?
6. Functionality and integrations
List every system the site must connect to and every non-obvious thing it must do. Booking, payments, CRM, email platform, inventory, login areas, calculators, multi-language, accessibility obligations. This list is where quotes diverge most sharply, so completeness here is worth more than polish anywhere else.
7. References, with reasons
Three to five sites — some competitors, some outside your sector — with a sentence each on what specifically you responded to. "This one, because the pricing page explains a complicated product without a call" is enormously more useful than a bare URL. Include one or two you dislike and why; the negatives are often more revealing.
8. Budget and timeline
A range with a ceiling, and a deadline with a reason attached. "March, because the trade show is in April" changes what a studio can propose. "As soon as possible" tells them nothing and usually costs you money. Our breakdown of what websites actually cost in the US and UK is a reasonable place to calibrate the number before you write it down.
9. Decision-making
Who approves work, who must be consulted, and how quickly feedback will come back. Naming one decision-maker in the brief prevents the single most common cause of overrun.
10. Constraints
Existing platform you must stay on, IT policies, regulatory or accessibility requirements, brand guidelines that cannot change, a domain or hosting arrangement you are locked into. Constraints stated early are design parameters. Constraints discovered late are rework.
Questions To Ask Yourself First
Answer these before writing anything, because vague answers here produce a vague brief:
- If the new site worked perfectly, what would be measurably different in six months?
- What specifically is wrong with the current site? Name the pages.
- What does a prospective customer need to believe before they contact you?
- Which competitor's site do you find most persuasive, and why?
- What content already exists that is genuinely good?
- Who inside the organisation will maintain the site after launch?
- What has to be true for this project to be considered a failure?
Question seven is unusually productive. It surfaces unstated expectations that would otherwise appear as vague dissatisfaction in week nine.
What Not To Put in a Brief
- Prescribed solutions. "We need a parallax hero" is an answer to a question you are hiring someone else to answer. State the problem instead.
- Fake page counts. Inflating scope to seem substantial gets you quoted for work you do not need.
- Hidden must-haves. Anything that will be non-negotiable at review should be non-negotiable in the brief.
- Every idea anyone has ever had. Separate phase one from later phases explicitly, or everything gets priced.
What To Expect Back
A good response to a good brief is not just a price. It should include: a restatement of the problem in the studio's own words, a proposed approach with reasoning, a scope with explicit inclusions and exclusions, a phased timeline with client-side milestones marked, a clear payment schedule, and a statement of what you own at the end. If a proposal arrives with a number and a page count, you have learned something useful about how the project would be run.
Watch for the studio that pushes back on something in your brief. A challenge to your assumptions — done respectfully and with reasoning — is usually a better signal than enthusiastic agreement with everything, which is what a vendor does when the plan is to renegotiate later.
Kalex Studio works from written scope on every project, and we are happy to help shape a brief before there is any commercial conversation. Send us what you have, however rough.