Blog ·
Decisions ·
·
3 min read
How to brief a software project
A good brief saves weeks. It doesn’t need to be formal — it needs to be concrete.
By Will Fortes · Fortes Tech
The minimum that helps
- Problem in one sentence + a real example from last week.
- Who feels the pain (role).
- What you’ve already tried.
- Desired timeline and why.
- Budget range (even approximate).
- Links: current site, screenshots, access if any.
What you don’t need on day one
- A full wireframe.
- Preferred stack (unless legacy constrains it).
- Company history since 1998.
Quick answers
What if I don’t know what I need?
Describe the pain and impact. Discovery turns that into scope.