For 13 years, I worked at Volkswagen on steering systems and driver assistance systems, including emergency braking systems. Systems where failure is not an option.
In that world, you don’t learn how to write great concepts. You learn how to build systems that run reliably under real-world conditions.
Today I work with mid-sized companies struggling with the absence of AI automation, manual workflows, and data silos that drain capacity every single day. Tools that exist side by side instead of working together. Tasks that disappear between email and conversation. Data living in three systems at once and never coming together.
I diagnose first. Then I optimize. Then I build the technical solution. In that order, never the other way around.
Tasks are discussed, but never formally assigned.
Your team spends more time searching for information than actually working. Jira, email, Confluence, yet another chat tool , everything is somewhere, nothing is immediately findable.
As a decision-maker, you have no real-time view of progress. You have to chase updates instead of looking at a dashboard.
Your experts waste hours manually transferring data from one system to another. Time that should be spent on the actual project.
Projects constantly stall at the same interfaces because processes aren’t automated and dependencies go unrecognized.
Manual steps that could long since be handled by AI automation are draining capacity from mid-sized companies every single day.
That's how we've always done it.
In almost every company, there are processes no one questions anymore. They run, and that’s reason enough. Those who start asking why almost always find the source of their chaos.
n the corporate world, I often asked: “Why do we actually do it this way?” The answer was almost always the same: “That’s how we’ve always done it. It just grew over time.“
I build AI automation for mid-sized companies. From diagnosis to a finished system that runs stably.
As an engineer, I’ve learned to structure systems logically. I’m not a consultant who hands over a concept and leaves. I’m the one who’s still there afterwards, making sure it works.
I diagnose first, build second.
I don’t connect tools. I build systems.
I stay on board until the structure is in place and the data flows.
Engineering instead of consulting means: I build the technical bridge between your current state and a scalable future.
More than 10 years in the automotive industry teaches you that a system must work under real conditions, not just in a presentation. I’ve led projects where failure was not an option, and I bring that standard to every engagement.
This engineering mindset is what I bring to AI automation for mid-sized companies today — with the goal that systems don't just work, but run reliably long-term.
My goal is to take as much off your plate as possible. After our initial conversation, I work fully autonomously where the project allows. I handle the technical details and present you with clear decision templates. To keep you in the loop at all times, I offer regular status meetings on request. You keep strategic control while I carry the operational responsibility.
An IT systems house maintains your infrastructure. I optimize your processes. I don't build standard solutions; I build custom architecture that connects your software, processes, and systems into an efficient whole. I'm not an external service provider — I'm your technical architect.
Consultants typically deliver concepts and strategy papers. I deliver working systems. My approach is "Engineering Instead of Consulting." That means I don't just accompany you through planning. I take technical responsibility for the execution. Where the consultant closes the presentation, I'm just getting started: with the realization of your stable IT structure.
Stability is the top priority. New solutions are developed in a test environment wherever possible and only moved to production after thorough quality assurance. Your day-to-day operations continue without interruption throughout.
Yes, absolutely. I see myself as the interface. In many cases it makes good sense to involve existing partners. I speak their language, define technical requirements precisely, and ensure everyone is pulling in the same direction.
Security is not an add-on, it's part of the architecture. I primarily use solutions with servers located in Germany/EU and ensure GDPR compliance at every integration point.
Start the free analysis now and find out exactly where AI automation can immediately free up capacity in your company.
