Reasons to get in touch
Use this page for an initial question about a digital product, system modernisation, data integration, financial technology process, responsible AI or long term operations. You may also express general interest in professional collaboration. A message does not need a finished architecture or exact feature list. The first task is to understand who has the problem and why the current process is insufficient.
For support under an existing contract, use the channel agreed for that project. This public form is not an emergency security incident line or a place to send credentials. For an initial business inquiry, use the form or chat; verified company details appear below and in the footer.
Writing a useful brief
Begin with the goal in one or two sentences. Explain who will use the result, how work happens now and where delay, errors or risk occur. Add known systems, kinds of data and meaningful constraints such as a deadline or hosting requirement. Say whether you seek a new application, a change to an existing service, a consultation or a continuing team. If you are unsure which fits, that uncertainty is useful information.
A budget or time frame helps identify a realistic first step, though neither is required for an initial message. More useful is how success will be recognised: fewer manual corrections, faster user work, a reliable connection or safer operation. Detailed technical documents can be shared after an appropriate channel is agreed. Do not put customer personal data or passwords in the form.
A short or more detailed message
The short form needs a name, work email, subject and concise description. If useful, add organisation, approximate project stage, timing or links to public material. Optional fields are genuinely optional. The form does not accept files. Its purpose is to start a useful conversation rather than gather as much information as possible before speaking.
After submission, the message is stored securely and an authorised person may reply to the supplied email. We do not promise an automatic email confirmation or a fixed response time. If further details are needed, the next contact should identify specific questions and a safe way to share supporting documents. You may keep a copy of your message for your own records before sending it.
What an initial discussion should achieve
The first discussion should test whether we understand the same problem and who can decide on the next step. An uncertain brief may lead to a short discovery, map of data flows or technical experiment. A known scope may support a proposal with outcomes, assumptions and acceptance rules. If an existing product or smaller process change is a better choice, it should appear in the comparison.
Excoin s.r.o., company ID 29682223, has its registered office at Uzbecká 1463/1, 101 00 Praha 10, Czech Republic. The registered office identifies the company; it does not promise an in person meeting without arrangement. The contact form is intended for an initial project discussion; the Privacy page explains how its data is handled.