[PROJECT NAME] — Statement of Work (SOW)
Date: [DATE]
Version: [VERSION]
Client: [CLIENT NAME]
Author: [AUTHOR]
Engagement Path: [Fractional Data Team-as-a-Service (FDTaaS) | Data Foundations Sprint (DFS)]
Template: This is the single official Brainforge SOW template. All SOWs and proposals (including GTM sales proposals in
knowledge/sales/sales/leads/) follow this structure. The SOW Writing Agent uses this template. Seestandards/04-prompts/sow/sow-writing-agent.md.Path selection is required: Choose one renewal path before drafting:
- FDTaaS (Fractional Data Team-as-a-Service): annual/retainer model with rolling workstreams and quarterly planning.
- DFS (Data Foundations Sprint): milestone/sprint model for bounded foundation buildout.
- Taxonomy source:
knowledge/sales/sow-framework/README.md.
1. Executive Summary
Summarize the engagement in 3–5 paragraphs. Include:
- The Problem: What challenge is the client facing? What is broken or missing?
- The Solution: What will Brainforge deliver to address this?
- Expected Outcomes: What measurable results will the client achieve?
- Guiding heuristics (when applicable): 3–5 bullets on how we will operate (e.g. documentation first, low cost / high impact, reuse what exists).
- Expected outcome (one sentence): The single-line takeaway for the client.
- Investment: High-level cost range or pricing model (details in Section 12).
Tip: Write this section last, after the rest of the SOW is complete.
2. Objectives
List 3–6 high-level objectives the client wants to achieve. Keep these measurable and outcome-focused.
- Objective 1
- Objective 2
- Objective 3
3. Expected ROI (recommended for sales proposals)
Use a table to show value. Optional for internal or renewal SOWs; recommended for new client proposals.
| Outcome | Current State | Target State | Value |
|---|---|---|---|
| Outcome 1 | … | … | … |
| Outcome 2 | … | … | … |
4. Scope of Work
4.1 In-Scope
Describe what Brainforge will deliver. Structure should match selected path:
- FDTaaS: prefer workstream-based structure with flexible sequencing and capacity allocation.
- DFS: prefer phase or milestone structure with explicit completion checkpoints.
Option A — Workstream-based (good for multi-track or sales proposals):
Workstream 1: [Name]
Context: Brief situation, constraints, who’s involved.
Approach: Numbered steps or week-by-week (e.g. Week 1–2: …; Week 3–4: …).
Deliverables:
- Deliverable 1
- Deliverable 2
Workstream 2: [Name] — repeat Context, Approach, Deliverables.
Option B — Phase-based (good for linear or milestone-driven engagements):
Phase 1: [Phase Name] (Weeks X–Y)
Deliverables:
- Deliverable 1
- Deliverable 2
Acceptance Criteria:
- Criteria 1
- Criteria 2
Phase 2: [Phase Name] (Weeks X–Y) — repeat as needed.
4.2 Required Deliverables Summary
Table for quick reference. Include when each deliverable is due.
| Deliverable | When |
|---|---|
| … | … |
4.3 Out-of-Scope / What This Engagement Does Not Include
Explicitly list what Brainforge will NOT do:
- Item 1
- Item 2
- Item 3
5. Requirements & Inputs (Dependencies)
List what Brainforge needs from the client to execute. You may use the heading Dependencies for sales proposals.
Access & Permissions
- System access (APIs, databases, tools)
- Credentials or API keys
Documentation
- Requirements documents, existing data dictionaries or specs
Stakeholder Availability
- SME availability for questions
- Meeting attendance expectations
6. Project Timeline
Provide a summary timeline. Use a table and/or a short week-by-week block.
| Phase / Workstream | Dates | Focus | Deliverables |
|---|---|---|---|
| 1 | Week 1–2 | … | … |
| 2 | Week 3–5 | … | … |
Total Duration: X weeks
7. Assumptions
List assumptions that shape this SOW. If assumptions change, scope or timeline may need adjustment.
- Assumption 1
- Assumption 2
- Assumption 3
8. Risks & Mitigations
Identify potential risks and how they will be addressed. Use the Impact column.
| Risk | Impact | Mitigation |
|---|---|---|
| Risk 1 | Medium | Mitigation approach |
| Risk 2 | High | Mitigation approach |
| Risk 3 | Low | Mitigation approach |
9. Acceptance Criteria / Success Indicators
Define what success looks like for the engagement.
-
FDTaaS guidance: emphasize operating success indicators (adoption, reliability, turnaround time, stakeholder confidence), not rigid per-ticket acceptance gates.
-
DFS guidance: use milestone/phase acceptance criteria with completion thresholds.
-
Criterion 1
-
Criterion 2
-
Criterion 3
10. Communication Plan
Regular Meetings
- Weekly Standup (30 min): Progress updates, blocker resolution
- Bi-Weekly Review (60 min): Demo deliverables, gather feedback
- Ad-hoc Sessions: As needed for requirements or issue resolution
Async Communication
- Dedicated Slack channel or email thread for daily questions
- Shared workspace (Google Drive, Notion, or GitHub) for documentation
- End-of-phase status email summarizing progress and next steps
Escalation Path
- Technical blockers → [Brainforge Lead]
- Business/requirements questions → [Client Stakeholder]
- Timeline risks communicated within 24 hours of identification
11. Team
Brainforge Team
| Role | Name | Responsibility |
|---|---|---|
| Managing Lead | [Name] | Client POC, project alignment, roadmap |
| Engineering Lead | [Name] | Technical design, implementation |
| Engineer/PM | [Name] | Feature development, project coordination |
Client Team
| Role | Name | Involvement |
|---|---|---|
| Sponsor | [Name] | Decision-maker, approvals |
| SME | [Name] | Requirements, validation |
| Technical POC | [Name] | Access, integrations |
12. Pricing & Payment
Pricing Model
Choose the appropriate model for this engagement:
Option A: Fixed Fee
| Milestone/Phase | Fee |
|---|---|
| Phase 1 / Upfront | $X |
| Phase 2 / Completion | $X |
| Total | $X |
Option B: Sprint-Based
- Price per Sprint: $X per 2-week sprint
- Total Sprints: X
- Total Engagement: $X
Option C: Hourly
| Role | Rate |
|---|---|
| Managing Lead / Strategist | $250/hour |
| Senior Engineer / Architect | $200/hour |
| Engineer / Technical PM | $150/hour |
Billing Terms
- Invoicing: Bi-weekly or Monthly
- Payment Terms: Net 15 or Net 30
- Minimum Billing Unit: 1 hour, billed in 0.25-hour increments thereafter
- Email/Phone Response (15 min or less): Not billed
- Currency: USD
13. Sign-Off
By signing below, both parties acknowledge understanding and agreement with the scope, deliverables, timeline, and approach outlined in this Statement of Work.
Client ([CLIENT NAME]):
Name: ___________________________
Title: ___________________________
Date: ___________________________
Signature: _______________________
Brainforge:
Name: ___________________________
Title: ___________________________
Date: ___________________________
Signature: _______________________
Optional Sections (after Sign-Off)
Add when helpful for sales or clarity:
- Why Brainforge? — Approach bullets, relevant experience, differentiator.
- Case Studies — 1–2 paragraphs or one-pagers from similar engagements.
- Next Steps — Numbered list (e.g. Review proposal → Sign SOW → Grant access → Kickoff).
Citation for agents and writers
When generating or editing an SOW, use this template only:
- Path:
standards/02-writing/SOWs/sow-template.md - Checklist:
standards/02-writing/SOWs/sow-checklist.md - Agent:
standards/04-prompts/sow/sow-writing-agent.md - Renewal paths taxonomy:
knowledge/sales/sow-framework/README.md
GTM/sales proposals in knowledge/sales/sales/leads/ use this same template. Do not use a different SOW structure unless explicitly instructed.