Contacts
Start with
a clear message.
We prefer written first contact. A well-described inquiry lets us respond with relevant questions instead of generic answers.
01Inquiry guide
What to include in your email
You do not need a formal specification. A few honest paragraphs covering the points here are usually enough to begin a useful conversation.
- 01
Context
A short description of your organisation and the team that will work with us.
- 02
The problem
What is not working today, who is affected, and how you handle it currently.
- 03
Existing systems
Relevant software, hosting environments, data sources and integrations already in place.
- 04
Desired outcome
What a successful result would look like for you, described in practical terms.
- 05
Constraints
Timelines, budget range, regulatory considerations or internal policies we should know about.
- 06
Decision process
Who is involved in decisions and how you prefer to review progress.
02Good to know
Please avoid sending passwords, access keys or confidential personal data in a first message. If sensitive material is needed later, we will agree on an appropriate way to share it.
Attachments such as screenshots, process diagrams or exported documentation are welcome when they help explain the situation.
Every inquiry is read and considered individually. Response times depend on the volume and complexity of current requests.