Define goals and boundaries
Assign an owner, inputs and acceptance criteria. Separate exploratory trials from production delivery.
Begin with a reproducible task and agree on formats, permissions and expected output. Connect incrementally and retain the original workflow as a fallback.
Prepare inputs and access
Validate with sanitized samples first. Keep credentials on the server, use least privilege and document revocation.
Agree on sources, units, time zones, currencies and reporting cadence. Mark missing records explicitly rather than treating missing values as zero.
Execute and review
Start with a limited rollout and retain versions, errors and review records. Fall back to human handling on failure; avoid duplicate side effects.
Compare candidates with the same sanitized samples. Set quality thresholds, time budgets and fallback conditions. Start with a limited rollout and adjust from evidence.
Accept and improve
Check output quality, elapsed time and consumption against agreed samples. Hand over operating instructions and define review cadence and escalation owners.
Assess material changes and retain rollback points. Support hours, response targets and safeguards must be agreed for the project.
This is general practice guidance, not a customer case, API specification or service commitment. Confirm scope, pricing and responsibilities for each project.