Skip to content
FocalIDFocalID

How to write a software project brief that developers can price

A good brief gets you better proposals, closer estimates and fewer surprises. It does not need to be long or technical. Two to four pages that describe the problem clearly are worth more than fifty pages of features.

By the FocalID team in Colombo, , 2 min read

A person writing notes on paper at a desk beside a laptop and a mug.

What a brief should cover

  • The problem: what is slow, costly or impossible today, and what it costs you.
  • The users: who will use the system, how many of them, and on what devices.
  • The main journeys: the three to five things users must be able to do, described from start to finish.
  • Existing systems: what the new software must connect to, and what data already exists.
  • Constraints: deadline, budget range, security or legal requirements, languages.
  • Success: how you will know in six months that the project worked.

Describe problems, not screens

“A screen with a dropdown for each branch” tells a developer what to draw. “Branch managers need to see their own stock and request transfers from other branches” tells them what to solve, and lets them suggest something better. Describe what people need to get done and leave the design open.

Write journeys as short stories

For each main journey, write a few sentences: who starts it, what they do, what the system does and how it ends. For example: “A sales rep visits a shop, takes an order on a phone with no signal, and the order reaches the warehouse when the phone is back online.” One sentence like that carries several requirements a developer would otherwise have to guess.

Say what is out of scope

List what you do not want in the first version. It prevents suppliers from pricing different things and makes proposals comparable. Sort the rest into must have, should have and later.

Share a budget range

Buyers often hide the budget for fear of being charged all of it. The usual result is proposals that cannot be compared: one for a small tool, one for a platform. A range lets suppliers tell you what is realistic within it, and tells you quickly who is not a fit.

Before you send it

  • Have someone outside the project read it and explain it back to you.
  • Attach samples: current spreadsheets, forms and reports.
  • Name one person who can answer questions and make decisions.

Common questions

How long should a software brief be?

Two to four pages is enough for most projects, plus samples of the documents and data you use today.

Do we need technical knowledge to write one?

No. Describe the business problem and the users. Technical choices are the developer’s job to propose.

Should we include a deadline?

Yes, with the reason for it. A deadline tied to a real event helps the team decide what to deliver first.

Related