How to Write a Web Development Brief That Gets You Fixed-Price Quotes

The difference between a project that comes in on budget and one that runs 40% over almost always traces back to the brief. A vague brief forces developers to make assumptions — and those assumptions end up in expensive revision requests and scope disputes.

A fixed-price quote is only possible when a developer knows exactly what they are building. This guide shows you how to write the brief that gets you those quotes.

Why Most Briefs Fail

Most clients send something like: "I need a website for my catering business with around 8 pages, contact form, and a gallery. Can you give me a price?"

This is too vague to price accurately. The developer does not know: your target audience, what the gallery needs to do, whether you need a CMS, whether you have existing content, what hosting you have, what your timeline is, or what "done" looks like to you.

The result: a very wide quote range, or a low quote that becomes much higher through "out of scope" charges.

The 10-Section Brief Format

Section 1: Project Overview (2-3 sentences)

What is this for, and what is its primary purpose?
Example: "Website for a Sri Lankan catering company based in London. Primary purpose: generate enquiries from corporate clients for buffet catering. Secondary: showcase past events."

Section 2: Target Audience

Who are your visitors? Age, location, device, intent.
Example: "HR managers at medium-to-large London companies, 30-50 age range, primarily desktop users, searching for catering quotes."

Section 3: Pages and Content Structure

List every page by name with a one-line description of its content. This is the most important section.
Example: Home, About, Menus (3 sub-pages: Corporate, Wedding, Private), Gallery, Testimonials, Contact, FAQ

Section 4: Functional Requirements

Every piece of functionality, no matter how obvious it seems to you:
Contact form with email notification, Google Maps embed, Instagram feed, WhatsApp chat button, online quote request form, PDF menu downloads, image gallery with lightbox, Google Analytics

Section 5: Content You Are Providing

Be specific about what is your responsibility and what the developer is creating:
"I will provide: all text, 60 food/event photos, logo files. Developer to provide: stock images where needed, icon set, any custom graphics."

Section 6: Design Direction

3 reference websites you like, with specific notes on what you like about each. Mood: professional, warm, modern, traditional.
"Site A — like the clean menu layout. Site B — like the dark background with gold accents. Site C — like the overall simplicity."

Section 7: Technical Requirements

Platform preference, hosting details, integrations:
"WordPress preferred for easy CMS. Hosted on cPanel at [host]. Needs to work with Mailchimp for newsletter. Mobile-first responsive. PHP 8.x."

Section 8: Timeline

Your real deadline and any fixed dates:
"Need live by 1 June 2025 for a launch event. Design approval by 10 May. Content submitted by 20 April."

Section 9: Budget

State a range. This is not a negotiating weakness — it gets you a proposal that fits your actual budget rather than a generic quote.
"Budget: £1,200-1,800 for the build. Would consider a monthly maintenance retainer of £150-200 after launch."

Section 10: Decision Process

Who approves things and when can you make decisions?
"I am the sole decision maker. Available for a 30-minute briefing call any weekday evening. Can give design feedback within 48 hours of receiving mockups."

What to Do With the Brief

• Send it to 2-3 developers simultaneously — compare quotes based on identical requirements
• Ask each developer to confirm they have read it and flag any questions before quoting
• A developer who asks good clarifying questions is a better choice than one who just sends a price
• Use the brief as the basis for your contract — "scope of work" = the brief + developer's technical proposal