Why the Same Website Gets Wildly Different Quotes
A quote is a price for a set of assumptions. When the brief says nothing about something, the agency fills the silence with whatever it normally builds, and prices that.
Take a line we see all the time: "Five pages and a small shop." One studio reads that as a ready-made theme with your logo, where you upload twenty products yourself. Another reads it as a custom design, product photos edited and uploaded for you, and a card payment gateway connected and tested. A third assumes the same build plus copywriting and a year of maintenance. None of them is cheating. They are quoting three different jobs.
If a sentence can be read two ways, a careful agency prices the more expensive reading or adds a buffer, because a wrong guess comes out of its own margin. Every vague line in your brief carries a small risk premium. Clear answers remove it.
What a Website Brief Is, and What It Isn't
A website brief is a short document that explains what the business does, what the site has to achieve, what is in scope, what constraints apply, and how much time and money you have. For most small business sites, one or two pages is plenty.
It is not a technical specification, so you don't need wireframes or a chosen tech stack. A detailed requirements document usually comes later, written with the agency you hire. The brief's job is to give every agency the same picture, so their quotes describe the same work.
One rule makes briefs better almost immediately: describe the problem, not the solution. "We need a slider on the homepage" tells us about a component. "Visitors don't realise we also rent medical equipment" tells us about a problem, and there may be a better fix than a slider.
The Website Brief Sections That Change the Price
Not every question in a brief carries the same weight. These are the ones that move a quote up or down, in roughly the order an agency reads them.
| Section | What to write | Why it moves the price |
|---|---|---|
| Business and audience | What you sell, who buys, where they are, what device they use | Decides tone, languages, and how much the site must explain |
| The main goal | One action the site must drive, and how you measure it today | Shapes page structure, forms, and tracking work |
| Pages and templates | A page list, grouped by type (service page, product, blog post) | Agencies price templates more than raw page counts |
| Features and integrations | Booking, payments, CRM, WhatsApp, search, member areas | Integrations are where quotes differ most |
| Content | Who writes copy, who supplies photos, which languages | Copywriting and a second language can be a large share of the work |
| Who updates the site | What your team will change after launch, and how often | Decides between a CMS and a hand-coded build |
| Design inputs | Logo files, brand colours, three sites you like and why | Tells the agency whether to design from scratch or work to a brand |
| Ownership and access | What you expect to own and control at the end | Accounts set up in your name take a little longer but avoid lock-in |
| Budget, deadline, sign-off | A range, a date with a reason, and who approves | Tells the agency whether to propose a template, custom, or phased build |
Give the goal a number, even a rough one
"A modern, professional website" is not a goal, because every agency already thinks it delivers that. Compare it with: "Most of our enquiries come by phone from referrals. We want families searching online to be able to WhatsApp us, and we want to see how many do." That second version tells the agency to put contact buttons on every service page, to keep them visible on a phone, and to set up click tracking. If you want that last part done properly, our guide to tracking WhatsApp clicks in GA4 shows what to ask for.
Count templates, not just pages
Forty blog posts share one blog post template. Six service pages usually share one service template. Design and build time follows the number of different layouts, plus one-offs like a pricing calculator. When we built the site for PakTech, each service got its own page and URL, which is why our advice there was to list four to eight real services rather than eighteen synonyms. Your brief can do the same: name the real services, and an agency can see the template count at a glance.
Name every integration, and its owner
For each system the site must talk to, write three things: the name of the tool, what should flow between it and the site, and who controls the account. "Online payments" is vague. "Card payments plus cash on delivery for customers in Pakistan, through a gateway we haven't chosen yet" is something an agency can quote. If your sales team handles leads differently by type, say so. On the I-Realtor site, enquiry forms separate off-plan from ready property because the follow-up is different, and that is the kind of detail that belongs in a brief.
Say who will edit the site after launch
This one answer often decides the platform. The owner of Asian Elegance By Z needed to add products herself, and the team behind Patient Healthcare Services needed to change hours and offers without waiting on a developer, so both sites run on WordPress. A site that changes twice a year can be hand-coded. We compared the trade-offs on our own site in static HTML vs WordPress.
Share a budget range
Many owners hold the budget back, worried an agency will spend all of it. In practice a range tells the agency which kind of solution to propose. A modest range points to a well-chosen theme and a tight page list. A larger one opens up custom design or a phased plan. Without it, you get proposals aimed at three different budgets and have to start again. Our website cost guide can help you set a realistic range before you write one down.
Ownership and Access: The Part Most Briefs Leave Out
Write down, in plain words, what you expect to control when the project ends.
- The domain, registered in your name. ICANN's registrant rights and responsibilities page says the registrant assumes "sole responsibility for the registration and use" of the domain and must keep their contact details accurate. That registrant should be your business, not the agency. Our domain name guide covers the rest.
- Hosting in your account, with the agency added as a user if they need access.
- Analytics with you as an Administrator. In GA4, Google's user management help says you need the Administrator role to add or change users. If the agency is the only Administrator, you will need them every time someone joins or leaves.
- Search Console and Google Business Profile. Both let you add other people. Google Business Profile separates owners and managers, so keep ownership with the business and give the agency manager access. Our Search Console guide walks through verification.
- Theme and plugin licences, source files, and logins, listed in a handover document at launch.
If you are replacing a site that already gets search traffic, add one more line: "Old URLs must redirect to their new equivalents." Google's site move documentation recommends server-side permanent redirects, such as 301 or 308, from each old URL to its new one. Asking for it in the brief means it gets quoted instead of forgotten. The redesign SEO guide explains how to build that map.
Website Brief Template You Can Copy
Paste this into a document and answer each prompt in a few honest sentences. If a line doesn't apply, write "not needed" rather than deleting it, so the agency knows you thought about it.
WEBSITE BRIEF: [Business name] Date: [ ]
1. ABOUT US
What we sell, who buys it, where they are:
Current website (URL), and what works or doesn't:
2. THE MAIN GOAL
The one action we want visitors to take:
How we count that action today:
3. AUDIENCE
Who visits, on which device, in which language(s):
4. PAGES (group by type)
Service/product pages: [list]
Other pages: Home, About, Contact, Blog, [ ]
One-off pages or tools: [ ]
5. FEATURES AND INTEGRATIONS
Feature | Tool (if known) | Who owns the account
e.g. Payments | not chosen yet | us
6. CONTENT
Copy written by: us / agency / mix
Photos and video from: us / stock / shoot needed
Languages:
7. AFTER LAUNCH
What our team will update, and how often:
Support we expect (none / hourly / monthly):
8. DESIGN
Logo and brand files: attached / not yet
3 sites we like, and what we like about each:
3 sites we don't want to look like:
9. OWNERSHIP
Domain, hosting, analytics, Search Console and
Business Profile to be in our name: yes / discuss
10. MUST-HAVE NOW vs LATER
Phase 1:
Phase 2:
11. BUDGET, DEADLINE, SIGN-OFF
Budget range:
Launch date, and why that date:
Final approval by:
PLEASE INCLUDE IN YOUR QUOTE
What is included, what is excluded, number of design
revisions, payment stages, yearly running costs, and
what we receive at handover.
The last block is the part most templates skip. Telling agencies what you want to see in the quote is what makes the replies comparable.
How to Compare Website Quotes Once They Arrive
Even from the same brief, proposals come back in different shapes. Before looking at totals, put them on one grid.
- List every item your project needs, using your brief as the checklist.
- For each proposal, mark every item as included, excluded, or not mentioned.
- Ask each agency to price or clarify the items it didn't mention. Do this in writing, and send any new detail to every agency, not only the one who asked.
- Add the recurring costs (hosting, domain renewal, paid plugins, maintenance) over two or three years, not just the build fee.
- Only then compare totals.
| Item from your brief | Quote A | Quote B | Quote C |
|---|---|---|---|
| Custom design for home and service pages | Included | Theme only | Included |
| Copywriting | Not mentioned | Excluded | Included |
| Payment gateway set-up | Included | Included | Not mentioned |
| Design revision rounds | 2 | Not mentioned | 3 |
| Accounts in client's name | Yes | Not mentioned | Yes |
| Support after launch | 30 days | Excluded | Monthly plan |
Once the gaps are priced, the cheapest proposal often stops being the cheapest, and a quote that ignores half your brief has told you something about how the project would run. For the questions to ask in the follow-up call, see how to choose a web design company.
Common Website Brief Mistakes
- "Make it like this competitor's site." Fine as a starting point, but say what you like about it: the menu, the photography, the booking flow. Equally useful is the opposite list. Our Zebra Crossing case study ends with the same advice for any brand site: send logo files, three competitor sites you refuse to look like, and whether you need a cart now or later.
- A wish list with no priorities. When everything is a must-have, agencies quote everything. Split the list into launch and phase two.
- No named decision-maker. Five people giving separate feedback slows any project. Name one person who signs off, and collect feedback in one combined round.
Frequently Asked Questions
How long should a website brief be?
For most small business websites, one or two pages is enough. Clear answers on the goal, page list, features, content, budget range and deadline matter far more than length. A long brief full of wishes is harder for an agency to price than a short one with priorities.
Should I include my budget in a website brief?
Yes. A range is enough, even a wide one. It tells the agency whether to propose a theme-based site, a custom design, or a phased build, so the quotes you get back are aimed at your budget rather than three different guesses.
What is the difference between a website brief and a requirements document?
A brief explains the business, the goal, the scope, the constraints, the budget and the deadline, so agencies can quote. A requirements document goes much deeper into how each feature should work and is usually written later, often with the agency you hire during a discovery stage.
Can I send the same website brief to several agencies?
You should. Sending every agency the same written brief is what makes the quotes comparable. If one agency asks a question that adds new detail, send the answer to all of them so the quotes stay based on the same information.
Do I need to choose WordPress, Shopify or a custom build before writing the brief?
No. Describe what the site must do and who will update it after launch, and let the agencies recommend a platform. If you already have a preference or an existing system you must keep, say so in the brief.
