How to write a website brief (that gets you a good quote)
The quality of the brief shapes the quality of everything that follows — the quotes you get, how comparable they are, and how well the finished site fits. You don't need a twenty-page document. A clear one-pager that says what you want the site to *do* puts you ahead of most enquiries a developer sees. Here's how to write it.
Start with the goal, not the pages
The most useful thing you can tell a developer isn't "I need five pages" — it's "I need more enquiries from local customers" or "I need to sell online". Lead with what the website is for. The goal shapes everything: structure, design, functionality and priorities. A page count without a goal is guesswork.
What to include
- About your business — what you do, who for, and what makes you different.
- The goal — what a successful site would achieve in six months.
- Your audience — who you're trying to reach, and what they need.
- Rough structure — the main pages or sections you think you need.
- Features — anything beyond standard pages: booking, payments, logins, integrations.
- Examples — two or three sites you like (and why), and any you don't.
- Content — do you have copy and images, or will you need help?
- Timeline and budget — even a rough range helps enormously.
Keep it about outcomes, not instructions
Say what you want to achieve and let the developer propose how. "Customers can't find our opening times" is more useful than "make the header bigger" — it describes the problem, and a good developer will often solve it better than your first idea. Briefs that dictate solutions tend to get worse results than briefs that describe problems.
A simple structure to copy
One page is plenty: a short paragraph on your business; the goal; who it's for; a bullet list of pages; a bullet list of any special features; a couple of example sites; a note on content and timeline; and a budget range. That's a brief most developers would be glad to receive — and it'll get you quotes you can actually compare.
Common questions
What should a website brief include?
Your business and what makes it different, the goal for the site, your target audience, a rough page structure, any special features, a few example sites you like, whether you have content ready, and a timeline and budget range. Even a single page covering these puts you ahead.
Do I need to share my budget with a web developer?
It helps a lot. A budget range lets a developer propose the right solution rather than guess, and quickly rules out poor fits. A trustworthy one won't simply spend to your number — they'll recommend the right scope, and tell you if you need less than you think.
How long should a website brief be?
As short as it can be while still being clear — one page is often ideal. The goal is clarity, not length: what the site is for, who it's for, what it needs to include, and your rough timeline and budget. A focused one-pager beats a rambling document.
What if I don't know what I need?
That's normal, and fine. Describe the problem you're trying to solve rather than the solution, and a good developer will help shape the rest. You don't need the answers — you need to explain the goal clearly enough for someone to propose them.
Let's talk
Let's talk about your project.
Whether you've got a clear brief or just an idea, tell us what you have in mind and we'll give you an honest recommendation — even if that's a smaller project than you expected.