01 / What people bring me
You don't need to know the right word for it.
02 / Ways to work
From one decision to the whole build.
03 / What it isn't
So you don't waste a message.
- Not an IT service desk: networks, devices, email accounts and help-desk support.
- Not an ERP or SAP rollout partner.
- Not a strategy deck that ends up in a drawer. Every recommendation comes with what to do on Monday.
04 / How it starts
Three steps, no sales process.
You write a few lines
The situation, the decision, or what's stuck. No brief needed.
I reply within two working days
Myself, with a straight read on what I'd do.
If there's a fit, we agree a scope
What I'll do, what you'll get, and when. If you don't need me, I'll say so.
05 / Questions
Questions people ask
What is the difference between IT consulting and technology consulting?
IT consulting usually covers the systems a company runs on: networks, devices, ERP and IT operations. Technology consulting, as I do it, covers the technology decisions that shape the business: what software to build or buy, how to fix a stuck project, how to lead an agency or a team, and where AI pays.
Do you work with small and mid-sized companies, not only startups?
Yes. I work with founders and with owners and leadership teams of small and mid-sized companies, in Munich and across Germany. I work in English.
Do you also build the software?
Yes. Where a decision leads to a build, my team and partners can deliver it, led by me, so you don't need a separate agency. You can also keep your own team or agency and use me for the decisions only.
How does it start?
You send a few lines on the situation. I reply myself within two working days with a straight read, and if there is a fit, we agree a scope. If you don't need me, I say so.