How to Brief a Web Designer: The One-Page Brief That Gets You an Accurate Quote

You can brief a web designer on one page: state the goal of the site, who it is for, the pages you need, examples you like and dislike with the reasons, how ready your content is, the functions required, the timeline, who makes decisions, plus a budget outline and one clear measure of success. A designer who receives that page can quote accurately, design in the right direction first time, and tell you honestly if your timeline or your expected spend does not match the work involved.

Most expensive misunderstandings in web projects are not caused by bad designers or difficult clients. They are caused by a brief that never happened — a competitor link sent as the whole instruction, a deadline mentioned in week six that existed from day one, a shop function assumed by one side and never imagined by the other. This guide fixes that at the source. It explains what a brief is and is not, walks through the nine elements with a complete fictional example, and shows how scope changes fairly change cost. Pair it with our companion guide to preparing your website content, because content readiness is the element briefs most often overstate.

What Is a Web Design Brief — and What Is It Not?

A brief is a decision document, not a design. Its job is to record what the website must achieve, who it serves, what it must contain and what limits the project works within, so that two people can point at the same page and settle any later disagreement about what was agreed. It is written by the client, in plain language, before design work starts, and it is short on purpose: one page forces the decisions that a ten-page wish list allows everyone to postpone.

A brief is not a list of colours and fonts. Visual taste matters, and examples belong in the brief, but a site chosen purely for its look, serving the wrong audience with the wrong pages, will fail beautifully. Nor is a brief a technical specification. You do not need to name a platform, a framework or a hosting type unless you already have a genuine constraint — an existing shop, an in-house team with a particular skill, a legal requirement. State the outcome you need and let the designer propose the route, then judge the proposal against the brief.

Finally, a brief is not a trap. Some clients hold back information — a fixed launch date tied to an event, a stakeholder who must approve, a function planned for phase two that affects phase one — hoping a lower quote will follow. It never works that way. The hidden fact surfaces mid-project, when changing course costs the most, and trust on both sides is damaged. A complete, honest one-pager is the cheapest insurance a small business can buy.

What Are the 9 Elements of a One-Page Brief?

The nine elements below fit on one page when each is written in two to four honest lines. The table shows what to write for each element and why the designer needs it. If an element genuinely does not apply — a brochure site with no deadline pressure, for example — write that explicitly rather than leaving a blank, because a blank reads as 'not yet decided' and a stated 'none' reads as a decision.

Write the brief before you request quotes, and send the same brief to every designer you approach. Identical inputs produce comparable quotes; different conversations produce quotes that cannot be compared, which is how the cheapest-looking option becomes the most expensive project.

Element	What to write	Why it matters
1. Goal	The one main job of the site: enquiries, online sales, bookings, credibility for larger contracts	Every design decision is judged against this; two goals need a stated priority
2. Audience	Who visits, in what situation, on what device, and what they need to decide	Language, layout and trust signals all change with the audience
3. Pages	The list of pages for launch, and what each page must do	Page count and page complexity drive most of the work
4. Examples	2–3 sites you like and 1–2 you dislike, with the reason for each	Reasons transfer; bare links do not — the designer learns the principle behind your taste
5. Content readiness	What text and photos exist now, what is being written, and by when — honestly	Design around real content differs completely from design around placeholders
6. Functions	Forms, booking, payments, accounts, languages, integrations — each named	Functions carry setup, testing and often ongoing costs; surprises here are the expensive kind
7. Timeline	Launch date if one exists, what drives it, and your availability for feedback	A date tied to an event or season changes how work must be sequenced
8. Decision-maker	One named person who approves, plus anyone who must be consulted	Approval by committee, discovered late, is the classic cause of redesign loops
9. Success measure	One observable result: enquiries per week, online orders, fewer phone queries on a topic	Gives both sides the same finish line, and a basis for judging the site after launch

What Does a Complete Brief Look Like? An Example

Example — clearly labelled as an example. The brief below is written for a fictional bakery, Crumb and Craft, in a fictional situation. The business, names, dates and details are illustrative only, included so you can copy the shape and the level of honesty for your own brief.

