Writing a website brief that gets accurate quotes

A website brief exists to make quotes comparable. A brief that specifies these details tells an agency, in writing, exactly what to quote against. Most briefs fail at that job before they are read past the first line, because they describe what the business wants rather than what has to be built. This section works through what a brief must contain and how to write one without knowing web design vocabulary yet. It also covers the specific decisions — success measures, page count, functional versus content requirements, budget disclosure, deadlines, assets and internal sign-off — that turn a paragraph into something a supplier can quote against.

Why an underspecified web design brief is expensive, not just annoying

An underspecified brief costs money on both sides of the table, not only yours. When a brief says “we need a new website” and nothing else, a supplier fills every gap with an assumption — how many pages, whether copywriting is included, whether the business supplies its own photography — and different suppliers fill the same gaps differently. The quotes that come back are not three prices for one job; they are three prices for three different, unstated jobs, and comparing the numbers tells you only which supplier assumed the least.

There is a second, less obvious cost, and it is worth naming plainly because it is not accidental. A vague brief is commercially convenient for some suppliers, because gaps in the brief become chargeable variations once the project has started. A page count that was never fixed, a function nobody specified in writing, a round of content that was assumed rather than stated — each of these can legitimately be billed as work beyond scope, and the supplier did not create that ambiguity, the brief did. That is not an accusation against any particular supplier; it is a structural incentive built into an unclear document, and the fix is to remove the ambiguity rather than to hope nobody uses it.

What this brief template section covers: budget, timeline and technical requirements

Page	What it answers
What a brief must contain	The minimum a supplier needs before a quote can be accurate
Writing a brief without the vocabulary	How to brief accurately before you know the industry’s terms
Defining success before you start	What “success” has to mean before you can brief against it
Page count and how to arrive at one	Working out a realistic page count instead of guessing
Functional vs content requirements	Why the two get conflated, and what that costs
What to leave out of a brief	What to hand to the designer’s judgement instead of specifying yourself
Budget ranges and how to disclose them	Whether stating a range helps or hurts you
Deadlines and the financial-year rhythm	Deadlines, and Australia’s end-of-financial-year buying pattern
Supplying assets	What you need to hand over, and when
Getting internal sign-off first	Settling internal disagreement before a supplier sees it
How your business model shapes a brief	Why a services business, a retailer and a not-for-profit brief differently
Local vs national businesses	What changes about a brief when the business trades beyond one region

Each page is short enough to read in one sitting and specific enough to act on immediately. None of them assumes you already know web design terminology — that is the subject of one of them.

How a design brief and a scope of works differ: proposals vs a project brief

A brief states what you want and why; a scope of works states what will be built and for how much. The brief is written before you contact a supplier, and it belongs to you. The scope is written by the supplier in response to it, and it becomes part of the contract. Confusing the two is common and costly. A business that treats its own brief as though it were already a scope stops asking questions once a supplier accepts the job. The gaps left in the brief then become the supplier’s document to fill, on the supplier’s terms, after money has changed hands.

Where a website brief generator does the mechanical part

Write a brief any web supplier can quote against is this site’s own tool: a short set of questions, answered in your browser, that assembles a brief in the shape this section describes and appends the questions a supplier should answer before you sign anything. It exists because the mechanical part of assembling a brief is exactly the part people forget under time pressure — remembering to state page count, functional requirements and asset ownership in one document, rather than across three emails. A checklist that runs itself is more reliable than one you have to remember to consult.

What tends to go wrong when this section is skipped: agencies, redesigns and vague direction

Three patterns account for most of the disputes that show up after a website project has already started. Quotes that cannot be compared, because each supplier assumed a different page count or a different split of who writes the content. A design that gets reopened late, because the person who approved it was not actually the person with final authority over the budget. And a build that stalls midway through, because content was assumed to arrive on its own and nobody scheduled the time to write it. Each of those three failures traces back to one specific gap in the brief. Each gap has its own page in this section, rather than being treated as a single, generic “communication problem”. The fix for a missing page count is different from the fix for unclear sign-off, even though both look similar from the outside once the project has already gone wrong.

How this section relates to the rest of the site: choosing an agency for your web design

This section is deliberately narrow: it covers the document you write before you contact a supplier, not the process that follows once you have. What drives the cost of a website picks up once a figure needs explaining. Web designer versus web developer picks up once you need to work out which kind of supplier the brief should even go to. The standards section covers what happens to ownership and contracts once a supplier has been chosen. A brief written using this section does not remove the need to read those; it makes the conversations they cover shorter, because the underlying facts are already settled.

How to use this section so your brief gets accurate quotes

Read what a brief must contain first; it sets the floor that everything else in this section refines. If web design terminology is unfamiliar, read writing a brief without the vocabulary next — it is written for exactly that position and assumes nothing. From there, work through the remaining pages in order. Or jump straight to whichever decision is currently stuck: a budget you are unsure whether to disclose, a deadline that keeps slipping, or an internal disagreement about scope that needs settling before a supplier ever sees the document.

None of this replaces a conversation with a supplier. It exists to make that conversation start from a document specific enough that the answers you get back are about your project, not about the gaps you left in the brief. For where the brief sits inside web design as a whole, start with web design in Australia.