Statement of Work

This Statement of Work is governed by the Master Services Agreement between Eclipse Labs AI and the Client referenced above. Capitalised terms not defined here have the meanings given in the MSA.

1. Background

[2-3 sentences describing the client's situation, the problem to be solved, and why this engagement exists. E.g., "The Client operates a B2B procurement platform and requires AI-driven workflow automation to reduce manual processing time across their renewal pipeline."]

2. Scope of Work

The Provider shall deliver the following services:

1. [Service/activity description — e.g., "Audit existing renewal workflow and identify automation opportunities"]
2. [Service/activity description — e.g., "Design and build AI agent orchestration for deal analysis"]
3. [Service/activity description — e.g., "Develop production-ready front-end application with full documentation"]
4. [Service/activity description — e.g., "Deliver team training on iteration framework and handover"]

3. Deliverables

Deliverable	Format	Due
[Workflow audit report]	[PDF + diagrams]	[Week 2]
[Agent orchestration configuration]	[Documented playbook]	[Week 4]
[Production application + source code]	[HTML/CSS/JS + repo]	[Week 8]
[Training session + iteration framework]	[Live session + PDF]	[Week 9]

4. Milestones and Payment Schedule

Milestone	Amount
Milestone 1 — Discovery & Audit	[£/$ AMOUNT]
Milestone 2 — Design & Configuration	[£/$ AMOUNT]
Milestone 3 — Build & Delivery	[£/$ AMOUNT]
Milestone 4 — Training & Handover	[£/$ AMOUNT]
Total	[£/$ TOTAL]

5. Client Responsibilities

The Client shall:

• Designate a primary point of contact with authority to approve deliverables
• Provide timely access to systems, data, and personnel as reasonably required
• Review and provide feedback on deliverables within [5] business days of submission
• Ensure all information provided to the Provider is accurate and complete

Delays caused by the Client's failure to meet these responsibilities may result in adjusted timelines and, where significant, additional fees as mutually agreed.

6. Acceptance

1. Upon delivery of each milestone, the Client shall have [5] business days to review and either accept or provide written feedback specifying deficiencies ("Review Period").
2. If the Client does not respond within the Review Period, the milestone shall be deemed accepted.
3. The Provider shall address any reasonable deficiencies within [5] business days at no additional cost, provided the deficiency falls within the agreed scope.
4. Requests for work outside the agreed scope constitute a change request and will be addressed through a separate SOW or amendment.

7. Assumptions and Exclusions

Assumptions

• [E.g., "Client will provide API access to existing systems by Week 1"]
• [E.g., "All content and copy will be provided by the Client"]
• [E.g., "Hosting and domain configuration are the Client's responsibility"]

Exclusions

• [E.g., "Ongoing maintenance and support beyond the handover period"]
• [E.g., "Third-party software licences or API costs"]
• [E.g., "Data migration from legacy systems"]

8. Change Requests

Either Party may propose changes to the scope. All changes must be documented in writing, agreed by both Parties, and may result in adjusted fees and timelines. No change shall be binding until a written amendment or new SOW is signed.

This SOW is subject to the terms of the Master Services Agreement between the Parties. Review by qualified legal counsel is recommended.