Service · Software requirements specification
Agree what the software is before anyone builds it.
What it is
A software requirements specification is the document that says what will be built. It is written before design and code, and it is what the build is checked against.
Who it is for
The people who will use the system, and the person paying for it. A campaign site, an admin tool, and a public product do not share one vague brief. Each gets its own users and its own jobs.
What we write
Scope, and what is out of scope. The screens and actions the system must support. The data it stores. The rules for accounts and permissions. What “done” means for the first release, in sentences a client can accept or reject.
What happens next
The specification is agreed, then the software is built to it. A change after that is a change to the document, not a surprise in the last week. We do not start a build from a slide deck.