How to Write a Project Brief That Gets Accurate Quotes
The number one reason agencies give vague estimates? Vague briefs. If your project request is “we need a website,” don’t be surprised when the quote comes back as “somewhere between $5,000 and $50,000.”
A clear project brief gets you accurate quotes, faster timelines, and better results. Here’s how to write one.
Why the Brief Matters
A project brief is the foundation of your entire project. It’s what agencies use to understand your needs, estimate costs, and plan the work. A good brief:
- Gets you accurate, comparable quotes from multiple agencies
- Reduces back-and-forth during the proposal phase
- Sets clear expectations for scope and deliverables
- Prevents the dreaded “that wasn’t in the original plan” conversation
You don’t need a 30-page document. One to two pages covering the right things beats a novel covering the wrong things.
What to Include
1. About your company
Two to three sentences about what your business does, who your customers are, and what makes you different. Agencies need context to make smart recommendations. Don’t assume they’ll research you thoroughly before quoting.
2. The problem you’re solving
This is the most important part. Don’t just say what you want built — explain why. “We need a new website” is a solution. “Our current site doesn’t convert visitors into leads” is a problem. The problem tells the agency what success looks like.
3. What you need built
Be as specific as you can about the deliverables:
- Type of project (marketing site, web app, e-commerce store, etc.)
- Key pages or screens
- Core features and functionality
- Integrations (payment processing, CRM, email, analytics)
- Content — are you providing it or does the agency need to create it?
It’s okay to say “I’m not sure about this part” — that’s what discovery is for. But give your best understanding of the scope.
4. Target audience
Who will use this? A B2B SaaS platform for enterprise IT teams has very different design and functionality requirements than a consumer e-commerce store. Even a sentence or two here helps the agency make better decisions.
5. Examples and inspiration
Share 2-3 websites or apps you admire and explain what you like about them. “I like how Stripe explains complex features simply” is more useful than “I want it to look modern.”
6. Budget range
This is where people hesitate, but sharing a budget range helps everyone. You don’t need an exact number — a range like “$10,000-$20,000” tells the agency whether they should propose a Cadillac or a solid sedan. Without it, you’ll waste time on proposals that are wildly over or under your expectations.
7. Timeline
When do you need this done? Is there a hard deadline (product launch, conference, funding round) or is it flexible? Be realistic — a 20-page e-commerce site in two weeks isn’t happening without serious trade-offs.
8. Decision process
Who’s making the final call? How many proposals are you reviewing? What’s your decision timeline? This helps agencies prioritize and tailor their response.
What Not to Include
- Technical specifications — Unless you have strong technical opinions, let the agency recommend the stack. “Must be built in React” is usually less helpful than “must load fast and be easy to update.”
- Design mockups — Rough wireframes are great, but polished mockups before hiring a design team creates constraints that may not serve the project well.
- Feature wish lists with 50 items — Focus on the must-haves. A good agency will help you prioritize the nice-to-haves during discovery.
A Simple Template
Here’s a structure you can follow:
- Company overview: Who you are, what you do, who your customers are
- Problem: Why you need this project (the business problem, not the technical solution)
- Scope: What needs to be built (pages, features, integrations)
- Audience: Who will use this
- Inspiration: 2-3 examples of what you like and why
- Budget: A realistic range
- Timeline: When you need it, and whether that’s flexible
- Process: How you’ll evaluate proposals
What Happens Next
A good agency will read your brief, ask smart follow-up questions, and come back with a proposal or a discovery call. The better your brief, the less time you’ll spend in back-and-forth — and the more accurate the estimates you’ll receive.
If an agency doesn’t ask follow-up questions after reading your brief, be cautious. Either the brief was perfect (unlikely) or they’re not paying close enough attention.
Related Articles
What Does a Web Development Agency Actually Do?
Not sure what a web development agency handles vs. freelancers or in-house teams? Here's what agencies actually do, how projects work, and what to expect.
How to Fire Your MSP's Web Service Without Losing Your IT Support
A practical playbook for keeping your IT provider for IT and moving the website work to a real web shop. Includes the access checklist, the conversation script, and the red flags to watch for during the handoff.
Should Your IT Company Build Your Website?
Your MSP keeps your printers running and your servers patched — but should they also build the website that brings you new customers? An honest look at where MSPs end and web agencies begin.
Get insights delivered
Practical web development & business insights. No spam — just the good stuff, once or twice a month.