Statement of Work¶
| SOW Number: | [SOW_NUMBER] |
| Date: | [SOW_DATE] |
| Master Services Agreement: | MSA #[MSA_NUMBER], dated [MSA_DATE] |
| Consultant: | Base2ML LLC |
| Client: | [CLIENT_LEGAL_NAME] |
This Statement of Work ("SOW") is entered into pursuant to and governed by the Master Services Agreement referenced above ("MSA"). Capitalized terms not defined in this SOW have the meanings given to them in the MSA.
1. Project Overview¶
[TWO_TO_THREE_SENTENCE_DESCRIPTION_OF_THE_PROJECT, ITS_PURPOSE, AND_THE_BUSINESS_PROBLEM_IT_ADDRESSES]
2. Scope of Work¶
2.1 Included¶
The following activities are within the scope of this engagement:
- [SCOPE_ITEM_1]
- [SCOPE_ITEM_2]
- [SCOPE_ITEM_3]
- [SCOPE_ITEM_4]
- [SCOPE_ITEM_5]
2.2 Excluded¶
The following are explicitly outside the scope of this engagement. Any of these items may be added via a written Change Request:
- [EXCLUSION_1]
- [EXCLUSION_2]
- [EXCLUSION_3]
3. Deliverables¶
| # | Deliverable | Description | Due Date |
|---|---|---|---|
| 1 | [DELIVERABLE_NAME] | [BRIEF_DESCRIPTION] | [DATE] |
| 2 | [DELIVERABLE_NAME] | [BRIEF_DESCRIPTION] | [DATE] |
| 3 | [DELIVERABLE_NAME] | [BRIEF_DESCRIPTION] | [DATE] |
| 4 | [DELIVERABLE_NAME] | [BRIEF_DESCRIPTION] | [DATE] |
| 5 | [DELIVERABLE_NAME] | [BRIEF_DESCRIPTION] | [DATE] |
4. Milestones and Timeline¶
| Milestone | Description | Target Date | Payment Trigger |
|---|---|---|---|
| Project Kickoff | [DESCRIPTION] | [DATE] | Deposit due |
| [MILESTONE_2] | [DESCRIPTION] | [DATE] | [PAYMENT_TRIGGER] |
| [MILESTONE_3] | [DESCRIPTION] | [DATE] | [PAYMENT_TRIGGER] |
| Project Completion | Final delivery and acceptance | [DATE] | Final payment due |
Estimated total duration: [DURATION]
5. Pricing¶
5.1 Fee Structure¶
[SELECT AND COMPLETE THE APPLICABLE STRUCTURE:]
Fixed Fee: - Total project fee: $[AMOUNT]
Hourly: - Rate: $[RATE] per hour - Estimated hours: [ESTIMATE] - Not-to-exceed amount: $[CAP] (additional hours require written approval)
Hybrid: - Fixed base fee: $[AMOUNT] covering [SCOPE_DESCRIPTION] - Hourly rate for additional work: $[RATE] per hour
5.2 Payment Schedule¶
| Payment | Amount | Trigger |
|---|---|---|
| Deposit | $[AMOUNT] ([PERCENTAGE]%) | Upon execution of this SOW |
| [MILESTONE_PAYMENT] | $[AMOUNT] ([PERCENTAGE]%) | [TRIGGER: e.g., completion of Milestone 2] |
| Final Payment | $[AMOUNT] ([PERCENTAGE]%) | Upon final delivery and acceptance |
| Total | $[TOTAL_AMOUNT] |
5.3 Payment Terms¶
Invoices are due within [NET_15 / NET_30] days of the invoice date, per the MSA. The deposit is due upon signing and is required before work begins.
5.4 Additional Costs¶
[DESCRIBE ANY ANTICIPATED ADDITIONAL COSTS, e.g., third-party software licenses, cloud infrastructure, travel. OR STATE: "No additional costs are anticipated. Any out-of-pocket expenses require prior written approval from Client."]
6. Acceptance Criteria¶
6.1 Review Process¶
Upon delivery of each Deliverable, Client will have five (5) business days to review and either accept the Deliverable in writing or provide a written list of specific, actionable issues that must be addressed.
6.2 Acceptance¶
A Deliverable is considered accepted upon the earliest of:
- Client's written acceptance (email is sufficient)
- Client's use of the Deliverable in production or for business purposes
- Expiration of the five (5) business day review period without written objection
6.3 Revisions¶
One (1) round of revisions is included for each Deliverable, limited to issues within the original scope and acceptance criteria. Revisions will be completed within [REVISION_TIMEFRAME, e.g., five (5) business days] of receiving Client's feedback.
Additional revision rounds or revisions that constitute scope changes will be handled through the Change Management process described in Section 8 and billed at $[HOURLY_RATE] per hour.
7. Assumptions and Dependencies¶
7.1 Client Responsibilities¶
Client agrees to provide the following in a timely manner. Delays in Client deliverables may result in corresponding adjustments to the project timeline:
- [CLIENT_RESPONSIBILITY_1, e.g., "Access to relevant document repositories and systems within 5 business days of project kickoff"]
- [CLIENT_RESPONSIBILITY_2, e.g., "A designated point of contact available for questions and feedback within 2 business days"]
- [CLIENT_RESPONSIBILITY_3, e.g., "Sample documents representative of the full document corpus for initial testing"]
- [CLIENT_RESPONSIBILITY_4, e.g., "Feedback on deliverables within the review periods specified in Section 6"]
7.2 Timeline Dependencies¶
- [DEPENDENCY_1, e.g., "Project timeline assumes kickoff within 10 business days of SOW execution"]
- [DEPENDENCY_2, e.g., "Milestone 2 cannot begin until Client provides production data access"]
- [DEPENDENCY_3, e.g., "Final delivery date assumes no more than one revision round per deliverable"]
7.3 Key Assumptions¶
- [ASSUMPTION_1, e.g., "Document volume does not exceed X documents / Y GB"]
- [ASSUMPTION_2, e.g., "Documents are primarily in English and in PDF, Word, or text format"]
- [ASSUMPTION_3, e.g., "Client's existing infrastructure meets the minimum requirements outlined in the project kickoff"]
If any assumption proves incorrect, Consultant will notify Client promptly and the Parties will discuss the impact on scope, timeline, and cost through the Change Management process.
7a. Success Criteria¶
The following measurable criteria define a successful engagement. These are used to evaluate completion and inform the decision to proceed to a full deployment:
| # | Criterion | Measurement |
|---|---|---|
| 1 | [CRITERION_1, e.g., "Document ingestion"] | [MEASUREMENT, e.g., "Successfully indexes X documents within Y days of receiving data"] |
| 2 | [CRITERION_2, e.g., "Query accuracy"] | [MEASUREMENT, e.g., "Answers N test queries with relevant source citations"] |
| 3 | [CRITERION_3, e.g., "Deployment availability"] | [MEASUREMENT, e.g., "System accessible via HTTPS with 99% uptime during pilot period"] |
| 4 | [CRITERION_4, e.g., "Executive findings"] | [MEASUREMENT, e.g., "Delivers audit reports identifying risks, conflicts, and actionable insights"] |
Important: Success criteria measure delivery of the scoped services, not business outcomes. AI-generated outputs depend on the quality and completeness of Client-provided data. Consultant does not guarantee specific accuracy rates, business results, or ROI. See MSA Section 7a (AI and Platform Performance Disclaimer).
8. Change Management¶
8.1 Change Requests¶
All changes to the scope, timeline, or deliverables described in this SOW must be documented in a written Change Request.
8.2 Process¶
- Either Party submits a written Change Request describing the proposed change
- Consultant assesses the impact on scope, timeline, and cost and provides a written response within five (5) business days
- Both Parties sign the Change Request before any work on the change begins
- Approved Change Requests become part of this SOW
8.3 No Unauthorized Work¶
Consultant will not perform work outside the scope of this SOW without an approved Change Request. Client acknowledges that verbal requests or informal communications do not constitute authorization for additional work.
9. Team and Resources¶
9.1 Consultant Team¶
| Role | Name | Responsibilities |
|---|---|---|
| Project Lead | [NAME] | Overall project delivery, primary client contact |
| [ROLE] | [NAME] | [RESPONSIBILITIES] |
9.2 Client Team¶
| Role | Name | Responsibilities |
|---|---|---|
| Client Sponsor | [NAME] | Executive oversight, approvals |
| Point of Contact | [NAME] | Day-to-day coordination, feedback, access provisioning |
| [ROLE] | [NAME] | [RESPONSIBILITIES] |
9.3 Communication¶
- Status updates: [FREQUENCY, e.g., weekly] via [METHOD, e.g., email summary]
- Meetings: [FREQUENCY AND FORMAT, e.g., bi-weekly 30-minute video call]
- Primary communication channel: [EMAIL / SLACK / TEAMS / OTHER]
10. Signatures¶
By signing below, both Parties agree to the terms of this Statement of Work, which is governed by the Master Services Agreement referenced above.
Base2ML LLC
| Signature: | ________ |
| Name: | [CONSULTANT_SIGNER_NAME] |
| Title: | [CONSULTANT_SIGNER_TITLE] |
| Date: | ________ |
[CLIENT_LEGAL_NAME]
| Signature: | ________ |
| Name: | [CLIENT_SIGNER_NAME] |
| Title: | [CLIENT_SIGNER_TITLE] |
| Date: | ________ |
---¶
Sample: Metis Pilot Engagement SOW¶
The following is a completed example showing how this template might be filled in for a typical Metis pilot deployment. This section is for reference only and is not part of the SOW template above.
SOW Number: SOW-2026-001 Date: April 15, 2026 Client: Keystone Building Group LLC
Project Overview¶
Base2ML will deploy the Metis knowledge assistant for Keystone Building Group's operational document library. The pilot will demonstrate Metis's ability to ingest, index, and answer questions against Keystone's safety manuals, project specifications, and standard operating procedures, enabling field supervisors and project managers to find critical information faster.
Scope of Work¶
Included: - Document ingestion and processing for up to 500 documents (PDF, Word, and text formats) - Index configuration and optimization for construction industry terminology - Three (3) quality audit reports assessing retrieval accuracy and relevance - Pilot access to the Metis assistant for up to 10 users for 14 calendar days - Executive findings presentation with usage analytics and recommendations
Excluded: - Integration with existing ERP, project management, or field software systems - Custom UI development or branding - Ongoing support beyond the 14-day pilot period - Document creation, editing, or reformatting
Deliverables¶
| # | Deliverable | Description | Due Date |
|---|---|---|---|
| 1 | Configured Metis Instance | Ingested documents, tuned index, tenant configuration | Week 1 |
| 2 | Quality Audit Report #1 | Baseline retrieval accuracy across 50 test queries | Week 1 |
| 3 | Pilot Access | 10 user accounts with Metis assistant access | Week 2 |
| 4 | Quality Audit Reports #2-3 | Mid-pilot and end-of-pilot accuracy and usage reports | Weeks 3-4 |
| 5 | Executive Presentation | Findings, usage analytics, and go/no-go recommendation | Week 4 |
Pricing¶
| Payment | Amount | Trigger |
|---|---|---|
| Deposit | $X,XXX (50%) | Upon execution of this SOW |
| Final Payment | $X,XXX (50%) | Upon delivery of executive presentation |
| Total | $X,XXX |
Success Criteria¶
| # | Criterion | Measurement |
|---|---|---|
| 1 | Document ingestion | Successfully indexes up to 500 client documents within 3 business days of receiving data |
| 2 | Query capability | Answers queries with relevant source citations across ingested document corpus |
| 3 | Audit delivery | Delivers 3 quality audit reports identifying risks, contradictions, and actionable insights |
| 4 | Pilot availability | Metis assistant accessible via HTTPS for up to 10 users during 14-day pilot window |
| 5 | Executive findings | Delivers executive presentation with findings and go/no-go recommendation |
Results depend on the quality and completeness of Client-provided documents. AI outputs are not guaranteed to achieve specific accuracy rates.
Key Assumptions¶
- Document volume does not exceed 500 documents or 2 GB total
- Documents are primarily in English
- Client provides document access within 5 business days of kickoff
- Client designates a point of contact available for questions within 2 business days