CabCode — Statement of Work
SoW Reference: SOW-_______________ Effective Date: _______________ Associated PSA Date: _______________
This Statement of Work ("SoW") is entered into pursuant to the Professional Services Agreement dated PSA Date (the "Agreement") between:
CabCode (operated by Ambisaw Ltd) Ambisaw Ltd, c/o Elco, 24 Church Street, Rickmansworth, WD3 1DD info@ambisaw.com 020 3371 7935 ("CabCode" or "Provider")
and
_______________ ("Customer") AddressEmailPhone
All capitalised terms not defined in this SoW have the meanings given to them in the Agreement. In the event of a conflict between this SoW and the Agreement, the Agreement shall prevail unless this SoW expressly states otherwise.
1. Background and Objectives
Describe the business context and what the Customer is looking to achieve. For example:
The Customer wishes to engage CabCode to integrate the CabCode platform with the Customer's existing systems in order to describe objective, e.g., "streamline the flow of design data into the Customer's accounting and project management workflows".
The key objectives of this engagement are:
- Objective 1, e.g., "Integrate CabCode with the Customer's Xero accounting system to enable automatic invoicing from completed design orders"
- Objective 2, e.g., "Integrate CabCode with the Customer's Salesforce CRM to synchronise customer and project records"
- Objective 3, e.g., "Provide training to the Customer's team on the integrated workflows"
2. Scope of Professional Services
2.1 In-Scope Services
Describe the specific work to be performed. Be as detailed as possible.
| Ref | Service Description | Details |
|---|---|---|
| 2.1.1 | e.g., Discovery and requirements gathering | e.g., Workshops with Customer's finance and operations teams to document integration requirements, data mappings, and workflow specifications |
| 2.1.2 | e.g., Xero integration — development | e.g., Build API integration between CabCode and Customer's Xero instance to enable automatic creation of invoices, synchronisation of payment status, and reconciliation of accounts |
| 2.1.3 | e.g., Salesforce integration — development | e.g., Build API integration between CabCode and Customer's Salesforce instance to synchronise customer records, project data, and order status |
| 2.1.4 | e.g., Testing and quality assurance | e.g., End-to-end testing of all integrations in a staging environment, including data integrity checks and error handling validation |
| 2.1.5 | e.g., Deployment and go-live support | e.g., Deployment of integrations to production, monitoring during initial go-live period, and on-call support for 5 business days post-launch |
| 2.1.6 | e.g., Training and documentation | e.g., Up to 2 training sessions (remote) for Customer's team, plus written user guide for the integrated workflows |
2.2 Out-of-Scope
The following items are expressly outside the scope of this SoW. Any request for out-of-scope work shall be managed through the change control process in Section 5 of the Agreement.
- e.g., Any changes to the Customer's Xero or Salesforce configuration beyond what is required for the integration
- e.g., Data cleansing or migration of historical records
- e.g., Development of custom reports or dashboards within Xero or Salesforce
- e.g., Ongoing maintenance or support beyond the post-launch period specified above
2.3 Assumptions
This SoW is based on the following assumptions. If any assumption proves incorrect, CabCode may submit a change request to adjust the scope, timeline, or fees accordingly.
- e.g., The Customer has active, appropriately licensed Xero and Salesforce accounts with API access enabled
- e.g., The Customer will provide a dedicated staging/sandbox environment for each third-party system for testing purposes
- e.g., The Customer's systems are running current, supported versions and are accessible via standard APIs
- e.g., The Customer will make its designated point of contact and relevant team members available for workshops and testing within the agreed timeline
3. Deliverables
| Ref | Deliverable | Description | Acceptance Criteria |
|---|---|---|---|
| D1 | e.g., Requirements specification | e.g., Document detailing integration requirements, data mappings, and workflow designs, approved by Customer | e.g., Written sign-off by Customer's project lead |
| D2 | e.g., Xero integration | e.g., Working API integration between CabCode and Xero, deployed to production | e.g., Successful completion of agreed test cases in staging; invoices created accurately in Xero from CabCode orders |
| D3 | e.g., Salesforce integration | e.g., Working API integration between CabCode and Salesforce, deployed to production | e.g., Successful completion of agreed test cases in staging; customer and project records synchronised accurately |
| D4 | e.g., User guide and training | e.g., Written user guide plus 2 remote training sessions delivered | e.g., User guide delivered; training sessions completed |
Acceptance of Deliverables shall be governed by Section 7 of the Agreement.
4. Timeline and Milestones
| Milestone | Target Date | Dependencies |
|---|---|---|
| e.g., Project kick-off | Date | e.g., Signed SoW and receipt of deposit |
| e.g., Requirements sign-off (D1) | Date | e.g., Completion of discovery workshops |
| e.g., Xero integration complete (D2) | Date | e.g., Requirements sign-off; Xero sandbox access provided |
| e.g., Salesforce integration complete (D3) | Date | e.g., Requirements sign-off; Salesforce sandbox access provided |
| e.g., User acceptance testing | Date | e.g., All integrations deployed to staging |
| e.g., Go-live and deployment | Date | e.g., Successful UAT sign-off |
| e.g., Training and handover (D4) | Date | e.g., Go-live complete |
| e.g., Post-launch support period ends | Date | e.g., 5 business days after go-live |
Target dates are estimates and are subject to the Customer meeting its obligations under Section 4 of the Agreement and the assumptions in Section 2.3 of this SoW.
5. Fees and Payment
5.1 Fee Structure
Select and complete the applicable fee structure. Delete the others.
Option A — Fixed Price:
| Item | Fee (excl. VAT) |
|---|---|
| e.g., Discovery and requirements | £___________ |
| e.g., Xero integration | £___________ |
| e.g., Salesforce integration | £___________ |
| e.g., Testing and deployment | £___________ |
| e.g., Training and documentation | £___________ |
| Total | £___________ |
Option B — Time and Materials:
| Role | Day Rate (excl. VAT) | Estimated Days |
|---|---|---|
| e.g., Integration Architect | £___________ | n |
| e.g., Developer | £___________ | n |
| e.g., Project Manager | £___________ | n |
| Estimated Total | £___________ |
Time-and-materials fees shall be invoiced based on actual time recorded. The estimated total is provided for budgeting purposes only and is not a cap unless expressly stated.
5.2 Payment Schedule
| Payment | Amount | Due Date / Trigger |
|---|---|---|
| e.g., Deposit | e.g., 30% of total | e.g., Upon signing this SoW |
| e.g., Milestone payment | e.g., 40% of total | e.g., Upon completion of integrations (D2, D3) |
| e.g., Final payment | e.g., 30% of total | e.g., Upon go-live and acceptance of all Deliverables |
5.3 Expenses
e.g., No expenses are anticipated for this engagement. Any expenses must be pre-approved in writing by the Customer.
5.4 Additional Terms
All fees are exclusive of VAT, which shall be charged at the prevailing rate. Payment terms are as set out in Section 6 of the Agreement.
6. Customer Responsibilities
In addition to the Customer's obligations in Section 4 of the Agreement, the Customer shall:
- e.g., Provide API credentials and sandbox access to Xero and Salesforce within 5 business days of project kick-off
- e.g., Make the designated point of contact available for a minimum of 4 hours per week during the engagement
- e.g., Participate in user acceptance testing within the timeframe set out in the timeline
- e.g., Provide timely feedback on Deliverables within the Acceptance Period specified in the Agreement
7. CabCode Project Team
| Role | Name |
|---|---|
| e.g., Project Lead | Name |
| e.g., Integration Developer | Name |
| e.g., Account Manager | Name |
8. Customer Project Team
| Role | Name | |
|---|---|---|
| e.g., Project Sponsor | Name | |
| e.g., Primary Contact | Name | |
| e.g., IT Lead / Systems Admin | Name |
9. Intellectual Property Reminder
As set out in Section 8 of the Agreement, all integration code, connectors, APIs, configurations, scripts, custom modules, and related materials developed by CabCode under this SoW are and shall remain the exclusive intellectual property of Ambisaw Ltd. The Customer receives a licence to use the Deliverables in accordance with Section 8.3 of the Agreement.
10. Additional Terms
Include any SoW-specific terms not covered above, or write "None."
Signatures
By signing below, each Party agrees to this Statement of Work, which is governed by the terms of the Professional Services Agreement dated PSA Date.
CabCode (Ambisaw Ltd)
Signature: ___________________________ Name: ___________________________ Title: ___________________________ Date: ___________________________
Customer
Signature: ___________________________ Name: ___________________________ Title: ___________________________ Date: ___________________________
This document is a template and does not constitute legal advice. Consult a qualified attorney to tailor this statement of work to your specific engagement.
CabCode® is a registered trademark in the United Kingdom, owned by Ambisaw Ltd. All rights reserved.