How to write a software brief
A good brief is one or two pages. It is not a contract. It is how a studio quotes the same object you have in your head.
Start with the problem and who feels it. Then list only what version one must do. Add what is explicitly out. Add stack preferences only if they are real constraints. Add a date and a budget band.
If you cannot write the out of scope list, you are still dreaming the whole product. That is fine. We will help you cut. The brief still needs a first cut from you.
Must haves only
If everything is required, nothing is. Version one needs a spine.
Show the workaround
The spreadsheet, the WhatsApp group, the inbox. That is the spec hiding in plain sight.
Common questions
Can I just fill your Start a project form?
Yes. That form is a brief. Use this guide if you want to arrive even sharper.
Keep going
Get a quote for what you want to build
A 5 minute brief. We reply within one business day. No pressure to hire.