# A project brief template that gets you better quotes

Most software quotes are vague because the request was vague. This template walks you through what a development team needs to know: what your business does, how the work happens today and where it breaks, who will use the system, what must be in the first version and what can wait, which data and systems it has to connect to, and your dates and budget. It takes about thirty minutes. You don't need technical words; plain answers are better. Send the same brief to every team you talk to, so their answers can be compared fairly.

## How to use it

1. Answer each section in your own words. Short sentences are fine; examples are better than adjectives.
2. Ask the people who do the work every day to read the "problem today" section and correct it.
3. Mark each scope item as "first version", "later" or "not needed". This decides cost more than anything else.
4. Send the same brief to every team you are considering, and compare their questions as well as their prices.

## Your business

- [ ] What does your business do, and who are your customers?
- [ ] How many people work in the team that would use the system?
- [ ] Where do you operate, and in which languages?
  - Tip: Say if you need Arabic (right to left), English, German or more than one.

## The problem today

- [ ] Describe how the work happens today, step by step.
  - Tip: Take one real example, such as one order or one request, from start to finish.
- [ ] Where does it break or slow down?
  - Tip: Lost messages, typing the same thing twice, waiting for one person, mistakes in totals.
- [ ] Which tools do you use now?
  - Tip: Excel or Google Sheets, WhatsApp, paper, email, or software you already pay for.

## What success looks like

- [ ] The one result that would make this project worth it.
- [ ] How you will know it worked, in a month and in a year.
- [ ] What must not change for your customers or staff.

## Who will use it

- [ ] List each kind of user: owner, managers, staff, customers, suppliers.
- [ ] Roughly how many people in each group?
- [ ] Which devices will they use: phone, computer, tablet?

## Scope

- [ ] Must have in the first version.
  - Tip: Keep this list short: what your team would use every day from the first week.
- [ ] Can wait for a later version.
- [ ] Not needed, so nobody quotes for it.

## Data and connections

- [ ] Which existing data has to move into the new system, and where is it now?
- [ ] Which systems must it talk to?
  - Tip: Accounting, e-invoicing, payments, WhatsApp, email, a website or an app you already have.
- [ ] Any rules on where data is stored or who may see it.

## Practicalities

- [ ] When do you need it, and why that date?
- [ ] Your budget range, or how you will decide.
  - Tip: A range helps a team suggest the right first version instead of guessing.
- [ ] Who decides, and who will answer the team's questions?
- [ ] How you like to work: weekly call, WhatsApp, email.

---

From NOVA Solutions · novasolutions.bassemhazem.com
https://www.nova-solutions.co/en/resources/project-brief-template
