How to write a website or software brief (with a template)
A clear brief is the cheapest way to improve a technology project. It takes an hour or two to write, it gets you quotes you can compare, and it prevents the misunderstandings that cause delays later.
- Describe the problem and the outcome you want, in your own words.
- Split requirements into must-haves and nice-to-haves before asking for quotes.
- Name one decision-maker and give a budget range.
What a brief is for
A brief tells a provider what problem you want solved, for whom, and within what limits. It does not need technical language. In fact, describing the problem in your own words is more useful than naming a technology you have heard about.
The one-page template
Copy these headings and write two or three lines under each.
| Section | What to write |
|---|---|
| About the business | What you do, who your customers are, how big the team is. |
| The problem | What is slow, missing or going wrong today. Give a real example. |
| The goal | What should be different after the project, in a way you can measure. |
| Users | Who will use it: customers, staff, managers. What each needs to do. |
| Must-haves | The few things without which the project fails. |
| Nice-to-haves | Useful extras that can wait for a later phase. |
| Existing tools | Software, spreadsheets and accounts already in use that it must work with. |
| Budget and timeline | A range is fine. Mention any fixed date such as a launch or admission season. |
| Decision-maker | Who approves the work, and who answers daily questions. |
Describe outcomes, not screens
Compare these two requirements:
- Vague: "We need a dashboard."
- Useful: "Each morning the manager needs to see yesterday's enquiries, how many were contacted, and which are still waiting, without opening three files."
The second version tells the team what success looks like and lets them suggest the simplest way to reach it.
Separate must-haves from nice-to-haves
Every extra feature adds cost, time and things that can break. Launching with the must-haves and adding the rest after real use is nearly always faster and cheaper overall. If everything is marked essential, ask which three items you would keep if you could only have three.
Common mistakes
- Copying a competitor's feature list without knowing which features their customers actually use.
- Leaving out the people who will use it. Ask front-desk and operations staff what slows them down.
- No budget range. Providers then guess, and quotes become impossible to compare.
- Too many decision-makers. Name one person with the final say.
What to expect back
A good provider will respond with questions before a price. They may challenge parts of the brief or suggest a smaller first phase. That is a healthy sign: it means they are thinking about your outcome and not only about the size of the invoice.
Questions people ask
Do I need a brief if I only have a rough idea?
No. A short conversation is enough to begin, and a good provider will help you shape the idea. Writing even half a page first simply makes that conversation faster and the quote more accurate.
Should I share my budget with the provider?
Sharing a range helps. It lets the provider propose the best solution within your limits and tell you early if the goal and budget do not match. Without it, you may receive proposals that are far too small or far too large.
Keep reading
Want help applying this to your business?
Tell us your situation and we will give you a straight answer on what to do first.