Skip to content
NOVA
← Resources

Templates and checklists

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

0 of 22 ticked

Questions

Do I need technical knowledge to fill it in?

No. Describe your business and your work in plain words. A good team turns that into a technical plan and asks you when something is unclear.

How long should a brief be?

One or two pages is enough. What matters is a real example of the work today and a short list of what must be in the first version.

Should I say my budget?

A range helps. It lets a team tell you what fits in it, and what to leave for later, instead of quoting for everything.

Can I send this brief to NOVA directly?

Yes. Use the brief form on this site, or tell Spark what you wrote and it will send it to the team. A person from NOVA reads every brief and answers.