Statement of Work — Template

Template Instructions: Replace every [BRACKETED] field with the actual value before sending to Client. Remove this instruction block and any unused optional sections before execution. All bracketed fields are required unless marked "(optional)."

Document Information

| Field | Value | |---------------------|------------------------------------| | SOW Number | SOW-[YEAR]-[NUMBER] (e.g. SOW-2026-001) | | Effective Date | [EFFECTIVE DATE] | | Version | 1.0 | | Master Agreement| This SOW is governed by the Master Services Agreement between Studio and Client, effective [MSA EFFECTIVE DATE] ("MSA"). Capitalized terms used but not defined here have the meanings given in the MSA. |

1. Parties

Studio: Sage Ideas LLC Orlando, Florida, USA sage@sageideas.dev sageideas.dev Primary Contact: [STUDIO CONTACT NAME], [STUDIO CONTACT TITLE]

Client: [CLIENT LEGAL ENTITY NAME] [CLIENT ADDRESS] [CLIENT EMAIL] Primary Contact: [CLIENT CONTACT NAME], [CLIENT CONTACT TITLE] Billing Contact: [BILLING CONTACT NAME AND EMAIL] (if different)

2. Project Name and Description

Project Name: [PROJECT NAME]

Project Description: [2–5 sentence plain-English description of the project. What are we building, for whom, and why? Example: "A customer-facing self-service portal allowing [Client]'s enterprise clients to manage subscriptions, download invoices, and submit support tickets. The portal will integrate with [Client]'s existing Salesforce CRM and Stripe billing infrastructure."]

Business Goal: [What outcome does Client want to achieve? Example: "Reduce inbound support ticket volume by 40% by giving clients direct access to account management."]

3. Scope of Work

3.1 Deliverables

The following deliverables are included in this SOW:

| # | Deliverable | Description | Format / Notes | |----|--------------------------------------|-------------------------------------------------------------------|-----------------------------------| | 1 | [DELIVERABLE NAME] | [What it is and what it does] | [File format, tech stack, etc.] | | 2 | [DELIVERABLE NAME] | [What it is and what it does] | [File format, tech stack, etc.] | | 3 | [DELIVERABLE NAME] | [What it is and what it does] | [File format, tech stack, etc.] | | 4 | [DELIVERABLE NAME] | [What it is and what it does] | [File format, tech stack, etc.] | | 5 | Documentation & Handoff Package | Technical documentation, deployment guide, env variable reference, and a recorded walkthrough video | Markdown + Loom video |

Add or remove rows as needed.

3.2 Technical Specifications

[Optional: Define the tech stack, platforms, or constraints. Example:]

• Frontend: [e.g., Next.js 14, TypeScript, Tailwind CSS]
• Backend: [e.g., Node.js, Supabase, Prisma]
• Infrastructure: [e.g., Vercel, AWS, Railway]
• Integrations: [e.g., Stripe, Cal.com, Resend, Salesforce]
• Source control: [e.g., GitHub — private repository, Client receives ownership on final payment]
• Browser support: [e.g., latest 2 versions of Chrome, Firefox, Safari, Edge]

4. Timeline and Milestones

Estimated Start Date: [START DATE] Estimated Completion Date: [END DATE]

All dates are estimates contingent on timely Client cooperation per Section 3 of the MSA. Schedule may shift if Client-provided feedback, approvals, or content are delayed.

