Web Development

How to Brief a Web Developer (So You Don't Waste Everyone's Time)

By Web Dev NC · June 23, 2026

Learn what to include in a website project brief so developers can quote accurately, avoid scope confusion, and build the right website faster.

The single biggest predictor of a smooth web project is a clear brief. Not the developer’s skill. Not the budget. The clarity of the brief.

We’ve had $499 projects finish on time and under budget. We’ve had $10,000 projects spiral into delays and frustration. The difference was almost always the quality of the brief at the start.

Here’s how to write one that works.

Quick Answer

A strong website brief explains the business goal, audience, required pages, features, integrations, content status, deadline, budget range, examples, and decision process. The goal is not to write a perfect technical document. The goal is to give the developer enough context to quote the right work.

What a Brief Does

A good brief does three things:

  1. Forces you to think through what you actually want — you’d be surprised how many people realize mid-project they hadn’t thought about X
  2. Gives the developer everything needed to quote accurately — vague briefs get vague quotes with large contingency buffers
  3. Becomes the reference document when scope creep starts — “is this in the original brief?” is how you manage additions

The Brief Template

Copy this, fill it in, send it.

Section 1: About Your Business

Business name:
Industry:
Location: (and who you serve geographically)
What you sell/do: (2–3 sentences for someone who knows nothing about your business)
Who your customers are: (be specific — not “anyone who needs our service”)

Section 2: Project Overview

Project type:
(New website / Redesign / New pages on existing site / Web app / eCommerce / Mobile app)

One-sentence description of what you need:
Example: “A 6-page WordPress business site for a Charlotte roofing contractor that generates phone calls and quote requests.”

Why now? (What’s the trigger — new business, rebrand, existing site isn’t working, new service launch?)

Section 3: Pages and Features

List every page you need:
Example:

  • Homepage
  • About Us
  • Services (overview)
  • Roof Repair (service page)
  • Roof Replacement (service page)
  • Contact / Get a Quote

Features needed: (check all that apply)

  • Contact form
  • Online booking / appointment scheduling
  • Blog / news section
  • eCommerce / online shop
  • User login / accounts
  • Email newsletter signup
  • Gallery / portfolio section
  • Chat widget
  • Map / location
  • Other: ___

Integrations needed:
(CRM? Booking system? Payment processor? Email marketing? List the specific tools if you know them.)

Section 4: Content

Who is writing the copy?
(You / a copywriter you’re hiring / the developer / not sure)

Do you have a logo? (Yes/No/In progress)
Do you have photos? (Yes/No — note: stock photos are fine for a start but real photos convert better)
Do you have a brand guide? (Colors, fonts, style)

Is there existing content to work from? (current website, Word docs, PDFs)

Section 5: Design Direction

Are you providing a design? (Figma file, mockup, wireframe?)
If no: describe the visual direction in words, and provide 2–3 websites whose design you like (and what you like about them)

What feeling should the website convey?
(Professional and corporate / Friendly and approachable / Premium and minimal / Bold and energetic / etc.)

What are your brand colors? (Hex codes if known)

Section 6: Technical Requirements

Do you have hosting? (If yes: who? Shared / VPS / dedicated?)
Do you have a domain? (If yes: who’s the registrar?)
Any specific technology requirements? (WordPress required? Specific page builder? Must integrate with X system?)
Who will maintain the site after launch? (You / ongoing developer relationship / nobody)

Section 7: Timeline and Budget

Hard deadline? (If yes: what is it and why does it matter?)
Ideal launch date:
Budget range: (A realistic number is more useful than an undefined low-cost target)

Section 8: Competitors / Inspiration

Who are your top 3 competitors? (Include their website URLs)
2–3 websites you like (and what specifically you like about them)
2–3 websites you don’t like (and what specifically bothers you)

Common Brief Mistakes

“I’ll know what I want when I see it.”
This is the most expensive sentence in web development. It means unlimited revision cycles at your developer’s hourly rate.

Listing features without explaining purpose.
“We need a calculator” — but what does it calculate, who uses it, what does it output? Purpose determines complexity determines cost.

Not knowing the content situation.
Many projects stall at content. If you don’t know who’s writing the text for your website, figure that out before you brief a developer.

“Like Apple’s website but for a plumber.”
Specific is useful. “Apple’s website” describes a visual aesthetic and massive simplicity — fine. “Clean, minimal, high-quality photography, few words per screen” is more actionable.

“Whatever you think is best.”
Some flexibility is good. Completely deferring to the developer on business decisions (what should the homepage say? what’s your main service?) is not — only you know your business.

How We Use Your Brief

When you send us a brief, we:

  1. Read it completely
  2. Note anything unclear or missing
  3. Send back a list of clarifying questions (usually 5–10)
  4. Use your answers to build a formal scope-of-work document
  5. Price based on that scope

The better your brief, the shorter our clarifying questions, the faster you get a quote, and the more accurate that quote will be.

Start with a consultation — 30 minutes, we’ll walk through the brief framework live for your project.

Related:

Have a project in mind?

Book a Free Consultation