Direct access to the responsible expert

Cloud architecture, DevOps and AI integration that also hold up in live operations.

I step in when platforms need to become sustainable, operational processes must stay under control and new AI capabilities have to be integrated cleanly into existing systems.

  • Architecture that still works under load and in day-to-day operations
  • Delivery and operating models that reduce friction for teams
  • AI capabilities with clear value, clear interfaces and clear governance

Service model

Three layers that need to be designed together

Architecture on its own is not enough. Only when platform, operations and extensibility fit together do you get systems that survive day-to-day reality and do not fall apart with the next change.

Cloud and platform architecture

Target architectures, platform design and technical guardrails that do not just look good in concept decks, but continue to work under real constraints.

DevOps, infrastructure and operations

Automation, rollout paths, monitoring and operating models that keep technical complexity from turning into permanent operational stress.

Production AI integration

Add LLM and assistant capabilities where interfaces, security and operational boundaries are already under control, not as a demo but as a production extension.

Project spotlights

Selected projects with measurable technical impact

Enterprise loyalty platform with multiple teams and complex integration boundaries

Context: Further development of an enterprise-wide loyalty platform with app, backend and integration components in a retail environment with high organisational and technical interdependence.

Role: Technical project lead with responsibility for architecture decisions, technical guardrails and coordination across multiple sub-teams.

Technical core: Azure Functions, event-driven flows, APIs, SAP-related integrations and standardized deployment and operating processes across team boundaries.

Impact: Clear technical guardrails in a complex programme, more stable integration flows and faster delivery of new capabilities despite distributed responsibilities.

Kubernetes platform for reproducible deployments and lower operational overhead

Context: Greenfield build of an on-premises platform for multiple containerized services, with a focus on standardising infrastructure and rollouts.

Role: Architecture owner and implementation lead for cluster build-out, ingress, storage, deployment standards and monitoring.

Technical core: Idempotent Ansible roles, Helm-based deployments, a standardised TLS and ingress strategy plus a central monitoring stack.

Impact: Reproducible infrastructure instead of manual exceptions, significantly lower operational effort and faster onboarding for new services.

AI voice assistant as a credible feasibility proof instead of an isolated demo

Context: Feasibility project for AI-supported voice interaction in an existing VoIP environment with real interfaces and real system boundaries.

Role: Target architecture design, technical interface definition and iterative prototype delivery.

Technical core: LLM integration, Python-based dialogue logic and robust communication paths between AI and telephony.

Impact: A credible prototype that showed how AI can be connected to production-adjacent systems without ignoring architecture or operations.

How I work

Direct access, clear decisions and operational depth

You work directly with the person making technical decisions and thinking through their operational consequences. No handovers between sales, architecture and implementation, and no unnecessary coordination layers.

  • Direct access to the responsible expert
  • Technical decisions shaped with operations, implementation and team fit in mind
  • Operationally deep enough for delivery, senior enough for clear guardrails
  • Clear communication with CTOs, IT leaders and technical stakeholders

Profile

Who takes technical ownership

I work at the intersection of architecture, implementation and operations. My role becomes valuable where technical complexity should not be passed on, but instead structured clearly and delivered in a way that holds up over time.

  • Technical leadership across platform, cloud and integration projects
  • Team lead and moderator for technical decision processes
  • Practical background in Kubernetes, Azure, APIs, automation and AI integration

Contact

Does this fit your initiative?

If you are looking for direct technical ownership in a platform, integration or AI initiative, a short intro call is the best way to find out whether I am the right fit.