Bring one critical data flow. Start with operational reality.

Explain what must be delivered or decided, who relies on it and what changes when the result is late, wrong, incomplete or difficult to prove.

List source and target system types, file hand-offs, SQL or transfer steps, quality checks, analytical delivery and any Python or review activity. High-level categories are enough for the first exchange.

Include the important permissions, approvals, retention expectations, incident path and reviewer evidence. Do not send credentials, customer records or confidential architecture in the initial email.

A useful next step can be a capability fit review, synthetic workflow walkthrough or pilot scope with explicit acceptance. No capability or commercial commitment exists until it is confirmed in writing.