How to write a project brief that gets you a useful answer
A brief is not a specification. It is the shortest document that lets someone understand the problem. What to include, what to leave out, and a template you can copy.
Most project briefs fail in one of two ways. Some are a single line, we need a new website, which leaves every important decision to guesswork. Others are thirty pages of features that describe a solution before anyone has agreed on the problem. Both lead to quotes you cannot compare and conversations that go in circles.
A useful brief sits in between. It explains the situation clearly enough that a capable team can ask good questions, suggest an approach and give you a realistic range.
Start with the problem, not the feature list
Describe what is not working today and why it matters. Who is affected, how often, and what it costs you in time, money or missed opportunities. A clear problem statement lets the people you hire propose something better than what you would have specified.
What to include
Brief essentials
- A short description of the business and who your customers are.
- The problem, in plain language, with a concrete example.
- Who will use the result: customers, staff, or both.
- What exists today: current site, tools, data and integrations.
- What success looks like in six months.
- Must-haves versus nice-to-haves, kept as separate lists.
- Constraints: deadline, budget range, technical or legal requirements.
- Who makes decisions and who provides content.
Be honest about budget
Many people leave budget out, hoping to avoid being overcharged. In practice it makes proposals harder to compare. The same goal can be met in very different ways at different prices, and a range lets a team tell you what is realistic within it, or tell you early that it is not.
What to leave out
- —Design preferences stated as requirements, unless they are brand rules.
- —Technology choices you have no strong reason for.
- —Detailed screen-by-screen specifications before the problem is agreed.
- —Every idea you have ever had. Put future ideas in a separate section.
A template you can copy
- 01About us: two or three sentences.
- 02The problem: what is going wrong, with one real example.
- 03The people: who uses this and what they need to do.
- 04Today: what we use now and what we must keep.
- 05Success: how we will know this worked.
- 06Scope: must-haves, then nice-to-haves.
- 07Constraints: timing, budget range, requirements.
- 08Contacts: who decides, who supplies content.
Finally, treat the brief as a starting point. The best sign of a good partner is the questions they ask back. If nobody challenges anything in it, they probably have not read it closely.
Written by Taskless Studio
