How this works
- This is the one document you sign to start an engagement with CCS. Print it or sign electronically.
- It incorporates by reference the Master Services Agreement, the Data Processing Addendum, and — if elected below — the Service Level Agreement, each as published on this SOW's effective date.
- Bracketed fields are filled in per engagement. One SOW per application or project; later projects get their own SOW under the same MSA.
This box is a summary only — the sections below are the order form.
Statement of Work No. [___]
This Statement of Work ("SOW") takes effect on [EFFECTIVE DATE] (the "SOW Effective Date") between Cream City Solutions LLC ("CCS") and:
| Client legal name | [CLIENT LEGAL NAME] |
|---|---|
| Entity type / jurisdiction | [e.g., Manitoba corporation] |
| Address | [CLIENT ADDRESS] |
| Primary contact (name, email, phone) | [CONTACT] |
| Notice email for legal notices | [EMAIL] |
This SOW is governed by the Master Services Agreement (version [MSA v___]) published at creamcity-solutions.com/legal/msa, the Data Processing Addendum (version [DPA v___]) published at creamcity-solutions.com/legal/dpa, and — if elected in Section 6 — the Service Level Agreement (version [SLA v___]) published at creamcity-solutions.com/legal/sla, each as published on the SOW Effective Date, which the Client accepts by signing this SOW. The dates on the signature lines below do not change the governing versions. Each party should retain (or attach to its copy of this SOW) the incorporated documents as of the SOW Effective Date; CCS preserves all published versions and provides them on request. In a conflict, MSA Section 3.2 (order of precedence) applies.
1. The application
| Application name | [NAME] |
|---|---|
| One-line description | [What it does, for whom] |
2. Scope
Included (the initial build / the subscribed service covers):
- [Feature or module 1]
- [Feature or module 2]
- [Feature or module 3 — add rows as needed]
Explicitly out of scope (quoted separately if wanted later):
- [e.g., mobile app, third-party integration X, data migration beyond Y records]
Assumptions. This SOW's scope, fees, and timeline assume: [data provided in an agreed format; third-party APIs function as documented; up to N users; Client decisions within 5 business days — edit as needed]. If an assumption proves wrong, scope, fees, or timeline are adjusted by written change request (MSA Section 3.4).
Data migration. [Not included. / CCS will migrate up to N records from SOURCE; the Client is responsible for the accuracy and completeness of the source data and will verify migrated data before go-live.]
3. Hosting model
Check one (see MSA Section 6). If no box is checked, CCS-hosted applies:
- ☐ CCS-hosted (default) — CCS runs the Application on its infrastructure and is responsible for hosting operation and security.
- ☐ Client-hosted — the Application runs in the Client's own cloud accounts: [describe accounts/platforms]. The Client provisions, secures, and pays for that infrastructure.
4. Fees and payment
| One-time implementation / setup fee | $[AMOUNT] — billed [on signing / 50% on signing, 50% at launch / milestones below]. This fee is for configuration and deployment of CCS's Platform (see MSA Sections 4.2 and 5.1). |
|---|---|
| Monthly subscription | $[AMOUNT] per month, flat — billed monthly in advance, starting [at launch / on DATE]. Adjustable only as MSA Section 4.7 provides. |
| Currency & payment method | All fees in [U.S. dollars (USD) / Canadian dollars (CAD)], paid by [ACH / wire / credit card]; bank and FX fees are the Client's. |
| Invoicing | Invoices to [AP EMAIL]. PO number, if required: [___] (absence of a PO does not excuse payment). |
| The subscription includes | Hosting (if CCS-hosted), maintenance, security updates, support (MSA Section 3.5 or the SLA if elected), and minor improvements — individual changes of up to [4] hours of effort, at CCS's reasonable discretion. Major new features or modules are scoped and quoted as separate SOWs or written change requests. |
5. Timeline and acceptance
| Target start | [DATE] |
|---|---|
| Milestones (optional) | [e.g., Working preview — DATE; Pilot with real data — DATE] |
| Target launch | [DATE] |
Dates are good-faith targets, adjusted in writing if scope changes or Client inputs arrive late (MSA Sections 3.3–3.4).
Acceptance. The initial build is accepted when the first of these happens: the Client confirms acceptance in writing; the Client begins using the Application with real business data in production; or the Client does not report a material failure to conform to Section 2 within 10 business days after CCS states in writing that the build is ready. On early termination, CCS is paid for work performed to the termination date (MSA Section 4.2).
6. Service levels and support
Check one. If no box is checked, No SLA applies:
- ☐ The Service Level Agreement published at creamcity-solutions.com/legal/sla applies to this Application (version locked per the incorporation paragraph above; where it conflicts, it modifies the MSA as stated in the SLA).
- ☐ No SLA — support is provided on a commercially reasonable efforts basis (MSA Section 3.5).
| Support contact (CCS) | [SUPPORT EMAIL — defaults to cmcelven@creamcity-solutions.com] |
|---|
7. Data profile and AI features
| Description of Processing (DPA §2.2) | [Categories of personal information and individuals — e.g., customer contact records; employee records; debtor/enforcement records] |
|---|---|
| Sensitivity tier | ☐ Standard ☐ High-sensitivity (Annex A high-sensitivity measures apply; AI features that send personal information to AI Sub-processors are enabled only if listed below) |
| AI-assisted features (DPA §2.5) | [None. / List features and the data categories each sends to which AI Sub-processor.] |
8. Client responsibilities
- A primary point of contact empowered to make decisions and give timely feedback.
- Content, branding, data, and third-party account access the build needs (accounts the Client connects are Client-Connected Services — MSA Section 6.3).
- [Anything engagement-specific — e.g., sample records, legal text for notices, hardware]
9. Special terms (if any)
[None. / e.g., Canadian data residency elected per DPA Section 6.3; custom ownership of a specific Deliverable per MSA Section 5.4 — identify it exactly and state the assignment.]
10. Signatures
|
Cream City Solutions LLC Signature: ______________________ Name: ______________________ Title: ______________________ Date: ______________________ |
[CLIENT LEGAL NAME] Signature: ______________________ Name: ______________________ Title: ______________________ Date: ______________________ |