How to brief a development project
A clear brief saves weeks of back-and-forth, and it takes less than two pages to write.

Most proposals go wrong because the brief left too much open. A development team can only answer the question it was asked. If the brief is vague, the proposal will be vague too, and the real discussion gets pushed into the first month of work.
Use the sections below as a template. Short, honest answers beat polished ones. Where you do not know something, say so and mark it as an open question.
1. Start with the goal
Write one or two sentences about the problem you want to solve, not the software you want built. "Customers cannot reschedule deliveries without calling us" is more useful than "we need a portal".
- What is happening today that you want to change?
- Why now? A deadline, a launch or a growing backlog all shape the plan.
2. Describe the users
List who will use the product and what each group needs to get done. Two or three sentences per group is plenty.
- Who are they (customers, staff, partners)?
- What devices and browsers do they use?
- How comfortable are they with technology?
3. Define the scope
Split the work into what must be in the first release, what would be nice to have, and what is clearly out. The last list matters most, because it stops the project from quietly growing.
- Must have: the features without which the release is pointless.
- Should have: valuable, but the release can ship without them.
- Not now: ideas you want to park for later.
If you already have wireframes, screenshots of similar products or a rough process diagram, attach them. A single sketch can replace a page of text.
4. Share what already exists
Many projects are not built from a blank page. Tell the team about the systems the new work has to live alongside.
- Existing code, databases or hosting setup
- Third-party services such as payments, email or analytics
- Preferred languages or frameworks, and the reason for them
- Any design system or brand guidelines
5. List the constraints
Constraints are not problems; they are information. The sooner they are on the table, the easier it is to propose something realistic.
- Timeline: fixed dates and the reasons behind them.
- Budget: a range or a ceiling helps the team size the work. If you cannot share it, say how you would like to compare options.
- Compliance and security: data handling needs, and whether an NDA should be signed before details are shared. See security and NDA.
- Working hours: the overlap you need for meetings. Our notes on time zones explain how this is usually handled.
6. Say how you will measure success
Pick a few outcomes you can check after launch. They do not need to be complicated.
- Fewer support requests about a specific task
- A page that loads within a target you choose
- A process that used to take a day now taking an hour
7. Explain how decisions get made
Name the person who answers questions and approves work, and say how quickly they can respond. Slow decisions are one of the most common reasons projects slip. Also mention who owns the final result; our page on code ownership covers what to agree on.
8. Ask for what you want back
Tell the team what the proposal should contain: an approach, a rough timeline, the people involved, risks and open questions. If you are unsure which way of working suits you, read about engagement models and the choice between offshore and nearshore teams first.
A quick checklist
- Goal in two sentences
- Users and their main tasks
- Must-have, should-have and not-now lists
- Existing systems and preferences
- Timeline, budget range and constraints
- Success measures
- Decision-maker and response time
When your draft is ready, send it through the contact page. A brief does not have to be perfect. It only has to be clear enough to start a good conversation.