Most businesses write a better website brief than they realize. The trouble starts once the quotes are in.
This summer an industrial B2B manufacturer booked a meeting with us. We called to prepare, met online for an hour that afternoon, and sent our quote the same evening. The next day, with our quote already in their inbox, the company sent the written brief it was giving every candidate. It was one of the clearest we have seen: platform requirements, performance targets, structured data, AI search goals, and the process it expected, all on one page.
Five weeks later, the company chose another agency. The reason given was sector experience, which the brief had asked for as an attachment, and design awards, which it had not mentioned. The technical requirements that made up most of the brief were not part of it.
That gap is common, and it is expensive. This post looks at what the brief asked for, what the decision rested on, and how to score a web design quote against your own requirements so the two stop drifting apart. It is for owners and managers of established businesses comparing web agencies now. If you are still planning, start with how to plan a website project before design begins and come back when the quotes arrive.
What a good website brief looks like
The brief ran to five sections. Here is the shape of it, with identifying details removed.
The company wanted a premium B2B website design built around a full product catalog. Every product page would carry its technical specifications as readable HTML, not downloadable PDFs. It asked for a custom interface rather than a heavy template, a mobile-first build with green Core Web Vitals scores, and a content management system the team could use to add products without slowing the site down. English first, more languages later.
The SEO section was the most specific. Product, Organization, and FAQ schema on every product page, so AI tools could read certifications and approval codes directly. Text that AI assistants could quote as a direct answer to buyer questions. Clean URLs, a proper heading hierarchy, alt text, and optimized metadata across the catalog.
Then it set out strict milestones: wireframes, design, development, SEO setup, quality assurance, launch. And it told candidates what to include with their quote: a relevant portfolio, a proposed technology stack, a phase-by-phase timeline, and pricing broken down by phase or deliverable.
Two details give the brief extra weight. The manager who wrote it had found our agency through ChatGPT and Claude, which is the AI search visibility the brief was asking for, proven by their own search. And the company had a hard deadline: an autumn trade show where the new site needed to be live.
If your brief covers that much ground, you have done the hard part. Every candidate knows what "good" means for this project.
What we answered, and what we could not
We replied to every line of the brief in writing within the hour. Most lines had a direct answer: WordPress with a lightweight builder and custom fields for uniform product templates, a named SEO plugin for the schema, a full stack list, and a fixed timeline of six and a half weeks at the outside.
Two requests we could not meet as written, and we said so. We had no industrial catalog in our portfolio, only prior familiarity with the sector, plus client testimonials and public reviews that show how we work. What we could offer was the same thing we bring to every project: a strategy before a design. Every site we build starts with who it is for, what those people should do when they arrive, and what stands in the way. For an industrial manufacturer, that means product pages built around how buyers search, not around how the industry usually presents itself.
The second request was pricing by phase, and we do not work that way. We quote the whole build as one fixed package, because SEO is not a phase we add at the end. It shapes the structure, the templates, and the copy from the first wireframe. Split it out as a line item and you get numbers that look comparable across agencies and are not.
We also raised something the brief did not ask for. The company expects to pass, within two years, the size threshold at which the EU accessibility rules stop exempting small businesses. We advised a site that is accessible from the start, or at least built so accessibility can be added without a rebuild, and quoted for that foundation. A brief can only cover what its author already knows to ask for. A good quote fills in the rest. If your company is growing, read the EU web rules before you write your brief, so you know what to ask for.
One more thing came up in the meeting. The competitor site the client pointed to was clean and conventional: short sections, a readable layout, the information a buyer needs close to hand. The unfinished site they already had leaned the other way, with a template-based build, animated effects, an auto-scrolling carousel, and many images without alt text on a homepage of fewer than 400 words. None of that is unusual for a first draft. It does work against page speed, which the brief asked for, and against the accessibility we had recommended. In a sector where buyers arrive looking for specifications, approvals, and a way to get in touch, restraint tends to convert better. We suggested the site should look as clean as the best of their competitors and load faster than any of them.
Saying no to two requests, and questioning the direction of an existing draft, is a risk in any pitch. It is still the right way to answer a brief. A quote that claims to tick every box is the one to trust least.
What the decision was based on
After a month of collecting quotes, the company chose an agency with, in their words, a lot of industrial B2B experience and award-winning design and development.
Both are reasonable things to value, and for some projects they should carry real weight. The first was in the brief, as one of four items to attach to the quote. We had said plainly that we had no industrial portfolio to show. The second, awards, appears nowhere in the brief.
Now read the requirements again. Green Core Web Vitals is a measurable output. Product schema on every page is checkable. HTML specifications instead of PDFs is a build decision. Citation-ready structure is a content and markup discipline. Strict milestones are a working method. Each of these can be verified in a quote, on a live site, or in a reference call. None of them is predicted by a design award or by the number of factories in a portfolio.
This is not an argument that the other agency was the wrong choice. It may be an excellent one, and an agency that has built industrial catalogs before brings real advantages, covered below. The point is narrower. The company wrote a brief about performance, structure, and search visibility, and decided on portfolio and reputation. Both sets of criteria are legitimate. They were not the same set.
Why briefs and decisions drift apart
In our experience this happens for five reasons, usually in combination.
- The brief is written by one person and the decision is made by several. Whoever writes the requirements understands them. The people who sign off on the spend often do not read them closely, and fall back on signals they recognize: awards, logos, who else the agency has worked for.
- Portfolio stands in for risk. "They have done this before" feels safer than "they explained how they would do it." Sector experience does reduce some risk: the agency knows the buyer's vocabulary and the shape of a catalog. It says nothing about whether their sites load fast, validate cleanly, or get cited by AI tools. Ask for those things directly.
- Line-item pricing invites comparison of the wrong numbers. One agency's "design" line includes wireframes, accessibility testing, and two revision rounds; another's does not. One builds search structure into every template; another adds an SEO plugin at the end and calls it a phase. The totals are comparable. The lines are not.
- The brief goes out after the first quotes come in. A quote built from a call and a meeting answers the questions that came up in that hour. A quote built from a written checklist answers the checklist. Side by side, the second looks more complete, whether or not the work behind it is, and the agency that quoted first is measured against a document it had not seen.
- The brief has no scoring rule. A list of requirements without weights or pass/fail marks turns into a general impression once the proposals pile up. Impressions favor whoever presents best, not whoever answers best.
How to score a web design quote against your brief
The fix is mechanical, and it takes about an hour.
Step 1: Turn each requirement into a question with a verifiable answer
"Green Core Web Vitals" becomes: show me three live sites you built and their current PageSpeed Insights scores on mobile. "Schema on every product page" becomes: which tool produces it, and can I validate a page you built with Google's Rich Results Test? "Citation-ready content" becomes: show me a page of yours that an AI assistant currently quotes, or explain how you structure one.
If a requirement cannot be turned into a question like this, it is a preference, not a requirement. Keep it, but do not let it outweigh the ones you can check.
Step 2: Decide the weights before the quotes arrive
Give every requirement a weight that reflects its business consequence. For a B2B website design built around a catalog, page speed and product page structure outweigh homepage visuals, because that is where buyers arrive from search. Write the weights down. If sector experience matters to you, add it as a weighted line so it competes openly with the rest.
Step 3: Mark every quote against every line
Three marks are enough: meets, partly meets, does not address. A plain "we do not do this" scores higher than silence. A known gap can be planned around. Silence gives you nothing to plan with.
Step 4: Check ownership and continuity separately
This sits outside the brief because it is a condition, not a criterion. Before the project starts, confirm that the domain is registered in your company's name, that you will hold administrator access to the site and hosting, and that nothing from a previous developer can lock you out. The company in this story had a half-finished draft with a former developer and a reasonable worry about losing access to it, so we archived the draft the same day. If a previous developer holds any part of your site, read who owns your website before you sign anything new.
Step 5: Compare totals, then the gaps
Look at total cost against total scored value. Then look at each quote's "does not address" marks and ask whether you can live with them. Only after that should presentation, awards, and rapport tip the balance between two close candidates. They are useful tie-breakers. They are not the criteria.
What not to do
- Do not spend a month collecting quotes when the deadline is fixed. Set a two-week window, tell candidates, and decide inside it. Every week spent comparing is a week taken from the build.
- Do not ask for quotes before the brief is written. Send the same document to every candidate before any of them prices the work. If a quote arrives first, send the brief and ask for a revised quote against it.
- Do not ask for phase pricing and then compare phases. Ask for a total, a timeline, and what happens when scope changes. That last answer tells you more about how the project will go than any line item.
- Do not let a portfolio stand in for a reference. A screenshot shows launch day. A reference call with a client who has been live for a year tells you whether the site still loads fast, whether the agency still answers, and what maintenance turned out to cost.
- Do not treat your own brief as optional. If you wrote it, hold every quote to it. If the criteria have changed, rewrite the brief and tell the candidates. Quiet criteria are unfair to the agencies and expensive for you.
When sector experience should win
Sometimes industry familiarity deserves the top weight. If your product data lives in a system that must feed the website automatically, an agency that has integrated with it before saves weeks. If your buyers expect a specific convention, such as a technical data sheet layout or a distributor locator, an agency that has built it will get it right faster. If regulation shapes what you can say on the page, prior experience with that regulator is worth paying for.
Even then, put it in the brief as a weighted line. Every candidate then knows what they are being measured on, and the ones without it can decide early whether to compete. That is fairer to the agencies and faster for you.
The decision in one sentence
Write the website brief you mean, weight it before the quotes arrive, score every quote against it in writing, and let reputation and portfolio break ties rather than make the decision.
If you are still shortlisting, read what to look for when hiring a web designer first. If you have a brief in hand and want a second opinion on how the quotes stack up, our website design and development process starts with that review. We will tell you plainly where our own quote falls short.
Frequently asked questions
What should a website brief include?
The business goal, who the site needs to reach, platform and performance requirements, accessibility obligations now and as the company grows, the content you already have, integrations, the languages you need now and later, the deadline, and how you will judge the quotes. The last item is the one most briefs leave out.
How do I compare web design quotes fairly?
Compare totals against your scored requirements, not phase lines against phase lines. Different agencies put different work under the same heading, so line items look comparable and are not. Ask each candidate what happens when scope changes, and treat a plain "we do not do this" as a better answer than silence.
Does my web agency need experience in my industry?
It helps most when your project depends on a specific integration, a sector convention, or a regulator. It says little about page speed, structured data, or AI search visibility, which you should verify directly. If it matters to you, add it to the brief as a weighted criterion.
What makes a B2B website design work for AI search?
Product information as readable HTML rather than PDF downloads, Product and FAQ schema on each page, headings that match how buyers phrase their questions, and answers written so they can be quoted in one or two sentences. Our guide to AI search optimization covers the structure in detail.
