What to write in a software brief
Eight things to put in a brief so a developer can quote accurately and build what your business actually needs.

- Describe the problem and the daily routine, not the screens you imagine.
- List who will use the system and what each person needs to do.
- Split must-haves from nice-to-haves, and say how you will judge success.
A good brief does not need technical language. It needs enough detail for a developer to understand how your business runs today and what should be different afterwards. A clear brief gets you a more accurate quote and fewer surprises once work begins.
1. The problem in one paragraph
Start with what is going wrong and what it costs you. "We lose track of stock between the warehouse and the shop, and only find out at month-end" is more useful than "we need an inventory module".
2. How the work happens today
Walk through a normal day. Who takes the order, where is it written, who checks it, how does it reach accounts? Attach photos of registers, sample invoices and the spreadsheets you use. Messy real examples help more than tidy descriptions.
3. Who will use it
List each role, how many people hold it and what they need to do. A cashier, a store manager and an owner checking reports from home need very different screens.
4. Must have, nice to have, later
Split your wishes into three lists. Must-haves are what the system has to do on launch day. Nice-to-haves can follow if time allows. "Later" holds ideas the design should leave room for, so they do not force a rebuild.
5. What it must connect to
Name the systems that already hold your data: an online store, accounting software, a marketplace account, a spreadsheet that has to keep working. Say which way the data should flow.
6. The data you already have
Say roughly how many products, customers or students you have, and where those records live. Moving data is often a large part of the work, so it belongs in the quote.
7. Practical limits
- A date you are working towards, and why it matters
- The devices staff will use: phones, tablets or counter computers
- Internet and power conditions at each location
- A budget range, if you are comfortable sharing one
8. How you will know it worked
Pick two or three measures you can check before and after, such as the time it takes to close the day or the number of orders entered twice. They keep the project honest for you and for whoever builds it.

Related guides

When to move from spreadsheets to an ERP system
The signs that spreadsheets have outgrown the business, when to wait, and how to move without disruption.
Read the guide →
How to choose a POS system for a small shop
The questions to ask before you commit to any point-of-sale system, and how to test the answers with your own data.
Read the guide →
Shopify, WooCommerce or a custom store: how to decide
A plain comparison of the three main ways to build an online store, and the questions that decide between them.
Read the guide →