Introduction
A good website brief tells a developer who the site is for, what it must do, what already exists, who supplies content and what limits apply. Quotes differ mostly because each agency fills gaps with its own assumptions. Remove the gaps and the quotes become comparable. You do not need technical language or a long document. Two to four pages that state facts, priorities and exclusions will do more than a polished design wish list. The sections below explain what to include and why, followed by a fictional worked example.
What a Useful Website Brief Needs to Say
A website project brief is a set of decisions and known facts, not a description of how you want the site to feel. Developers price effort: pages to design, templates to build, integrations to connect, content to handle and reviews to manage. If your document leaves those unclear, each bidder guesses differently and you end up comparing guesses.
There is a tradeoff in length. A one-paragraph request invites a generic quote. A forty-page specification can lock you into decisions you have not tested. Aim for enough detail that a developer can identify the main cost drivers, and mark anything uncertain as an open question rather than hiding it.
Start With Audience and Evidence
Name the two or three groups who use the site, and say what each is trying to do. "Customers" is too broad. "Purchase managers comparing suppliers before requesting a quote" tells a designer what to put first.
Then add evidence for your claims about those groups. This can be modest: the pages visitors currently use most in your analytics, common questions your sales team hears, the search terms people use to find you, or complaints about the current site. If you have no data, say so. That is useful information, because it suggests the project may need a short discovery phase before fixed scope is agreed.
Describe Page Types and Workflows, Not Just a Sitemap
A list of page names hides most of the work. Ten service pages that share one template are far cheaper to build than ten that each need a different layout. Group pages by type and say how many of each exist: home, service, product, case study, article, location, legal, and so on. Note which are new, which are migrated and which need rewriting.
Workflows matter just as much. Describe what happens after a visitor acts. Who receives an enquiry, in which system, and what reply is expected? Does a quote request need file upload? Is there a login area? Do orders or bookings need to reach accounting or inventory software? Each handoff is a possible integration, and integrations are common sources of quote differences. Your web design requirements should state them even if you are unsure how they will be built.
Name Content Owners and Constraints
Delays often come from content, not code. For every page type, name the person who writes, approves and supplies images or documents, and note when they are available. Say whether you expect the developer to write copy, edit yours or only place it. Be clear about who photographs products or people.
Constraints should be listed plainly:
- Existing domain, hosting or email arrangements that must stay.
- Software the team already uses, such as a CRM or accounting package.
- Fixed dates, like an exhibition or campaign, and what happens if they are missed.
- Brand assets, accessibility needs and languages required.
- Redirect and ranking concerns if you are replacing an existing site. No developer can promise that rankings will stay unchanged, but they can plan URL mapping if they know the old structure.
- Sector-specific content, such as regulated claims, which your own professional adviser should review before publication.
Free quote · reply within 24 hours
Talk to the developers who'd build it
No account managers. Send your brief and get one fixed price and delivery window in writing within 24 hours.
A Hypothetical Worked Example
The following is a fictional illustration, not a real client or project.
Imagine Sahyadri Lab Supplies, a made-up distributor of laboratory consumables in Maharashtra, replacing a five-year-old website. Its brief might read like this:
Audience: Procurement officers at colleges and testing labs who compare suppliers and request quotes; a smaller group of lab technicians looking up product specifications. Evidence: Analytics show most visits land on product pages; the sales team says roughly half of calls ask whether an item is in stock; there is no data on mobile use yet.
Page types: Home; about; 12 category pages; about 300 product pages imported from a spreadsheet; 4 downloadable certificate pages; contact. Workflows: Visitors add items to a quote list and submit it; the sales inbox and CRM both receive it; no online payment in this phase. Content owners: The sales manager approves product data; the owner approves copy; the developer is not expected to write product descriptions. Constraints: Keep the current domain and email; launch before an exhibition in the second half of the year; budget ceiling stated separately; order tracking and a customer login are out of scope for now.
Every line here removes an assumption. A bidder knows the catalogue is imported rather than hand-built, that a quote list is the main custom feature and that payments are excluded. The open question about mobile use is stated honestly, so bidders can propose a quick check.
Vague Statements Compared With Quote-Ready Ones
| Vague statement | Quote-ready version | Assumption removed |
|---|---|---|
| We need an ecommerce site | Quote list with CRM handoff; payments excluded this phase | Payment gateway and checkout scope |
| Around 300 products | 300 products imported from one spreadsheet, fields listed | Manual entry versus bulk import |
| Modern, clean design | Two competitor sites you like and one you dislike, with reasons | Design direction and revision rounds |
| Content will be ready soon | Sales manager supplies product data by an agreed date | Waiting time and responsibility |
Be Honest About Budget and Timing
Withholding your budget rarely produces a better price. It usually produces quotes that are either unaffordable or scoped below your needs. Give a ceiling or range, say which parts are fixed, and which could move to a later phase. Applicable taxes should be confirmed separately with each bidder, and ask them to separate build, content work, migration and ongoing care, since these are different kinds of cost.
For timing, give your fixed dates and the reason for them, then ask each bidder to state the assumptions behind their schedule, including how fast you can supply content and give feedback.
Comparing the Quotes You Receive
Ask every bidder to respond against the same headings. Where a quote differs sharply from the others, check which assumption caused it: fewer templates, no migration, no content support or a different integration approach. Questions from a bidder are a good sign, because they show someone is testing your assumptions before committing to them. Update your document with the answers and send the same version to everyone so the comparison stays fair.
Conclusion
Before you contact anyone, write the audience, page types, workflows, content owners and exclusions on one page, and mark each uncertain item as an open question. That single page is enough to start a useful conversation and will expose most of the gaps early.
If you would like a second pair of eyes on a draft, you can share it with NextGen Fusion through the contact page. There is no need to polish it first; unclear sections are a reasonable place to begin.
Free quote · reply within 24 hours
Want a fixed price for your project?
No account managers. Send your brief and get one fixed price and delivery window in writing within 24 hours.
Keep reading on Hiring a Developer
- Hiring a Web Development Team in India from GermanyHire web developers in India from Germany: the time gap in winter and summer, GDPR transfers and SCCs, who owns the code and how invoices should work.
- How to hire a web developer without getting burned: questions to ask firstHow to hire a web developer without getting burned: what to prepare, which questions to ask, the warning signs, and what must be in writing before you pay.
- Hiring a Web Development Team in India from CanadaHiring web developers in India from Canada: the time difference by province, PIPEDA rules for customer data, written copyright transfer and how to invoice.

