Statement of Work Template
Each Networkz project engagement is governed by a Statement of Work (SOW) executed under the Master Services Agreement. This template shows every section of an SOW. A specific SOW will be prepared and signed for each engagement.
How This Works
After your free scoping consultation, Networkz will prepare a project-specific SOW that fills in all the sections below with your project's details. The SOW is executed alongside the MSA. Fields shown in [brackets] are placeholders to be completed for each engagement.
Parties and Governing Agreement
1. Project Overview
1.1 Project Name
[Project name — e.g., "FastAPI Backend for [Client] SaaS Platform"]
1.2 Background and Context
[Brief description of the Client's business, the problem they are solving, and why this system is being built. Example: "[Client] operates an e-commerce platform serving SMBs in India. The existing backend cannot handle concurrent API requests at scale. Networkz will design and deliver a new high-performance FastAPI backend with a PostgreSQL data layer."]
1.3 Project Objectives
- [Primary objective — e.g., "Deliver a scalable RESTful API handling 1,000+ concurrent requests"]
- [Secondary objective — e.g., "Reduce average API response time to under 100ms"]
- [Additional objective as needed]
2. Scope of Work
Networkz will design, develop, and deliver the following system components:
| Component | Description | Deliverable |
|---|---|---|
| Database Architecture | [e.g., PostgreSQL schema design, indexing strategy, migration scripts] | Schema documentation + migration files |
| API Layer | [e.g., FastAPI application with endpoints for user auth, product catalogue, order management] | Working API + OpenAPI documentation |
| Caching Layer | [e.g., Redis integration for catalogue caching] | Redis integration code + configuration |
| CI/CD Pipeline | [e.g., GitHub Actions workflow for automated testing and deployment] | Working CI/CD configuration |
| Deployment | [e.g., Deployment to GCP Cloud Run with environment configuration] | Live production deployment + deployment guide |
| [Additional component] | [Description] | [Deliverable] |
3. Explicitly Out of Scope
The following are not included in this SOW:
- [e.g., Frontend / client-side UI development (unless specified above)]
- [e.g., Mobile application development]
- [e.g., Third-party API integrations not listed in Section 2]
- [e.g., Legacy system data migration beyond the schema defined in Section 2]
- [e.g., Security penetration testing]
- [e.g., Post-launch maintenance beyond the 30-day support period in Section 13]
Any work not described in Section 2 or listed as in-scope elsewhere in this SOW will require a written Change Order.
4. Milestones, Deliverables, and Timeline
| # | Milestone | Deliverables | Target Date | Fee (INR) |
|---|---|---|---|---|
| M0 | Deposit / Project Start | Project kickoff; initial scoping document provided | [Date of SOW execution] | [30% of total] |
| M1 | Database Architecture | PostgreSQL schema, ERD, migration scripts, architecture document | [Date] | [Amount] |
| M2 | API Layer & Core Endpoints | FastAPI application, all specified endpoints, OpenAPI documentation, unit tests | [Date] | [Amount] |
| M3 | Integrations & Caching | Redis integration, third-party integrations as specified, integration tests | [Date] | [Amount] |
| M4 | Deployment & QA | CI/CD pipeline, production deployment, QA report, deployment documentation | [Date] | [Balance] |
Total Project Fee: INR [Total] (exclusive of applicable taxes)
Target dates are estimates based on timely Client feedback and approvals. Delays caused by Client (see MSA Section 6.2) may result in revised dates.
5. Payment Schedule
| Payment | Amount | Due Date / Trigger |
|---|---|---|
| Deposit (30%) | INR [Amount] | Due within 5 business days of SOW execution — before work commences |
| Milestone 1 Payment | INR [Amount] | Due within 7 business days of M1 approval |
| Milestone 2 Payment | INR [Amount] | Due within 7 business days of M2 approval |
| Milestone 3 Payment | INR [Amount] | Due within 7 business days of M3 approval |
| Final Payment (M4) | INR [Amount] | Due within 7 business days of M4 approval — triggers full IP transfer |
Payment method: Bank transfer (NEFT/RTGS/IMPS) or UPI to account details provided on the invoice.
IP in Deliverables transfers to the Client only upon receipt of the final payment. See MSA Section 15.
6. Acceptance Criteria
Each Milestone will be accepted when the Deliverables meet the following criteria:
| Milestone | Acceptance Criteria |
|---|---|
| M1 — Database Architecture | [e.g., All entities described in the requirements are represented; ERD is provided; migrations run cleanly on PostgreSQL 15+; schema supports specified query patterns] |
| M2 — API Layer | [e.g., All endpoints described in Section 2 are functional; OpenAPI docs are accurate; unit test coverage ≥ 80%; authentication and authorisation work as specified] |
| M3 — Integrations | [e.g., Redis caching reduces specified query response time by ≥ 50%; all third-party integrations return expected responses in staging environment] |
| M4 — Deployment & QA | [e.g., Application deployed to production environment; CI/CD pipeline runs green; QA report documents all test results; deployment guide allows independent re-deployment] |
The Client has 7 business days to review and respond to each Milestone delivery. Non-response within 7 business days constitutes acceptance.
7. Revisions
Each Milestone includes up to two rounds of revisions to correct genuine non-conformances with the acceptance criteria in Section 6. Revisions that add new features, change requirements, or extend scope constitute a change and require a Change Order under Section 8.
8. Change Orders
Any change to scope, deliverables, timeline, or fees must be agreed in a written Change Order before implementation. Networkz will provide a written estimate of the impact on timeline and fees within a reasonable period. No change will be implemented without a signed (or email-confirmed) Change Order.
Change Order reference: [CO-YYYY-NNN-XX] (to be assigned sequentially).
9. Client-Provided Materials and Access
The Client agrees to provide the following before the project commences or by the dates specified:
- [e.g., Access to existing codebase / Git repository — by [Date]]
- [e.g., Database credentials for staging environment — by [Date]]
- [e.g., Access to cloud provider account (GCP/AWS) — by [Date]]
- [e.g., API credentials for [third-party service] — by [Date]]
- [e.g., Brand assets and design files — by [Date]]
- [e.g., Product requirements document — by [Date]]
Delays in providing these materials may result in revised delivery dates (see MSA Section 6.2).
10. Technical Environment and Constraints
| Parameter | Specification |
|---|---|
| Primary language(s) | [e.g., Python 3.12 / Go 1.22] |
| API framework | [e.g., FastAPI 0.115 / Gin] |
| Database | [e.g., PostgreSQL 16] |
| Caching | [e.g., Redis 7] |
| Hosting platform | [e.g., GCP Cloud Run / AWS Lambda / Vercel] |
| CI/CD | [e.g., GitHub Actions] |
| Container | [e.g., Docker] |
| Target environment | [e.g., Linux (Debian-based container)] |
| Performance targets | [e.g., P95 API response time < 100ms under 500 concurrent users] |
| Other constraints | [e.g., Must support mobile clients; must be backward-compatible with v1 API] |
11. Communication and Reporting
| Item | Detail |
|---|---|
| Primary communication channel | [e.g., WhatsApp / Email / Slack / Notion] |
| Networkz point of contact | hello@networkz.in |
| Client point of contact | [Name] — [email] — [phone] |
| Progress updates | [e.g., Weekly written update every Monday] |
| Check-in calls | [e.g., 30-minute video call at each Milestone delivery] |
| Response time expectation | [e.g., Both parties will respond to written queries within 1 business day] |
12. Deployment Environment
Unless otherwise agreed, Networkz will deploy the final production build to the environment specified in Section 10. The Client is responsible for maintaining access and billing for the hosting environment after deployment.
Networkz will provide a deployment guide sufficient for the Client or their technical team to re-deploy independently.
13. Post-Launch Support Period
Networkz will provide 30 days of post-launch support from the date of final Milestone acceptance at no additional charge. This support covers:
- Bug fixes for defects in the Deliverables as delivered (not caused by third-party changes or Client modifications);
- Reasonable questions about the codebase and deployment.
This support period does not include new features, integrations, or performance enhancements. Ongoing support after the 30-day period is available under a retainer.
14. Open-Source Disclosures
The following open-source libraries and frameworks are expected to be used in this project:
| Library / Framework | Licence | Role |
|---|---|---|
| [e.g., FastAPI] | [e.g., MIT] | [e.g., API framework] |
| [e.g., SQLAlchemy / Prisma] | [e.g., MIT] | [e.g., ORM / database layer] |
| [e.g., Pydantic] | [e.g., MIT] | [e.g., Data validation] |
| [Additional dependencies as identified during development] |
A complete bill of materials will be provided with the final Deliverables. See MSA Section 16 for open-source licence obligations.
15. Signatures
By signing (or confirming by email) below, both parties agree to the scope, milestones, payment schedule, and terms set out in this SOW, and agree that this SOW is incorporated into and governed by the Networkz Master Services Agreement.
Signature Block (to be completed on execution)
For and on behalf of NETWORKZ:
Name: ___________________________
Title: Proprietor
Date: ___________________________
Signature: ______________________
For and on behalf of [Client Name]:
Name: ___________________________
Title: ___________________________
Date: ___________________________
Signature: ______________________