Web & mobile · Project brief
What to prepare before you hire a web agency: a brief that gets accurate estimates
Send three agencies the line “we need a new website” and you will get three estimates that are miles apart — and all three can be honest. The gap comes from what the brief leaves out. Here is what to write down first, so the numbers that come back describe the same project.

Why the estimates don’t match
An agency that gets a one-line request is pricing a guess. One team assumes ten page templates and that you load the content yourself. Another assumes forty pages of new copy, a product catalog, a CRM integration and a migration of the old blog. Both quotes are reasonable for the project each of them imagined.
Every unknown in a brief gets handled in one of two ways: padded or ignored. Padding makes you overpay. Ignoring it turns into change requests in month three. A good brief removes most of the unknowns before anyone writes a number.
It doesn’t need to be long. Three to five pages is enough, and it should describe the problem and the constraints, not the solution. Leave the sitemap and the tech stack to the people you are hiring, unless you have a real reason to fix them in advance.
Goals and audiences
1. Name the job of the site in one sentence. “A modern site that reflects our brand” is a wish, not a goal. “Get 40 qualified quote requests a month from facility managers” is a goal: it tells the agency what to design for and tells you later whether it worked.
2. Rank the goals. Most sites have a primary goal and two or three secondary ones: hiring, investor relations, dealer support. Say which one wins when they conflict, because they will — on the home page, in the navigation, in the budget.
3. Share the baseline. Monthly visitors, conversion rate, where leads or orders come from today, what the current site does badly. Give read-only access to analytics. An agency that can see the numbers estimates the work instead of the worst case.
4. Describe two to four audiences by the task they come to do. For an industrial pump maker, that might be a procurement manager comparing specs and lead times, an engineer who needs CAD files, and a distributor looking for a price list behind a login. For each, note what they must find on the first visit and what device they use. An engineer on a job site is on a phone.
Content and integrations
These two items move the estimate more than design does, and they are the ones briefs most often skip.
Content inventory. Export the current sitemap into a spreadsheet: URL, page type, monthly traffic, and a decision for each page — keep, rewrite, merge or delete. Then add what is new. The agency needs to know how many page templates you need, how many pages fill them, and who writes and photographs everything. For a store, add the number of SKUs, variants per product, and where product data lives today. “About 600 SKUs in a spreadsheet, photos for half of them” is a very different project from “1,200 SKUs synced from the ERP with full photo sets.”
Content is where schedules usually slip. If your team will write the copy, say how many hours a week someone actually has for it.
Integrations. List every system the site has to talk to: CRM, ERP or inventory, payments, shipping, email platform, booking, chat, analytics. For each, write down:
- what data moves and in which direction (“new leads to HubSpot,” “stock levels from the warehouse every 15 minutes”);
- who owns the account and can give access;
- whether there is an API and where its documentation is;
- what happens today when the sync fails.
“Integrate with our ERP” can mean two days or two months. One line per data flow is what separates the two.
Budget, timeline and decision makers
Give a budget range. Many companies hold it back so as not to anchor the price. In practice, each agency then guesses your range, and you get either a stripped-down proposal or one you can’t afford. A range like “$40–60k for the build, up to $2k a month after launch” lets every agency propose the best version that fits. Split one-time costs from ongoing ones: hosting, licenses, support, content updates.
Give a date and the reason for it. “Live before the trade show on March 10” is a constraint the agency can plan around. “ASAP” is not. If the date is soft, say so.
Name the people. Write down who approves design, who signs off on copy, who holds the budget, and who can stop the project late. The last one matters most: the IT lead who first hears about the project a week before launch, or the founder who sees the design for the first time in week eight. Bring them in at the start. Also name one day-to-day contact with real time for the project, and say how many review rounds you expect.
Explain how you will choose. Tell agencies when you will decide, on what criteria, and whether you want a fixed price or a time-and-materials estimate with a range. You will get proposals you can compare line by line.
What to do this week
- Write the site’s job in one sentence, with one number you will track.
- List two to four audiences and the top task of each.
- Export the sitemap to a spreadsheet and mark every page keep, rewrite, merge or delete.
- List every integration with its owner, data flow and API documentation.
- Agree on a budget range and a launch date with the reason behind it.
- Name the approver, the budget holder and the day-to-day contact.
Boson Group designs and builds websites, online stores and mobile apps. If you want a second pair of eyes on your brief before it goes out to agencies, write to team@boson.group.




