Write to
VEWAI LTD

An email is most useful when it describes the situation rather than a proposed solution.

Helpful details include: the process or product the work concerns; what currently happens and where it breaks down; the systems, tools or codebases already in use; who will use the result and what they need to do with it; any constraints that cannot change, such as a platform, a data location or an internal deadline; and what a good outcome would look like in practice.

If part of the work is already specified — a document, a schema, a design file or an existing repository — mentioning that it exists is enough at the first stage. Nothing needs to be finished before a conversation starts.