Start with the right problem.
You have an agreed process, an accountable owner, and access to the systems involved.
Where the process is too inconsistent, the source data is unavailable, or nobody can own its decisions, the next step may be to simplify the work first.
Bring the context.
- An agreed scope and acceptance criteria
- Appropriate access through your own accounts
- A named reviewer and representative test cases
Keep credentials and confidential records out of the initial brief. Any access is agreed separately through business-owned accounts.
Something you can inspect.
- 01Agree the data contract and approval gates
- 02Build and test normal, duplicate, and failure paths
- 03Review the pilot together before release
WHAT LEAVES WITH YOU
- Scoped workflow implementation
- Representative failure and replay tests
- Training and handover documentation
Agree what done means.
An agreed workflow, test record, operating notes, and a handover your team can use.
Third-party plans and API usage are separate. Scope, schedule, fees, and any ongoing service are agreed before work starts.