/ Contact / direct
Contact
Easiest by email: briefly describe your process or goal. You can attach anonymized samples.
/ Send an inquiry
Get in touch now
Briefly describe what is on your mind. I reply in writing within 1-2 working days with an honest first read. If you prefer to book a slot directly, use the booking widget on the right.
30 min · Intro call
Mike Gölz
Intro call · 30 minutes
In 30 minutes we clarify use case, data context, and constraints. You speak directly with the engineer, not a sales rep. Free and no obligation.
- Duration
- 30 minutes
- Format
- Remote · Zoom
On click, Cal.com (EU-hostable) loads as an iframe. Only then cookies are set and data flows to Cal.com. Before that: zero third-party requests.
/ What the first conversation looks like
From click to honest assessment in under 5 working days.
No sales funnel. No automated calendar widget routing you through seven required fields. Four concrete steps, then you know whether the project is worth doing.
Step 01 · today
You send a short note
Fill the form or write directly. 2-5 minutes of your time. That is all that is needed at this stage.
Step 02 · 1-2 working days
I reply in writing
First read: what I see from your request, which questions I have, whether a call makes sense. Or an honest no with a recommendation if it does not fit my focus.
Step 03 · within 2 weeks
30-minute conversation
Short call (Teams, Meet, Zoom, phone). I ask specifically about the realities: what has grown over time, what cannot leave the building, who maintains it afterward. You talk to the engineer who later builds, not to a sales rep.
Step 04 · within 5 working days
Written assessment
A 2-4-page document: understanding of the current situation, risks, three realistic options with effort and sequence. You can think it through internally, with or without me.
If you want to dive deeper from the start: the 90-minute Deep-Dive workshop (€390 fixed) is the paid version with a written assessment and three realistic options.
/ What helps as a first step
- A short description: which process, which data, which tool.
- If possible: an anonymized sample file or a screenshot (via the email reply).
- A rough timeline if you have one. If not, that is fine too.
- On AI topics: please mention whether cloud is allowed or it must be on-prem.
/ What you do not have to do
- No discovery-call sequences as a warm-up.
- No five-page requirement document. A paragraph is enough.
- No NDA up front. Honestly, most first conversations do not need one.
/ What I promise, and what I do not
YES · ALWAYS
- You speak to the engineer who later builds, not to a sales rep.
- You get an honest read, even when the project does not fit me in the end.
- Your sample data comes back or gets deleted, your call, documented.
NO · NEVER
- No sales funnel, no drip campaign, no 'let us stay in touch' without reason.
- No discovery calls meant to sell you something upfront.
- No data in foreign clouds without your explicit consent.
Classic route if you do not like forms.