Correspondence guide / 03
Start with context,
not a specification.
A concise description of the situation can be more useful than a long feature list. Here is what to include when making an inquiry.
Describe what prompted the question
Explain what you are considering, who the idea would affect, and what is unclear. If a current tool or manual arrangement is involved, describe it in general terms. Mention a deadline only when it affects the discussion.
You do not need to decide on an application framework or prepare a design. A short example of the task can help more than a list of technical terms.
Make the assumptions visible
Separate what you know from what you expect. You may know that information is entered twice, while only suspecting that a new tool would be the best response. Both are worth mentioning, but they are different kinds of information.
Explain any practical limits, such as limited time to maintain a tool or a need to keep an existing system. An initial conversation can clarify questions without implying that development is the next step.
Confirm the scope before proceeding
Any potential collaboration needs a direct discussion about suitability, availability, responsibilities, and the intended outcome. This website does not establish an agreement, quote a delivery schedule, or promise a service.
Before sharing confidential material, agree on an appropriate way to exchange it. The public email address is intended for ordinary business inquiries; do not send passwords, access keys, or private customer records.