17 November 2026
How to Write a Website Brief That Gets Accurate Quotes

You asked three agencies for a quote and got three prices that look nothing alike. One is a few thousand ringgit, one is several times that, and one is “from RM X, subject to scope.” They aren’t being difficult. They were each answering a different question, because yours wasn’t specific enough to have one answer.
A written brief fixes that. It doesn’t need to be long or technical. It needs to say what you want, why, and what limits apply, so every agency prices the same project. Here’s how to write one.
Why quotes differ so much
Most of the gap comes from guessing:
- Different assumptions about scope: one agency assumes 5 pages and another assumes 25.
- Different assumptions about content: who writes the text, takes the photos or translates it?
- Different assumptions about features: does “online booking” mean a simple form or a full system with payments?
- Different assumptions about what comes after launch: training, maintenance, hosting, changes.
- Different levels of risk: an agency that doesn’t understand a requirement will either pad the price or leave it out and charge later.
A brief removes most of these. Our post on what a website costs in Malaysia explains what drives price. This post is about asking in a way that makes the answers comparable.
What a good brief does
A good brief lets two agencies read the same document and come back with prices you can compare line by line. It also helps you: writing it forces decisions you’d otherwise face halfway through the project, which is when changes cost the most.
It doesn’t have to be perfect. If you don’t know something, say so, and write down what you’re unsure about. Honest gaps are far better than confident guesses.
The nine parts of a useful brief
1. About your business
Two or three sentences: what you do, who you serve, where you operate, and how long you’ve been going. Add your current website address, if you have one.
2. The goal of the project
What should the website achieve, in terms you can measure? “More enquiries” is a start. “Increase enquiry form submissions and WhatsApp messages from the website” is better. If you know your current numbers, include them. (Our post on how many leads your website should generate helps you work them out.)
3. Who it’s for
Describe your main visitors: who they are, what they’re trying to do, and what might stop them. Say which languages they read.
4. What you have now
If this is a redesign, say what works and what doesn’t, which pages bring enquiries, and what must be kept, such as addresses, rankings or key content. If rankings matter, say so up front. Changing a site without a redirect plan can lose them (see our article on revamping an old website).
5. Scope: pages and features
List the pages you expect, and the features you need. Be specific:
- Pages: home, about, services (how many?), portfolio, blog, contact, anything else.
- Features: enquiry forms, WhatsApp button, online booking, payments, member login, search, multiple languages, a blog, a store.
- Integrations: payment gateways, CRM, email tools, booking software, maps.
Separate must-haves from nice-to-haves. That one split often accounts for most of the price difference between quotes.
6. Content: who provides what
For each of these, say whether you’ll provide it, or you want the agency to:
- Page text and headings
- Photography and video
- Logo and brand files
- Translations
- Product or service data
Late or missing content is the most common cause of delay and extra cost (see our timeline for a redesign).
7. Design direction and references
Share two or three websites you like, with a note on what you like about each, and what you dislike. Say whether you have brand guidelines. “Like this, but…” works better than “make it modern.” Our article on turning a reference site into something original explains how agencies use these.
8. Technical and practical requirements
- Platform preferences, if any, or “open to recommendations” (our comparison of WordPress and Next.js can help).
- Who will edit the site after launch, and how technical they are.
- Hosting and domain: do you already have them, and who holds the logins?
- Tracking and SEO needs: analytics, ad tracking, search visibility.
- Accessibility, security or compliance requirements that apply to you.
- Payment methods your customers expect, such as FPX or e-wallets, if you sell online.
9. Timeline, budget and decision process
- Target launch date, and whether it’s flexible. Say why the date matters, such as a campaign or event.
- Budget range. This surprises people, but giving a range helps. It lets the agency propose what fits instead of guessing, and shows who is realistic. If you’re nervous about naming a figure, give a range and say it’s flexible for the right scope.
- Who decides, how many people will give feedback, and how quickly you can respond.
- How you’ll judge proposals, and when you’ll decide.
What to ask each agency to include in the quote
Add a short section to the brief that tells agencies what you want back. For example:
- A breakdown of costs by phase or deliverable
- What’s included and what isn’t
- Number of design rounds included
- Timeline with milestones, and what they need from you and when
- Who will work on the project
- Ongoing costs: hosting, maintenance, licences
- Ownership: who owns the code, design files, domain and accounts
- What happens after launch: support, training, fixes
Quotes that follow your structure are easy to compare. Quotes that ignore it tell you something too. (Our agency buyer’s checklist covers what else to look for.)
A fill-in template
Copy this into a document and complete it. Skip what doesn’t apply, and write “not sure” where that’s true.
| Section | Your answer |
|---|---|
| Business name and what you do | |
| Current website (if any) | |
| Main goal (with a number if possible) | |
| Target visitors and languages | |
| What works and doesn’t on the current site | |
| Must keep (content, URLs, rankings) | |
| Pages needed | |
| Features needed (must-have) | |
| Features wanted (nice-to-have) | |
| Integrations and payment methods | |
| Content you’ll provide / want help with | |
| Two or three reference sites, with notes | |
| Platform preference / who edits the site | |
| Domain, hosting and access | |
| Target launch date, and why | |
| Budget range | |
| Decision-maker and feedback process | |
| What to include in the quote |
Common mistakes
- Writing a brief that describes only the look, with nothing about goals or features
- Leaving content out, and then being surprised by a writing and photography charge
- Treating every feature as a must-have
- Hiding the budget, then comparing quotes that were never aimed at the same size of project
- Sending a different brief to each agency, which makes the quotes impossible to compare
- Not saying who decides, so feedback arrives from five people at once
- Asking for a quote with no brief at all
What to do after you send it
- Offer a short call, so agencies can ask questions. Good agencies will ask them.
- Give every agency the same answers to any questions, so nobody has an advantage.
- Set a deadline for quotes, and say when you’ll decide.
- Compare like with like. Line up the quotes against your sections. Where an agency’s scope is narrower or wider than the brief, ask why.
- Look at the questions they asked, as much as the prices. An agency that asked sharp questions about your goals understood your project.
- Ask for a demo or a worked example, if available. Some agencies, including us, offer a demo for eligible clients (see our article on why we do this), and it can show you how they think before you commit.
If you can’t write a full brief
A half-finished brief is still better than none. If you’re not sure about goals, features or budget, say so, and ask the agency to help define them. Some will run a short discovery session. Just be clear that you’re comparing like with like, and expect to pay for that time if it’s substantial.
The honest summary
A website quote is only as precise as the question it answers. A brief that states your goal, scope, content, constraints, budget and timeline gets you quotes you can actually compare, fewer surprises during the project, and a clearer sense of which agency understood what you need.
Not sure how to describe your website project, or want help turning rough ideas into a brief you can send to agencies? Tell us what you’re planning and we’ll help you shape it. [See how we approach web development projects →]