We use cookies to improve your experience. By continuing to use this site, you agree to our Privacy Policy.
Want better website quotes? Write a better brief first.
Georgiana Nutas
-1.png&w=3840&q=75)
Written by
Georgiana Nutas
Building modern web applications at BluDeskSoft. We write about what we learn along the way.
We'd love to chat about your project. First consultation is always free - no strings attached.
AI builders are fast and cheap, but their real limits usually appear after launch.
Most businesses start a web project the same way: they write up a list of pages they think they need, add a few reference websites, maybe mention a technology preference, and send it to three agencies. Then the quotes come back, and none of them match. One is €3,000. Another is €18,000. A third asks ten follow-up questions before pricing anything.
If you want to know how to write a website brief that produces useful, comparable quotes, the answer isn't a longer document. It's a clearer one. Agencies don't struggle with long briefs. They struggle with briefs that describe outputs without explaining the underlying problem.
This guide walks through what a good brief actually needs, why most briefs fail, and a simple template you can use before reaching out to any agency.
Here's what a typical brief looks like:
"We need a new website with a homepage, about page, services page, blog, and contact form. Modern design, mobile-friendly."
That's a starting point. It's not a brief.
The problem is that "we need a new website" can mean at least a dozen different things:
Each of those situations needs a different response. If the brief doesn't say which one applies, the agency has to guess. Some will ask questions first. Others will quote fast and quote the wrong project.
A vague brief means you're not comparing agencies. You're comparing assumptions.
The single most predictable indicator of a successful web project isn't the technology chosen or the agency's portfolio. It's the quality of the brief. Misaligned expectations at the start are the origin of most scope creep, budget overruns, and projects that require a second redesign six months later.
Before listing anything, explain what's actually happening in the business.
Are you launching a new product? Repositioning the company? Trying to generate more qualified leads? Preparing for fundraising? Replacing a site that's become a technical liability? Moving upmarket, and the current site doesn't reflect that?
This matters because the right approach differs depending on the answer. A startup landing page built to validate an idea is a different project from a corporate site built to close enterprise deals. A SaaS marketing site is a different project from a local service business website. Knowing which problem you're solving shapes every decision that follows: stack, structure, content, scope.
At BluDeskSoft, the first thing we ask about is the business outcome, not the technology. The stack comes after the problem is clear.
A good brief answers one question clearly:
What needs to be different if this project works?
"A modern website" is not an answer. "Modern" doesn't convert visitors. It doesn't close deals. It doesn't explain products. It's an aesthetic preference, not a business goal.
Better goals:
The goal doesn't need to be perfect. But it needs to be specific enough to guide real decisions. A goal of "lead generation" leads to a different conversation than "credibility for enterprise prospects", even if the deliverable looks superficially similar.
This is the section most briefs skip, and it's often the most useful.
Don't just say: "Our current website is outdated."
Go deeper:
This kind of honesty saves everyone time. If you've already redesigned the homepage and leads didn't improve, the problem probably isn't visual design. It might be positioning, messaging, search intent, or conversion flow. A good agency won't treat all those situations the same way.
Your website is not for everyone. Even if your business has multiple customer types, the brief should define the primary audience, the people you most need to reach.
Include:
A website targeting startup founders should probably be direct, fast, and outcome-focused. A website for enterprise procurement teams needs more proof, risk reduction, and process detail. The same design won't work equally well for both, and an agency that doesn't know which audience you're building for will make the wrong call at every step.
Most pages fail not because they look bad but because they don't guide the visitor toward a clear next action.
Your brief should specify the primary action you want visitors to take:
This shapes how the whole project gets built. If the main goal is demo bookings, the CTA strategy matters. If the goal is inbound inquiries, the contact flow matters. If the goal is product adoption, onboarding, and application UX matter. A page exists to help someone take a step; the brief should say which step.
One of the most useful things you can put in a brief is a short history of what's already been attempted:
This prevents repeating old mistakes. If you've already invested in SEO but traffic doesn't convert, the issue might be internal linking, service page clarity, or CTA flow, not more content. If a redesign didn't move leads, the issue might be positioning, not design.
Google's own documentation on helpful content emphasizes that visibility alone doesn't produce results; the content and page experience must give users a reason to act. Knowing what's already been tried tells the agency where the real gap is.
Technology preferences belong in the brief, but they shouldn't replace context.
Include:
The reason behind the preference matters. "We want WordPress" is useful. "We want WordPress because our marketing team needs to publish content independently and doesn't have a developer on call" is much more useful. It tells the agency whether WordPress is a firm requirement or a default assumption that might be reconsidered.
Sometimes WordPress is the right answer. Sometimes a custom Next.js build with a headless CMS makes more sense. Sometimes, a no-code tool is enough. The brief should give the agency enough context to make a recommendation, not just a specification to follow blindly.
Content is the most common reason web projects stall.
Clarify upfront:
A project can sit idle for weeks waiting on a homepage draft. If you expect the agency to handle content creation or restructuring, say so in the brief, and budget for it. If you're providing everything internally, set a realistic deadline for when it will be ready.
Also, be honest about content quality. Existing copy may not be usable if the positioning has shifted since it was written.
Many businesses hide their budget because they're worried agencies will price up to the maximum. The opposite tends to happen: a vague budget constraint yields a vague scope, which results in a quote that doesn't match what the project actually needs.
A realistic budget range helps the agency recommend the right approach. The work will look different at:
Timeline matters equally. If you need to launch in four weeks, the scope has to reflect that. If you have three months, there's room for discovery, testing, and iteration. A good agency should help you make trade-offs, but they need honest constraints to work from.
Reference sites are useful when they come with context.
Don't just send five links and write: "We want something like this."
Instead, explain the specific thing you find useful:
This separates taste from strategy. Visual references are not a replacement for a clear goal. If the reference site is performing well because of its messaging and conversion flow, a new design that copies the aesthetics but not the thinking won't produce the same result.
Some things make a brief less useful:
Specific words mean different things to different people. The brief's job is to reduce interpretation, not add it.
Here's a structure that covers everything an agency needs to quote accurately:
1. Company overview — What you do, who you serve, where you are in the business.
2. Project context — Why this project is happening now.
3. Main goal — What needs to be different if the project works.
4. Current problems — What's not working with the existing website or process.
5. Audience — Who will use the site, what they care about, and how they decide.
6. Desired actions — What you want visitors to do.
7. Scope — Pages, features, or flows you think are needed (flagged as assumptions, not requirements).
8. Content — Who provides copy, images, case studies, and whether existing content can be reused.
9. Technical requirements — CMS, integrations, hosting, performance, multilingual, analytics.
10. Budget range and timeline — Honest constraints.
11. Success metrics — What should be measurably better 90 days after launch?
12. References — Sites you like, with a note on what specifically works about them.
The point isn't to eliminate questions. It's to improve the questions.
A strong agency will still ask things. They should. If an agency sends a quote without asking about business context, audience, constraints, or success criteria, that quote is fast, not accurate.
The brief opens the door. It tells the agency enough to engage seriously, ask the right follow-up questions, and recommend the right scope. Teams that invest 30 to 60 minutes in a thorough brief consistently get proposals that are specific, scoped, and grounded in real objectives. Teams that skip it tend to end up with surprise invoices, scope creep, and results that need fixing within a year.
The most useful sentence in any website brief isn't a list of pages or a technology preference.
It's this:
"We need our website to help the right people understand our offer faster, trust us sooner, and take the next step with more confidence."
That's the difference between ordering pages and commissioning a business tool.
Start with the outcome. Then define the audience, the problems, the constraints, the actions, and what success looks like. The quote will be more accurate. The scope will be clearer. And the final result will have a much better chance of solving the right problem.
At BluDeskSoft, we help founders and growing businesses turn unclear digital projects into fast, reliable web products. If you're preparing a brief and want to think through the scope before reaching out to agencies, drop us a message. We're happy to help you structure it.
BluDeskSoft.png&w=3840&q=75)
-3.png&w=3840&q=75)
-4.png&w=3840&q=75)