# Software project brief

## Project name

A short name for the work

## Business problem and desired outcome

What needs to change, and how will you know it worked?

## Users and main workflows

Who uses the system and what must each person complete?

## Required features and later additions

Separate the first release from ideas for later.

## Existing systems and data

Current tools, integrations, imports and access constraints

## Design, languages and content

Brand assets, reference screens and who supplies the content

## Budget and ongoing costs

Budget range and any limit on recurring costs

## Timing and dependencies

Target date, approvals and other work needed before launch

## Acceptance and support

How you will review the work, and the support needed after launch

Ask proposals to identify deliverables, exclusions, timeline, fees, operating costs, acceptance, ownership and support.