DIALECT®Begin a Project

How to write a software project brief

Describe who will use the software, what they do today, and what the finished application has to handle.

A feature list can describe what a company imagines without explaining why it needs it. “Dashboard, notifications, and approvals” leaves a developer guessing about the work being coordinated, the information involved, and the consequences of a missed step.

The company does not need to design the technical solution before asking for help. It does need to describe the current situation, the intended users, and the outcome the project should make possible.

For example, an approval tool may need to handle an absent manager or an incomplete request. Including those situations lets the developer estimate the work and suggest a simpler approach where one is available.

The current process

The brief can follow one item through the existing process. For an approval tool, that means explaining who submits a request, what information they provide, who reviews it, and how the decision reaches the next person.

The example should include the awkward parts. Requests may arrive incomplete, an approver may be absent, or someone may need to correct an earlier decision. These situations help establish what the application needs to handle.

Existing documents, screenshots, and sample records can clarify the process when they can be shared appropriately. They should come with an explanation of what the team finds difficult today.

Users, data, and integrations

The developer needs to understand who will use the tool and which actions each person may perform. A manager reviewing all requests has different needs from someone checking only their own submission.

The brief should identify the systems holding the information and the person who can answer questions about them. Access arrangements and integration limits can materially change the project. Our article on API integrations and MCP describes two approaches to connecting software, depending on the intended workflow.

Where the request concerns reporting, the brief should include the definitions behind the figures. The comparison of custom and off-the-shelf dashboards explains why that work belongs before interface development.

Acceptance criteria

The brief should give examples that both sides can use to review the finished work. An ordinary request should reach the right reviewer. An incomplete request should show the person what is missing. An unavailable connection should leave the team with an understandable state and a way to continue.

Use those examples to review the application during development. Accessibility, the devices people use, and any performance requirements should also be identified when relevant to the job.

The first release needs a clear boundary. Additional ideas can be recorded separately so that an estimate for the initial scope does not become an implied commitment to everything discussed.

Handover and maintenance

The company should explain who will own the application and how it expects to operate it. The proposal needs to cover deployment, access, documentation, and support, including responsibility for connected services.

Budget and timing constraints should be shared as constraints rather than hidden tests for the estimate. If the proposed scope cannot fit them, the developer can suggest a smaller release or further investigation. Our guide to internal tool development costs explains which requirements commonly change the amount of work.