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.

  1. The problem

    What goes wrong today, and for whom. One or two sentences is enough.

  2. The user

    Who will use it day to day, and what they are doing when they reach for it.

  3. Who pays

    The person or business that pays for it, if that is not the user.

  4. How you will charge

    A subscription, a one-off price, a charge per use, or not decided yet.

  5. Platforms

    Web, iPhone, Android, or all of them, and which comes first.

  6. What exists

    Designs, code, a prototype, a spreadsheet that does part of the job, or nothing yet.

  7. Version one

    What the first version must do, and what it can leave for later.

  8. Other tools

    What it has to join: payments, email, an accounts package, a calendar, or a system of your own.

  9. Personal data

    What it holds about people, and why it needs each item.

  10. 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.

Email your brief

More on how a product is built and published is on Build to sell. You can also use the enquiry form.