How to write a software project brief (with a template)
How do you write a software project brief?
Answer eight questions in plain language: what problem you are solving and who has it, who will use the software, the three to five things the first version must do, what happens today, which systems it must connect to, what constraints apply, your budget range and timeline, and what success looks like. One or two pages is enough. Leave the technical design to the people you hire.
A brief is not a specification
A brief describes the business problem; a specification describes the software. You do not need wireframes, a database design or a list of every screen to start. A good development company turns your brief into a written scope with a price and a date, and asks questions where the brief is thin. What it cannot do is guess what happens in your business today. Only you can write that part.
A clear brief also saves money. Every question the brief leaves open becomes an assumption in someone's estimate, and assumptions get priced with a margin for risk.
What should a software project brief include?
Eight things. Each has its own section below, and the template further down puts them in order.
- The problem, and who has it.
- The users and their roles.
- The three to five things the first version must do.
- What exists today: the spreadsheets, tools and workarounds in use.
- Integrations: the other systems it must talk to.
- Constraints: fixed dates, rules, devices, languages.
- A budget range and a timeline.
- What success looks like a few months after launch.
Start with the problem, not the solution
Describe what goes wrong today, who it happens to and what it costs them in time, money, errors or lost customers. 'We need an app' is a solution. 'Our receptionists take bookings by phone and copy them into a shared spreadsheet, so double bookings happen every week' is a problem, and a developer can work with it.
If you have numbers, use them: hours spent each week, orders lost, how many people do the work by hand. Your own numbers tell the developer what the software is worth to you, and that shapes what they should propose.
Name every kind of user and what each must do
List the kinds of people who will use the software and what each needs to do: customers, staff, managers, admins, partners. Roles matter more than headcount, because each role needs its own screens, rules and permissions. Say roughly how many of each there will be, and whether they work at a desk, on a phone or somewhere with a poor signal.
List the three to five things the first version must do
This is the hardest part of the brief and the most valuable. Write each item as something a user does from start to finish: 'A customer books and pays for a slot', 'A manager sees today's bookings and who has paid'. If your list has twenty items, it is a wish list. Keep the few without which the first version is useless, and put the rest under 'later'.
A small first version reaches real users sooner, and real users are the best guide to what to build next. Our article on what an MVP costs shows how far each extra feature moves the price.
Describe what happens today instead
Every piece of software replaces something, even if it is a person with a spreadsheet and a phone. Describe the current process step by step and attach examples with personal data removed: a screenshot of the spreadsheet, a sample invoice, the form customers fill in. The exceptions and workarounds you describe here are where most of the real rules live.
If there is existing software, say what it is, who built it, whether you have its code and whether its data must move across. If the thing being replaced is a spreadsheet, our guide to replacing spreadsheets with custom software covers what to expect.
List the systems it must talk to
Name every outside system the software has to send data to or read data from: accounting, a CRM, a payment provider, an email service, a warehouse system, a government portal. For each, say what should pass between them and whether you know of an API. Integrations are often the hardest part to estimate, because the other system's documentation and test environment are outside your developer's control. The earlier they are named, the better the estimate.
Write down the constraints
Constraints are the facts the software has to live with. Include the ones that apply:
- A fixed date, such as a launch, a season or the end of a contract with another vendor.
- Rules you must follow: data protection, industry regulation, accessibility, where data may be stored.
- Devices and platforms: the web, iPhone, Android, a tablet at a front desk.
- Languages and currencies.
- Technology you must keep, such as an existing database or the cloud provider your company already uses.
- Who on your side makes decisions, and how much time they have each week.
Give a budget range and a timeline, even rough ones
A budget range is not a commitment. It tells the developer which version of the product to propose. The same idea can be built for very different amounts, and without a range you get either a quote for the most expensive version or a guess. If you have no idea where to start, our MVP cost calculator gives a first range in a minute.
For the timeline, separate the date you would like from the date you must hit, and say what happens if it slips. A hard date with a flexible scope is a workable brief. A hard date with a long, fixed feature list usually is not.
Say what success looks like
Finish with how you will know the software worked, three to six months after launch: bookings taken online instead of by phone, invoices sent the same day, a manager who no longer spends Friday afternoons reconciling spreadsheets. Success measures keep everyone honest about which features matter, and they make scope decisions easier when something has to give.
What should you leave out of a brief?
A brief gets worse when it tries to do the developer's job. Leave out:
- Technology choices, unless you genuinely must use something. Say what you need to keep, and let the developer propose the rest and explain why.
- Screen-by-screen designs. Finished mock-ups commit you to decisions before anyone has tested them.
- Every feature you might want one day. Keep a separate 'later' list instead.
- Long company background. Two sentences on what you do and for whom are enough.
- Passwords, real customer data and anything confidential. Describe the data; share samples later, with personal details removed.
Common mistakes in software project briefs
- Describing the solution instead of the problem, so nobody can suggest a simpler way.
- Listing features without users. 'Reports' means nothing until you say who reads them and what they decide from them.
- Leaving out what happens today, which is where the hidden rules are.
- Hiding the budget, which turns every quote into a guess.
- Treating everything as essential. If nothing can be cut, the price and the date can only go up.
- Forgetting life after launch: who answers users' questions, who pays for hosting, who looks after the software.
- Sending different briefs to different companies, then comparing prices for different products. Send everyone the same brief and ask everyone the same questions.
A software project brief template you can copy
Copy these lines into a document and answer each in a sentence or two. Leave a line blank rather than guessing: a gap tells the developer what to ask about.
- Company and contact: who you are, what your company does, and who decides on this project.
- What you need: a new product or MVP, changes to an existing system, a mobile app, or support for software that is already live.
- The problem: what goes wrong today, who it happens to, and what it costs.
- Users and roles: each kind of user, roughly how many, and what each must be able to do.
- First version: the three to five things it must do, each written as a user doing something from start to finish.
- Later: the features that can wait for a second release.
- What happens today: the current process, tools and spreadsheets, with examples attached and personal data removed.
- Existing software: what it is, who built it, whether you have the code and whether its data must move.
- Integrations: each outside system, what passes between them, and whether it has an API.
- Constraints: fixed dates, rules to follow, devices, languages, technology you must keep.
- Budget range: under $10k, $10k–$50k, $50k+, or not sure yet.
- Timeline: as soon as possible, one to three months, later this year, or just exploring, plus any date you must hit.
- Success: what will be different three to six months after launch, and how you will measure it.
- After launch: who will run and support it: your own team, the developer, or not decided yet.
How the brief fits our inquiry form
Our inquiry form follows the same shape, so a brief written with the template drops straight into it. It asks for your name, work email, company and, if you like, a phone number; what you need (New product / MVP, Existing system, Mobile app or Support only); a budget range (Under $10k, $10k–$50k, $50k+ or Not sure yet); and a timeline (As soon as possible, One to three months, Later this year or Just exploring).
The last field is the brief itself, with one prompt: what should it do, who uses it, and what happens today instead? A few paragraphs answering those three questions are enough to start. Paste in your brief, or just its problem, users and first-version lines, and send it through the form. We reply within one working day. Next comes a call, with no slides, about what breaks today and who it hurts, and then a written scope with a price and a date, whether it is a new product or MVP or software shaped around an existing business.
How long should a software project brief be?
One or two pages is enough for most projects. A brief that answers the eight questions in a few sentences each is more useful than a long document nobody reads closely. The detail belongs in the scope the development company writes back.
Should I include my budget in a software brief?
Yes, as a range. It tells the developer which version of the product to propose and saves you from quotes for things you would never buy. If you genuinely do not know, say so and ask for options at two or three price points.
Do I need wireframes or designs before writing a brief?
No. Rough sketches, or screenshots of tools you like, can help explain an idea, but finished designs are not needed and can lock in decisions too early. Working software you can click, early in the project, will tell you more than any mock-up.
What is the difference between a brief and a scope?
The brief is what you write: the problem, the users and the limits. The scope is what the developer writes back: what will be built, in what order, for what price and by what date. You should be able to read the scope and recognise your brief in it.
Can a development company help me write the brief?
Yes, and a good one will ask the questions that fill the gaps. Write down the problem, the users and what happens today; the rest can be worked out together on a call. Turning that into a written scope with a price and a date, before you sign anything, is part of how we work.