Talk to an engineer

Tell us what you are building, or what is costing you more than it should. Your message goes to the people who work on these systems, not into a queue and not to a reseller. We reply within 2 business days, and if your question is technical the reply comes from someone technical.

  • No sales script. The first conversation is a working one.
  • No newsletter. One reply from one person, and nothing you did not ask for.
  • No obligation. If we are the wrong supplier for you, we will say so.

Send us a message

Short on purpose. The more specific you are, the more useful our first reply will be.

This is where our reply will go. Please check it — a mistyped address is the most common reason an answer never arrives.

If you are early and there is no company yet, put what you are calling it.

If nothing fits, choose "Something else" and describe it in the message. Nobody will hold you to this.

We ask because it decides whether a cost analysis is worth your time. Below roughly $10,000 a month the arithmetic usually does not work, and we would rather tell you that now than after a workshop.

Architecture, constraints, deadlines, regulatory position — whatever you can share. If you need an NDA in place before you can describe it, say that in the first line and we will start there.

We reply within 2 business days.

We use what you send us to answer your enquiry and for nothing else. No newsletter, no drip campaign, and your details are not passed to a reseller or sold to anyone. Full detail in the Privacy Policy; company details in our legal notice.

What happens next

Nobody enjoys sending a message into an unknown process. Here is the whole of ours.

1. A person reads it — within 2 business days

Not an auto-responder with a ticket number, and not a qualification call to find out whether you are worth a conversation. Someone who works on the relevant systems reads what you wrote and replies to it. If your message contains a technical question with a short answer, you will often just get the answer.

2. A first conversation, on your terms

A call or a meeting, whichever suits you, with an engineer in the room rather than an account manager reading from a briefing sheet. We will ask what you are running now, what has to be true for the project to work, and what your constraints are — regulatory, commercial and technical. You should arrive with your hardest question. It is the cheapest test either of us will run, and there is no slide deck to sit through first.

3. Whatever proof you need next

Depending on what you are evaluating, the next step is one of these, and all of them come before you commit to anything:

  • A technical deep-dive on the platform or the architecture, with your engineers and ours in the same session.
  • A Proof of Performance session — a live load and stress test on the scenarios you choose, with the results in your hands.
  • A cloud cost analysis — we look at your actual bill and usage and tell you which workloads can move and which should stay exactly where they are.
  • Named references under NDA — we do not publish client names, and we will introduce you to clients in a comparable position once we know what you are evaluating.
  • A written answer to your security questionnaire, question by question.

4. A proposal only when it is worth writing

We write the proposal after the technical picture is clear, not before, because a proposal written from a form submission is a guess with a price on it. And if the honest conclusion is that you should stay where you are, or that another kind of supplier fits you better, that is what you will be told. It costs us a proposal and saves you a project.

Other ways to reach us

Email

[email protected] — the same inbox the form writes to, read by the same people. Use it if you would rather attach a document, or if your compliance team needs the exchange in writing from the start.

LinkedIn

Minimal Code Systems on LinkedIn — for company updates. Enquiries sent as LinkedIn messages are slower than the form, because they arrive in a different inbox.

Registered office

Minimal Code Systems AG
Bahnstrasse 58
8105 Regensdorf
Switzerland

UID CHE-206.432.155 · Full company details on our legal notice.

Visits are by appointment. Our engineering and operations teams work across Zurich, Frankfurt and Istanbul, so tell us where you are and we will arrange the meeting sensibly — in person where it is worth the travel, and remote where it is not.

Why there is no phone number here

We do not publish one. A written first message reaches the engineer who can actually answer it, instead of whoever happens to pick up. Once we are working together you get direct contacts for the people on your account, and for platform-as-a-service customers, operational escalation paths that do not go through a switchboard.

Before you write to us

How quickly will I hear back?

Within 2 business days. Swiss business days, excluding public holidays. If you have a deadline that makes that too slow, say so in the first line of your message and we will work to it.

Do I have to be a large organisation to talk to you?

No. The one threshold on this site is for infrastructure cost work: below roughly $10,000 a month of public cloud spend, a cost analysis usually does not pay for itself, and we would rather tell you that than run a workshop. There is no minimum for anything else — early-stage exchange projects are a normal first conversation.

Can we sign an NDA before we discuss details?

Yes. Say so in the first line of your message and we will sort that out before the technical conversation. Discretion is a large part of what our clients buy, which is also why there are no client logos on this website.

I only want to see the platform. Do I have to fill this in?

Only this form. The live demo is not public — ask for it here, choose "Live demo access", and we send you the link. No sales call. Come back to this page when you have questions the product cannot answer.

What will you do with my details?

Answer your enquiry. That is all. We do not run a newsletter, we do not add you to a nurture sequence, and we do not pass your details to anyone as a lead. The full detail — what we collect, why, how long we keep it and how to have it deleted — is in the Privacy Policy.

Who will actually reply?

Someone who works on the systems you asked about. For technical enquiries that means an engineer, not a sales team relaying questions to one.

Still deciding what you need? Start with Blockchain & FinTech, Cloud & Infrastructure or Business Process & Automation — or write to us anyway and we will point you at the right one.