| Milestone | Description | Target Date | |--------------------------------|----------------------------------------------------|----------------------| | M1 — Kickoff | Kickoff call, confirm scope, access credentials | [DATE] | | M2 — [MILESTONE NAME] | [Brief description of what's complete] | [DATE] | | M3 — [MILESTONE NAME] | [Brief description of what's complete] | [DATE] | | M4 — [MILESTONE NAME] | [Brief description of what's complete] | [DATE] | | M5 — Client Review & Feedback | Client review period; feedback due within 10 business days | [DATE] | | M6 — Revisions Complete | Studio incorporates approved feedback | [DATE] | | M7 — Final Delivery & Handoff | All Deliverables delivered; documentation complete | [DATE] |

Add or remove milestones as appropriate for the project.

5. Fees and Payment Schedule

Engagement Type: [Fixed-Price / Time-and-Materials / Retainer — choose one]

5.1 Fixed-Price (if applicable)

Total Project Fee: $[TOTAL AMOUNT] USD

| Invoice | Amount | Due | |----------------------|---------------------|------------------------------------------------------------| | Kickoff Deposit (25%) | $[25% OF TOTAL] | Due before work begins. Non-refundable once Studio commences work. | | Milestone 3 Invoice | $[AMOUNT] | Due within 30 days of M3 delivery and acceptance | | Milestone 5 Invoice | $[AMOUNT] | Due within 30 days of M5 delivery and acceptance | | Final Invoice | $[REMAINING BALANCE] | Due within 30 days of final delivery and acceptance |

All invoices are payable within Net 30 of invoice date. Overdue invoices accrue interest at 1.5%/month.

5.2 Time-and-Materials (if applicable)

Rate: $[HOURLY RATE] USD per hour

Estimated Hours: [LOW]–[HIGH] hours

Not-to-Exceed Budget: $[CAP AMOUNT] USD (Studio will notify Client upon reaching 80% of budget)

Invoices are issued [weekly / bi-weekly / monthly] for hours worked. Invoices are due within Net 30.

5.3 Retainer (if applicable)

Monthly Retainer Fee: $[MONTHLY AMOUNT] USD

Hours Included: [NUMBER] hours per month

Overage Rate: $[HOURLY RATE] USD per hour for hours exceeding the monthly allotment

Billing Cycle: Invoiced on the [1st / 15th] of each month, due Net 30.

6. Acceptance Criteria

Deliverables are accepted when they materially meet the following criteria:

| Deliverable | Acceptance Criteria | |-------------------------------|-------------------------------------------------------------------------------------| | [DELIVERABLE 1] | [Specific, measurable criteria — e.g., "All pages load under 3 seconds on desktop Chrome LCP test"] | | [DELIVERABLE 2] | [Criteria — e.g., "Form submissions deliver email notifications within 30 seconds"] | | [DELIVERABLE 3] | [Criteria — e.g., "All unit tests pass with ≥80% code coverage"] | | Documentation Package | Documentation accurately describes all key functions, API endpoints, and deployment steps; walkthrough video runs 15–30 minutes |

Client has 10 business days to accept or reject each Deliverable per MSA Section 4.2. Non-response within 10 business days constitutes acceptance. Rejections must specify in writing how a Deliverable fails to meet the criteria above.

7. Out of Scope

The following are explicitly not included in this SOW. Any of these items may be added via a written Change Order:

• [ITEM 1 — e.g., "Ongoing hosting or infrastructure management after handoff"]
• [ITEM 2 — e.g., "Content creation, copywriting, or photography"]
• [ITEM 3 — e.g., "Third-party license fees or API subscription costs"]
• [ITEM 4 — e.g., "User training sessions beyond the handoff walkthrough"]
• [ITEM 5 — e.g., "Mobile native app (iOS/Android) development"]
• [ITEM 6 — e.g., "SEO, paid advertising, or marketing services"]
• Bug fixes or changes to portions of the codebase not authored by Studio in this engagement

8. Assumptions

Studio has scoped this project based on the following assumptions. If any assumption proves incorrect, Studio will notify Client promptly, and the Parties will negotiate a Change Order to address the impact on scope, timeline, or fees.

• [ASSUMPTION 1 — e.g., "Client will provide all written content and imagery at least 10 business days before M3"]
• [ASSUMPTION 2 — e.g., "Client has valid licenses for all existing systems Studio will integrate with"]
• [ASSUMPTION 3 — e.g., "Client's existing API endpoints are documented and functional prior to integration work"]
• [ASSUMPTION 4 — e.g., "A maximum of 2 rounds of revisions per deliverable is included; additional rounds are billed at the standard hourly rate"]
• [ASSUMPTION 5 — e.g., "Client will designate a single point of contact with decision-making authority"]
• [ASSUMPTION 6 — e.g., "Studio will have read/write access to all necessary credentials, repos, and systems within 3 business days of Kickoff"]

9. Client Responsibilities

Client agrees to fulfill the following responsibilities. Delays attributable to Client may extend the project timeline without penalty to Studio:

• Designate a primary point of contact authorized to approve deliverables
• Respond to requests for feedback, approvals, and content within 5 business days (or as specified in individual milestones)
• Provide access to all necessary credentials, APIs, staging environments, and accounts within 3 business days of Kickoff
• Supply all content, copy, and design assets by the dates specified in the timeline
• Conduct Deliverable reviews promptly within the 10-business-day acceptance window
• Notify Studio immediately of any internal stakeholder changes that may affect project requirements

10. Change Orders

All changes to scope, deliverables, timeline, or fees require a written Change Order signed by both parties before Studio implements the change. Studio will provide a Change Order estimate within 5 business days of a written change request. No verbal commitments to scope changes are binding.

Change Orders may be submitted via email and accepted via email confirmation if both parties explicitly agree to the modified scope and fees in writing.

11. Intellectual Property

Assignment

Subject to MSA Section 5, upon receipt of payment in full for this SOW, Studio assigns to Client all Intellectual Property Rights in the Deliverables specifically created for this Project.

Repository Transfer

Upon full payment, Studio will transfer the GitHub repository (or equivalent) to Client or an organization Client designates, remove Studio's access, and deliver all relevant environment variables, credentials, and third-party API key documentation.

Studio Pre-Existing IP

Studio retains ownership of all Pre-Existing IP incorporated into the Deliverables. Client receives a perpetual, non-exclusive license to use that Pre-Existing IP as embedded in the Deliverables per MSA Section 5.3.

Open Source

The following open-source packages are expected to be incorporated under their respective licenses: [LIST MAJOR OSS DEPENDENCIES OR STATE "To be documented in project handoff materials"]

12. Post-Engagement Support

Following final acceptance and delivery, Studio provides a 90-day post-engagement support window at no additional charge, covering:

• Bug fixes in Studio-authored code that do not perform as specified in this SOW
• Clarification on documentation or implementation details
• Minor adjustments within the original scope

Support requests must be submitted to sage@sageideas.dev within the 90-day window. Support does not cover new features, third-party service changes, issues caused by Client-side modifications, or infrastructure failures outside Studio-authored code.

After the 90-day window, ongoing support and maintenance may be engaged under a separate retainer SOW.

13. Governing Agreement

This SOW is governed by the Master Services Agreement between the Parties. In the event of any conflict between this SOW and the MSA, this SOW controls solely with respect to the specific Project defined herein.

14. Approvals

By signing below, both Parties agree to the terms of this Statement of Work and authorize Studio to commence work upon receipt of the kickoff deposit (if applicable).

SAGE IDEAS LLC

Signature: ___________________________

Printed Name: ________________________

Title: ________________________________

Date: _________________________________

[CLIENT LEGAL ENTITY NAME]

Signature: ___________________________

Printed Name: ________________________

Title: ________________________________

Date: _________________________________

This Statement of Work is prepared by Sage Ideas LLC. Questions? Contact sage@sageideas.dev.