Statement of Work — Template
Document ID: WBL-SOW-[PROJECT-ID]-v1.0 SOW Date: [DATE] Incorporated into MSA: WBL-MSA-v1.0 (dated [MSA DATE])
This Statement of Work ("SOW") is entered into by the Parties identified below and is incorporated by reference into the Master Service Agreement ("MSA") previously executed between the Parties. Capitalized terms used but not defined herein have the meanings given in the MSA. In the event of conflict between this SOW and the MSA, this SOW governs for the purposes of this Project.
Parties
| Agency | Webility |
| Client | [CLIENT LEGAL NAME] |
| Client Contact | [Name, Title, Email, Phone] |
| Agency Project Lead | [Name, Title, Email] |
| SOW Reference | WBL-SOW-[PROJECT-ID]-v1.0 |
| MSA Reference | WBL-MSA-v1.0 |
Table of Contents
- Project Overview
- Scope of Services
- Deliverables
- Exclusions
- Project Timeline & Milestones
- Client Responsibilities
- Assumptions
- Acceptance Criteria & Review Process
- Fees & Payment Schedule
- Change Order Process
- Project Contacts & Communication
- Special Terms
- Sign-Off
1. Project Overview
| Field | Details |
|---|---|
| Project Name | [PROJECT NAME] |
| Project Type | ☐ Web Design & Development ☐ Branding & Identity ☐ AI & Automation ☐ Maintenance / Retainer ☐ Other: ________ |
| Project Summary | [1–3 sentence description of what this project is and its primary goal] |
| Business Objective | [What the Client aims to achieve — e.g., "Launch a new e-commerce storefront targeting B2B buyers in North America, with a focus on lead generation and product discovery."] |
| Primary Success Metric | [How the Client and Agency will know this project was successful — e.g., site goes live on time, design approved by stakeholders, automation reduces manual processing by X%] |
| Estimated Start Date | [DATE] |
| Estimated Completion Date | [DATE] |
2. Scope of Services
The Agency shall perform the following services for this Project:
2.1 [Service Area — e.g., Discovery & Strategy]
Delete or rename service areas to match the actual project type.
- [Service task 1 — be specific]
- [Service task 2]
- [Service task 3]
2.2 [Service Area — e.g., Design]
- [Task 1]
- [Task 2]
2.3 [Service Area — e.g., Development]
- [Task 1]
- [Task 2]
2.4 [Service Area — e.g., Testing & QA]
- [Task 1]
- [Task 2]
2.5 [Service Area — e.g., Launch & Deployment]
- [Task 1]
- [Task 2]
Example: Web Design & Development Project
Replace the section above with this example content for a standard website project. Delete this block when using.
2.1 Discovery & Strategy
- Kickoff meeting and project brief review
- Competitor and market research (up to 3 competitors)
- Sitemap and information architecture definition
- Technical platform recommendation
2.2 UI/UX Design
- Wireframes for up to [X] page templates (desktop)
- High-fidelity mockups for up to [X] page templates (desktop + mobile)
- Up to [X] rounds of design revisions per deliverable
- Design system / component library (colors, typography, buttons, form elements)
- Handoff to development via Figma
2.3 Development
- Next.js / WordPress / [PLATFORM] implementation
- Responsive layout for desktop, tablet, and mobile
- CMS integration and content entry for up to [X] pages
- Contact form with email notification
- Basic SEO setup: meta tags, Open Graph, sitemap, robots.txt
- Google Analytics 4 or equivalent tracking setup
- Integration with: [list third-party tools — e.g., CRM, booking system, newsletter]
2.4 Testing & Quality Assurance
- Cross-browser testing (Chrome, Firefox, Safari, Edge — latest 2 versions)
- Mobile device testing (iOS Safari, Android Chrome)
- Performance audit (Lighthouse score target: 85+)
- Accessibility review (WCAG 2.1 AA — critical violations)
- Broken link and form submission testing
2.5 Launch & Deployment
- Deployment to production server / hosting platform
- DNS propagation support
- SSL certificate setup
- Post-launch monitoring for [X] business days
- Handover documentation and credential transfer
3. Deliverables
The following specific outputs will be delivered to the Client upon completion of the relevant project phase:
| # | Deliverable | Description | Format | Due Phase |
|---|---|---|---|---|
| D-01 | [Deliverable Name] | [Brief description] | [PDF / Figma / Git / Live URL / etc.] | Phase [X] |
| D-02 | [Deliverable Name] | [Brief description] | [Format] | Phase [X] |
| D-03 | [Deliverable Name] | [Brief description] | [Format] | Phase [X] |
| D-04 | [Deliverable Name] | [Brief description] | [Format] | Phase [X] |
| D-05 | [Deliverable Name] | [Brief description] | [Format] | Phase [X] |
Note: Deliverables listed here represent the complete contracted output. Any additional outputs not listed above are considered out-of-scope and require a Change Order.
4. Exclusions (Out of Scope)
The following are explicitly excluded from this SOW unless covered by a signed Change Order:
- Copywriting or content creation beyond what is specified above
- Photography, video production, or custom illustration
- Paid advertising campaigns or ad spend management
- Search engine optimization (beyond basic on-page SEO)
- Third-party software licensing fees
- Ongoing hosting, maintenance, or support beyond the post-launch period
- Custom functionality beyond what is described in Section 2
- Migration of existing content beyond [X] pages/items
- Training sessions beyond [X] hours
- Translation or multilingual content
- [Other specific exclusion relevant to this project]
Any request for excluded services will be addressed through the Change Order process (Section 10).
5. Project Timeline & Milestones
All dates are estimates. Final dates are confirmed at kickoff and may be adjusted for Client delays in accordance with MSA Section 7.2.
| Phase | Description | Estimated Start | Estimated End | Client Action Required |
|---|---|---|---|---|
| Phase 1 | [Phase Name — e.g., Discovery & Strategy] | [DATE] | [DATE] | Kickoff meeting, content brief approval |
| Phase 2 | [Phase Name — e.g., Design] | [DATE] | [DATE] | Approve wireframes and design mockups |
| Phase 3 | [Phase Name — e.g., Development] | [DATE] | [DATE] | Provide content, credentials, integrations |
| Phase 4 | [Phase Name — e.g., Testing & Revisions] | [DATE] | [DATE] | Review and sign off on staging site |
| Phase 5 | [Phase Name — e.g., Launch] | [DATE] | [DATE] | DNS access, written launch approval |
5.1 Timeline Conditions
(a) Client Review Windows: The Client has [5] business days to review and respond to each submission unless otherwise specified in the timeline above. Delays in Client responses will shift all subsequent dates accordingly.
(b) Agency Delay: If the Agency anticipates a delay to the timeline through no fault of the Client, the Agency will notify the Client in writing within [3] business days.
(c) Timeline Reset: If the Project is paused due to Client inaction for more than [15] consecutive business days, the timeline may be renegotiated and the Agency may bill for re-mobilization.
6. Client Responsibilities
The Client must provide the following for the Project to proceed on schedule:
6.1 Before Kickoff
- Signed MSA and this SOW
- Payment of deposit (see Section 9)
- Access to: [list — e.g., existing website, hosting account, domain registrar, brand assets]
- Brand guidelines, logo files (vector format), and approved color palette
- List of key stakeholders and their decision-making authority
6.2 During the Project
- Written approval at each phase gate before the next phase begins
- Provide all text content for [X] pages by [DATE]
- Provide high-resolution photography or image rights (if not included in scope)
- Timely access to: [e.g., third-party APIs, CRM credentials, database]
- Attendance at scheduled review calls (minimum [X] designated reviewers)
- Consolidate feedback into a single document per round (not multiple rounds of separate feedback from different stakeholders)
6.3 At Launch
- Written sign-off on staging environment before go-live
- DNS transfer/update (Client responsibility unless hosting is managed by Agency)
- Final payment cleared before launch (see Section 9)
7. Assumptions
This SOW is based on the following assumptions. If any of these assumptions prove incorrect, a Change Order may be required:
- The Client's primary language for content and the deliverables is [LANGUAGE].
- The project involves [X] unique page designs (not counting content-only variations).
- The Client will supply all required text content in a ready-to-use format.
- Third-party APIs and platforms referenced in scope are available, functional, and appropriately documented.
- The existing hosting environment (if applicable) is compatible with the proposed tech stack.
- rounds of revisions are included per deliverable as specified in Section 8. Additional rounds are billable.
- The Client has the legal right to use all materials provided to the Agency.
- [Add project-specific assumptions here]
8. Acceptance Criteria & Review Process
8.1 Review Rounds
Each deliverable includes the following number of revision rounds:
| Deliverable Type | Included Revision Rounds |
|---|---|
| Wireframes / UX | [X] rounds |
| Visual Design Mockups | [X] rounds |
| Development / Functional Build | [X] rounds |
| Copywriting / Content | [X] rounds |
| [Other] | [X] rounds |
A "revision round" means one consolidated set of feedback submitted in writing. Each revision round results in one revised version. Additional rounds beyond what is included are billed at the Agency's standard hourly rate of [RATE]/hr.
8.2 Acceptance Process
- The Agency submits a deliverable and notifies the Client in writing.
- The Client has [5] business days to review and provide:
- Written approval ("Accepted"), or
- Written feedback with specific, actionable changes requested within scope.
- If the Client does not respond within [5] business days, the deliverable shall be deemed accepted.
- After the included revision rounds are exhausted, the Client shall formally accept the deliverable before the next phase begins.
8.3 Acceptance of Final Deliverables
Final acceptance ("Project Completion") occurs when:
(a) All deliverables listed in Section 3 have been formally accepted in writing by the Client, or deemed accepted per Section 8.2; and (b) All outstanding payments have been received by the Agency.
Upon Project Completion, the IP assignment described in MSA Section 5.4 takes effect.
8.4 Post-Acceptance Changes
Changes requested after a deliverable has been accepted are out-of-scope and require a Change Order.
9. Fees & Payment Schedule
All amounts are in [CURRENCY] and exclude applicable taxes.
9.1 Project Fee Summary
| Item | Amount |
|---|---|
| Total Project Fee | [AMOUNT] |
| Deposit (due on signing) | [50% — AMOUNT] |
| Remaining Balance | [50% — AMOUNT] |
9.2 Milestone Payment Schedule
| Payment | Due Date / Trigger | Amount |
|---|---|---|
| Deposit | Upon signing this SOW — non-refundable | [AMOUNT] |
| Milestone 2 | Upon Client approval of [Phase 2 deliverable] | [AMOUNT] |
| Milestone 3 | Upon Client approval of [Phase 3 deliverable] | [AMOUNT] |
| Final Payment | Before launch / final delivery | [AMOUNT] |
| Total | [TOTAL] |
Milestone payments must be received before the Agency proceeds to the next phase.
9.3 Retainer / Ongoing Services (if applicable)
| Service | Billing Cycle | Monthly Amount |
|---|---|---|
| [Service — e.g., Maintenance Plan] | Monthly | [AMOUNT] |
| [Service] | Monthly | [AMOUNT] |
Retainer services are billed on the 1st of each month and payable within 15 days.
9.4 Hourly Rate for Additional Work
Work outside the scope of this SOW, if approved via Change Order, shall be billed at:
[HOURLY RATE]/hr for [development / design / strategy — specify as applicable]
9.5 Third-Party Costs
Third-party costs (hosting, domain registration, stock images, fonts, plugins, APIs, software licenses) are not included in the project fee unless explicitly listed above. Such costs will be estimated and pre-approved before being incurred, and invoiced at cost + 10% administration fee.
10. Change Order Process
10.1 What Requires a Change Order
A Change Order is required whenever the Client requests:
- Any work not described in Section 2 (Scope of Services)
- Additional deliverables beyond those listed in Section 3
- A significant change in direction after a deliverable has been approved
- A reduction in scope (which may affect payment terms without eliminating deposit obligations)
- An acceleration of the timeline that requires overtime or resource reallocation
10.2 Change Order Procedure
- Either Party may initiate a change request in writing.
- The Agency will assess the impact on timeline, fees, and scope and provide a written Change Order estimate within [5] business days.
- The Change Order must be approved and signed by both Parties before the Agency acts on the change.
- Verbal approvals or approvals by email are not sufficient to authorize a Change Order unless a formal Change Order document is subsequently signed.
10.3 Emergency Work
If the Client requests urgent work that cannot wait for a formal Change Order (e.g., a critical production issue), the Agency may proceed with written email confirmation from the Client, provided a formal Change Order is signed within [3] business days.
11. Project Contacts & Communication
11.1 Primary Contacts
| Role | Name | Phone | Availability | |
|---|---|---|---|---|
| Agency Project Lead | [Name] | [Email] | [Phone] | [Hours] |
| Client Primary Contact | [Name] | [Email] | [Phone] | [Hours] |
| Client Billing Contact | [Name] | [Email] | — | — |
| Client Technical Contact | [Name] | [Email] | [Phone] | [Hours] |
11.2 Communication Standards
- Primary channel: [e.g., Email / Slack / Project Management Tool]
- Weekly status update: Every [DAY] via [email / call / shared status doc]
- Response time (Agency): Within [1] business day during business hours
- Response time (Client): Within [2] business days for routine items; [5] business days for deliverable reviews
- Escalation: If either Party cannot reach their counterpart for more than [3] business days, escalate to [Name / email]
11.3 Project Management Tool
All project tasks, timelines, and deliverable tracking shall be managed in: [Tool — e.g., Notion / ClickUp / Linear / Asana] Client access link: [URL]
12. Special Terms (If Applicable)
Use this section for any project-specific terms not covered above. Delete this section if unused.
12.1 Hosting & Ongoing Support
Upon project completion, the Client may elect to continue with a Webility [Maintenance Plan / Hosting Plan] at a monthly rate of [AMOUNT], governed by a separate Maintenance & Support Agreement. If the Client does not elect ongoing support, Webility's post-launch responsibility is limited to the warranty period defined in the Handover document.
12.2 Data & AI-Specific Terms
(Include for AI/automation projects)
- Client Data used to configure, train, or test AI systems remains the property of the Client.
- The Agency will not use Client Data to train AI models for use with other clients.
- Any AI-generated outputs are provided as-is and are not guaranteed to be free from errors or bias.
12.3 Confidentiality of Project
(Include if the project is confidential or the Client requests NDA-level confidentiality) This project and all related materials are subject to the confidentiality terms in MSA Section 6. The Agency agrees that [specific terms — e.g., the existence of this project / the Client's identity] shall not be disclosed publicly or referenced in Agency marketing without prior written consent from the Client.
12.4 Subcontracting Notice
The Agency may engage the following known subcontractors for this Project:
- [Name / Role — e.g., "Freelance Illustrator for custom icons"]
- [Name / Role]
13. Sign-Off
By signing below, the Parties confirm that they have read and understood this Statement of Work, that it accurately reflects the agreed Project scope and terms, and that it is incorporated into and governed by the Master Service Agreement (WBL-MSA-v1.0).
Webility LLC (Agency)
Signature: ___________________________
Name: ___________________________
Title: ___________________________
Date: ___________________________
[CLIENT LEGAL NAME] (Client)
Signature: ___________________________
Name: ___________________________
Title: ___________________________
Date: ___________________________
Post-Signature Checklist (Agency Internal Use — Remove Before Sending)
- Deposit invoice sent
- Project added to Agency project management tool
- Kickoff meeting scheduled
- Technical access request sent to Client
- Project folder created with NDA/MSA/SOW copies
- Project lead notified and timeline confirmed
Webility — WBL-SOW-[PROJECT-ID]-v1.0 | This template requires legal review before use.