Start with the work, not the technology
Describe a specific situation, who encounters it and what happens today.
Fictional example: a studio receptionist receives requests across several conversations and checks available times manually.
Public guide
A useful brief before the first proposal
Questions, materials and criteria that make a software discussion more concrete.
Tick items as you prepare the context. The selection stays on this page and is not sent anywhere.
0 / 15 items prepared
Choose the first useful change
A bounded scope is easier to verify than an unlimited list of features.
Example: a visitor chooses a service and submits a preferred time; reception sees the context in one shared place.
Prepare materials and dependencies
Content, access and permissions can influence the project as much as development.
Do not include passwords in a brief. Required access and the verification environment are arranged separately.
Define verification and handover
For each important activity, describe the input, action and expected result.
Example: if saving fails, the enquiry is not shown as sent, and the user can keep their information for a retry.
Compare proposals against the same scope
A useful comparison puts deliverables and responsibilities side by side, not just the final amount.
Ask what is included, what is optional and how scope changes are approved.