# Software Development statement of work

Replace everything in [brackets]. Delete sections that don’t apply.

---

## Project details

Project: [Name]
Client: [Company]
Provider: [Your business]
Reference: [SOW-001]
Governing agreement: [Master service agreement dated … / terms attached]

## 1. Background and objectives

[Why the project exists and what success looks like.]

## 2. Scope of work

1. **Discovery:** [activities]
2. **Build sprints:** [activities]
3. **User acceptance testing:** [activities]
4. **Launch and handover:** [activities]

## 3. Deliverables

| # | Deliverable | Description / format | Due |
| --- | --- | --- | --- |
| 1 | [Working software deployed to the client’s environment] | [Detail] | [Date] |
| 2 | [Source code in the client’s repository] | [Detail] | [Date] |
| 3 | [Technical documentation and deployment notes] | [Detail] | [Date] |
| 4 | [Handover session for the client’s team] | [Detail] | [Date] |

## 4. Out of scope

- [Hosting, third-party APIs and licences unless listed]
- [Features not listed in the agreed backlog]
- [Support after the warranty period]
- [Data migration from legacy systems]

## 5. Assumptions and client responsibilities

- [A product owner available for sprint reviews]
- [Access to existing systems and test data]
- [Decisions on priorities within agreed timeframes]

If these are late, dependent dates move by the same amount of time.

## 6. Milestones

| Milestone | Target date | Depends on |
| --- | --- | --- |
| Discovery | [Date] | [Approval or input] |
| Build sprints | [Date] | [Approval or input] |
| User acceptance testing | [Date] | [Approval or input] |
| Launch and handover | [Date] | [Approval or input] |

## 7. Acceptance

The client’s named approver reviews each deliverable within [5] working days. Deliverables are accepted on written approval, or when the review period passes without material issues being raised.

## 8. Changes

Changes to scope, deliverables or timeline are agreed in writing, with the effect on fees and dates, before work begins.

## 9. Fees and payment

Fee: [Amount and basis]
Schedule: [Payment by milestone]
Expenses: [At cost with approval / included]

## 10. Sign-off

Client: [Name, title, signature, date]
Provider: [Name, title, signature, date]

---

## Before it’s signed

- [ ] Every deliverable is specific and testable.
- [ ] Exclusions cover the requests you can already predict.
- [ ] Client responsibilities have dates.
- [ ] A named approver and review window are set.
- [ ] The change process is clear.
- [ ] Fees match the proposal.

---

# Example: Keel Labs statement of work for Harbour Freight Ltd

Key sections for a driver scheduling web app. Both companies are fictional.

## Deliverables

| # | Deliverable | Phase |
| --- | --- | --- |
| 1 | Working software deployed to the client’s environment | Discovery |
| 2 | Source code in the client’s repository | Build sprints |
| 3 | Technical documentation and deployment notes | User acceptance testing |
| 4 | Handover session for the client’s team | Launch and handover |

## Out of scope

- Hosting, third-party APIs and licences unless listed
- Features not listed in the agreed backlog
- Support after the warranty period
- Data migration from legacy systems

## Client responsibilities

- A product owner available for sprint reviews
- Access to existing systems and test data
- Decisions on priorities within agreed timeframes

## Fees

Total: $24,620.00 excluding tax
Schedule: Invoiced at the end of each phase: Discovery, Build sprints, User acceptance testing, Launch and handover

## Acceptance testing

The client has ten working days after each release to report defects against the agreed acceptance criteria. Releases with no reported defects in that time are accepted.

Template by Angelwood — https://angelwood.io/templates