What you have
- Data sources, documents or representative examples.
- Current workflow, prototype or system.
- Existing metrics, baseline or expected output.
Contact
Start with the problem, not the tool.
A useful first message describes the current situation, the decision or workflow that needs to improve, and the evidence available to assess it. No need for a polished brief.
What to include
What you want
- The decision, process or user experience that should improve.
- The deliverable you expect from a first engagement.
- How the result will be reviewed or accepted.
Constraints
- Timeline or sequencing requirements.
- Technical environment and integration boundaries.
- Security, privacy and confidentiality requirements.
Who is involved
- Technical owner.
- Business or product stakeholder.
- People who will operate or review the result.
Use LinkedIn for a short introduction or to discuss consultancy and contract work.
Before sharing information
Do not send confidential datasets, credentials, personal data or internal documents in an initial message. A suitable access and confidentiality process should be agreed before sensitive material is reviewed.
A first conversation is for clarifying scope and fit. It does not imply acceptance, availability, a fixed delivery date or a guaranteed outcome.