A software product brief
Ten questions to answer before you ask anyone for a quote. It is a guide to thinking the product through, not a form: nothing on this page is sent or stored. Print it and write on it, or answer the questions in an email.
-
The problem
What goes wrong today, and for whom. One or two sentences is enough.
-
The user
Who will use it day to day, and what they are doing when they reach for it.
-
Who pays
The person or business that pays for it, if that is not the user.
-
How you will charge
A subscription, a one-off price, a charge per use, or not decided yet.
-
Platforms
Web, iPhone, Android, or all of them, and which comes first.
-
What exists
Designs, code, a prototype, a spreadsheet that does part of the job, or nothing yet.
-
Version one
What the first version must do, and what it can leave for later.
-
Other tools
What it has to join: payments, email, an accounts package, a calendar, or a system of your own.
-
Personal data
What it holds about people, and why it needs each item.
-
How you will know it works
What a user does with it that tells you it is doing its job.
Short answers are fine, and “not sure yet” is a good answer. We go through each of them with you before we write the specification.
More on how a product is built and published is on Build to sell. You can also use the enquiry form.