Guide
How to write a software project brief developers can estimate
Vague requests get vague quotes. A one-page brief that covers the problem, the users, the first version and the constraints gets you estimates you can compare.
When three developers give you three very different quotes, it is rarely because one of them is wrong. Usually each of them has filled the gaps in the request with different assumptions. A short brief removes most of those gaps.
What a brief is for
A brief is not a specification. Its job is to make sure everyone pictures the same first version, so that estimates describe the same thing. One page is usually enough.
Tip: Write for someone who has never seen your business. If a sentence only makes sense to your team, rewrite it.
The sections that matter
The problem
Describe what is hard, slow or impossible today, and for whom. "Our booking process is messy" is hard to estimate. "Bookings arrive by phone and email, are copied into a spreadsheet, and double bookings happen most weeks" is not.
Who will use it
Name the groups of people and roughly how many there are. Staff using an internal tool all day need different things from customers who visit once a month.
What success looks like
Pick one or two outcomes you could measure, such as "invoices go out the same day the job is finished". These help a developer suggest what to build first.
The first version
List the few things users must be able to do in the first release. Keep the rest in a separate "later" list. If everything is in the first version, nothing gets built quickly.
What exists today
Mention the spreadsheets, tools and systems involved now, and anything the new software must connect to. Integrations are often where estimates differ most.
Timeline, budget and constraints
A date with a reason ("before the spring season") and a rough budget range help a developer propose a scope that fits. Constraints such as regulations, devices or weak mobile signal change the design, so state them early.
Leave the open questions open
If you do not know something yet, say so. "We are not sure whether customers need an app or a website" is useful information. A good partner will help you answer it, and a guess presented as a decision causes rework later.
A quick checklist
- The problem is described in terms of people and outcomes, not technology
- The first version fits in a short list
- Existing tools and integrations are named
- Timeline and budget are stated, even as ranges
- Unknowns are listed as open questions
If you want a head start, the project brief generator on this site turns your answers into this structure and lists what is still missing.
- MVP
- Planning
Try it yourself
- Project brief generatorAnswer a few questions and get a structured software brief you can share with any developer, including the open questions you still need to answer.
- MVP scope plannerSort your feature list into must, should, could and won’t, size each one, and see what a genuinely minimal first release looks like.
Want a second opinion on your brief?
Send it over. We reply with questions, a suggested first release and honest next steps.
Keep reading
- How to choose a custom software development companyWhat to look for, what to ask and which warning signs to watch for when choosing a company to build your software.
- MVP development cost: what founders should budgetWhat goes into the cost of an MVP, the line items founders forget, and how to plan a budget that leaves room to improve after launch.
- How much does it cost to build an app?The factors that decide what an app costs to build and run, and how to get an estimate you can compare between developers.