Goal: Take celebration-cake orders online with a deposit, so the shop stops losing orders that currently arrive as long message threads. Secondary goal: a credible site we can show to two local cafes we hope to supply. Audience: Local parents and office managers ordering cakes one to three weeks ahead, mostly on phones, mostly within a 10-mile radius. They need flavours, sizes, prices and lead times without calling. Pages: Home; Cakes (one page per category: celebration, wedding, everyday); How to Order; About; Contact with a map and parking note. Gallery inside the cake pages, not a separate page. Examples we like: A bakery site with large, honest photos and prices visible without enquiring — we like the openness, not its colours. A cafe site with a very short order form — we like the three-field simplicity. Example we dislike: A competitor with music, animations and no prices anywhere — it feels evasive to us and our customers ask about price first. Content readiness: Menu and price list final. Cake descriptions half written, finished within two weeks. Photos: we have phone photos of most cakes; a half-day photo session is booked before launch. Logo exists as a file. Functions: Order form that calculates a deposit, card payment for the deposit, two languages on key pages in phase two (not launch). No customer accounts. Timeline: Launch before the wedding season rush in late spring; the owner can review drafts twice a week. Decision-maker: The owner decides; the head baker is consulted on cake pages only. Success measure: At least half of celebration-cake orders arriving through the site form, with deposits paid, within three months of launch.

Notice what makes that example work. It is specific where specificity is cheap — pages, functions, dates — and honest where honesty is uncomfortable — content only half ready, photos still to be taken. It gives reasons for taste instead of just links. And it names one decision-maker. A designer reading it can quote without a follow-up meeting, and any later disagreement can be settled by pointing at the page. Write yours to the same standard, even if your answers are less tidy. A brief that says 'content not started, need guidance' is far more useful than one that claims everything is ready when it is not.

How Do Scope Changes Create Cost Changes?

A quote prices the brief, not every possible version of the website. When the brief changes — pages added, a function introduced, content arriving in a different form than promised — the work changes, and fair pricing changes with it. Understanding that mechanism, before it happens to you, is what separates a calm project from an argument. Changes cost for three ordinary reasons: new work takes new hours, changed work means finished work is redone, and late changes arrive when the project schedule has no slack left to absorb them.

The size of the effect depends on timing and type, described here in relative terms because honest pricing varies by project. Adding a simple text page before design starts is a small change. Adding the same page after the design system is built is still modest. Adding online payments, accounts or a second language late is a large change, because each of those touches design, build, testing, legal pages and content at once. Moving a launch date earlier is also a scope change: it buys priority and overtime, not the same work faster for free.

Change-request etiquette keeps this fair on both sides. Put every change in writing, in one place. Ask for the effect on price and date before approving the change, not after. Expect the designer to state both clearly, and to say no or 'phase two' when a change would damage the launch. In return, batch your feedback — one consolidated list per review round, from the named decision-maker — instead of a drip of daily messages that each restart the designer's thinking. Our guide to custom website costs in the USA explains the main cost drivers behind quotes, which helps you predict which of your ideas are small changes and which are large ones before you request them.

What Questions Should a Good Designer Ask Back?

A good brief invites good questions, and the questions a designer asks are one of the clearest trust signals you will get. A designer who quotes instantly, asks nothing, and agrees with everything is not being efficient — they are either guessing, planning to charge for every discovery later, or not expecting to be involved long enough for the answers to matter. Expect questions that probe the brief where it is vague, commercial where it is unrealistic, and practical where your plan meets real visitors.

The strongest questions usually concern the audience's next step, the content that does not yet exist, and what happens after launch — updates, backups, and who fixes what. Treat those questions as free consultancy: each one identifies a decision you would otherwise make accidentally, under time pressure, later.

• What should a visitor do on each page — and what happens in your business when they do it? Who answers the form, how fast, and what do they send back?
• Which content is genuinely ready? A follow-up that asks to see the actual files separates real readiness from hopeful readiness.
• What do you already have? Domain, hosting, existing site, analytics, brand files, photography — and what state each is in.
• Who are your real competitors online — not the shop across town, but the sites your customers actually compare you with in search results?
• What happens after launch? Who updates pages, adds products, checks backups and renews the domain — and what support do you expect to be included?
• What would make you call this project a failure? The mirror of the success measure, and often the most honest answer in the whole conversation.

How Do You Decide Priorities When Not Everything Fits?

Most briefs contain one quiet contradiction: everything listed, at the highest finish, by a fixed date, inside a modest expected spend. Something has to give, and the brief is where you choose what gives — deliberately, in advance — instead of letting the project choose for you under pressure. Rank your pages and functions into three groups: launch essentials, launch if time allows, and phase two. Write the ranking into the brief. Designers plan differently, and far more calmly, when they know which items can move without anyone treating it as a failure.

