Build for handover.
I get involved from day one: building platforms and pipelines and introducing new technologies. My goal is for the team to carry on independently afterwards.
Service model
Architecture alone isn't enough. Only when platform, operations, and AI extensibility align do systems emerge that hold up day-to-day and don't fall apart at the next change cycle.
Containerized platforms, CI/CD pipelines, infrastructure as code, and monitoring – built so rollouts stay reproducible and teams aren't trapped in constant operational firefighting. Focus areas: Kubernetes/OpenShift, Ansible, Terraform, GitLab CI / Azure DevOps, Prometheus, Grafana, hybrid and multi-cloud environments.
Integrating LLM and agent capabilities where interfaces, security, and operational readiness are properly defined. Also where legacy systems need to be connected via modern interfaces (MCP, APIs) – without diving into legacy code. Focus areas: LLM integration into existing systems, Model Context Protocol (MCP), agent architectures with governance, AI-assisted developer tools.
Target architectures, platform design, and technical guardrails that don't just look good on paper but work under real-world constraints and compliance requirements. Focus areas: Public Cloud (Azure-focused, AWS and GCP as needed), on-premises, hybrid setups, integration architectures.
Engagement formats
Different initiatives call for different depths of engagement. All three formats share the same principles: clear deliverables, documented knowledge transfer, no lock-in.
Goal: Build platform, team, and ways of working so both can continue independently after the engagement.
What you get
Goal: Clear assessment and prioritized roadmap for a specific initiative.
What you get
Goal: Targeted technology adoption or focused knowledge transfer.
What you get
Project spotlights
Mid-sized industrial client, DACH region
Context: Greenfield setup of an on-premises Kubernetes platform for multiple containerized services in an industrial company without existing platform expertise in the internal team.
Role: Architecture ownership and technical implementation of cluster setup, ingress, storage, deployment standards, and monitoring – combined with structured knowledge transfer to the technical contact.
Technical core: Idempotent Ansible roles, Helm-based deployments, standardized TLS and ingress strategy, central monitoring stack.
Impact: Reproducible infrastructure, significantly reduced operational overhead, faster onboarding of new services. The technical contact runs the platform independently today.
Multiple sub-project teams, mature retail IT
Context: Further development of a company-wide loyalty and bonus program (app, backend, couponing, integrations) in the German retail sector. Mature retail IT environment with high organizational and technical interdependencies and multiple sub-project teams.
Role: Technical project leadership with responsibility for architecture decisions, technical guardrails, and coordination across multiple sub-project teams.
Technical core: Azure Functions, event flows, APIs, SAP-adjacent integrations, standardized deployment and operations processes across team boundaries.
Impact: Clear technical guardrails in a complex initiative, more stable integration flows, faster delivery of new features despite distributed responsibilities.
Innovation project commissioned by client
Context: Innovation project commissioned by a telecommunications provider to integrate AI assistants into an existing telephony infrastructure in a production-ready way. The result was presented as a tech teaser at an industry conference.
Role: Target architecture, definition of technical interfaces, iterative prototype implementation.
Technical core: LLM integration, Python-based dialog logic, robust communication paths between AI and telephony.
Impact: A working prototype with a clear statement on how AI can be meaningfully integrated into production-adjacent systems – without ignoring architecture and operations. At the same time, a communicable innovation anchor for the client.
Methodology
The "no lock-in" promise lives or dies by what actually happens during the engagement. The following elements are part of every Tech Lead engagement.
How I work
You work directly with the person who makes the technical decisions and thinks through their operational consequences. No handoffs between sales, architecture, and delivery. No unnecessary coordination loops. Most projects start with a short intro call – followed, if useful, by a compact architecture audit before the engagement begins.
Profile
I work at the intersection of architecture, delivery, and operations. I step in where technical complexity can't simply be handed off, but needs to be structured clearly and implemented reliably.
Contact
If you're looking for direct technical responsibility on a platform, AI, or cloud initiative, let's use a short initial call to find out whether I'm the right partner for it.
