How to Write a Website Development Brief That Gets Accurate Proposals

Digital Agency, Tip and Tricks, Web Design, Web Development
19 November 2026

Writing a website brief is difficult when you know something needs to change but haven’t worked out what the project should involve. Your team may agree that the site is holding the business back, while having quite different ideas about how to fix it.

 

You don’t need to settle every question before approaching an agency. A good partner will help you investigate the problem and develop the brief, drawing on your knowledge of the business and their experience of delivering websites. At JTB, that work begins with understanding what prompted the project, so we can help you decide what deserves investment before recommending a solution.

 

Start with the problem you can see

 

Your initial brief can be a straightforward account of what is happening and why it matters. Perhaps the business has expanded, but customers still associate you with a small part of what you offer. Explaining that gives an agency much more to work with than asking for a more modern website.

 

You could put it like this:

 

Our business has grown, but the website still reflects our old service offering. Customers often call to ask whether we provide services that are already listed online, and we need help understanding why they’re being missed.

There is enough here to begin a useful conversation. The agency can explore whether the difficulty lies in how the services are described, how people find them or a wider gap in awareness. Any research or analytics you already have will help, but you shouldn’t have to commission an investigation just to prepare for the first meeting.

 

Use workshops to bring the business into the conversation

 

The person writing the brief rarely has the whole picture. Marketing may see the website’s performance, while sales and customer service hear the questions people ask after visiting it. Bringing those perspectives together can uncover a problem that no single team could explain on its own.

 

At JTB, we facilitate workshops to help clients make those connections. Taking the example above, a customer service colleague might explain that people use a different name for a service from the one the business uses internally. That would give us something specific to investigate, rather than assuming a new design would solve the problem.

 

Our UX and digital strategy work helps turn these discussions into priorities and identify where more evidence is needed. Workshops can reveal promising opportunities, but customer research or technical investigation may still be necessary before we recommend acting on them.

 

Develop a reverse brief together

 

We use what we learn to help write the brief and reflect our understanding back to you. This reverse brief explains the problem we believe needs solving, the outcomes we are working towards and the questions that remain open. Reviewing it together gives everyone a chance to challenge the direction before it becomes an agreed scope.

 

It also helps us distinguish a necessary requirement from an idea worth exploring. A requested feature might prove useful, or we might find that an existing system can do the job. Those decisions give the project a clearer purpose and can save effort that would otherwise go into building something unnecessarily.

 

For ANZSOG, our discovery work included interviews with internal stakeholders and alumni, alongside navigation testing and structural analysis. The resulting discovery and solution definition document informed ANZSOG’s redevelopment RFP. The organisation could then brief the build using findings from that work, showing how an agency can help develop the brief itself.

 

Include the practical details you already know

 

As the direction becomes clearer, the brief needs to explain the conditions the project must work within. Your available budget and the reason for your launch date are particularly useful, because they help an agency recommend an approach your organisation can realistically deliver.

 

You can also describe necessary functionality in everyday terms. If enquiries need to reach the right sales team automatically, explain how they are handled today and what you want to improve. JTB’s development team can investigate the systems and connections needed; you don’t have to specify the technical solution.

 

Existing documentation can help with that investigation, particularly where other suppliers or internal IT teams are involved. Any organisational requirements around accessibility, security or performance should also be shared early, with the agency helping to clarify what they mean for delivery.

 

The plan needs to account for your people as well. Knowing who approves the work and how much time your team can contribute helps avoid a schedule that depends on decisions or content you cannot realistically supply.

 

Make responsibilities clear before comparing prices

 

Content is a useful example of why the same brief can produce very different proposals. “Migrate the existing website” might mean transferring approved pages to one agency, while another allows for reviewing and rewriting them. Both have responded to the request, but they have priced different amounts of work.

 

You don’t need a finished content plan before approaching an agency, although responsibility for that work must become clear before you commit. If your team can approve copy but cannot write or upload it, the proposal needs to reflect that. Protecting existing search traffic also requires an agreed approach to redirects and migration checks.

 

This is where a detailed conversation can be more valuable than adding pages to the brief. It helps establish what the agency will deliver, what your team will take on and whether the budget covers the whole project.

 

Look for a proposal you can understand

 

A useful proposal explains how the recommended work responds to your brief and makes its assumptions visible. When comparing agencies, ask them to walk you through anything they expect you to supply, what remains unpriced and what could change the estimate. You should be able to follow the reasoning behind the figure.

 

That discussion should extend to how the work will be reviewed and tested. A proposal that includes accessibility evaluation, migration support and training represents a different commitment from one that assumes those activities happen elsewhere. Ongoing costs and support arrangements deserve the same clarity.

 

A fixed price can be appropriate when the work is sufficiently understood. If a significant integration remains uncertain, a separate discovery stage may be the more responsible first commitment. The agency should explain what that investigation will resolve and how it will inform the delivery budget, alongside how later scope changes would be agreed.

 

A good brief develops through this exchange. Your knowledge of the business gives the agency a starting point, and their investigation helps turn it into a project you can assess with confidence. If you’re still working out what your website needs to do, talk to JTB about developing your brief; we can help you get from the initial concern to an agreed direction.

Blog

You made it this far
Let's chat
Let's chat
1300 66 99 58
333 Drummond Street Carlton 3053 Melbourne, Australia

    Hi, my name is

    I'm from

    You can call me on

    and email me at

    I would like to chat about...

    (optional)
    (optional - 10mb max)

    Wow, so nice of you  
    We’ll be in touch shortly to learn more about your project.

    Projects

    4

    St Leonard's College

    Education

    Industry Beans

    Food & Drink Hospitality & Leisure

    Small Wonder

    Hospitality & Leisure Retail

    Sushi Sushi

    Food & Drink Technology