The business case
- Name one repetitive process and the person responsible for it.
- Record current volume and time per item from a sample.
- Identify the cost of a missed, duplicated, or incorrect result.
- Choose a small scope with a useful outcome.
The workflow
- Write the exact trigger and any exclusions.
- List source and destination systems.
- Choose a stable record matching key.
- Assign ownership for each field that changes.
- Define missing-data, duplicate, and conflict handling.
- Name the person who reviews exceptions.
The build agreement
- Document deliverables and out-of-scope work.
- Confirm account access and platform capabilities.
- Separate build fees, subscriptions, usage, and support.
- Agree on acceptance criteria and payment milestones.
The acceptance test
- Verify a normal example at the destination.
- Test duplicate, missing, and unexpected inputs.
- Test a failed connection and safe recovery.
- Confirm no unintended record changes or repeated messages.
- Have the process owner review representative results.
The handover
- Confirm business ownership of accounts and billing.
- Document the workflow and dependency list.
- Explain where failures appear and how to respond.
- Record support coverage, response expectations, and exclusions.
- Agree who approves future changes.