# Software project brief template

Use this before requesting estimates. Keep the finished brief to one to three pages. If a section is unknown, write “open to recommendation” instead of guessing.

## 1. Business outcome

- What should change for the business or customer?
- Why does this need to happen now?
- How will you know the project worked?

## 2. Users and their problem

- Who is the primary user?
- What are they trying to accomplish?
- What do they use today, and why is it insufficient?

## 3. Version-one scope

List the smallest complete journey the first release must support.

1. A user can:
2. A user can:
3. An administrator can:

Explicitly out of scope:

-
-

## 4. Existing assets and constraints

- Existing code repository:
- Designs or wireframes:
- Brand/content assets:
- Required integrations:
- Required technology or hosting:
- Security, privacy or regulatory constraints:

## 5. Data

- What data enters the product?
- Where does it come from?
- Is any of it personal, financial, medical or confidential?
- How long must it be retained?
- Does existing data need to be migrated?

## 6. Delivery expectations

- Target launch window:
- Fixed external dates and why they are fixed:
- People available for decisions and feedback:
- Expected review cadence:

## 7. Budget and commercial model

- Approved budget range:
- Preferred model: fixed milestones, time and materials, or open to recommendation:
- Ongoing support needed after launch:

## 8. Acceptance criteria

For each version-one journey, write one observable result. Example: “A customer can pay for the monthly plan and immediately see an active subscription in their account.”

## Questions for the developer

- What assumptions have the largest effect on the estimate?
- What should be validated before committing to the full build?
- What could be removed from version one without breaking the outcome?
- What access, content or decisions do you need from us?
- What does handover include?

Prepared by Ijaz Khan — https://ijazkhan.com/contact