How to Write a Website Brief So Agency Quotes Are Comparable
Three agency quotes for the same five-page site can differ wildly because each vendor assumed a different scope. This template fixes that before you ask.

On this page
Picture three agency quotes for the same "simple five-page website." One comes back as a single line total. One includes a booking system you never asked for. The third assumes you will write all the copy yourself. The totals are far apart, but the real difference isn't price. It's scope.
A good website brief fixes that. The template below covers what to put in it, so every agency prices the same job and you can compare quotes on the things that matter.
Why Most Agency Quotes Can't Be Compared#
When a brief says "we need a modern website that generates leads," each agency fills the gaps with its own assumptions. One assumes a template with light customization. Another assumes custom design, a CMS and a blog migration. Both are reasonable readings of the same sentence.
So you aren't comparing prices. You're comparing guesses about what you meant, and picking the middle quote or the cheapest becomes a bet on whose guess was closest.
A clear brief also protects you after signing. Scope disputes often start with "we thought that was included." If the brief lists the item and the quote prices it, that argument has nowhere to start.
We'd rather answer a detailed brief than a vague one. We can quote accurately in less time, and the client gets a number that holds.
Start With the Business Outcome, Not the Pages#
Agencies can build any list of pages. What they can't know without your help is what the site is for. Open the brief with the result you need, and let vendors propose how to get there.
Write one primary goal and two secondary goals#
State one primary goal in a single sentence, with a number and a date. Compare these two:
- Weak: "Get more leads from the website."
- Usable: "Generate 30 qualified quote requests a month by September 1, up from about 10 today."
Then add up to two secondary goals, such as cutting phone enquiries about opening hours, or giving existing customers a place to download invoices. Rank them. When the budget tightens, the ranking tells everyone what to cut last.
Resist a list of seven equal priorities. A site asked to do seven things equally rarely does any of them well, and the quotes you get back will describe seven different projects.
Name what success looks like in 90 days#
Add a short paragraph on what you'd check three months after launch. Tie it to numbers you already track:
- Quote form submissions per month
- Booked appointments through the site
- Online orders or revenue
- Support emails or calls on topics the site should answer
You don't need a promised result from vendors. The point is to show them what the site is judged on, so they can flag a mismatch early. An agency that reads "30 quote requests a month" and asks about your current traffic has understood the brief.
Define Scope: Pages, Features and Integrations#
Scope is where quotes drift furthest apart. Give vendors a structure to count against. Three lists cover it.
Page list with purpose for each page#
List every page you expect, with one line on what it's for and who it serves. A table works well:
| Page | Purpose | Main action |
|---|---|---|
| Home | Explain what we do, route visitors | Click to services or quote form |
| Services (4 pages) | One page per service, with scope and process | Request a quote |
| About | Build trust, show the team | Contact |
| Contact | Capture enquiries | Submit form |
| Blog (setup only) | Home for future posts, no migration | None at launch |
Be explicit about repeating templates. "Four service pages" and "a services section" can mean very different amounts of work. Also say whether existing content is being migrated, and how many pages or posts.
Features and user workflows written as steps#
"Booking system" means different things to different vendors. Describe the workflow instead, one step at a time:
- A visitor picks a service and a date from available slots.
- They enter name, phone and email, and pay a deposit.
- They receive an email confirmation, and we receive a notification.
- They can reschedule from a link in the email.
Now every vendor is pricing the same four steps. If a step needs custom logic, such as blocking out staff holidays, say so. Bookings, client portals and invoicing are often where off-the-shelf plugins run out and build work starts. Our post on custom DashNex modules shows what that work looks like when the result has to run inside your own platform.
Integrations, logins and data that must move#
List every outside tool the site must talk to, and say which direction data flows. Typical entries:
- Payment processor
- Email marketing or CRM
- Calendar
- Analytics and ad pixels
- Existing customer database or product catalog
Add anything that needs user accounts, such as member logins or a customer area, and specify who can see what. Then list the data that must move over: customer records, past orders, blog posts, redirects from old URLs. Migration is easy to underquote, so make vendors price it on purpose.
Specify Content, Design Inputs and Ownership#
Waiting on content and discovering you don't own what you paid for are two of the costliest surprises in a web project. The brief can head off both.
Who supplies copy, photos and video#
For each content type, state who produces it and who approves it:
- Copy: written by you, written by the agency, or written by you and edited by the agency. Agency copywriting is usually a separate line item, so ask for it separately.
- Photos and video: existing library, stock, or new shoot. Say who pays for licensing and who handles the shoot.
- Brand assets: logo files, colors, fonts and any brand guidelines you already have. If you have none, say you need a basic identity.
- Design: custom design from scratch, a modified template, or a design you've already approved.
Set a rule for delays too. If you owe content by week three and deliver it in week seven, does the launch date move? Agree the answer before work starts.
Ownership of code, domain, hosting and accounts#
This section protects you for years. State plainly what you must own at handover:
- The domain, registered in your name with you as the account holder
- Hosting or platform accounts, with you as the owner and the agency as a collaborator
- All source code and design files, with a clear license to use and modify them
- Admin access to every connected tool: analytics, email, payments
- Written documentation of how the site is built and deployed
Ask each vendor to confirm these in the quote, not later in the contract. If an agency holds your domain, or hosts the site on its own account with no handover clause, you will pay to leave. It's also why we build client sites on platforms the client owns outright, which we explain in why we build client sites on DashNex.
Set Timeline, Budget Range and Post-Launch Support#
Some owners hide the budget, hoping to see the "real" price. It tends to backfire. Without a range, vendors guess, and you get quotes sized to their guess instead of your need.
State a launch date and what drives it, such as a trade show or a seasonal peak. Give a budget band wide enough to be honest, and say which items are fixed and which are flexible. For context on typical ranges before you write the band, see our guide to small business website cost in 2026, which compares DIY, freelancer and agency routes.
Then describe the support you expect after launch: response times for bugs, how many content edits a month you want handled, who updates software, and how backups work. "Ongoing support" without terms is not a quote line. It's a hope.
Ask for quotes that split build, hosting and support#
Require three separate sections in every response:
- Build: a one-time cost, itemized by page group, feature and integration.
- Hosting and running costs: monthly or annual, including domain, licenses and any third-party fees.
- Support and maintenance: what's included, response times, and what counts as extra work.
The split matters because a low build price can hide a high monthly fee. To see how that plays out, work through our method for the real three-year cost of a software subscription and apply it to each vendor's recurring lines.
Ask for Quotes in a Fixed Format and Score Them#
End the brief with a response format, and give the same one to every vendor. Ask for identical headings, the same cost split, and a written list of assumptions and exclusions. Quotes that arrive in a fixed shape can be laid side by side in minutes.
Here's a simple scoring grid. Score each vendor from 1 to 5 per row, multiply by the weight, and add it up. Adjust the weights to your priorities.
| Criterion | Weight | What a 5 looks like |
|---|---|---|
| Scope match | 30% | Every page, workflow and integration in the brief is addressed by name |
| Ownership | 20% | Domain, code, hosting and accounts handed over in writing |
| Line-item pricing | 20% | Build, running costs and support split, with each feature priced |
| Support terms | 15% | Response times, included hours and exclusions stated |
| Timeline | 15% | Dated milestones, with client deadlines marked |
Price is deliberately absent from the grid. Compare totals only after the scores are in, and only between quotes that scored acceptably on scope. A cheap quote that missed half the brief is not cheaper.
Red flags in vague responses#
Watch for these:
- A single lump-sum price with no breakdown, so you can't tell what was left out
- "As needed" or "TBD" on migration, integrations or support
- No mention of ownership, or terms that tie the domain or hosting to the agency
- Template language that never references your goals, pages or workflows
- No stated assumptions, which often means they'll surface later as change orders
- A timeline with no client dependencies, as if content would arrive on its own
A vendor who asks questions before quoting is a good sign. One who sends a polished number the same day may be guessing.
Your Next Step This Week#
Copy the headings from this article into a document and fill in the primary goal first, with a number and a date. Then list your pages and write each workflow as steps. Send the finished brief to three vendors with the fixed response format attached.
When you're close to launch, run the result against our website launch checklist so nothing in the handover gets missed.
Get new posts by email
One email when something new is published. Unsubscribe any time.


