How to use this template: Send this to your client before work begins — not after. This document protects both of you. Two variants are included: a standard single-deliverable SOW and a milestone-based variant for longer engagements. Choose the one that fits your project. Delete all
>lines before sending.
Standard SOW — Use when the project is one defined deliverable with a clear end state. Examples: one automation build, one landing page rewrite, one audit.
Milestone-based SOW — Use when the project has multiple phases, each with its own deliverable and approval step. Examples: multi-automation buildout (3–5 automations), full website copy (4+ pages), product setup + onboarding + training sequence.
SCOPE OF WORK
Project: [Project name — specific. E.g., "CRM-to-Proposal Automation, HubSpot + PandaDoc"] Client: [Client name] Provider: [Your name / company name] Date: [Date] Version: 1.0
[Two to four sentences describing what this project is and what it produces. Write it as if explaining to someone who wasn't on the sales call. E.g.: "Flowmatic will build a Make.com automation that connects Northbrook Consulting's HubSpot CRM to PandaDoc. When a deal moves to the 'Proposal Sent' stage in HubSpot, the automation generates a draft proposal in PandaDoc using the client data from the deal record and sends it to the assigned sales rep for review. Northbrook will receive full ownership of the Make.com scenario and a trigger documentation PDF at handoff."]
List every output the client will receive. Same format as your outputs table in Template 4: what it is, what format, when they receive it.
| Deliverable | Format | Delivery date or trigger |
|---|---|---|
| [Deliverable 1] | [Format] | [Date or trigger — e.g., "Day 5 after project start"] |
| [Deliverable 2] | [Format] | [Date or trigger] |
| [Deliverable 3] | [Format] | [Date or trigger] |
Three worked examples:
Flowmatic: