API Integration Statement of Work Template

Count everything. A deliverable a client cannot count is a deliverable a client can expand.

1. 2.1A middleware service on the client's AWS account syncing the 4 objects in the mapping table (Appendix A) between the client's platform and Salesforce Sales Cloud.
2. 2.2Field mappings for up to 85 fields across those objects, with transformations documented in Appendix A.
3. 2.3Bidirectional sync for Accounts and Contacts, one-way sync to Salesforce for Orders and Invoices, at 5-minute intervals.
4. 2.4Error handling: retries with exponential backoff, a dead-letter queue and a daily error digest emailed to the client's admin.
5. 2.5A one-time historical backfill of up to 250,000 records.
6. 2.6Monitoring dashboard, alert rules and an operations runbook.

Name what the engagement does not include. These are the lines your PMs will cite most often.

1. 3.1Systems and objects not in the mapping table.
2. 3.2Salesforce configuration beyond creating the custom fields listed in Appendix A, including flows, Apex and page layouts.
3. 3.3Real-time (sub-minute) sync and event streaming.
4. 3.4Data cleanup, deduplication and merge rules in either system.
5. 3.5Changes required by vendor API version deprecations announced after signature.
6. 3.6Middleware hosting costs and vendor API usage fees.

The mapping table includes one revision round after the technical design review. After sign-off, each added or changed field mapping is estimated individually under Change Control.

Acceptance needs a measurable test and a window. Without both, delivery never formally ends.

1. 5.1A test set of 200 records per object syncs correctly in each supported direction on staging.
2. 5.2Failed records appear in the dead-letter queue and the daily digest with a readable reason.
3. 5.3The backfill completes with a reconciliation report showing counts per object in both systems.

Tie each dependency to a date so a late input has a known effect on the schedule.

1. 6.1The client provides sandbox and production credentials with sufficient API limits for 5-minute sync.
2. 6.2Source data uses stable unique identifiers that can act as external IDs.
3. 6.3A Salesforce administrator on the client side is available for field creation approvals.
4. 6.4Vendor APIs behave as documented at signature.

Any new system, object, field, sync direction or frequency, and any work caused by a vendor API change, is a change. The agency documents the request against the mapping table, estimates hours and cost, and notes any schedule effect within two business days. Work begins after written approval.