Use the goal and the success measure to rank. For the fictional bakery, the deposit-taking order form outranks the second language because the goal is orders and the measure counts them. For another business, credibility pages might outrank a booking function. There is no universal order — there is only your goal, applied consistently. This is also where platform choices belong: as context for the designer, not as a demand. If you have a preference or an existing system, say so and say why. Our comparison of WordPress versus a custom website explains the trade-offs a designer will weigh when they recommend a route for your brief.

What Mistakes Make Briefs Fail?

Briefing by competitor link only. A link says 'be like this' without saying in what respect — their prices, their photography, their booking flow, or merely their colour? The designer guesses, the client meant something else, and the first design round is wasted discovering it. Links belong in the brief, always with the reason attached, as the example above shows.

'Make it pop' and other untranslatable instructions. Vague praise-words — pop, wow factor, premium feel, user-friendly — mean different things to every reader, so they cannot be designed to or quoted against. Translate each one into something observable: 'premium' might mean generous white space, restrained colours and professional photography; 'user-friendly' might mean the order form fits on one phone screen. If you cannot translate it, cut it and keep the observable parts.

Hiding a hard deadline. A launch tied to a wedding season, a trade fair, a lease start or a funding announcement is a fact the designer needs on day one, because it changes sequencing, staffing and what corners can safely be cut. Revealed in week six, the same deadline buys panic. Put the date and the reason in the brief, and say what 'launched' must minimally include for that date to count.

• Designing by committee in disguise: the brief names one decision-maker, but feedback arrives from four people with conflicting tastes. Name the decider and keep the promise.
• Overstating content readiness: 'text is ready' that turns out to mean 'in someone's head'. Show the files or describe the real state.
• No success measure: without one, every opinion about the finished site is equally valid, which means the loudest opinion wins.
• Asking for quotes on different briefs: send every designer the same page, or you are comparing conversations, not prices.

How Do You Send the Brief and Start Well?

Send the brief as a single document — one page if you can, two at most — with your content pack or a clear statement of its state. Ask each designer to reply with three things: a quote tied to the brief's pages and functions, a timeline that names when they need content and feedback from you, and any questions or disagreements they have with the brief itself. That last item is deliberate. A designer who pushes back on one element, with reasons, is showing you how they think; file that response alongside the price when you decide.

At kickoff, agree the review rhythm the brief promised: how many rounds, through whom, and within how many days feedback will come. Then protect your own side of the schedule as carefully as you expect the designer to protect theirs, because most project delays after a good brief are feedback delays. Keep the brief beside you at every review. When a new idea appears — and good ideas will — test it against the goal, the success measure and the phase-two list before it becomes a change request. That single habit, more than any other, is what the one-page brief is for.

Frequently Asked Questions

How long should a web design brief be?

One page is the ideal: nine elements, each in two to four honest lines. Two pages is acceptable for a site with a shop or several functions. If your brief runs much longer, it probably contains design detail that belongs in later discussions, while the decisions that matter risk getting buried.

Should I include my expected spend in the brief?

Yes — include plus a budget outline as a genuine range. Designers work to a level of finish, and a range lets them tell you what is achievable inside it. Withholding it does not produce lower quotes; it produces incomparable ones, padded guesses, or designs you cannot afford to build.

What if I do not know which pages I need?

Write the goal and audience first, then list the questions visitors must be able to answer and the actions they must be able to take. Pages usually follow from that list. A designer can refine the page list with you — that is normal consultancy — but the underlying visitor needs should come from your knowledge of your customers.

Can I use the same brief to get several quotes?

Yes, and you should. Send the identical brief to each designer so the quotes are comparable. Differences between quotes then reveal real differences in approach, inclusions and experience, rather than differences in what each designer happened to assume.

What is the difference between a brief and a specification?

A brief records goals, audience, pages, functions, limits and success measures in plain language, written by the client. A specification is the detailed technical and design document produced afterwards, usually by the designer or developer, describing exactly how the brief will be implemented. You write the brief; the specification is a response to it.

How do I handle a change I want after the project has started?

Put it in writing, ask for its effect on price and launch date before approving it, and expect finished work affected by the change to be redone at a fair cost. Batch changes where you can, and consider honestly whether the idea belongs in phase two instead — many do.

What if a designer asks no questions about my brief?

Treat it as a warning sign, not efficiency. A designer who asks nothing is guessing at your audience, content and goals, and those guesses surface later as revisions or extra charges. Prompt them with the questions in this guide; if the answers stay shallow, choose a designer who engages with the brief.